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

docs/TestDriverInitialMilestones.md

@@ -1,8 +1,18 @@
 # TestDriver Research Prototype — Initial Milestones
 
-**Status:** v0.1  
+**Status:** v0.1 — **canonical milestone sequence**  
 **Purpose:** Establish the minimum evidence-producing development loop needed to validate the core test-driver concepts.
 
+> This document is the single canonical source for milestone identifiers `M0`–`M10`.
+> The competing sequences formerly in `INTENT.md` and `TestDriverConceptModel.md` § 15
+> are superseded — see framework finding
+> `research/findings/F-0001-milestone-sequence-drift.md`.
+>
+> **Canonical order is not execution order.** The milestones define *what must be
+> true*; `workplans/TD-WP-0002-vertical-spike-crystallization.md` defines *the order
+> in which we get there*, driving one thin thread through M1–M7 rather than
+> completing each milestone in turn.
+
 ---
 
 ## Milestone 0 — Research Control Plane