android-room-databaselisted

# Android Room Database ## When To Use - Use this skill when the request is about: room database android, dao query migration android, room schema export. - Primary outcome: Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence. - Handoff skills when the scope expands: - `android-local-persistence-datastore` - `android-testing-unit` ## Workflow 1. Confirm the data source, persistence boundary, sync model, and device capability involved. 2. Model contracts explicitly before wiring network, storage, media, or background APIs. 3. Apply the recommended AndroidX or platform pattern with migration-safe defaults. 4. Validate offline, retry, and process death behavior against the sample apps and scenarios. 5. Escalate security, performance, or release risk to the linked supporting skills when needed. ## Guardrails - Prefer typed models and explicit serializers over ad-hoc maps or bundles. - Keep background work idempotent and cancellation-aware. - Do not leak storage, media, or networking details into presentation code. - Treat user data durability, privacy, and migration paths as part of the implementation. ## Anti-Patterns - Blocking the main thread with disk or network calls. - Treating retryable sync failures as terminal user-facing errors. - Mixing cache models and wire models without a mapping layer. - Requesting broad storage or notification capabilities when a narrower API exists. ## Examples ### Happy path - Scenario: Persi