221702ef6b
Building the Explorer's UI Screens browser turned up a limit on a claim the format doc states flatly. `ui-rat-layout.md` says the element declaration table is the screen's back-to-front draw list, verified 11/11 on the tutorial pause bundle -- and that reproduces exactly here. `GP_TITLE.pak` build 7 does not: painting in declaration order puts the full-screen background art (element 13) over the wordmarks (elements 0-5). Ruled out rather than guessed at: there is no depth key in the 60-byte entry. Across the title build's 30 entries every unknown word is constant, and `+36` -- the one that varies -- is an instance index on the `kind = 0x4` repeated entries, not a layer. Recorded as an open item with the cheapest next step (composite two more screens that have both a background and overlapping foreground, and check whether their background sits adjacent to a `kind = 0x10` PRMD entry as the title's does). The viewer paints in declaration order and does not paper over it, so a screen whose background lands on top is showing this bug rather than a decode failure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>