docs(render): establish Campaign OVERHAUL baseline

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

@@ -1,6 +1,10 @@
 # Campaign FW — the retail frame walk (implementation plan)
 
 **Status:** ACTIVE (opened 2026-08-30; spec approved by owner 2026-08-30).
+**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
+world-construction and render-solidity implementation work.
 **Spec (approved):**
 [`docs/superpowers/specs/2026-08-30-campaign-w-retail-frame-walk-design.md`](../superpowers/specs/2026-08-30-campaign-w-retail-frame-walk-design.md)
 — note: the campaign letter is **FW** (frame walk); the spec predates the
@@ -452,12 +456,17 @@ Post-refactor dense Arwic uncapped vs the SAME baseline: CPU p50
 is now FASTER than the old static path. The refactor's own crash
 round (VK_ERROR_DEVICE_LOST) taught the binding contract: leaf draws
 and alpha flushes rebind set-0 between ranges, so DrawOrderedRange
-rebinds per call; only the ring WRITES are once-per-frame. FOLLOW-UP
-FILED: alloc p50 still ~1.5 MB/frame on the walk path (baseline
-133 KB) - the per-frame driver/leaf/populator object graph in
-DrawWalkDrivenStatics; hoist to renderer fields with per-frame
-Reset (FW3.4 closeout or FW6 polish; CPU-neutral today, GC-hitch
-hygiene).
+rebinds per call; only the ring WRITES are once-per-frame.
+**FW6 ALLOCATION CLOSEOUT (`b8befded`).** The ~1.5 MiB/frame follow-up is
+closed: `RetailPViewRenderer` now owns one retained `WalkFrameDriver`,
+`WalkProductionFrameContext`, and `WalkProductionLeafRenderer`; `RebindFrame`/
+`Reset` replace per-frame reconstruction, and abort/reset paths preserve the
+terminal ledger. The exact-binary nine-stop closeout route reports steady
+allocation p50 between 138.6 and 204.5 KiB/frame across its stops (the old
+dense-town tail was ~1,500 KiB/frame; the pre-walk baseline was 133 KiB/frame).
+The connected route is not the original dense-Arwic perf vehicle, so this is
+mechanism + bounded-live evidence rather than a fabricated same-scene A/B; the
+campaign's CPU stop rule was already cleared by the exact dense-Arwic pair.
 
 - **FW3.4 — perf checkpoint + gates.** BASELINE CORRECTION: the
   519.7 fps / 1.869 / 1.096 ms numbers are the Aerlinthe