docs(overhaul): prepare owner G4 checklist and reconcile active status

docs/architecture/acdream-architecture.md

@@ -1218,8 +1218,12 @@ transaction: a walk contributes its exact landscape set, while a null-root
 safety frame completes `hasCompletedView=true` with an empty landscape set and
 no reconstructed fallback. Login and portal-space retain
 `hasCompletedView=false`. The former terrain frustum/AABB reconstruction and
-last-frame point-light feedback seam are deleted. Directional shadows remain
-the next typed landscape consumer (S5-c2).
+last-frame point-light feedback seam are deleted. The opt-in directional-shadow
+consumer landed in S5-c2: the frame builder captures the prior-completed
+landscape set/flag; `DirectionalShadowCasterFrame.Select` selects world casters
+through the registry's retail CELLARRAY, or a building's `EffectCellId`, and
+the terrain shadow selection uses the same product. Selection projects onto
+retained topology without introducing a second visibility flood (IA-24).
 
 Point-light retention follows retail's two independent products: seven dynamic
 and forty static candidates, with POINT lights ranked from the light owner's

docs/plans/2026-04-11-roadmap.md

@@ -518,7 +518,26 @@ Plus polish that doesn't get its own phase number:
 
 ## Phases ahead — agreed order
 
-### Campaign FW — the retail frame walk (ACTIVE 2026-08-30)
+### Campaign OVERHAUL v2 — world solidity (ACTIVE, G4 unpassed, 2026-09-05)
+
+The five-slice successor owns geometry, cross-cell membership, retail walk,
+depth/alpha ordering and consumer/material closeout. S1-S5 implementations and
+the gate-found repairs are landed; final Release candidate `eea83ac88` has
+17,094 hermetic passes and passing lifecycle/reconnect/R6 checks. Canonical
+InstalledDat is not wholly green (eight unchanged failures/one skip), and one
+final visual control failed at native shutdown (#422 symptom recurrence).
+Owner G4, explicit carried-result disposition and final documentation closeout
+remain; no main merge or CLOSED claim. FPS/C2 is owner-deferred and the known
+retail cathedral slab leak is unchanged. The current ledger is
+[`2026-09-01-campaign-overhaul-world-solidity.md`](2026-09-01-campaign-overhaul-world-solidity.md),
+with the [owner checklist](../research/2026-09-01-overhaul/g4-owner-checklist.md).
+
+### Campaign FW — the retail frame walk (execution superseded by OVERHAUL)
+
+The checkpoint below is retained history, not today's implementation model
+or gate status. OVERHAUL replaced ordinary-mesh GPU clip routing with the
+retail admission/depth/ordering contracts; the architecture document and
+successor ledger own current truth. FW's historical PASS rows do not pass G4.
 
 **Tagline:** retail owns every frame decision; modern code only moves bytes.
 
@@ -549,7 +568,7 @@ laws are complete (`90eba0ec`, `4d037974`). The complete Release gate passed
 standard connected routes passed on `b8befded` (lifecycle/reconnect with zero
 warnings/failures; all nine R6 checkpoints with zero failures). The owner passed
 the cathedral/transition, restored-particle, Tusker terrain/object, and lingering
-spell-worldobject matrices. Campaign FW remains ACTIVE only for the physical
+spell-worldobject matrices. At that checkpoint, FW remained active for the physical
 camera-feel verdict and the final post-probe-removal Release re-gate. Safety
 rollback before the final batch: `572de1ec`; accepted closeout checkpoint:
 `b8befded`.

docs/plans/2026-05-12-milestones.md

@@ -12,18 +12,20 @@ world-lifecycle automation protects fresh login, outdoor/world-edge/dungeon
 travel, same-location revisit, exact graceful disconnect, and uncapped
 fresh-process reconnect with canonical JSON/PNG evidence.
 
-**Active render prerequisite (2026-08-31): Campaign FW — retail frame walk.**
-The production cutover and camera port are code-complete: one retail-derived
-walk now owns rooting, portal recursion, per-view clipping, draw order, depth
-events, and shared-alpha barriers. The cathedral through-wall mechanism was a
-whole-mesh submission after Boolean portal admission; exact walk aperture clip
-slots now route shells, statics, and dynamics together. Both standard connected
-routes pass on the accepted `b8befded` checkpoint, as do the owner-gated
-cathedral transition/particles/seams, Tusker terrain/object stability, and
-completed spell-worldobject retirement matrices. The campaign remains ACTIVE
-only for the physical retail-camera feel verdict and final post-probe-removal
-Release re-gate. Plan/ledger:
-[`2026-08-30-campaign-fw-frame-walk.md`](2026-08-30-campaign-fw-frame-walk.md).
+**Active render prerequisite (2026-09-05): Campaign OVERHAUL v2 — G4 unpassed.**
+The five-slice successor to FW has landed the geometry, membership, retail
+walk, depth/alpha and consumer/material cutovers, plus the gate-found exterior,
+portal-reveal, lighting, equipped-item and cathedral-wall repairs. The final
+candidate is Release `eea83ac88`; hermetic17,094/17,094 and the final lifecycle,
+reconnect and R6 checks pass. Canonical InstalledDat retains eight documented
+failures/one skip; a final visual-control run also failed at native shutdown
+despite graceful network logout. Neither is silently counted as PASS.
+The final owner matrix and explicit carried-result disposition remain, followed
+by documentation closeout; no main merge before G4. FPS/C2 is owner-deferred,
+and retail's known cathedral slab leak is unchanged. FW's old ordinary-mesh
+clip model is historical, not the current architecture. Plan/ledger:
+[`2026-09-01-campaign-overhaul-world-solidity.md`](2026-09-01-campaign-overhaul-world-solidity.md);
+[remaining owner checklist](../research/2026-09-01-overhaul/g4-owner-checklist.md).
 
 Before new M4 quest/emote/character-creation subsystem bodies enter the App
 layer, the active structural prerequisite is the behavior-preserving

docs/plans/2026-08-30-campaign-fw-frame-walk.md

@@ -1,6 +1,8 @@
 # Campaign FW — the retail frame walk (implementation plan)
 
-**Status:** ACTIVE (opened 2026-08-30; spec approved by owner 2026-08-30).
+**Status:** EXECUTION SUPERSEDED by Campaign OVERHAUL (opened 2026-08-30;
+spec approved by owner 2026-08-30). Historical stages and evidence are retained;
+this status is not a new user-acceptance or merge claim.
 **Successor execution ledger (owner-requested 2026-09-01):**
 [`docs/plans/2026-09-01-campaign-overhaul-world-solidity.md`](2026-09-01-campaign-overhaul-world-solidity.md).
 Campaign OVERHAUL preserves FW as evidence/history but owns all further

docs/plans/2026-09-01-campaign-overhaul-world-solidity.md

@@ -715,6 +715,8 @@ the wall run instead exited0xC0000374 after graceful status/ACK. This is a
 retained FAIL matching carried#422's symptom, not proven same root cause or
 AMD#477. No speculative fix or Windows diagnostic-setting change.
 Broader owner matrix and G4 are still owed; these observations do not close it.
+The remaining owner session and explicit carried-result boundaries are in
+`docs/research/2026-09-01-overhaul/g4-owner-checklist.md`; no row is pre-passed.
 Known retail leak unchanged, FPS/C2 deferred, no main merge.
 
 ### Rollback ledger

docs/research/2026-09-01-overhaul/g4-owner-checklist.md

@@ -0,0 +1,80 @@
+# G4 owner checklist — final candidate, 2026-09-05
+
+Status: **NOT RUN / NOT ACCEPTED**. This is the remaining owner session,
+not another implementation or review round. Binding scope is the campaign
+plan's S5 gate and section10 scene matrix. The automatic checks do not replace
+the owner's judgment. Do not merge or mark the campaign closed from this card.
+
+## Candidate and launch
+
+Use the existing Release binaries built at
+`eea83ac884d0b0fd74d86a17a16d7d5d93f64d94`; documentation checkpoint
+`64d7a3981a39b50ee9a33556b01384d480a33e37` records the final controls.
+Exact App/Core/package hashes and green build evidence are in
+`c1a-integrated-verification.md`. Recipe10 package is
+`C:\Users\erikn\Documents\Asheron's Call\acdream-v10-s5-c5.pak`.
+
+Before launch, recheck binary/package hashes, both client processes and ACE
+UDP9000; record the launch commit, flags, profile, process and log directory.
+Keep the saved High/MSAA4, near4/far25 profile for the normal candidate run.
+No rebuild beside either client; no code change after the accepted binary.
+Owner session has no automatic route or automatic close. A retail comparator
+is needed for the two-client row and known cathedral slab comparison; launch
+each client in its own command. Close owned clients gracefully when agreed.
+
+## What is already evidenced
+
+- Release build: zero warnings/errors. Literal hermetic lane:17,094 passes.
+- Two fresh actual geometry/membership runs and the unchanged seven-fixture,
+  25-frame Signature8 corpus pass with equal products.
+- Canonical InstalledDat is **not fully green**:376 pass,8 existing failures,
+  1 existing skip. `c1c-integrated-verification.md` names them; final evidence
+  verifies unchanged identities. Do not describe this as an entire-lane PASS.
+- Final capped lifecycle, fresh uncapped reconnect and nine-stop R6 passed;
+  `s5-final-lifecycle-stability-verification.md` retains their limits/warnings.
+- Five final visual-control routes produced51 inspected PNGs. Portal reveal,
+  exterior wall block/escape, dungeon lighting and captured geometry passed
+  narrowly; `s5-final-visual-controls.md` has every path and proof boundary.
+- Four controls exited0. The wall control instead exited0xC0000374 after
+  graceful status/logout: **process FAIL**, matching carried#422's symptom.
+  No native stack proves its cause; it is not established as AMD#477.
+
+## Owner session
+
+For every row retain PASS/FAIL, actual `/loc`, symptom if any, and PNG/log
+paths. All rows below remain **PENDING** on this final binary. The starting
+locations are navigation aids, not a substitute for movement or camera work.
+
+| Row | Check | Start / navigation |
+|---|---|---|
+| 1. Cathedral walls and hands | Cross the south transition; hold a weapon/wand, rotate and zoom. Body, held item and walls must keep correct depth. Walk into the repaired exterior wall and back away; no penetration/sticking. Exact retail push-out x is not required. | South: F4180106 [37.181568 46.790077 169.804993] to F4180104 [37.310383 48.895710 169.804993]. Wall: F4180012 [49 39.257545 160.004990]. |
+| 2. Cathedral stairs/ramp and two clients | Walk the stairs with camera fully out/tilted; slabs and chamber walls remain stable. Compare the known exterior slab leak to retail: same slab/extent, not removal. Stand on the formerly invisible exterior ramp and record its actual pose. Place the second actor behind a wall: occluded except through a retail-valid sightline. | Stairs: F4180113 [39.502899 19.589222 181.119247], plus plan section10's0107/0112 pair. Remote actor: F4180112 [36.299465 18.594580 169.804993]; observer in0104,0101 and outdoors. Exterior ramp has no recovered standing pose; the indoor020009A2 witness is not a substitute. |
+| 3. Facility Hub | Complete the stair circuit: bottom, side, ascent and top. Zoom/pan/rotate; player, stairs and walls stay whole. | `/teleloc 8A02015E 60.251431 -38.848198 -5.995000 0.995004 0 0 -0.099833` |
+| 4. Nanto and Holtburg | Continuously rotate at Nanto: waterfalls persist and houses occlude correctly. Walk Holtburg town, through a building doorway and around the lifestone: intact buildings, no terrain leak, correct particle/depth behavior. | Nanto:`/teleloc E43D001E 93.826614 126.522484 120.005005 1 0 0 0`; Holtburg:`/teleloc A9B40019 84 7.1 94.005 1 0 0 0`. |
+| 5. Two ordinary dungeons | Traverse the preselected0125 and8C04 interiors, including available stairs/portals and camera seams. Walls/floors stay solid and lighting usable. Arrival stills alone do not pass this row. | `/teleloc 01250126 30 -60 6.005 1 0 0 0`; `/teleloc 8C0401AD 12.319900 -28.482000 0.005000 -0.338946 0 0 -0.940806`. |
+| 6. Tusker combat | Use the owner's dense combat route. Fight, cast and rotate; terrain/scenery/actors stay stable, held items show, spell objects retire. | Owner's route; record actual location. The training dungeon is not a combat substitute. |
+| 7. Travel and sustained movement | Portal to/from outdoor, building and dungeon destinations, including adjacent repeated3032/3031 hops. No stuck/partial reveal; record unusually long waits. Add ten minutes of actual free movement and include cathedral/Neftet jumping from the earlier crash reports. | Existing `route-474-portal-reveal.txt` pins the adjacent pair. Neftet:`/teleloc 8763000E 40.4574 129.281 8.004999 1 0 0 0`. Timed idle waits do not count as free movement. |
+
+On any crash, preserve that run's time/logs, stop its gate and record FAIL;
+network logout or a client-authored code0 does not override the OS exit.
+Do not retry just to replace a failed record. The lead reads local crash
+reports/Windows evidence without changing registry, driver or dump settings.
+
+## Acceptance and remaining closeout
+
+Owner PASS must identify the tested rows and any explicit carried exception.
+The historical acceptance of#422 in Campaign VM is not automatically a new
+OVERHAUL acceptance. A good visual session does not prove the original AMD
+reset's initiating cause, remove the installed-data failures, or convert
+the recorded shutdown failure to PASS. Their disposition remains explicit.
+
+FPS/C2 performance work is owner-deferred. Retail's known cathedral leak is
+unchanged; its proposed post-campaign improvement is not part of this gate.
+
+After the owner results, reconcile the shipping documentation before closure:
+architecture, WorldBuilder inventory, divergence register, launch options,
+FW ledger (superseded, not deleted), roadmap/milestones and campaign memory.
+Keep the existing failure records. Only when G4 and that closeout actually
+agree with the code can the campaign be marked CLOSED — USER ACCEPTED and
+the authorized merge considered. Do not rebuild the accepted product for
+documentation-only changes.