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

port: my backdrop predicate is exact in GP_TITLE and its reading was wrong

Browse Source 
I offered 'a declared opaque-black backdrop distinguishes standalone from
composited' and asked for it to be tested against archives I do not have. It was.

The split reproduces exactly: derived independently from the disc, GP_TITLE gives
12 with and 4 without, the four being entries 0-3 -- my build_00, build_01,
press_start, press_start_jp -- with element names matching. Two genuinely
different paths, my export against their disc reader.

The reading does not survive. Disc-wide the predicate is rare, 76 of 965 builds at
7.9%, with GP_HANGAR_ARSENAL 0 of 390, GP_OPTIONS 0/14, GP_PAUSE_MENU 0/6. Read as
'composited' it makes 92% of the game composited, which the archives do not
support.

What survives is narrower: it separates screens that BEGIN FROM BLACK from
everything else, and their sharpening is the part I would not have reached -- the
negative class is heterogeneous, so a two-way rule cannot express it.

My caveat named the exact test that refuted the reading, but I still put the
refuted interpretation into verify-screen's header as a stated fact while the
hedge lived in DECISIONS.md. Corrected, with the 7.9% figure and an explicit do
not carry this into the four unexported archives. Hedging in the write-up does not
protect the claim shipped in the tool -- the same delivery gap as the
capture-phase term, repeated four iterations after fixing it once.

Within GP_TITLE the rule is exact and --black for those twelve is justified from
the file rather than assumed.

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:37:08 +00:00
parent c6735f55a6
commit d8488640a8
2 changed files with 62 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
tools/port/verify-screen
View File

@@ -67,9 +67,23 @@
# 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.
# 📌 The audit is a rule worth having WITHIN THIS ARCHIVE, and its first
# reading was wrong. I called it "standalone versus composited"; the Decoder
# ran it disc-wide and it does not carry: **76 of 965 builds, 7.9 %**, with
# `GP_HANGAR_ARSENAL` **0 of 390**, `GP_OPTIONS` 0/14, `GP_PAUSE_MENU` 0/6 --
# screens a player plainly sees AS screens. Read as "composited", the rule
# makes 92 % of the game composited, which the archives do not support.
#
# ✅ What survives is narrower: it separates **screens that begin from black**
# from everything else. The negative class is heterogeneous -- a pause menu
# over gameplay, a hangar over a 3D scene and a plate over a title are not the
# same kind of thing -- which is exactly what a two-way rule cannot express.
#
# ⚠️ Within `GP_TITLE` it is exact and independently reproduced from the disc
# (12/4, the four being entries 0-3). That is the only archive it is claimed
# for. Do NOT carry it into `GP_READY_ROOM`, `GP_HANGAR_ARSENAL`,
# `GP_MISSION_SELECT` or `GP_OPTIONS`: in three of them it classifies every
# screen alike, so it would look like a clean answer and say nothing.
# * `--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