handoff: say which index space a build number is in -- 10/11 meant two different screens
The port challenged HANDOFF's loading-screen row and was right. The Q2 row said "0/1 and 10/11 are the LOADING screen"; the dated section above it says "entries 0, 1, 12, 15". Both are true, in different index spaces, and the page did not say which. Verified against the bytes rather than the table: screen list GP_TITLE.pak -> 12 builds, ordinals 0..11 screen list --all GP_TITLE.pak -> 16 builds, ordinals 0..15 Only under --all does the ordinal equal the pak entry. Without it ordinal 10 is entry 12 and ordinal 11 is entry 15. `screen info --all --build 10` shows palogo_sqex; --build 11 shows palogo_gamearts / seta / anima; 12 and 15 show pgloading_*. So in ENTRY space 10/11 are the publisher and developer splashes, which is exactly the screen the wrong reading would have renamed. It would have validated silently: the port's screen_names.json is keyed by entry. Q2 row corrected to entry space and marked; the trap is in METHOD under "Mechanics that have bitten", with the rule that a number leaving this repository says "entry N", never "build N". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
This commit is contained in:
@@ -89,6 +89,18 @@ agent's loop prompt, i.e. nowhere durable. See [`README.md`](README.md) for the
|
||||
* **Raw grep cannot see inside compressed pak entries.**
|
||||
* **Commit messages go in a file** (`git commit -F`); a literal `|` in a table
|
||||
cell needs escaping; `git log --all -- <path>` can hang.
|
||||
* **"Build 10" of a pak is ambiguous — always say which index space.**
|
||||
`sylpheed-cli screen list GP_TITLE.pak` reports **12** builds and numbers them
|
||||
0–11; `screen list --all` reports **16** and numbers them 0–15. Only under
|
||||
`--all` does the ordinal equal the pak entry. Without it, ordinal 10 is pak
|
||||
entry **12** and ordinal 11 is entry **15** — so "builds 10/11 are the loading
|
||||
screen" and "entries 12/15 are the loading screen" are the same true statement,
|
||||
while "**entries** 10/11 are the loading screen" is false: those are the
|
||||
publisher (`palogo_sqex`) and developer (`palogo_gamearts`/`seta`/`anima`)
|
||||
splashes. This cost a wrong line in HANDOFF that the port caught, and it would
|
||||
have validated silently because the port's `screen_names.json` is keyed by
|
||||
entry. **Write `entry N`, not `build N`, whenever the number leaves this
|
||||
repository.**
|
||||
|
||||
## Runtime / emulator
|
||||
|
||||
|
||||
Reference in New Issue
Block a user