f0ssel changed the title fix: sync workspace automatic_updates with template require_active_version fix: sync workspace automatic updates with template require active version

f0ssel changed the title fix: sync workspace automatic updates with template require active version fix: sync workspace auto-update setting when template requires active version

f0ssel changed the title fix: sync workspace auto-update setting when template requires active version fix: sync workspace automatic updates with template active version requirement

f0ssel changed the title fix: sync workspace automatic updates with template active version requirement fix: synchronize workspace automatic updates with active version requirement

f0ssel changed the title fix: synchronize workspace automatic updates with active version requirement fix: document consistent require_active_version evaluation

f0ssel changed the title fix: document consistent require_active_version evaluation fix(cli): proactively use active template version when require_active_version is set

…_version is set

When a template has require_active_version enabled, coder start and
coder restart now proactively use the active template version for all
users (including admins), matching the web UI behavior where the only
button shown is 'Update and start'.

Previously, the CLI only checked workspace.AutomaticUpdates but ignored
TemplateRequireActiveVersion. This caused admins using the CLI or VS Code
extension to silently start on stale template versions. The fix adds
TemplateRequireActiveVersion to the existing OR condition in
buildWorkspaceStartRequest(), matching how server-side autostart already
handles it.

The 403->retry fallback remains as a safety net but is no longer the
primary path for any user.

Fixes #22030