Root `TODO.md` is a raw dump inbox, not a roadmap. The 2026-05-06 dump has been promoted into this durable plan and cross-referenced with existing roadmap/design documents. Future agents should use this plan and the referenced docs instead of treating the old raw dump as instruction.
## Existing Durable Homes
These raw notes already had a suitable home and should be continued there:
| Typed SF environment schema | `SF_*` env vars should fail early with actionable diagnostics instead of late runtime surprises. | Tier 1 | Add an SF-owned env schema module and route startup/tool validation through it. |
| Autonomous-path coverage ratchet | Global coverage thresholds are too broad; autonomous/recovery paths need higher targeted confidence. | Tier 2 | Started with focused DB-authority/UOK runtime suites; continue with dispatch and recovery families before changing global thresholds. |
| End-to-end milestone lifecycle tests | DB-only runtime state needs integration proof across plan, execute, validate, and complete. | Done | Added runtime-state regression coverage proving SQLite slice/task order stays authoritative over stale markdown/JSON projections, and DB-backed runtime refuses implicit roadmap, plan, and summary imports. |
| MCP server residue/docs cleanup | SF currently ships the MCP client extension only; tracked MCP server source was removed. | Done | Removed untracked `packages/mcp-server/` residue and updated durable docs so future work never recreates an SF MCP server. |
| `auto-dispatch.js` / `auto-prompts.js` decomposition | Known design debt, but explicitly out of scope until requested as a dedicated refactor. Do not start it while fixing DB authority, UOK safety, or roadmap triage. |
## Acceptance Criteria
-`TODO.md` contains no untriaged raw notes.
- New work starts from this plan, `BUILD_PLAN.md`, or `docs/dev/UOK-SELF-EVOLUTION.md`, not from deleted raw dump text.
- Items that need implementation are converted into SF milestone/slice/task state before code changes begin.