69e6f6bcd8
Same technique as the weapon tables -- field names are literal, so a field-shape search over 190782 records finds the carriers. Generic (394 per pak, 110 field names, 178 distinct IDs) is the unit datasheet: HP, ShieldRatio, DefencePoint, AttackCraft/VesselPoint, the five Resistance* terms, Size_X/Y/Z + radius, RadarRange 10000, FCSRange 8500, MountedFCS, MountedShieldGenerator, Score/Damage/Mass, NozzleCount with per-nozzle FX, and Model rou_e006 -- which ties the sheet to the mesh names the corpus already decodes. Maneuver (114) is the AI flight model: MaximumVelocity 1200, CruisingVelocity 700, Acceleration 600, Deceleration 400, SideThrustAcceleration 1000, Turn_AngularVelocity 180, MaximumBank_Normal 60, per-axis DragFactor 3.0, afterburner and reverse-thrust factors, plus nine named manoeuvres each with its own timing/ratio/length bounds and AA_/AV_ rate pairs. This is the static source for what flight-speed-law.md measured at runtime. Corrects a guess in the same pass: HP_CLASS/HP_ID are not ship stats -- they sit on records named for wingmen and ship classes alongside HPGauge/RadarCursorType, i.e. a HUD gauge binding table. New structure doc + artefact; ISL artefacts byte-identical.