Order the spec into seven milestones (V-719)

Ordered by what makes her untrustworthy if it ships late, not by code
work: the audit ruled that out, since none of the four broken
capabilities is a code defect. Honesty, then the config-and-data four,
then voice, then proactive delivery, then breadth, then email and
calendar behind their product decision, then the undesigned seven.

Doc gaps and missing scenarios bind every milestone rather than forming
one, so they cannot collect at the end.

--no-verify: committing on master by the owner's call this session.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

CLAUDE.md

@@ -15,6 +15,8 @@ under `docs/`. Read that doc before changing the subsystem.
 | `docs/world.md` | touching search, Kiwix or the world chain |
 | `docs/language.md` | changing a prompt contract or a Russian word list |
 | `docs/ecosystem.md` | touching Nexus, Praxis or Hexis |
+| `docs/spec.md` | asking what a capability is for, or whether it is done |
+| `docs/roadmap.md` | picking what to work on next |
 | `docs/rearchitecture.md`, `docs/design.md` | changing the shape of anything |
 | `docs/workflow.md` | the five stores, the doc tiers, the guards |
 | `docs/caveats/` | a known limit, its task id and its revisit trigger |