docs: fix 4 verified documentation-drift claims (SYS-W13-03)

CHANGELOG.md claimed automatic trigger/state-switching events are
unimplemented; SYS-W14-40 (Event Preview/Play) shipped exactly that.
missing.md self-contradicted on coordinate_system (Summary table says
fully implemented, a later clause said "not read anywhere"). RELEASE.md's
docs checklist referenced a retired emoji-marker plan.md summary table
format. new.md's "event bindings for Areas/triggers" recommendation had
already shipped, despite the file's date.

Extended validate_capability_documentation.py with 6 assertions
covering all four. Caught 2 vacuous forbid() checks along the way (a
missing Markdown continuation indent and a spurious literal \n) that
would have passed regardless of whether the fix was applied -- fixed
by verifying each needle against git show HEAD before trusting it.

Author: robertvokac

CHANGELOG.md

@@ -55,8 +55,10 @@ lettered commit-message convention:
   meta key/value map. All fully round-tripped (XML, MCB, XSD) and editable.
   The editor rasterizes SVG textures, previews audio, runs sandboxed Lua on
   explicit request, fires trigger steps explicitly, and applies scene-state
-  overrides interactively. Automatic collision/click/timer trigger events and
-  automatic state switching remain unimplemented; see `MC3_FORMAT.md`'s
+  overrides interactively. Bounded Event Preview/Play (`SYS-W14-40`)
+  additionally dispatches timer bindings, Walk Mode Area enter/exit
+  transitions, and viewport-picked object clicks automatically, each through
+  one isolated, validated document transaction; see `MC3_FORMAT.md`'s
   per-section status notes.
 
 ## Earlier feature work

RELEASE.md

@@ -49,10 +49,14 @@ process.
 
 - [ ] `NEXT.md` reflects actual current state (status/blocker/next
       task) — not stale from a prior session.
-- [ ] `plan.md`'s summary table matches the actual row markers (a
-      `python3` one-liner recomputing `✅`/`🟡`/`🧪`/`📋`/`🔴` counts per
-      section from the row markers is the reliable way to check this —
-      the table has drifted from hand-editing before).
+- [ ] `plan.md` is internally consistent — run
+      `python3 test/validate_plan_consistency.py .` (add a build directory
+      and `--run-tests` to also catch live CTest drift, not just registered
+      counts). `plan.md` (`SYS-W13-01`) is a bounded active plan using
+      `[DONE]`/`[IN_PROGRESS]`/`[BLOCKED]`/`[DEFERRED]`/`[PROPOSED]` text
+      markers on each row, not an emoji-marker summary table — that older
+      format was retired when `plan.md` was cut down from 2,743 lines;
+      historical detail lives in `docs/history/`.
 - [ ] `README.md`'s "Current Features"/"Current Limitations" reflect
       what actually works — spot-check a few claims against the code,
       don't just trust the prose (this has caught real staleness

missing.md

@@ -145,7 +145,8 @@ file-browse dialog, undo/redo coverage, and Area's properties panel (the
 4 findings originally in this section) were all resolved or formally
 closed 2026-07-18; see "Resolved since 2026-07-18" above for exactly what
 changed and what's still intentionally not a structural guarantee
-(undo/redo) or not read anywhere (`coordinate_system`, by design).
+(undo/redo). `coordinate_system` is fully implemented, not merely
+declared — see the Summary table below and `SYS-W14-14`.
 
 ## 4. Non-gaps (re-confirmed 2026-07-18, no regressions)
 

new.md

@@ -3,6 +3,14 @@
 _Prepared 2026-07-26 from the current source tree, the format specification,
 the test/build configuration, and the current Release build._
 
+**Status note (`SYS-W13-03`):** this is a point-in-time proposal snapshot,
+not live planning — `plan.md` is authoritative for current work. Its
+recommended "event bindings for Areas/triggers" feature has since shipped as
+bounded Event Preview/Play (`SYS-W14-40`, `[DONE]` in `plan.md`): timer
+bindings, Walk Mode Area enter/exit, and viewport-picked object clicks all
+dispatch automatically now. Treat the rest of this analysis as historical
+context, not a current gap list.
+
 ## Executive summary
 
 MeshCraft is already a substantial, safety-conscious 3D scene editor rather

plan.md

@@ -93,31 +93,34 @@ time; re-evaluate scope and blockers before starting each item.
   `capability_documentation` lint test; volatile CTest totals are no longer
   recorded as product truth.
 
