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/VERSION.md

@@ -1,8 +1,44 @@
 # Planning Package Version
 
-- **Package:** Adventure Storyteller Planning Package v4.0
+- **Package:** Adventure Storyteller Planning Package v4.1
 - **Revision date:** 2026-09-14
-- **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.
+- **Status:** **v1.0.0 released on 2026-09-14**: the signed tag `v1.0.0` and `main` both point at the signed release commit `432f041`. Milestones M1-M11 complete and closed; all 82 REQUIRED FOR V1 tests pass, with H09 not applicable. **v1.1 planning has begun** on `v1.1-development`: `V1.1-PLAN.md`. No v1.1 work package has started, and no v1.1 version or tag exists.
+
+## v4.1 — Post-release correction, and the v1.1 plan (2026-09-14)
+
+Documentation only. No product code, no requirement, no acceptance test and no
+schema changed.
+
+**Part 1 — post-release correction.** v4.0 was written before three owner
+events that have since happened: the closeout commit was signed (`432f041`),
+`main` was fast-forwarded to it, and the signed tag `v1.0.0` was created on it
+and pushed. The current-state wording that said otherwise is corrected. The M11
+report is not edited: its §T records the state at closeout, which was true when
+written.
+
+| Document | Change | Kind |
+| --- | --- | --- |
+| `README.md` | Status: v1.0.0 released; tag and `main` at `432f041`; v1.1 on `v1.1-development`. | developer docs |
+| `planning/README.md` | Current state, the release events, the map (v1.0.0 released, v1.1 planning), the stop rule restated for work packages, `V1.1-PLAN.md` in the document table and reading order. | index |
+| `planning/BUILD-MILESTONES.md` | Header status, **stale since M8** ("M9 is next"), now says complete and closed. A dated post-release note under M11's status, leaving the closeout paragraph as it stood. The *Post-v1 backlog* points at its triage. | milestone status |
+| `planning/VERSION.md` | This header and entry. | package version |
+
+**Part 2 — the v1.1 plan.**
+
+| Document | Change | Kind |
+| --- | --- | --- |
+| `planning/V1.1-PLAN.md` | **New.** Every post-v1 backlog item and every other recorded v1 residual risk, triaged. Six v1.1 work packages in order (A1, A2, B, C, D, E), each with objective, rationale, scope, non-scope, affected subsystems, acceptance criteria, regression requirements, dependencies, compatibility and risk. The v1.1 release criteria. A v1.2 list and future work. | planning |
+
+**Recommended scope: a focused v1.1.** Context-window safety, protocol-echo
+hardening, independent memory retention, browser coverage, recovery honesty and
+control-boundary contrast. Scheduled backups, identity-diagnostic extensions and
+media adapters are deferred, with the reason for each.
+
+**First brief to write:** WP-A1, the context-window safety reserve.
+
+**Requirement changes: zero.** Every v1.1 package improves the implementation of
+an existing requirement, so `SPECIFICATION.md` and `V1-ACCEPTANCE-TESTS.md` are
+unchanged.
 
 ## v4.0 — M11 closeout: v1 release validation accepted (2026-09-14)