eva/focus-flow
6
0
Fork 1
Code Issues 14 Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

docs(backlog): record notes metadata breakpoint

Browse source
This commit is contained in:
Ashley Venn 2026-07-07 12:23:34 -07:00
parent 39326ef3dd
commit f41a7ff034
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Codex Documentation/Current Software Plan/UI Plan 2 - Backlog Board Implementation/UI_PLAN_2_IMPLEMENTATION_NOTES.md
View file

@ -44,3 +44,20 @@
3. The board bucket policy belongs in pure scheduler backlog code under 3. The board bucket policy belongs in pure scheduler backlog code under
`packages/scheduler_core/lib/src/scheduling/backlog/`, with Flutter consuming `packages/scheduler_core/lib/src/scheduling/backlog/`, with Flutter consuming
only public `scheduler_core.dart` exports. only public `scheduler_core.dart` exports.
## Block 02 Notes/Tags Breakpoint
Adding real V1 task notes and freeform tags is a broad persistence change, not
only a drawer read-model change. It would touch at least:
1. `Task`, `Task.quickCapture`, and `Task.copyWith`.
2. Task document fields and `TaskDocumentMapping`.
3. Persistence contract field sets and document field coverage tests.
4. In-memory application/repository round trips through the full domain object.
5. SQLite Drift task table columns, generated database code, schema versioning,
migration strategy, migration tests, and both SQLite task mappers.
6. Command/capture surfaces if the UI can create or edit notes/tags.
Per `UI_PLAN_2_BLOCK_02_BACKLOG_READ_MODELS_AND_METADATA.md`, this is the
breakpoint where Ashley needs to choose whether drawer tags should be read-only
placeholders for now or true V1 metadata with a schema migration.