Prepare the QM 1.0.5 rollout

[16francej]

What changed

• Sign every live-session canary request with the configured portal identity while preserving the admin actor on admin routes.
• Build the Postgres session-search GIN index concurrently so rollout does not block writes.
• Recover an invalid index left by an interrupted concurrent build, and make Fly's live gate reject any invalid index.
• Set the CLI package version to 1.0.5.

Why

The deployment canary declared itself as a web surface but only attached x-portal-identity to admin reads. Production therefore rejected its ordinary /v1/turns call with 401 portal identity required.

The session-search index was also created with plain CREATE INDEX, which could hold a write-blocking lock during rollout. PostgreSQL can leave an invalid same-named index after a failed concurrent build, so startup now drops that invalid index concurrently before retrying.

The latest published package is 0.1.4 and main had already advanced its unreleased source version to 0.1.10; 1.0.5 intentionally begins the stable 1.x line requested for this release.

Validation

• Focused identity, index, DDL, and retry tests — passed
• Root typecheck, contract typecheck, ESLint, Oxlint, Knip, and Prettier — passed
• CLI typecheck, 515 unit tests, and packed-artifact test — passed
• GitHub CI, including clean-runner CLI E2E and the real Postgres failed-index/retry test — passed
• Reviewed candidate deployed blue/green to the isolated Fly beta stack against its real Postgres database
• qm check --live — service identity/config, object storage, portal health, invalid-index query, real model turn, persistence, title, error check, and cleanup passed
• qm conformance — passed
• Production image dependency audit — 0 vulnerabilities

The local Docker E2E command was stopped because the workstation Docker daemon was unresponsive before test execution; PR CI ran the same suite successfully on a clean runner.