tegwick c856cb9e64 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		2026-08-22 23:07:31 +02:00
..
TestDriverConceptModel.md	T01: establish canonical milestone sequence, record F-0001	2026-08-22 23:07:31 +02:00
TestDriverImprovementLoop.md	Register with State Hub, persist concept assessment, seed first workplan	2026-08-22 22:40:39 +02:00
TestDriverInitialMilestones.md	T01: establish canonical milestone sequence, record F-0001	2026-08-22 23:07:31 +02:00
TestDriverResearchPrototype.md	Register with State Hub, persist concept assessment, seed first workplan	2026-08-22 22:40:39 +02:00