Planning v4.1: record the v1.0.0 release, and plan v1.1

Documentation only. No product code, requirement, acceptance test or
schema changes.

Post-release correction. v4.0 was written before the closeout commit was
signed (432f041), main was fast-forwarded to it, and the signed v1.0.0 tag
was pushed. Current-state wording now says so in README.md,
planning/README.md, BUILD-MILESTONES.md and VERSION.md. BUILD-MILESTONES.md's
header had been stale since M8. The M11 report is not edited: its §T
records the state at closeout.

v1.1 plan. planning/V1.1-PLAN.md triages the post-v1 backlog and the other
recorded v1 residual risks, and orders them into work packages, not
milestones:
- A1: a context-window safety reserve, plus reporting a turn the server
  truncated
- A2: removing protocol echoes from stored narration, and a genre-neutral
  state rule
- B: long-term memory retention that holds without help from state
- C: browser coverage of Retry, Save Points, correction, length, failure
  and export download
- D: integrity_check on backups, and a warning when an export exceeds the
  import limit
- E: WCAG 1.4.11 control-boundary contrast

Scheduled backups, the import limit, identity detectors and duplication
suppression move to v1.2; media adapters are future work. The first brief
to write is A1.

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

planning/BUILD-MILESTONES.md

@@ -1,6 +1,6 @@
 # Adventure Storyteller — Production Build Milestones
 
-**Status:** In implementation. M1-M8 complete and accepted (M1 and M2: 2026-09-02; M3 and M4: 2026-09-03; M5: 2026-09-04; M6, M7 and M8: 2026-09-06, each of the last four after an independent review and a corrective pass). **M9 — Export, Backup, Recovery, and Migration Hardening — is next, and has not been started.**  
+**Status:** **Complete. M1-M11 are closed, and v1.0.0 was released on 2026-09-14** (signed tag `v1.0.0` on signed commit `432f041`, which `main` also points at). This document is the v1 milestone history and is not extended. Post-v1 work is planned as v1.1 work packages in `V1.1-PLAN.md`, not as further milestones.  
 **Base:** AI-DnD `d72f7c1bda0f34fccd84afb7a25c34eb01c901de`
 
 ## 1. Purpose
@@ -1466,6 +1466,10 @@ applicable (report §T). The acceptance takes effect with the owner's signed
 closeout commit. **No release tag exists**: tagging `v1.0.0` is a separate
 decision, and the tag must point at that signed commit.
 
+*Post-release note (2026-09-14):* both events have since happened. The closeout
+commit was signed as `432f041`, `main` was fast-forwarded to it, and the signed
+tag `v1.0.0` points at it. The paragraph above is kept as it stood at closeout.
+
 **M1-M11 are all complete. There is no M12.** Post-v1 work is backlog, listed
 below under *Post-v1 backlog*, and none of it is an unfinished v1 milestone.
 
@@ -1550,6 +1554,10 @@ Work recorded for after v1. None of it is a v1 requirement or an unfinished v1
 milestone, and none of it has a brief. Each item needs one before work begins.
 Sources are the M11 report's §P and §S.6.
 
+**Triaged on 2026-09-14 in `V1.1-PLAN.md`**, which orders it into v1.1 work
+packages, a v1.2 list and future work. The list below is kept as recorded at the
+M11 closeout; `V1.1-PLAN.md` is where its disposition now lives.
+
 - **Context-window safety margin.** The largest prompts leave 23-42 real tokens,
   and Ollama cuts an over-window prompt with no error. Consider a deliberate
   reserve, or counting with the narrator's own tokenizer.