Routine work on the sharpening lane needed a byte-identity control, so I
checked the baseline against itself first. Three of seven scenarios do not
reproduce run to run with ONE binary:
overlook-noon, water-lake, water-ocean, fence-shadowline-night identical
stormwind-canal-near bimodal: 7 of 15 pairs identical, rest 0.01% / max 96
inn-noon, volfog-inn usually the bottom bit; one pair 37.8% / max 199
`stormwind-canal-near` is the one that matters, because the water-mirror
write-up used it as a byte-identity control and it cannot be one. The identity
measured there was a coin flip that landed well.
The finding it supported still stands, but on its EXTENT and not on the
amplitude it was also quoted at. "0.75% of pixels by up to 96/255" reads as one
observation; it is two, and only the first is evidence. 96 is what the canal's
own flicker reaches with nothing changed at all — the amplitude says nothing.
0.75% against the scene's own 0.01% is 75x, which is the part that was real,
and the run condition is still the right fix.
docs/GRAPHICS.md's harness section now carries the table, so the next person
reaching for a control picks from the first row.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn