Apply post-M1 corrections to the planning package

planning/VERSION.md

@@ -1,8 +1,39 @@
 # Planning Package Version
 
-**Package:** Adventure Storyteller Planning Package v2  
-**Revision date:** 2026-09-01  
-**Status:** Phase 0 complete; architecture selected; production milestone plan approved for milestone-by-milestone implementation.
+**Package:** Adventure Storyteller Planning Package v2.1  
+**Revision date:** 2026-09-02  
+**Status:** Phase 0 complete; architecture selected; **Milestone M1 implemented and accepted**; M2 not yet briefed.
+
+## v2.1 — Post-M1 Corrections (2026-09-02)
+
+M1 implementation evidence contradicted or under-specified parts of v2. The
+corrections are recorded in the documents themselves and listed in
+`README.md` § *Post-M1 corrections applied*; the evidence behind them is in
+`reports/M1-BASELINE-REPORT.md` and `reports/M1-IMPLEMENTATION-REPORT.md`.
+
+In summary:
+
+- a trusted-LAN Ollama may be **HTTPS with a privately issued certificate**;
+  clients verify against the operating system's CA store, with full certificate
+  and hostname verification and no bypass option (ADR 002,
+  `TECHNICAL-DESIGN.md` §5, A06),
+- offline claims require a **fresh cache and no route out** to be evidence at
+  all, and vendored runtime artifacts should be integrity-verifiable
+  (ADR 004),
+- A05's invariant is about **accepted** history; the user's submitted text is
+  deliberately retained on a failed turn,
+- A06 requires a **real second machine and an HTTPS endpoint**; a plain-HTTP
+  LAN test is no longer sufficient evidence,
+- the standard test environment records **CPU/GPU/RAM**, because cold model
+  load on a CPU-only host exceeded the inherited 120 s client timeout,
+- `BUILD-MILESTONES.md` records M1 as complete and reframes M2's endpoint work
+  as **narrowing** an existing capability rather than inventing it,
+- `SECURITY-THREAT-MODEL.md` §53 distinguishes **inbound** TLS (still deferred)
+  from **outbound** certificate verification (required, done in M1).
+
+Nothing in the architecture selected in v2 was reversed.
+
+## v2 — Post Phase 0B Revision (2026-09-01)
 
 This v2 package supersedes the earlier planning package produced before the final Phase 0B review and the trusted-LAN Ollama deployment clarification.