2d28226b30
The backlog's cheapest open question about the 60-byte entry: kind is a flags word (0x10 untextured primitive, 0x4 repeated instance, 0x3002 button record), so a focus bit would be the obvious answer and the name-pairing in mark_focused_states would be a convention standing in for a real field. It is not. Over every screen build on the disc: 54 name-paired focused/base pairs, all 54 with IDENTICAL kind (all 0x0), NO bit ever set on the focused entry and clear on its base, and the only words of the entry that ever differ are +48 and +52 - the pivot. The two entries differ in where the sprite sits and in nothing else. The test asserts all four numbers rather than just printing them, so the negative is pinned instead of decaying back into a suspicion. Also noted: these buttons carry kind = 0x0, so the documented 0x3002 "button record" belongs to the .rat records and not to the .t32 sprites a menu draws. Closes the declaration table, not the question - the focused state could still be marked in the .rat record, the RATC child stream, or only in the game's code. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE