ee65631de8
`BACKLOG.md`'s "the declaration table is not a paint order on every screen" had been reasoned about but never measured. It is now measured, and the entry says so both ways. Confirmed: a framebuffer capture of Canary on the title screen shows the `PROJECT SYLPHEED` wordmarks over the full-screen background, so declaration order is not the paint order there. Refuted, and recorded rather than quietly dropped: * the `0x10`-adjacency first step this entry proposed. The background *is* next to a `kind = 0x10` `.prm` on both screens that have one — but on opposite sides (`GP_TITLE` puts the background after it, `GP_MISSION_SELECT` before), so no rule keyed on the `.prm` orders both. `GP_READY_ROOM` and `GP_OPTIONS` cannot serve as the third and fourth witnesses: neither carries a `.prm` or a full-screen background at all. * the placement-region group order and the RATC child order, as above. * reverse declaration order, by the same capture — it would draw the background over the copyright line, which is visible. And separated out: part of what the bad render showed was not ordering at all but the pivot/scale defect fixed two commits back. `ui-rat-layout.md` gains that rule, the correlation evidence, the unmeasured pivot-vs-centre gap, and the disc-wide demotion of "pivot is exactly half the texture" (49 % agree, 37 % are off by more than 16 px — `ptcopyright` is 694 px wide in the framebuffer and `pivot*2` says 618). Captures: `title-screen-oracle.png` (the game surface cropped out of the emulator window at (1,45), 1:1, bottom 45 rows clipped by the display) and `title-screen-composite-2026-08-18.png` beside it.