Checking the blast radius of the previous commit's `kind = 0x4` skip found 174 elements on the disc that are 0x4 with no non-0x4 element of the same sprite — GP_READY_ROOM pak entry 75 is 56 elements and every one is 0x4, a list of real icons a blanket skip would erase. So the rule is narrowed: skip an instance only when its template is present, which is the case the title capture covers. The title render is byte-identical before and after, so the narrowing changes nothing the evidence covers. And the claim that this "caught a regression" is WITHDRAWN, because measuring it refuted it: none of those 174 elements is in a bundle `is_build` accepts, so none of them ever reaches the compositor. The blanket skip would have been harmless in practice. The narrow rule is a precaution, not a fix, and the comment says so. The test that was going to assert the regression could not find such a build — correctly, since none is composable. It is replaced by one that pins the fact which makes the narrow rule safe: no composable build on the disc has a 0x4 element without its template, checked across 500+ builds. If that stops being true it fails, instead of a screen quietly going empty.