fix: explain ChatGPT component upgrade required before sign-in

[NOirBRight]

Summary

An existing managed ChatGPT component can remain on an older archive after opening a newer portable CodexHub. Sign-in then fails with a generic message, concealing the required component upgrade or restart.

Open sign-in
  incompatible installed component → explain upgrade + start
  running component needs restart → explain stop + start
  compatible component → existing login flow

Expose the same reason in settings status and the authenticated login API; show localized guidance beside the disabled login button and in the status notice. No automatic upgrade, restart, credential migration, or change to save behavior.

Evidence

• Before: the operator's 8b25514 portable connected to a still-running older component with no login control; open_login returned Restart the ChatGPT Web component before opening its login window. Four new HTTP regression cases failed.
  After: all four cases return actionable HTTP 409 codes without invoking login; the complete settings module passes 29 tests. Python core passes 3588 tests, 196 skipped, 283 subtests. Page JavaScript syntax and upgrade/restart/cancel button-state checks pass; report-only quality scan has zero parse errors.
• Local operational recovery used the already-verified 8b25514 bundled component, preserved settings bytes during upgrade, and opened a real mapped Chromium ChatGPT window. This validates recovery on AM01S; it does not claim a new Windows native UI qualification.
• A separate WebKitWebProcess SIGABRT came from the older graphical session at process exit. Its underlying cause remains unresolved and is not claimed fixed here. No credentials, raw account files, or core dumps are included.

Merge Danger

Door: two-way

Only settings-page guidance and login preflight change; compatible and stopped current components retain the existing login path.

Blast Radius: ChatGPT