T-20QT-vault-backfill-past-sessions
State: planning/draft · Impact: medium · Complexity: medium
Users who set a vault after months of use want their history. The writer task from
T-C4B1-vault-writer-task-exports-sessions is id-keyed and idempotent, so backfill is a job on
it: dry-run count first, then writes with vault:backfill_progress events, capped at 500 sessions
or 180 days per run. Reuses the filter core of api/v1/export.rs. The same job is the rewrite
path after a prefix or property change: existing notes keep their keys until backfill re-splices
them. It writes in whichever mode is configured, notes or daily entries.
See D-PVNF-pumice-vault-note-format and M-GYHW.
Proposed
Section titled “Proposed”To be defined when picked up.
Approach
Section titled “Approach”- To be defined.
| Area | Note |
|---|---|
apps/pumice/ | to be defined |
Acceptance criteria
Section titled “Acceptance criteria”- To be defined.
Out of scope
Section titled “Out of scope”- Changing the note format or the writer’s write discipline; backfill reuses both as they are.
- Backfilling sessions older than the cap in one run.