[Core] 3 - Protect Board and settings saves

[KacperKozak]

What to build

Extend shared persistence contracts through Board and settings save/read/delete callers on Android and iOS. Replace ordinary handwritten iOS writes with GRDB records; keep Room entity writes and preserve Board tombstones and settings semantics.

Part 3 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.swift - production behavior or caller to inspect
• modules/vescape-core/ios/telemetry/AppDataRepositorySettingsTests.swift - existing verification seam
• modules/vescape-core/ios/telemetry/AppDataRepositoryBoardLinkTests.swift - existing verification seam
• modules/vescape-core/android/src/main/java/expo/modules/vescapecore/telemetry/AppDataRepository.kt - production behavior or caller to inspect
• modules/vescape-core/src/index.ts - native bridge contract

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 runners verify Board identity, rename, tombstone, settings update/default handling and reopen preservation.
• Failed save rejects caller and never reports success; failed reads are explicit errors rather than default settings. Reuse slice 2 failure/reporting behavior.
• No new UI recovery framework; preserve existing successful flows and native ownership.
• Validate transactional failures and existing migration/restore data shapes.

Blocked by

• [Core] 1 - Test recording across hosts #461
• [Core] 2 - Surface recording storage failures #462

Related

• [Core] 1 - Test recording across hosts #461
• [Core] 2 - Surface recording storage failures #462
• [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
• [Core] 9 - Gate releases on storage contracts #469

[KacperKozak]

Implemented in e3f2d58 on persistence-reliability.