Planning v3.9: record M11's long-run evidence, and correct what v3.7 claimed

The planning package still described M01 as outstanding. It now records the
evidence run on 96c1bf5 and the two product defects found on the way. It also
corrects three statements that were never true.

- V1-ACCEPTANCE-TESTS.md: result blocks for M01-M04. M04 is recorded as
  recovered through authoritative state, with the owner's acceptance of that on
  2026-09-13 and the positional precondition explained.
  Correction: v3.7 said this file carried M11 results against every REQUIRED
  test. None were written, and the per-test matrix is the M11 report's §F. The
  §P3 M11 disposition said the report records the identity diagnostic's
  findings. It does not, and the disposition now says so.
- BUILD-MILESTONES.md: the M11 status block records the long-run evidence,
  the write-lock and protocol-leak defects, and what is left for the reviewer.
- DATA-MODEL.md §28B: M11 added two columns, not one.
  settings.context_window_override (migration 94, ef25b0a) was never
  recorded.
- TECHNICAL-DESIGN.md: "Background failure observability" gains the rule
  that nothing in a turn writes before the model call, and new §15.4 records
  that stored narration carries story only, with the extractor's rules.
- CONTEXT-AND-MEMORY.md §51 and ADR 013: as-implemented notes for the same
  two fixes.
- README.md and VERSION.md: status, milestone map, stop rule, and the v3.9
  entry.
- M11 report §Q: the "not revised" note is replaced by what v3.9 revised.

No requirement changes. No code changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136VBTMUKWYeU6G9HgbDbND

planning/README.md

@@ -5,7 +5,7 @@
 **Current state:** Phase 0 complete; AI-DnD forked as the production base;
 milestones **M1 through M8 implemented and accepted**; **M9 and M10 implemented,
 committed and signed**; **M11 implemented and verified, awaiting independent
-review and v1 acceptance**. M11 is the last planned milestone. M1-M6 were accepted on the dates below (M3 and M4: 2026-09-03;
+review and v1 acceptance**, with its long-run evidence complete (2026-09-13). M11 is the last planned milestone. M1-M6 were accepted on the dates below (M3 and M4: 2026-09-03;
 M5: 2026-09-04; M6: 2026-09-06). M5 and M6 were each accepted only after an
 independent review found a real defect and a corrective pass fixed it.
 
@@ -38,9 +38,12 @@ verified, and awaits independent review** (2026-09-07).
 `reports/M11-IMPLEMENTATION-REPORT.md` is the evidence package. It closed the
 context-window release blocker M8 found, fixed two defects the validation itself
 surfaced, and disposed of all four post-M8 playtest findings. **It is not
-accepted**, and there is no release tag. The work is committed and signed on
-`m11-release-validation` (`fedb714`); `main` remains M10, the last *accepted*
-milestone.
+accepted**, and there is no release tag. **M01-M04 now pass on a complete
+100-turn run** (2026-09-13, commit `96c1bf5`). That run found two more product
+defects, both fixed: a turn locking out its own memory bank, and the narrator's
+protocol stored as story. The report was revised to match (`d198806`). All of it
+is committed and signed on `m11-release-validation`; `main` remains M10, the last
+*accepted* milestone.
 
 **After M11 there is no further planned milestone.** What follows is
 independent review and the v1 acceptance decision, which is the repository
@@ -319,7 +322,8 @@ Milestone M10                       COMMITTED AND SIGNED (1013c94)
         v
 Milestone M11                       IMPLEMENTED AND VERIFIED (2026-09-07)
   v1 security, long-run, release    reports/M11-IMPLEMENTATION-REPORT.md
-  validation                        awaiting independent review; no release tag
+  validation                        M01-M04 evidence complete (2026-09-13);
+                                    awaiting independent review; no release tag
         |
         v
 v1 acceptance                       the repository owner's decision
@@ -330,7 +334,7 @@ v1 acceptance                       the repository owner's decision
 **One milestone at a time. Do not begin a milestone before its brief exists.**
 
 **Every planned milestone is now implemented.** M11 is verified and committed,
-and the next action is not another milestone: it is an independent review of
+its long-run evidence is complete, and the next action is not another milestone: it is an independent review of
 `reports/M11-IMPLEMENTATION-REPORT.md` against the acceptance contract, and then
 the owner's v1 acceptance decision. **Do not begin post-v1 work before that
 decision**, and do not treat M11's own report as the acceptance record.