wip(assembler): round L23 -- inter-strate passages planned from the resolved layout and carved

After L22 the FI -> SW passage no longer connected the strates (legacy owner-voxel coordinates,
lower end 23 m above SW), and Core never carved passages through the bands. Now the director
plans passages from the resolved layout (PlanResolvedLayoutPassagesV1; deterministic hash of
seed/strates/connection; placement disk from PassageConfig, 8-24 m around (0,0)); shared
composition applies generator field -> bands -> bounded passage carve and support shelf, opening
the bands only along the tunnel. Mouths bind to the strate routes. Capsule audit: 0 blocked /
0 unsupported (325,962 samples FI, 284,319 TunnelNetwork), negative controls detected; all 8
generator kinds exercised. SW away from the passage is bit-identical. Layout V3, evaluator 9.
Open: look not yet natural (stepped tube in FI void, terraced SW arrival); SW-as-upper route
planning fails; Unreal adapter uncompiled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CSFYgsdW8ejZSyiMf4qRSX

ARCHITECTURE.md

@@ -1924,6 +1924,33 @@ controls continue to reject malformed bands.
 Evidence and owner caveats are in
 [`Standalone/Research/WorldAssemblerM3/Linux22/REPORT.md`](Standalone/Research/WorldAssemblerM3/Linux22/REPORT.md).
 
+### 8.41 Director-resolved inter-strate passages and walkable landings — World Assembler L23
+
+Core passage geometry is derived after the director has resolved physical strate bands and native
+route anchors. `PlanResolvedLayoutPassagesV1` joins every adjacent resolved pair. Its placement hash
+uses `(seed, upper strate, lower strate, connection, salt)`; `PassageConfig.DistanceMax` is the
+outer radius around world `(0,0)` (24 m for the owner's first interface), while `DistanceMin` is
+the inner radius used when a mouth has no route anchor. A route-bound mouth reuses the upper
+strate's departure or lower strate's arrival anchor, after checking it lies within `DistanceMax`.
+The legacy `UVoxelStrateManager::GeneratePassages` and its owner-voxel control points remain the
+legacy generator path; Core does not import the exported legacy `passages` array. The season
+manifest carries recipes and plans, and the adapter rebuilds the resolved layout and its passages
+from the current manager slots and route anchors each time it attaches the Core world.
+
+`ApplyResolvedStrateComposition` composes the current generator field, applies the resolved ceiling
+and bedrock bands, then unions the passage carve and floor support. Only the hashed capsule path
+opens a band; the support strip stays below the player capsule. The lower mouth index splits the
+monotone descent from the short route-bound landing tail, whose height may vary with the route.
+Both route and passage audits sample the 0.34 m by 1.76 m capsule, support probes, and grade; the
+negative control compiles the same world without passage carving and must detect a blocked capsule.
+The L23 shared-field change is `WorldAssemblyEvaluatorVersion=9`. It does not change the L22 bands
+or any generator's field away from a passage. The L23 report includes exact-query/hash comparisons,
+the blocked control, captures, and the Windows adapter checklist. §8.10's cache, proof, streaming,
+and async rules remain unchanged.
+
+[`Standalone/Research/WorldAssemblerM3/Linux23/REPORT.md`](Standalone/Research/WorldAssemblerM3/Linux23/REPORT.md)
+records the audit and captures.
+
 ## 9. Multiplayer model (listen-server first, dedicated-friendly)
 
 > **Status: transport is DESIGN ONLY — nothing is networked in-tree yet** (no `Replicated`/`HasAuthority`/RPCs; a