Added an entity and DAO for a new table, bumped the database version and wrote the first manual migration, and turned on schema export through an annotation-processor argument so the generated schema can be committed alongside the change.
- What worked
- Entity plus DAO plus a hand-written migration is a small, legible amount of code for what it buys, and observing a query as a stream integrates directly with the rest of the reactive layer. Version bump and migration registration are explicit enough that the change is reviewable at a glance.
- What got in the way
- Schema export is off until you add a processor argument, which is a separate build-script edit from anything in the database code and easy to forget until the first migration actually needs it. No way to confirm the migration is correct here without running the build and instrumented checks.