875ac2632d
Deriving the child order from the bundle is what the port needs, so this collects data rather than guessing. Both multi-element screen objects live on the title: * a 7-element bundle paints 0 2 4 6 1 3 5 — evens then odds, a stable partition; * the 24-element title build paints 9 11 12 10 13 6 20 19 14 15 18 16 17 0 2 4 7 1 3 5 22 23 21 8. Two things the pair establishes. The list is GROUPED, not shuffled: elements sharing a sprite are contiguous (ptlogo1's three instances at slots 13-15, ptlogo2's at 17-19, the back2eff family at 8-12). And the five single-keyframe elements lead — exactly elements 9,10,11,12,13 have one keyframe, and the list opens with all five, which is a file-visible property. Refuted on this data: first-keyframe time and resting time (back2eff1 starts at 52 and rests at 56, yet paints after back2 at 66/80), declaration order and its reverse, and the RATC child order (ptbase2 is child 4 and paints first while ptlogo1 is child 0 and paints fourteenth). Not settled, and said so: the rule. The group CONTENTS are explained; the group ORDER is not, and two permutations are too few to build it.