[Core] 7 - Cover remaining persistence contracts

[KacperKozak]

What to build

Inventory every durable native store/table and finish the parity contract coverage not handled by preceding slices, including Privacy Zones, cached Board config, diagnostics and other stores found in production. Audit all ordinary iOS writes and swallowed DB failures.

Part 7 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

• modules/vescape-core/ios/telemetry/AppDataRepository+PrivacyZones.swift - production behavior or caller to inspect
• modules/vescape-core/ios/telemetry/TelemetryRepository.swift - production behavior or caller to inspect
• modules/vescape-core/ios/telemetry/TelemetryDatabase.swift - production behavior or caller to inspect
• modules/vescape-core/android/src/main/java/expo/modules/vescapecore/telemetry/TelemetryDao.kt - production behavior or caller to inspect
• modules/vescape-core/android/src/main/java/expo/modules/vescapecore/telemetry/TelemetryDatabase.kt - 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

• Publish a store/operation-to-scenario inventory; each persistent operation has executable coverage or an explicit reason it is covered by another scenario.
• Replace remaining fragile ordinary iOS inserts with GRDB record writes; exercise custom SQL and aggregate semantics against actual databases.
• Reuse simple failure propagation and native reporting. Failure of local diagnostic persistence must not recurse into the failing DB.
• Both host suites execute all shared scenarios; no dead duplicate persistence implementation remains.

Blocked by

• [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

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] 8 - Verify migrations and backup restore #468
• [Core] 9 - Gate releases on storage contracts #469

[KacperKozak]

Implemented in 3e34ffe on persistence-reliability.