docs(render): plan status — R-A4 ruled out by measurement; remaining work is R-A2b (indoor-flood edge-on robustness)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erik 2026-06-09 08:10:06 +02:00
parent c7069cf0b6
commit 8c78f1f07a

View file

@ -338,7 +338,19 @@ Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>"
---
## Task R-A4 (OPTIONAL — only if residual flicker remains and correlates with eye jitter > retail's ~36 µm)
> **STATUS 2026-06-08 (late) — R-A4 RULED OUT by live measurement; remaining work is R-A2b (indoor-flood
> edge-on robustness).** Shipped + visual-confirmed: R-A1 `7fe9809`, R-A2 `c62663d` (outside flap GONE),
> seam fix `2ec189c` (missing textures GONE). The indoor crossing flicker is CONCLUSIVELY pinned to the
> **flood/clip being non-monotonic near a doorway's EDGE-ON angle** — NOT the camera: on a clean one-way
> pass the eye glided smoothly (3 X / 18 Y direction-changes over 25.7k frames) and is ~1µm stable at
> rest (more stable than retail's settled tens-of-µm), yet the visible-cell count oscillated 414× with
> 648 `clip=0` events. So R-A4 (camera/eye-jitter) is OFF. Next = **R-A2b**: make the "is the room behind
> this opening visible?" decision robust when the opening is near edge-on (its on-screen area hovers at
> zero — coin-on-edge). FIRST read retail `GetClip` (0x5a4320) / `ClipPortals` near-edge-on handling to
> see how retail keeps it stable, THEN design + conformance-test + visual-gate. Canonical pinned
> diagnosis: memory `project_indoor_flap_rootcause` (2026-06-08 late CORRECTION).
## Task R-A4 (OPTIONAL — SUPERSEDED: eye-jitter ruled out; see STATUS note above. Kept for history.)
**Intent:** Tighten the camera boom toward retail's exponential smoothing (D8) and reconsider — DO NOT blindly rip out — the render-position interpolation (D7). Gate: only do this if, after R-A1R-A3, the visual gate still shows flicker AND `[pv-input]` shows our eye jittering well beyond retail's ~36 µm.