docs(audit): add resume-here handoff for next session

This commit is contained in:
2026-09-18 10:54:11 -07:00
parent 238fcc4f15
commit 8ac534c613
@@ -8,6 +8,17 @@
This captures the decisions made while consolidating the scattered requirements, so
context is not lost between sessions. Loose ends are collected in section 16.
## 0. Resume here (for a new session)
- Repo: `D:\dev\SlabUploader`. Branch: `docs/clean-main` (pushed to origin).
- State: `main` fast-forwarded to `d754cac` (all shipped code); old specs preserved behind tag `pre-simplification`; Phase 1 scaffold committed as `b42e3cb`; reconciled requirement set drafted as `238fcc4` (128 rows, 8 namespaces).
- Immediate next step: Ty reviews `docs/REQUIREMENTS.md` (Gitea branch `docs/clean-main`) and lists rewrite problems by requirement ID; the next session folds corrections in.
- After that: migrate capability and contract docs into `docs/capabilities/` and `docs/contracts/`, make them branch-neutral, and have them cite IDs instead of restating requirements.
- Gate that must stay green: `python tools/check_requirements.py`.
- Read first: `docs/STRUCTURE.md` (contract and namespaces), `docs/REQUIREMENTS.md`, `docs/MILESTONES.md`.
- Old-spec source: `git show pre-simplification:docs/<FILE>.md`. Raw extractions: `C:\Users\Ty\AppData\Local\Temp\opencode\slab-inventory\`.
- Deferred rulings: section 18.
## 1. Why this exists
Requirements are scattered across layers of docs (old `main` specs, current branch docs,