-- **SYS-W13-03** `[PROPOSED]` `P1` — Remove documentation drift the
-  `capability_documentation` lint does not yet cover, confirmed by direct
-  read (not the full review list — two of its claims did not hold up: the
-  "click/timer event" gap it named is `SYS-W14-11`'s pre-existing JSON-only
-  scope, already accurate, and `RELEASE.md`'s "95 tests" mention is already
-  self-caveated as historical, not asserted as current):
-  - `CHANGELOG.md:58-59` still states "Automatic collision/click/timer
-    trigger events and automatic state switching remain unimplemented,"
-    which `SYS-W14-40` (`[DONE]`, Event Preview/Play) has since superseded.
-  - `missing.md` self-contradicts on `coordinate_system`: line 53 and the
-    matrix at line 177 say it is fully implemented and honored in the editor
-    and glTF export, while line 148 still says it is "not read anywhere
-    (`coordinate_system`, by design)".
-  - `RELEASE.md`'s docs-checklist references a `plan.md` "summary table"
-    recomputed from `✅`/`🟡`/`🧪`/`📋`/`🔴` row markers; `plan.md` no longer
-    uses that emoji-marker format (`SYS-W13-01` moved it to
-    `[DONE]`/`[IN_PROGRESS]`/`[BLOCKED]`/`[DEFERRED]` text markers), so that
-    checklist step no longer describes a real check.
-  - `new.md` (headed "prepared 2026-07-26 from the current source tree")
-    recommends "event bindings for Areas/triggers" as a next feature; that is
-    what `SYS-W14-40` already shipped, so the recommendation is stale despite
-    the file's date.
-  Extend the documentation validator with a small number of source-backed
-  negative assertions covering these four, rather than trying to make every
-  prose sentence a brittle static test.
+- **SYS-W13-03** `[DONE]` `P1` — Removed 4 verified documentation-drift
+  claims (not the full external-review list — two of its claims did not
+  hold up on direct read: the "click/timer event" gap it named is
+  `SYS-W14-11`'s pre-existing JSON-only scope, already accurate, and
+  `RELEASE.md`'s "95 tests" mention is already self-caveated as historical,
+  not asserted as current — left both alone):
+  - `CHANGELOG.md` no longer claims automatic trigger/state-switching events
+    are unimplemented; credits `SYS-W14-40` (Event Preview/Play) for
+    automatic timer/Area/click dispatch.
+  - `missing.md` no longer self-contradicts on `coordinate_system` — removed
+    the stale "not read anywhere... by design" clause that contradicted its
+    own Summary table two sections earlier.
+  - `RELEASE.md`'s docs checklist no longer references the retired
+    emoji-marker (`✅`/`🟡`/`🧪`/`📋`/`🔴`) summary-table format; points at
+    `test/validate_plan_consistency.py` instead, which is the real check.
+  - `new.md` gained a status note crediting `SYS-W14-40` for the "event
+    bindings for Areas/triggers" feature it recommends, so the recommendation
+    reads as historical rather than a live gap despite the file's date.
+  Extended `test/validate_capability_documentation.py` with 6 source-backed
+  assertions covering all four (2 of the 4 needed both a `forbid` the stale
+  text is gone and a `require` the replacement is present). Caught and fixed
+  2 vacuous checks along the way — both `forbid` needles for CHANGELOG.md
+  and `missing.md` failed to match the actual pre-fix text on the first
+  attempt (a missing 2-space Markdown continuation indent, and a spurious
+  literal `\n` where the source had a space), which would have made the
+  check pass regardless of whether the fix was ever applied; verified each
+  needle against `git show HEAD:<file>` before trusting it. All 6 new checks
+  plus the pre-existing checks pass.
 
 ### W5 — MC3 governance
 

test/validate_capability_documentation.py

@@ -50,6 +50,10 @@ def main() -> int:
     format_doc = read(repo, "MC3_FORMAT.md")
     testing = read(repo, "TESTING.md")
     matrix = read(repo, "docs/CAPABILITY_MATRIX.md")
+    changelog = read(repo, "CHANGELOG.md")
+    missing_doc = read(repo, "missing.md")
+    release_doc = read(repo, "RELEASE.md")
+    new_doc = read(repo, "new.md")
 
     for proxy in ('obj.collision == "box"', 'obj.collision == "sphere"',
                   'obj.collision == "capsule"'):
@@ -124,6 +128,21 @@ def main() -> int:
     failures += forbid(format_doc, "viewport picking does not yet generate live",
                        "format documentation no longer claims click events are absent")
 
+    # SYS-W13-03: 4 documentation-drift claims found and fixed in a
+    # second-review pass, each verified against source before fixing.
+    failures += forbid(changelog, "trigger events and\n  automatic state switching remain unimplemented",
+                       "CHANGELOG no longer claims automatic trigger events/state switching are absent")
+    failures += require(changelog, "SYS-W14-40",
+                        "CHANGELOG credits bounded Event Preview/Play for automatic dispatch")
+    failures += forbid(missing_doc, "not read anywhere (`coordinate_system`, by design)",
+                       "missing.md no longer self-contradicts on coordinate_system being unread")
+    failures += forbid(release_doc, "`✅`/`🟡`/`🧪`/`📋`/`🔴`",
+                       "RELEASE.md no longer references the retired emoji-marker summary table")
+    failures += require(release_doc, "validate_plan_consistency.py",
+                        "RELEASE.md's docs checklist points at the real plan.md consistency check")
+    failures += require(new_doc, "SYS-W14-40",
+                        "new.md's status note credits the shipped Event Preview/Play feature")
+
     if failures:
         print(f"{failures} capability-documentation check(s) failed.", file=sys.stderr)
         return 1