docs(vm4): every Campaign AR document says what its evidence shows

Dated 'VM4 correction' notes, not silent rewrites:
- AR plan: NoOpRenderPackProductionIntegrationTests is a 2x2 recording-
  device fixture, not a production pin; the real invariance is VM0's.
  Both '14,928/14,928 zero skips' totals qualified: hermetic lane filter.
- Stage-2 connected report: the dense-town CPU figures ran under the
  automation observer (9.8 MB/frame alloc) and say nothing about the
  owner's hitch on the product; clean numbers are VM0's.
- Track A report + findings doc: TerrainUtils.GetNormal only orients
  scenery; the render normals were already smooth; A2 replaced central
  differences with retail's incident-face average (the reviewer's own
  premise error).
- Findings doc: 'retail brightens' is the fallback path only; real
  hardware runs the single-pass lerp (VM2). LandscapeDetailTextures = 0
  answers the landscape open question. VM0 production table added as the
  baseline.
- Completion audit retail-path row and the review's F1/F2/F3/F5 headers
  annotated with their closures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/plans/2026-08-21-atmospheric-rendering.md

@@ -342,7 +342,10 @@ Current authored-celestial Stage 1 automated gate (2026-08-22):
   including all source, tests, tools, and SDK samples, builds with **0 warnings
   and 0 errors** after that restore.
 - The repository-owned fresh-process hermetic gate passes
-  **14,928/14,928** tests with zero skips or failures across 14 assemblies;
+  **14,928/14,928** tests with zero skips or failures across 14 assemblies
+  **under the repository's hermetic lane filter** (Manual/Timing/Live/
+  InstalledDat/Diagnostic lanes excluded; a raw `dotnet test AcDream.slnx`
+  reports those lanes as skips/failures by design — VM4 correction);
   `AcDream.App.Tests` contributes **5,823/5,823**. Evidence is under
   `artifacts/atmospheric-rendering/stage1-moon-release-gate/`.
 - The App total includes the 9,500-caster 256-frame zero-managed-allocation
@@ -363,7 +366,8 @@ Recorded pre-moon automated checkpoint (not a current moon-scope completion
 claim):
 
 - The repository-owned fresh-process Release test stage passes
-  **14,880/14,880** tests with zero skips or failures across 14 assemblies.
+  **14,880/14,880** tests with zero skips or failures across 14 assemblies
+  (hermetic lane filter, as above).
   `AcDream.App.Tests` contributes **5,783/5,783**; campaign-focused App cases
   cover descriptor/asset/SPIR-V
   validation, pack-off/no-op invariants, atomic asynchronous candidate swaps,
@@ -760,10 +764,16 @@ require their own rows.
 acdream's default path has a stricter gate: zero new enhancement passes,
 images, buffers, submissions, or shader variants, with CPU/GPU deltas within
 the existing run-to-run noise envelope and deterministic reference captures
-unchanged. `NoOpRenderPackProductionIntegrationTests` pins the pre-campaign
-pass list, pipeline set, draw/dispatch tuple, framebuffer SHA-256, and complete
-resource ledger; the matrix's six physical retail rows independently record
-zero pack work at all three resolutions and both pacing modes.
+unchanged. `NoOpRenderPackProductionIntegrationTests` pins the pass list,
+pipeline set, draw/dispatch tuple, framebuffer SHA-256, and resource ledger of a
+**2x2 synthetic, one-draw composition fixture on a recording device that does
+not rasterize** — it proves the controller arm adds nothing to that shape, not
+that the production frame is unchanged. The matrix's six physical retail rows
+record zero pack work at all three resolutions and both pacing modes. The
+actual pack-off pixel and production-performance invariance against the
+pre-campaign build `6c79d35c` was established later by Campaign VM slice VM0
+([report](../research/2026-08-22-vm0-default-path-invariance.md), corrected
+2026-08-22).
 
 Measurement protocol:
 

docs/plans/2026-08-22-visualmaster-campaign.md

@@ -80,12 +80,12 @@ single-pass path darkens by ~10 %. Neither explains a scene-wide level.
 | VM1 | F2/F3 — #226 single-pass re-port + fade removal | **CLOSED 2026-08-22** — `05970306`, `388457a7`, `ae651312`, closeout; Opus APPROVE |
 | VM2 | F3 — which retail detail path ran | **CLOSED 2026-08-22** — single-pass; see [cdb note](../research/2026-08-22-vm2-retail-detail-path-cdb.md) |
 | VM3 | F4 — linear-light post stack | automated + **owner visual** |
-| VM4 | F5 — overclaiming docs, incl. the reviewer's own | docs |
+| VM4 | F5 — overclaiming docs, incl. the reviewer's own | **CLOSED 2026-08-22** |
 | VM5 | F8 — volumetric banding; F7 filed | automated |
 | VM6 | Foliage wind | automated + **owner visual** |
 | VM7 | Closeout: full gates, register, roadmap, merge | **owner** |
 
-Order is VM2 (done) → VM0 (done) → VM1 (done) → VM4 → VM5 → VM3 → VM6 → VM7. VM0 goes first because everything after it is measured
+Order is VM2 (done) → VM0 (done) → VM1 (done) → VM4 (done) → VM5 → VM3 → VM6 → VM7. VM0 goes first because everything after it is measured
 against the baseline it establishes.
 
 ---
@@ -220,6 +220,17 @@ clipping, highlights roll off". Budget unchanged (two `pow` per pixel).
 
 ## VM4 — Truthful documents (F5)
 
+**OUTCOME (2026-08-22): CLOSED.** Corrected in place, each with a dated
+"VM4 correction" note: the AR plan's 2x2-oracle sentence and both
+"zero skips" totals (now "under the hermetic lane filter"); the Stage-2
+report's turning-hitch paragraph (observer tax, not product); the Track A
+report's and the findings doc's `TerrainUtils.GetNormal` premise; the findings
+doc's "retail brightens" section (fallback only; single-pass lerp is what runs),
+its landscape-detail open question (`LandscapeDetailTextures = 0`, answered by
+VM2), and its open question 5; the completion audit's retail-path row; and the
+review's own F1/F2/F3/F5 headers. The VM0 production table is now the baseline
+in the findings doc §5.
+
 Correct, in the AR plan and its reports, the four sentences the review
 named: the 2×2 oracle described as a production pin; the turning-hitch
 conclusion drawn under the automation observer; the "zero skips" headline