checkpoint: preserve user-gated FW closeout fixes

This commit is contained in:
Erik 2026-08-31 08:27:37 +02:00
parent a2f2eb7d78
commit b8befded8b
22 changed files with 1005 additions and 198 deletions

View file

@ -538,6 +538,18 @@ Stages FW0FW6; no long-lived dual path.
**Spec:** [`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).
**Plan + ledger:** [`docs/plans/2026-08-30-campaign-fw-frame-walk.md`](2026-08-30-campaign-fw-frame-walk.md).
**2026-08-31 checkpoint — code complete, final connected gate pending.**
`RetailFrameWalk` is now the only production visibility/order owner. Exact
walk portal polygons route shells, statics, and dynamics through the same
Vulkan clip slots (`11e68aad`), fixing the cathedral defect's actual mechanism:
accepted content was previously emitted whole after a Boolean sphere test.
The stale frame-product carrier is deleted, and the retail camera adjustment
laws are complete (`90eba0ec`, `4d037974`). Release hermetic App gates passed
6,729/6,729 before a still-open character-selection client locked the Release
outputs. Campaign FW remains ACTIVE until both standard connected routes and
the complete cathedral/transition/physical-camera visual matrix pass. Safety
rollback before the final batch: `572de1ec`.
### Phase O — DatPath Unification — SHIPPED 2026-05-21
**Tagline:** ONE thing touches the DATs.