fix: repair post-merge storage and Runtime Host contracts

[liugddx]

Summary

Repair two independent post-merge regressions that currently form a required-CI bootstrap loop on main:

1. feat: durable message lifecycle from admission to execution #3721 and feat(workhub): add coordination session lifecycle #3764 both assigned session metadata migration version 30. JavaScript Map construction silently retained only the later migration, so current-main databases record version 30 without creating message_admissions.
2. refactor(runtime-host): use typed request as sole operation API #3784 removed operation-specific RuntimeHostConnection aliases but left three queue-test calls on queryTurn, stopTurn, and startTurn, so current main does not build.

The fixes remain separate commits in this PR.

Migration compatibility

Schema version advances to 31. Migration 30 retains the admission-table authority introduced by #3721. Migration 31 uses guarded creation to converge every version-30 shape that may already exist:

• admission tables only (feat: durable message lifecycle from admission to execution #3721 head);
• WorkHub coordination index only (feat(workhub): add coordination session lifecycle #3764 head and current main);
• both objects present.

Fresh/older databases run 30 then 31 and reach the same schema. Module initialization now verifies that migration keys cover every version exactly once by rejecting duplicate-or-missing Map entries.

The session metadata constructor also closes a newly opened DatabaseSync when schema configuration or migration rejects, so a newer-schema refusal does not leak its handle on Windows.

Runtime Host test migration

The three stale calls are migrated to the existing typed operations without changing inputs or assertions:

• turn.query
• turn.stop
• turn.start

Verification

• Session metadata store: 56 passed, 0 failed, including all three version-30 starting shapes and the five message-admission tests previously failing on main.
• Core, Storage, MCP, Runtime, and Runtime Host builds: passed.
• Runtime Host queue suite starts and exercises the repaired storage authority; 9/12 passed locally. Three tests hit the existing fixed 10-second Host-readiness deadline on this Windows machine, with no process error or protocol failure. The directly changed production UDS test passed in the first complete run; hosted CI is authoritative for timing.
• lint, format, and git diff --check: passed.

Fixes #3788. Fixes #3790.

AI use

Codex diagnosed the semantic merge collision, implemented the compatibility migration and stale-call updates, and ran the listed checks.

Checklist

• Tests cover the change and fail without it
• Core/Storage/MCP/Runtime/Runtime Host builds pass locally
• Session metadata migration and message-admission suites pass locally
• Lint, format, and git diff --check pass
• Exact-head required test passed before the trailer-only history rewrite; a fresh check was triggered for the new head

Does this PR entail a change in behavior?

• Yes - existing version-30 databases converge to schema 31 without losing either merged authority; stale test callers use the supported typed request API.
• No

[M4n5ter]

Reviewed the typed-request migration and the version-30 schema convergence. The changes preserve the affected test semantics, cover every known merged version-30 shape, and keep initialization failure cleanup bounded. Current CI is green and later main commits do not overlap these files.