v1.4.7

Fixed

• Codex Windows hooks now launch their packaged Python handler from an inline PowerShell relay. They work for a standard Windows user under Restricted script policy, including plugin paths with spaces, without asking for administrator rights or changing execution policy. Claude hooks continue to use the provider's Windows Bash host and Linux shell path.
• Claude routing now selects a verified same-login Opus profile when Sonnet 5 and Opus 5.5 are available, with a distinct Fable profile when explicitly enabled. CI-generated profiles, 18 agent definitions, and the routing reference match the refreshed capability artifact.
• Independent Codex and Claude root sessions in one project now own separate runs, agents, routes, Stop controls, and status. A second session can enable the project without blocking or abandoning a colleague's live run. Pending roots retain verified profiles while other sessions are active.
• Concurrent Windows hook processes use an interprocess state lock. Version 1.4.7 copies v1 state once into a separate v2 file, preserving the original for already-running 1.4.6 hooks.

Upgrade note

Already-running 1.4.6 sessions continue updating v1 state; their later completion does not synchronize into the v2 snapshot. Let those sessions finish and reload the plugin before relying on migrated completion status. Codex host hook trust and organization-managed execution restrictions still apply independently of Symphony's launcher.

Full changelog: v1.4.6...v1.4.7