docs(physics): close Campaign P visual matrix

docs/ISSUES.md

@@ -35,11 +35,12 @@ What does NOT go here:
   [`docs/architecture/code-structure.md`](architecture/code-structure.md).
 - **Active M4 prelude:** resume
   [`plans/2026-07-23-world-interaction-completion.md`](plans/2026-07-23-world-interaction-completion.md).
-  Slices 1–3, including the complete assessment surface, are user-accepted.
+  Slices 1–4, including equipped-child picking, are user-accepted. Vendor
-  Equipped-child picking and vendor browse/transactions remain Slices 4–6.
+  browsing and authoritative transactions remain Slices 5–6.
 - **Separate rendering gate:** `#225`, lifestone/particle alpha ordering. Its
   connected performance, lifetime, and unattended portal routes pass.
-- **Carried behavior debt:** `#116` slide response (Campaign P P2 scope;
+- **Carried behavior debt:** `#116` slide response, `#273` tight-gap
+  collision clearance, and deferred restricted-house gate `#274`;
   `#153` closed 2026-07-30 on the AD-30 hold + arrival StopCompletely +
   canonical outbound + reveal-barrier evidence chain). TS-50/TS-51/TS-53 are
   tracked in the divergence register.
@@ -98,6 +99,55 @@ Copy this block when adding a new issue:
 
 ---
 
