d9ae42dd55
compose now sorts elements by the word at +0x08 of their sprite's T8aD header instead of painting in declaration order, for every build except the two whose measured order is hard-coded. That word is non-decreasing in the order the game actually paints both measured screens, so every screen nobody has captured now gets its layering from the file rather than from the declaration table, which is provably not the paint order. Verified with artifacts and both ways, not by a green build: the disc test asserts the measured orders never invert the key and that the composite's key sequence is sorted, and reading the word from +0x0c instead makes it fail; the title composites identically; and GP_MISSION_SELECT — uncaptured — now composites cleanly, committed as a capture. Two things recorded rather than smoothed over: ties keep declaration order because the game breaks them some other way that is not known, and the developer-logo splash has no .rat child, so is_build rejects it and the compositor never sees that bundle at all — its measured order is inert in practice and screen render cannot draw it.