Apple Persistence Integrity

Preserve durable data by making store ownership, commit boundaries, migration, and recovery explicit.

Route the Work

1. Inspect every container, configuration, context/actor, schema, migration, store URL, writer, save, retry, fallback, import, delete, and reset path before editing.
2. Map the authority, identity, write path, propagation, delete semantics, and failure policy for each durable fact.
3. Read store-boundaries.md for SwiftData isolation, bounded queries, or any coexistence with SQLite, files, indexes, caches, IPC, or remote stores.
4. Read migration-and-recovery.md before changing schemas, container startup, fallback, quarantine, or reset behavior.
5. If Xcode MCP is available, run DocumentationSearch; use apple-documentation.md as the dated API index.

Preserve These Invariants