docs: Campaign FW - FW3.2b-2 static-cutover status in the plan

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

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

@@ -400,6 +400,23 @@ deeper commitment.
      suites; the connected lifecycle route; the offline pixel gate
      (outdoor statics); dense-Arwic pre/post pair (physical display).
 
+**FW3.2b-2 STATUS (2026-08-30, @`4918677b`): THE STATIC CUTOVER IS
+COMMITTED.** The walk drives every production static draw
+(`DrawWalkDrivenStatics` + the dynamics-remainder phases); the three
+static routes are deleted from the product builder; particle owners
+re-source from the walk's per-cell-turn visited sets (retail's own
+gate — `ShouldDrawParticles` @0x0050FE60). Landed evidence: the walk
+shadow probe ran 11k+ live frames faultless with walkCells ⊂ oldCells
+every frame. The old static path survives ONLY behind `!walkActive`
+for the executor-fake test path (15 retail-ordering regression tests;
+unreachable by production) — **its deletion is FW4 scope**.
+Transitional risks recorded in code: two-pass walk cost (FW3.4
+measures), interior slice-count reconciliation between the old clip
+assembly and the walk's exit-view survival, outdoor merged-flood
+punch coverage now riding the walk's building-BSP punches (owner
+visual gate verifies). Suites: hermetic 6,750/0; Walk 201/1;
+InstalledDat conformance 40/1 untouched.
+
 - **FW3.3 — ShellDrawLiftZ retirement.** THREE sites (the register row
   AP-32 lists only two — `LandblockBuildFactory.cs` bakes the lift into
   the drawn cell transform and is unlisted): delete all three, flip the