Their finding that screen render --black's premise is declared on the splash
builds is checkable across my whole export, and verify-screen passes --black to
all sixteen screens on that premise.
Audited by asking whether a screen declares a full-screen untextured primitive at
t=0 with fade_argb 0xff000000. Twelve do -- pteff00 on both titles, both menus and
both extras, palogo_eff0 on all four splashes, pgloading_eff00 on build_12/15.
Four do not: press_start, press_start_jp, build_00, build_01.
All four exceptions are composited rather than standalone. press_start is one
element, the plate, whose own name_why records it is composited over the title.
build_00/build_01 carry the pgloading_* set without the pgloading_eff00 backdrop
that build_12/15 declare.
Harmless where used: verify-screen gives --black to both renderers so the
assumption cancels in a consistency check, and verify-capture already scores the
plate over the title rather than on black. The exposure was real and the tooling
had already routed around it, which could only be established by looking.
The rule that falls out: a declared opaque-black backdrop distinguishes a
standalone screen from a composited one, derivable from the file rather than from
a name. Recorded as a rule with its evidence -- sufficient as observed, not proven
necessary, on four exceptions.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
c6735f55a6