release: ship session control compatibility in v0.1.32

[wolfiesch]

Outcome

• hydrate thinking-level and fast-mode state for sessions created by the current T4 client, including transport reconnects
• keep ordinary attachment to existing or TUI-owned sessions observer-only so the legacy OMP state read cannot claim the session lock
• make client runtime changes select both current and pinned-legacy bridge continuity gates in pull-request CI
• align package, client, site, documentation, and download identities to v0.1.32

The bundled OMP authority runtime remains the verified t4code-17.0.5-appserver-13 build. This is a client/release correction, not a runtime provenance change.

Release evidence

• focused client reconnect suite passed: 27 tests
• focused release, ownership, and CI-path suite passed: 41 tests
• pnpm check passed: release consistency, provenance, lint, and typecheck
• pnpm test passed across all workspaces
• built-app Playwright suite passed: 32 tests
• unsigned macOS DMG and ZIP were built for v0.1.32 and each inspected with 956 ASAR entries and the expected bundled runtime layout
• protected release automation remains responsible for Developer ID signing, notarization, stapling, Gatekeeper assessment, checksums, publication, and production-site verification

Risk and rollback

Low. State hydration is limited to sessions whose successful creation response was observed by the current client. Existing-session attachment is narrower than v0.1.31 behavior, and the pinned legacy continuity gate exercises that lock boundary. Rollback is the commits in this pull request before the v0.1.32 tag is created.

Checklist

• Current and historical release identities remain distinct
• No OMP runtime or app-wire provenance changed
• No secrets, private paths, or machine-specific values are included
• Signed artifacts remain fail-closed behind the protected release workflow