write-local-datasource

name	write-local-datasource
description	Use when a new feature needs to persist data locally in Alkaa — triggers on tasks like "add database support", "create a new table", "store this data in SQLDelight", or when write-feature Phase 2 requires a new entity in the local database.

Write Local DataSource

Overview

The local data layer spans eight phases per entity: DataSource interface, SQLDelight schema, DB migrations, DAO interface, DAO implementation, local mapper, LocalDataSource implementation, and DI registration. All phases must follow strict conventions.

Phases

1. DataSource Interface — Contract the RepositoryImpl depends on; uses repository models (not local types) → see references/DATASOURCE_INTERFACE.md
2. SQLDelight Schema — .sq schema file with named queries and field prefixes → see references/SCHEMA.md
3. DB Migrations — .sqm file required for any structural change to an existing table → see references/MIGRATIONS.md
4. DAO Interface — Observable streams vs. single reads contract → see references/DAO.md
5. DAO Implementation — asFlow().mapToList() and executeAsOneOrNull() patterns → see references/DAO.md
6. Local Mapper — SQLDelight type ↔ repository model (toRepo/fromRepo) → see references/MAPPER.md
7. LocalDataSource Implementation — Injects DAO + mapper; never accesses *Queries directly → see references/LOCAL_DATASOURCE.md
8. DI Registration — singleOf for DAOs/DataSources, for mappers → see