[Core] 9 - Gate releases on storage contracts

[KacperKozak]

What to build

Wire both host persistence contract suites into required CI/release prerequisites for the exact released revision. Keep device smoke tests separate for OS lifecycle and background recording.

Part 9 of the approved cross-platform persistence reliability plan. Android and iOS remain separate native implementations with shared observable contracts. Local planning document: docs/persistence-reliability-plan.md; this issue is self-contained. Type: AFK.

Likely files

• .github/workflows/ci.yml - CI/release integration
• .github/workflows/release-ios.yml - CI/release integration
• .github/workflows/release-android.yml - CI/release integration
• .github/workflows/promote-production.yml - CI/release integration
• scripts/test-ios.ts - host test/build entry point
• docs/persistence-reliability-plan.md - production behavior or caller to inspect

Implementation hints

Keep Room on Android and GRDB on iOS. Native owns durable truth; JS renders state and sends intents. Follow bidirectional @parity links and preserve bridge payloads. Custom SQL is allowed for migrations and aggregate updates with real DB tests. Use existing error UI and avoid a generic persistence/recovery framework. Diagnostics transport follows ADR 0031; Sentry handles errors independently of local event persistence. Use bun commands and appropriate scoped verification.

Acceptance criteria

• Both Android and iOS release paths cannot publish a revision with failing or missing native storage contracts; verify branch protection/workflow dependencies rather than assuming CI presence suffices.
• Use host runners, caching and changed-file selection only where safe; coverage cannot skip a platform or migration scenario silently.
• Demonstrate failed fixture blocks release gate and passing suites permit continuation without actually publishing a release.
• Document commands, measured runtimes, ownership of shared fixtures and supported upgrade matrix.

Blocked by

• [Core] 8 - Verify migrations and backup restore #468

Related

• [Core] 1 - Test recording across hosts #461
• [Core] 2 - Surface recording storage failures #462
• [Core] 3 - Protect Board and settings saves #463
• [Core] 4 - Protect Favorite storage operations #464
• [Core] 5 - Protect Tune and alert storage #465
• [Core] 6 - Surface history read failures #466
• [Core] 7 - Cover remaining persistence contracts #467
• [Core] 8 - Verify migrations and backup restore #468

[KacperKozak]

Implemented in 9d91c79 on persistence-reliability.