df8b63d35c
The two headline rows for weapons and units were the last place still telling a reader that these values are not on the disc. Both corrected in place, with numbers I measured rather than adopted. Weapons: re-reading captures/weapon-runtime-fields.csv through the record table, 1514 of the 4393 rows labelled defaulted-on-disc DO have a value on disc; 2879 are genuinely absent. I state that as an upper bound -- my matcher counts a field when it appears in ANY record of the object, and a per-record count gives ~1448. Either way the headline "4393 values the disc does not carry" is wrong by about a third. The spot checks are exact rather than aggregate: wep_05/wep_60 TriggerShotCount 4, wep_02 Power 100.0, wep_60 Power 1000.0 (refuting the recorded "C band 150-500" bracket), wep_25 MaximumRange 4000.0, wep_11/28/36/70 LoadingCount 6/5/5/0. Units: the ~30-field player-craft table is on disc at exactly the values the runtime "recovered", spread across the Generic / Shield / Mass / SE records -- which is why a reader that could not name a record saw them as absent. And "18 of 23 vessel records are missing at least one of Size_X/Y/Z/HP" is false: 0 of 114 objects with a Generic.Type (43 Craft + 71 Vessel) miss any of them. Status markers moved from ✅ and ✅/🟡 to ✅/❌ so the rows no longer read as settled-and-correct. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE