Erik efb5f2c3b8 docs(issues): #98 sharpened diagnosis — Path 5 vs Path 6 path-selection bug ... Updates issue #98 with the sharp diagnosis from the retail cellar cdb trace (commit 134c9b8): The bug isn't cell-resolver, isn't walk_interp, isn't dat-fidelity. It's BSP path-selection: our dispatcher picks Path 5 (Contact step_up) for the cellar ramp polygon when retail picks Path 6 (find_walkable land). The ramp is walkable (N.Z=0.695 > FloorZ=0.6642) so Path 6 is the correct choice. Investigation continues in next session at BSPQuery.FindCollisions path-selection logic. Also documents failed fix attempts this session as informational so next session doesn't re-attempt the same dead ends. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-22 13:26:26 +02:00
..
architecture	ship(O): Phase O — DatPath Unification — SHIPPED	2026-05-21 17:41:15 +02:00
audit	docs: update audit — Sprint 1 items verified (sequence counters + scenery LCG)	2026-04-13 13:51:39 +02:00
plans	ship(phys): A6.P3 slice 3 — cell-resolver ping-pong CLOSED + #98 re-diagnosed	2026-05-22 12:11:56 +02:00
research	capture(research): retail cellar-up trace for issue #98 — SHARP diagnosis	2026-05-22 13:25:57 +02:00
superpowers	plan(phys): A6.P3 slice 1 — indoor ContactPlane retention (Finding 2 fix)	2026-05-21 21:27:38 +02:00
bugs.md	docs: update bugs.md — close BUG-002/003/004, add BUG-005/006/007	2026-04-14 12:17:31 +02:00
ISSUES.md	docs(issues): #98 sharpened diagnosis — Path 5 vs Path 6 path-selection bug	2026-05-22 13:26:26 +02:00