f0dfff4fcd
Joining each stage's own EnumerateUnit table to its own EnumerateSquadron table is far sharper than the global partition: declared == deployed EXACTLY in 20 of 22 stages. S16 declares 4 it never deploys; S14 deploys 13 it never declares. Every per-stage deployed-but-undeclared count is 0 except S14's 13, and that 13 is the entire disc-wide total - so the exception is one stage, not a scattering. S16 explains what the table is. It declares 6 and deploys 2, and two of the six are UN_e901_ADAN_Boss and UN_e910_core_ADAN_GeneratorCore - exactly the units stage16-boss shows are brought in by their own loader chain (sub_82315AE8), not by the squadron roster. So EnumUnit_S<NN> is the stage's load manifest, not a mirror of the roster: a unit that code spawns is declared but never deployed. That also closes the 9 declared-but-never-deployed units by name: the S16 code-spawned pair above, Test_ADAN_PrometheusDriver_InsideP2_01, and six Ship_Test* placeholders. S14 remains the one unexplained cell, and it is not a missing table: EnumUnit_S14.tbl exists and declares six names, one of which is UN_mn040_Asteroid_Big. S14 therefore declares an asteroid but not the 13 Asteroid_cmesh entities it deploys, which refutes "asteroids are exempt from the manifest". Whatever the cause, it is specific to the collision-mesh entities. All fifteen artefacts byte-identical.