Fix stale Command Center failure status and expose Codex repair

[awtprod]

What changed

• Settle a Command Center run as failed when provider startup records an orchestration session error before native provider events begin.
• Keep the failure transition idempotent and revoke the run's active MCP scope.
• Put the Codex Update or reinstall action beside the installed version when no newer-version advisory is present.
• Add regression coverage for startup errors that previously left a route receipt stuck on Working / Running.

Why

Command Center marks a run as running as soon as its provider turn is dispatched. A Codex startup failure can occur before the provider runtime emits the event normally used to close that run. The linked task therefore showed Failed while the routing receipt stayed Running.

The provider repair action added in #12 was also available only inside expanded provider details when Codex was current, making it difficult to discover in the missing-Windows-sandbox-files case.

Impact

A failed Codex startup now appears consistently as failed in the task, sidebar, and route receipt. Windows users with a managed Codex installation can directly update or reinstall it from the provider row, even when it reports the latest version.

Validation

• 18 focused server and web tests passed.
• Server and web TypeScript checks passed.
• Focused ESLint, formatting, diff, secret-scan, and pre-commit checks passed.