The Decoder refuted my refinement: palogo_gamearts_eff/palogo_seta_eff hold a=255
at identical x, y and scale from t=15 to t=30, so that is a genuine plateau,
rest_plateau() handles it, and t=15 is correct for that path. They are not among
their four.
The consequence strengthens the rule rather than retracting it: my rest pose for
them really is the flash's peak, reached by the SOUND path -- so 'a rest render is
not a frame to score against a capture' does not depend on the fallback being
unsound. A plateau can itself be the held peak of a transient, and their census
understates exposure rather than bounding it.
Censused my own tree. The first answer, 28 elements across 12 screens, was wrong:
it counted the screen's exit ramp as the end of visibility, so ptmsg -- the main
menu's own footer -- and ptbtn00, the plate, came back as transients. No control
would have caught that; the arithmetic was right. What caught it was saying what
the number meant physically.
Re-keyed on the screen's span: 31 elements across 8 of 16 screens, all of them
eff/loop sparkles or the two loading screens, with ptmsg and ptbtn00 falling out
on their own. Exposure is twice what the splash finding suggested. None of it
reaches shipped output.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
9b30fdb279