[Core] 5 - Protect Tune and alert storage

[KacperKozak]

What to build

Extend shared contracts across Tune Profile saves, Tune History, and durable Alert configuration. Migrate ordinary iOS writes to GRDB records while retaining native Board configuration ownership and existing successful behavior.

Part 5 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/TuneProfileStore.swift - production behavior or caller to inspect
• modules/vescape-core/ios/telemetry/TuneProfileStoreTests.swift - existing verification seam
• modules/vescape-core/ios/telemetry/AppDataRepository.swift - production behavior or caller to inspect
• 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 platforms preserve Tune values/history and Board-owned Alert data across update and reopen.
• Atomic operations roll back on injected failures; callers receive explicit errors and established Sentry reporting.
• No failed read becomes default config or successful save. No changes to firmware commands or riding feedback semantics.
• Inspect actual peer stores and preserve native/TS contracts and existing relevant ADRs.

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] 3 - Protect Board and settings saves #463
• [Core] 4 - Protect Favorite storage operations #464
• [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 a4ec700 on persistence-reliability.