+## #274 — Restricted/barred-house entry needs a connected retail comparison
+
+**Status:** OPEN — explicitly deferred by the user on 2026-07-31
+**Severity:** LOW (validation debt; no confirmed failure)
+**Filed:** 2026-07-31
+**Component:** physics / EnvCell entry restrictions
+
+**Description:** Campaign P ported retail
+`CObjCell::check_entry_restrictions` and retired AP-71, but the final
+connected barred-house scenario was not run. The user requested that this
+gate be deferred and retained as an issue rather than block current work.
+
+**Acceptance:** at a known restricted house, use equivalent characters in
+retail and acdream. Both must reject an unauthorized character at the same
+threshold, while an owner/guest enters normally. Record the house/cell,
+character access state, and result before closing.
+
+---
+
+## #273 — ACDream can squeeze through tight world gaps that block retail
+
+**Status:** OPEN — live mismatch confirmed 2026-07-31; exact location/capture
+still required
+**Severity:** MEDIUM (world traversal differs from retail)
+**Filed:** 2026-07-31
+**Component:** physics / player collision shape and cell collision
+
+**Symptom:** in some tight world-geometry passages, acdream can pass through
+a gap that blocks the retail client. The Campaign P wall/corner slide,
+crowd, remote movement, door, portal, and general collision checks otherwise
+passed.
+
+**Scope:** this is not folded into #116, which tracks a specific
+near-perpendicular slide-response/fixture family. The new symptom is
+under-blocking or clearance divergence and may involve the active player
+sphere list, scale/pose, candidate-cell collision set, or a missing
+world-collision primitive.
+
+**Next evidence:** record one exact reproducible location, heading, movement
+input, character scale/equipment, and cell ID in both clients. Capture the
+acdream transition path and active Setup-derived sphere list before changing
+collision math.
+
+**Acceptance:** the captured tight gap blocks or permits traversal at the same
+clearance as retail without regressing normal doorways, stairs, wall grazing,
+or crowd movement.
+
+---
+
 ## #272 — Strength enchantments do not invalidate burden
 
 **Status:** DONE — 2026-07-31 (implementation, automated gates, and user live

docs/plans/2026-04-11-roadmap.md

@@ -35,7 +35,7 @@ N0–N6 with a permanent loss-injection gate at N5 and a user Coldeve
 endurance session as final acceptance. The plan is
 [`2026-07-29-network-transport-campaign.md`](2026-07-29-network-transport-campaign.md).
 
-**Campaign P — physics retail-feel parity (ACTIVE, started 2026-07-29):**
+**Campaign P — physics retail-feel parity (CLOSED 2026-07-31):**
 user-directed pre-vendor detour closing every physics-scope gap the
 2026-07-29 audit found: stat-coupled movement (burden/stamina/vitae →
 run/jump), the collision response-layer edge family (friction gate,
@@ -57,7 +57,11 @@ The matrix then exposed #272: burden was invalidated by base Strength but not
 by Strength enchantment add/purge. Runtime movement plus both retained burden
 surfaces now use effective Strength and the canonical enchantment-change edge;
 automated gates pass and the connected buff/death gate was user-accepted on
-2026-07-31. Campaign P then continues with the unfinished live matrix rows.
+2026-07-31. The final session also accepted burden/exhaustion, wall/corner,
+crowd, two-client remote/door/portal, and shallow-water behavior. The user
+waived the general sweep and explicitly deferred the barred-house gate as
+#274. A separate tight-gap clearance mismatch is carried as #273 pending an
+exact-location capture. World-interaction Slice 5 vendor browsing resumes.
 
 ---
 

docs/plans/2026-05-12-milestones.md

@@ -87,8 +87,10 @@ program: spell-bar overflow, status Use/Assess, assessment information,
 equipped-child picking, vendor browsing, and authoritative vendor
 transactions. This is deliberately using the extracted interaction owners and
 canonical shared main-panel host before quest/emote/character-creation bodies
-broaden the feature surface. Slices 1–3 are user-accepted; resume at Slice 4
+broaden the feature surface. Slices 1–4 are user-accepted. Campaign P closed
-equipped-child picking.
+on 2026-07-31 with tight-gap collision clearance (#273) and the deferred
+restricted-house gate (#274) explicitly carried; resume at Slice 5 vendor
+browsing.
 
 The separately authorized modern-runtime performance program has completed
 Slices A–D: corrected measurement, prepared-package bake/dedup, package-only

docs/plans/2026-07-29-physics-parity-campaign.md

@@ -1,5 +1,9 @@
 # Campaign P — Physics Retail-Feel Parity
 
+**Status:** CLOSED 2026-07-31 — final user matrix accepted; tight-gap
+clearance issue #273 and deferred restricted-house gate #274 are explicitly
+carried follow-ups.
+
 **Filed:** 2026-07-29. **Directed by the user** as a pre-vendor-management
 detour after the same-day physics/collision retail-fidelity audit. The
 world-interaction program (Slice 5, vendor browsing) resumes when this
@@ -411,7 +415,11 @@ root-caused, retail-ported, and user-accepted in the same session:
 
 Matrix rows accepted so far: speed parity, roof slide, downhill bounce,
 flat pop, uphill landing, and #269's slope-stop feel
-(rows 3/4/5-partial/12-partial). Remaining rows: 1, 2, 6, 7, 8, 9, 10,
+(rows 3/4/5-partial/12-partial). The 2026-07-31 final session accepted
-and 11. The #269 checkpoint passes 4,107 Core tests / 2 skips and 439
+burdened movement, exhausted jumping, wall/corner response, crowded-monster
+movement, two-client remote/door/portal behavior, and shallow water. The user
+waived the general sweep, deferred restricted-house validation as #274, and
+retained the separate tight-gap clearance mismatch as #273. Automated
+scenario 11 remains 20/20 passing. The #269 checkpoint passes 4,107 Core tests / 2 skips and 439
 Runtime tests / 0 skips; the complete Release suite passes 10,061 tests /
 5 skips / 0 failures.

docs/plans/2026-07-30-physics-parity-visual-matrix.md

@@ -72,3 +72,24 @@ manual halves of 11-12.
   threading at a specific site, or the #116 head-sphere change — both
   P3/final-slice deltas).
 - Other scenarios: not yet reported.
+
+## User matrix session 2 results (2026-07-31)
+
+- Scenario 1 (burdened movement): **PASS**.
+- Scenario 2 (exhausted jumping): **PASS**.
+- Scenario 6 (wall graze/corner movement): **PASS**.
+- Scenario 7 (crowded-monster movement): **PASS**.
+- Scenario 8 (two-client remote movement, doors, portals, and its collision
+  checks): **PASS**.
+- Scenario 10 (shallow-water sink-in): **PASS**.
+- Scenario 9 (restricted/barred house): **DEFERRED BY USER** and retained as
+  issue #274.
+- Scenario 12 (general movement sweep): **WAIVED BY USER**; the accepted
+  focused rows and existing automated soak are sufficient for this campaign.
+- A separate live mismatch remains: acdream can squeeze through some tight
+  gaps that block retail. This is outside the accepted wall-graze response
+  check and is retained as issue #273 pending an exact-location capture.
+
+Together with the previously accepted scenarios 3–5 and the automated
+20-login scenario 11, the Campaign P matrix is closed with #273 and #274 as
+explicit carried follow-ups.