Generalised the "does the referent exist?" sweep that cracked S14. The value
classes resolve as three different kinds:
AIID 31 values 31 records 0 files 0 unresolved
FormationID 126 values 126 records 0 files 0 unresolved
CollisionMeshes 18 values 0 records 18 files 0 unresolved
EnumerateSubobjective 17 values 0 records 17 files 0 unresolved
NamePlate 52 values 27 records 24 files 1 (empty string)
BackGroundID 10 values 0 records 0 files 10 unresolved
FormationID 126/126 re-derives unit-group-table's own "every FormationID
resolves" from a different direction, as the control.
The 27 NamePlate values that stage-definition-table called "non-file plate ids"
are record names - ACROPOLIS x114, NP_ArrowHead x84, NP_ASFrigate x78 - and the
split 24 files + 27 records + 1 empty = 52 matches the two-vocabularies count
already recorded there. So the census residual shrinks: 313 resolve as files
plus 27 as records = 340 of 344, leaving the 4 never-shipped _Test tables as the
entire residual. The old reading was a KIND error, not a missing-file error.
BackGroundID is a genuinely unresolved third kind: the ten sky names, used 6-36
times each, are neither record names nor pak keys under 10 prefixes x 9 suffix
forms.
Recorded as powerless so it is not re-run: the image holds 0 exact strings for
all ten backgrounds, but also 0 for Formation_4_Bird, AI_Structure,
NP_ArrowHead, ACROPOLIS and CollisionSet_S03.bin, every one of which does
resolve in data. The executable names no data value at all, so the negative
discriminates nothing.
All fifteen artefacts byte-identical.
07aecb3d04