2 Commits

Author	SHA1	Message	Date
Vijay Janapa Reddi	9ee3c34303	docs(vault-cli): PHASE_4_HANDOFF — update post-backfill ... Append 2026-05-03 update reflecting: - Phase 4 backfill complete (2,757 corrections proposed; 0 errors) - 6 cloud questions migrated (stray top-level MCQ fields → details) - Phase 8 CLI subcommand shipped (vault audit run/review/summarize/merge) Next session can skip Step 1 (backfill — done) and start at Step 2 (Phase 5 interactive review).	2026-05-03 18:39:37 -04:00
Vijay Janapa Reddi	87adaeec2f	docs(vault-cli): PHASE_4_HANDOFF.md — resume guide for next session ... Self-contained instructions for picking up where Phase 4 left off: - Sanity checks for the worktree (vault check, pytest, ruff) - Phase 4 backfill steps (cloud + edge --propose-fixes, retry global errors, re-merge, regenerate AUDIT_FINDINGS) - Phase 5 review workflow (apply_corrections.py with --filter-gate + --auto-accept-format for low-risk fixes) - Phase 6 schema-tightening checklist (LinkML pattern constraints, Details extra="forbid", lift gate into validator) - Phase 7 title verification - Phase 8 vault audit CLI subcommand (cron is already shipped) - Phase 9 release pipeline Includes: - Concrete CLI commands for every step - Cost estimates per step - Tooling reference (which script does what) - Open questions from CORPUS_HARDENING_PLAN.md §10 still to decide - Full commit log from this session - Troubleshooting (rate limits, codespell, scratch files) Total estimated time to ship vault 1.0.0: ~12h, mostly Phase 5 human review. Spread over 2-3 working days. CORPUS_HARDENING_PLAN.md Phase 4 → Phase 5 transition.	2026-05-03 14:31:45 -04:00