fix: saved Codex connection repair and movement authority

[MelaBuilt-AI]

Summary

• Resolve movement authority through the session's exact saved connection instead of the default harness capability list. Preserve attestation/schema/identity and autonomous capability checks; never fall back to another connection.
• Offer an explicit Use discovered installation repair when an old saved installation is absent and one matching environment/home/profile replacement is discovered without version metadata.
• Show every saved connection sharing a discovered installation; keep Add Agent and reattachment bound to the selected registration ID.

Evidence

• Production-entrypoint Codex fixture reproduced the operator's exact HTTP404 World session is unavailable before correction; GREEN after correction. User-directed follow is admitted, autonomous/wrong-actor requests refused, unavailable selected connection cannot fall back to a healthy default.
• Isolated React component tests reproduced missing repair control and only one visible connection before correction. GREEN on desktop and narrow viewport; exact repair/add/reattach callback identities asserted, screenshots inspected. No automated World-navigation journeys.
• 11 focused files / 40 tests PASS; architecture 11 tests PASS; root and web TypeScript, scoped ESLint/Prettier, normal production build and disposable startup/API smoke PASS.
• Fixed one test-fixture lint export before completion; preserved initial failure in local readiness log.

Acceptance and delivery boundary

• Operator repaired the original Codex saved installation on a separate native Windows PC via existing API; ready response and separate readback verified the original ID/name and updated path.
• Operator reports original Codex entry, no movement404, visible follow, completed homepage coding update and correct Worldview PASS on the existing installed build.
• Those results do not attest these not-yet-installed source changes. Updated setup UI and new installer hands-on acceptance remain pending.
• Aaron explicitly authorized implementation, commit/push, green GitHub CI/readiness, conditional merge, then new installers from merged main.
• No tags/Release/npm publication, automatic upgrades, user-state reset or retained-service cleanup. Existing bootstrap remains unchanged.