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

research/findings/README.md

@@ -0,0 +1,19 @@
+# Framework Findings
+
+Findings about **test-driver itself**, kept strictly separate from findings about
+any system under test. Classes are defined in
+`docs/TestDriverImprovementLoop.md` § 9:
+
+`PRODUCT_DEFECT` · `TEST_DEFECT` · `MECHANICAL_ADAPTATION` · `SEMANTIC_CHANGE` ·
+`CONCEPT_DRIFT` · `FRAMEWORK_LIMITATION` · `EVIDENCE_FAILURE` ·
+`UNNECESSARY_COMPLEXITY`
+
+File naming: `F-NNNN-<slug>.md`. Identifiers are stable and never reused.
+
+Each finding carries frontmatter (`id`, `class`, `status`, dates, originating
+workplan/task) and, when resolved, states which of the three §5 resolution paths
+was taken. A finding that leaves an open question records it under "Residual" and
+names the task that will answer it — residuals are not parked in prose.
+
+The wider research control plane (`hypotheses/`, `experiments/`, `concepts/`,
+`decisions/`) is built in `TD-WP-0002-T03`.