forked from Ports/goldeneye-pc-port
James Dansereau
d5fd08f40c
Gated GE_D288 to num_dls 550-755 (the reported bug window, same pattern GE_D236RM already uses) and raised the bbox threshold from 0.15 to 0.5. Volume dropped 116k -> 28,883, but that's still not the isolated signal -- traced the remaining noise to a bad assumption in the probe itself: bbox_frac from a raw x/w divide is meaningless once any_behind_camera=1 (w<0 or near-zero), which is exactly why the surrounding D233 code already defers to GL's own clipper for that case rather than trusting the divide. Restricting to any_behind_camera=0 (2,128 hits) still found no match for the target color (83,62,44); the persistent hits across the window look like static level geometry, not the transient bug triangle. Working theory: the bare -level_20 boot's scripted intro camera may not reach the same state the original visual bug report came from -- the same "deterministic boot flag != deterministic camera path" pattern this session's D236 passes independently hit on a different level. Recorded a revised next-step list in findings.md; a live human repro is now more promising than further headless probing of this specific approach. No src/game changes. findings-index.csv regen was a no-op.