M11 closeout: accept v1 release validation

The browser, offline and identity runs had last been taken on ef25b0a. The
closeout repeated them on the exact release-candidate tree, 3652dc6, whose
product code is identical to 96c1bf5, where the 100-turn evidence was run. No
product code changed, so the long-run evidence stands.

On 3652dc6:
- backend suite: 1421 passed, 17 skipped, 0 failed
- frontend suite: 161 of 161; lint clean
- production build clean
- docker build --no-cache: image SPA byte-identical to the local build
- browser regression: 38 of 38
- no-network container: 23 of 23
- identity diagnostic: 0 signals; the scripted self-test's detectors fire
- release-shaped smoke test from the image: 14 of 14

- M11 report: new S (exact-tree verification, including the identity
  results the report never carried) and T (acceptance record). Corrections:
  the REQUIRED FOR V1 count is 82, not 85, and L's browser narrator was
  qwen2.5:3b-instruct. P gains risks 16 and 17; risk 6 is widened.
- BUILD-MILESTONES.md: M11 COMPLETE / ACCEPTED, and a post-v1 backlog.
- V1-ACCEPTANCE-TESTS.md: the P release gate's result, and the P3
  disposition's run.
- planning/README.md, VERSION.md (v4.0), README.md: status, map, stop rule.
- tools/m11_browser.py: the G01 import wait could not fail, because the
  scenario's campaign is titled "Hidden Knowledge". It now waits for the
  imported source's row.

Found and carried, not fixed. The identity run stored protocol shapes the
extractor leaves, on 4 of 10 turns at a 4,096 window: event-call syntax and a
parroted length hint. The owner chose residual risk. The state rule's example
is fantasy, and the state lagged the narration. None occurs in the 100-turn
evidence.

No requirement changes. No release tag.

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

planning/VERSION.md

@@ -1,8 +1,37 @@
 # Planning Package Version
 
-- **Package:** Adventure Storyteller Planning Package v3.9
+- **Package:** Adventure Storyteller Planning Package v4.0
 - **Revision date:** 2026-09-14
-- **Status:** Phase 0 complete; architecture selected; **Milestones M1-M8 implemented and accepted**; **M9 and M10 implemented, M10 committed and signed**; **M11 implemented and verified, awaiting independent review/acceptance** (2026-09-07). M11 is the last planned milestone before v1 acceptance. Its long-run evidence is complete (2026-09-13): all 85 REQUIRED tests pass, with H09 not applicable.
+- **Status:** Phase 0 complete; architecture selected; **Milestones M1-M11 complete**; **M11 accepted at its closeout (2026-09-14), and the v1 release gate passed** on the release-candidate tree. All 82 REQUIRED FOR V1 tests pass, with H09 not applicable. There is no further planned milestone. The signed closeout commit and any `v1.0.0` tag are the repository owner's, and neither exists as of this revision.
+
+## v4.0 — M11 closeout: v1 release validation accepted (2026-09-14)
+
+No requirement change, and no product code change. The closeout re-ran the
+black-box evidence on the exact release-candidate tree, `3652dc6`. Its product
+code is identical to `96c1bf5`, where the 100-turn evidence was taken. The
+browser, offline and identity runs had last been run on `ef25b0a`.
+
+| Document | Change | Kind |
+| --- | --- | --- |
+| `reports/M11-IMPLEMENTATION-REPORT.md` | **New §S**: the closeout's exact-tree verification, including the identity diagnostic's results, which the report had never carried. **New §T**: the acceptance record. **Corrections**: the REQUIRED FOR V1 count is 82, not 85 (the 85 counted four SHOULD rows and left out H09), and §L's browser narrator was `qwen2.5:3b-instruct`, not the `-16k` model. §A, §B, §D.1, §F (A06, G01), §L, §O, §P and §R now reflect the closeout. | milestone report + corrections |
+| `BUILD-MILESTONES.md` | **M11 marked COMPLETE / ACCEPTED.** A *Post-v1 backlog* section records work that is not a milestone. | milestone status |
+| `V1-ACCEPTANCE-TESTS.md` | **§P V1 Release Gate gains its result.** The §P3 M11 disposition now records the diagnostic's run. | acceptance evidence |
+| `planning/README.md` | Status, milestone map, stop rule, and why the M11 report stays in `reports/`. | index |
+| `README.md` | One status sentence: v1 release validation passed; not yet tagged. | developer docs |
+| `backend/tools/m11_browser.py` | **Harness fix.** G01's import wait could not fail, because the campaign's own title contains "hidden". It now waits for the imported source's row. | release-test infrastructure |
+
+**What the closeout found.** No release blocker. One harness defect, fixed. Three
+non-blocking observations, all from the identity run on a 4,096 window:
+
+- the extractor leaves event-call syntax and a parroted length hint in stored
+  narration;
+- the state rule's fixed example carries fantasy slugs, which the model copied;
+- the state lagged the narration.
+
+The owner chose on 2026-09-14 to carry the extractor gap as a residual risk
+rather than change product code. Report §S.4.
+
+**Requirement changes: zero.**
 
 ## v3.9 — M11's long-run evidence, and the two defects it took to get it (2026-09-14)