Erik 165f67add4 docs(spec): indoor walkable-plane BSP port — design ... Brainstormed spec for resolving the cellar-descent / 2nd-floor / invisible-obstacle indoor collision regressions reported post-Phase 2. Root cause: Phase 2 commit eb0f772 introduced TryFindIndoorWalkablePlane as a stop-gap walkable-plane synthesis when the indoor BSP returns OK. Its body does a linear first-match XY scan over cellPhysics.Resolved with no Z-proximity test, so multi-Z indoor geometry (cellars, 2nd floors, balconies) collapses to wrong-floor selection. Walking UP stairs works because step_up routes through DoStepDown → TransitionalInsert(5) → BSPQuery.FindCollisions Path 3 (StepSphereDown) which already uses FindWalkableInternal — the retail-faithful BSP walkable-finder. The linear scan only fires in the OK-no-wall branch. Fix: route TryFindIndoorWalkablePlane through the existing FindWalkableInternal via a thin new BSPQuery.FindWalkableSphere wrapper. Extends FindWalkableInternal's signature to expose the hit polyId (dictionary key, since ResolvedPolygon doesn't carry its own id). Threads the foot-sphere radius through TryFindIndoorWalkablePlane's signature (was hardcoded to nothing — used the localFootCenter alone). Deletes the now-dead PointInPolygonXY helper. Awaiting user spec review before plan. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-19 21:08:49 +02:00
..
plans	docs(plan): Indoor portal-based cell tracking implementation plan	2026-05-19 16:40:03 +02:00
specs	docs(spec): indoor walkable-plane BSP port — design	2026-05-19 21:08:49 +02:00