Remote-control bridge auto-registration silently stops after app update (session stays connected regardless)

Observed behavior: Up until a certain app update, every new Desktop session auto-registered with the remote-control bridge ("Enabling remote control for session ..." followed by bridge_state: ready → connected). After the update, this auto-registration stopped happening for newly started sessions (multiple session starts with zero such events). On a linked mobile device this made the Desktop session appear "disconnected", even though the underlying process kept running normally. A manual toggle (turning "Remote control" off/on for a session) visibly reinitialized the bridge component; sessions registered automatically again afterward.

Expected behavior: Auto-registration should keep working reliably across app updates without a manual per-session toggle. Additionally, connection status on the mobile device should reflect actual process state (running vs. truly terminated), not just bridge-registration status.

Example A (last working auto-registration before the outage):

[info] Enabling remote control for session [session_id]
[info] [oauth-v2] using cached token for orgId=[org_id]
[info] [rcAutoEnable] verdict: enable=true source=explicit_pref
[info] [remote-control] bridge_state: ready
[info] Remote control enabled: https://claude.ai/code/[token]
[info] Mapping internal session [session_id] to CLI session [cli_session_id]
[info] [remote-control] bridge_state: connected

Example B (first successful registration after manual toggle, several days later): same pattern, different session/CLI IDs.

Environment: macOS Desktop App + iOS companion app. The auto-registration outage coincided with the update to version 1.20186.1 (first occurrence right after that update). Currently installed version: 1.21459.0.