fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

port: audit the --black premise -- declared on 12 screens, assumed on 4, all composited

Browse Source 
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
This commit is contained in:
Sylpheed port agent
2026-08-30 17:32:09 +00:00
parent ec37e8f9fc
commit c6735f55a6
2 changed files with 62 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
tools/port/verify-screen
View File

@@ -49,6 +49,27 @@
# * `--black` because Godot clears to black and the screen carries its own
# background. The CLI's default dim slate stands in for a 3D scene behind an
# in-mission screen, which is not this screen.
#
# ⚠️ THAT PREMISE IS DECLARED ON 12 OF 16 SCREENS AND ASSUMED ON 4. Audited
# 2026-08-30: a screen "carries its own background" when it declares a
# full-screen untextured primitive at `t=0` with `fade_argb 0xff000000` --
# opaque black. Twelve do (`pteff00`, `palogo_eff0`, `pgloading_eff00`).
# Four do NOT, and all four are COMPOSITED rather than standalone:
#
# press_start / press_start_jp -- one element, the plate, drawn OVER the
# title; its own `name_why` says so. The game never shows it on black.
# build_00 / build_01 -- loading variants carrying the `pgloading_*` set
# WITHOUT the `pgloading_eff00` backdrop that build_12/15 declare.
#
# ✅ Harmless HERE, because both renderers are given `--black` and the
# assumption cancels in a consistency check. It would NOT be harmless in an
# oracle comparison, and `verify-capture` already avoids it: the plate is
# scored as `--screen=title --overlay=press_start`, over the title, not on
# black.
#
# 📌 The audit is also a rule worth having: **a declared opaque-black
# backdrop distinguishes a standalone screen from a composited one**, and it
# is derivable from the file rather than from a name.
# * `--primitives --animated` because those are what make the CLI draw the same
# element set. `--focus` is NOT passed: nothing is focused at rest (HANDOFF
# Q5 measured initial focus as unstable boot to boot, so choosing one is