refactor: remove retired data format support

docs/DESIGN_SYSTEM.md

@@ -1700,10 +1700,9 @@ Exclusive child-record relationships use a searchable assignment block directly
 after the record identity. The header names the parent type, states the
 relationship and capacity in plain language, and shows current usage as `N / N`.
 The registry repeats the assigned parent beside each child so exclusivity can be
-audited without opening the editor. Legacy records may remain visibly
-`UNASSIGNED`, but creation, restoration, and successful edits require a valid
-active parent. Capacity rules are enforced on the server and never communicated
-by color alone.
+audited without opening the editor. Records that require an exclusive parent
+must always have a valid active assignment. Capacity rules are enforced on the
+server and never communicated by color alone.
 
 Rank cards present the complete rank description, structured effects, point
 cost, Credits, and material cost together. Specialized Alpha, Beta, and Gamma
@@ -1762,8 +1761,9 @@ user buys every available Rank 1 and Rank 2 in preceding rows and enforces the
 49-point limit. Cost telemetry lists Credits and components beside each rank.
 
 Saved loadouts store focus, node ranks, nine Skill Chips, effect modes, and
-combat assumptions. Version 1 loadouts keep their three legacy chips in an
-unassigned recovery list until the user places them under compatible abilities.
+combat assumptions. The builder accepts only the current complete structure.
+Invalid local drafts are discarded; invalid server records are unavailable and
+removed through a backed-up database migration.
 
 ### Calculation revision controls