feat(render) Campaign FW3.2b-2: THE STATIC CUTOVER - the walk drives production statics

The retail frame walk now drives every production static draw. In
RetailPViewRenderer.DrawInside, when the concrete executor + the
packed product + the FW3.1 walk registries are all wired (all
production compositions - anything less throws):

- A pre-walk events-only collection pass (the shadow sink generalized
  to WalkVisitedSetCollector) gathers the frame's visited cells,
  buildings, and landscape-cell turns; the visited cells union into
  prepareCells so EnvCellRenderer prepares every shell the driver
  draws.
- DrawWalkDrivenStatics runs the WalkFrameDriver over the production
  world data (WalkProductionWorldData over RenderSceneQuery + the
  building registry): sky, terrain slices, outdoor statics at their
  landscape-cell turns, buildings (alpha barrier -> punch/look-in
  passes -> shell) in retail order, interior clear+seals as leaf
  closures (the old tail block's drain reasoning moves with them),
  flood cells shell-then-contents. Landscape/cell-stage particle
  owners re-source from the walk's visited sets - retail gates
  particles per cell turn (ShouldDrawParticles @0x0050FE60), which
  this is; the old sphere filter was the approximation.
- DrawLandscapeDynamicsPhase + DrawBuildingLookInDynamics carry the
  dynamics-only remainder (LookInObject now dynamic-classified,
  late outside-dynamics + weather, particle unions); DrawDynamicsLast
  and the outdoor flush are unchanged.
- The product builder stops emitting LandscapeOutdoorStatic /
  LandscapeBuildingShell / CellStatic (methods deleted, dead index
  tracking removed); LookInObject loads cells with
  includeStatics: false.

The old static path survives ONLY behind !walkActive for the
standalone/diagnostic executor-fake path that keeps 15 retail-ordering
regression tests exercising the barrier/punch/seal machinery; no
production composition can reach it. Its deletion is FW4 scope (the
plan's "deleting the patch apparatus") - recorded in the plan.

Transitional risks recorded in code/report: the two-pass walk cost
(FW3.4 measures), the interior slice-count reconciliation between the
old clip assembly and the walk's own exit-view survival, and the
outdoor merged-flood punch coverage now riding the walk's own
building-BSP punches (retail-faithful per FW1; the owner visual gate
verifies).

Suites (lead-verified): full Release build 0 warnings; hermetic
6,750/0 (baseline minus the three deleted route tests); Walk lane
201/1; InstalledDat Walk conformance 40/1 untouched. The two
IL-branch tests the implementation round reported failing pass in
every lead run - the recurring parallel-load flake pair.

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

src/AcDream.App/Rendering/Wb/WbDrawDispatcher.OrderedStream.cs

@@ -210,6 +210,32 @@ public sealed unsafe partial class WbDrawDispatcher
         }
     }
 
+    /// <summary>
+    /// Campaign FW3.2b-2: the production frame/encoder pair for
+    /// <see cref="WalkFrameDriver"/>'s own <see cref="SubmitOrderedStream"/>
+    /// calls (contrast this stage's diagnostic-target callers, which supply
+    /// their own frame/encoder — see <see cref="SubmitOrderedStream"/>'s own
+    /// doc comment). Reads the SAME world-pass scope <see cref="SubmitRhi"/>
+    /// already requires (<see cref="RequireRhiFrame"/> /
+    /// <c>_scope.RequireEncoder()</c>) — fails loud rather than handing the
+    /// driver a null pair when the world phase is not bracketing.
+    /// </summary>
+    internal (IGpuFrame Frame, IGpuPassEncoder Encoder) RequireWalkSubmission() =>
+        (RequireRhiFrame(), _scope!.RequireEncoder());
+
+    /// <summary>
+    /// Campaign FW3.2b-2: the live colour-attachment size, for
+    /// <see cref="WalkProductionFrameContext"/>'s viewport (the walk's ray
+    /// caster needs the REAL viewport, not the FW0/FW1 capture-client
+    /// fixture constants — see that class's own doc comment). Null outside
+    /// the world phase (no scope published yet); the caller falls back to
+    /// the fixture constants with a comment in that case rather than
+    /// failing loud, since a missing scope here is a startup-ordering
+    /// timing question, not a misconfiguration.
+    /// </summary>
+    internal (int Width, int Height)? WalkAttachmentExtent =>
+        _scope is null ? null : (_scope.AttachmentWidth, _scope.AttachmentHeight);
+
     /// <summary>
     /// Submits <paramref name="stream"/> in walk order through the existing
     /// RHI: per-instance-first emission (see the type doc comment), one