T01: establish canonical milestone sequence, record F-0001

Three documents defined conflicting milestone sequences; an unqualified
reference to e.g. 'M2' was ambiguous across the corpus.

- docs/TestDriverInitialMilestones.md (M0-M10) is now canonical
- INTENT.md and ConceptModel section 15 carry superseded banners plus a
  mapping table rather than being deleted
- canonical order is explicitly distinguished from execution order
- research/findings/ established; F-0001 filed as CONCEPT_DRIFT, resolved
  via path 2 (concept deliberately revised), with one residual for T10

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1629012@bnt-lap001
Assistant-Session: 78d4fb13-8a1e-474b-87a3-9b9261c49a39

workplans/TD-WP-0002-vertical-spike-crystallization.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Vertical spike: falsify the crystallization thesis"
 domain: infotech
 repo: test-driver
-status: proposed
+status: active
 owner: codex
 topic_slug: custodian
 created: "2026-08-22"
@@ -76,7 +76,7 @@ satisfying to build, and impossible to validate at this stage:
 
 ```task
 id: TD-WP-0002-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "b1755e17-279a-56cf-86eb-359e9739070a"
 ```
@@ -91,6 +91,12 @@ Pick one canonical sequence, mark the others superseded in place, and commit
 first entry in the framework findings log — the project should catch this on
 itself before it catches anything else.
 
+**Done 2026-08-22.** `docs/TestDriverInitialMilestones.md` (M0–M10) is canonical;
+the `INTENT.md` and Concept Model § 15 sequences carry superseded banners with a
+mapping table. Recorded as `research/findings/F-0001-milestone-sequence-drift.md`.
+`INTENT.md` and `docs/` are now tracked. One residual carried to T10: the finding
+taxonomy has no class for document-to-document drift.
+
 ## Decide intent provenance and the classification mechanism on paper
 
 ```task