clean: remove obsolete repair debug code + unused core utilities

docs/technical/animation.md

@@ -37,9 +37,8 @@ Use `useClonedObject` when a GLTF scene is reused by a component instance. It me
 src/components/three/
 ├── gameplay/
 │   ├── RepairCaseModel.tsx
-│   ├── RepairCaseObject.tsx
-│   ├── RepairGameZone.tsx
-│   └── RepairModuleSlot.tsx
+│   ├── RepairGame.tsx
+│   └── RepairRepairingStep.tsx
 ├── interaction/
 │   ├── GrabbableObject.tsx
 │   ├── InteractableObject.tsx

docs/technical/architecture.md

@@ -62,7 +62,7 @@ Keep the player and map octree outside the Rapier provider until there is a deli
 - `src/components/three/models/` contains reusable model helpers such as `ExplodableModel`.
 - `src/components/three/interaction/` contains reusable interaction wrappers such as `InteractableObject`, `TriggerObject`, and `GrabbableObject`.
 - `src/components/three/handTracking/` contains R3F hand tracking debug models such as the glove overlays.
-- `src/components/three/gameplay/` contains the repair gameplay components: the reusable production `RepairGame` flow, the repair case, the debug repair game zone, and module slots.
+- `src/components/three/gameplay/` contains the reusable production `RepairGame` flow, repair case, repair steps, and repair prompt components.
 - `src/components/three/world/` contains reusable world/environment objects such as `SkyModel`.
 
 ## Editor System

docs/technical/zustand.md

@@ -181,4 +181,4 @@ Current overlays:
 
 ## Next Steps
 
-The next natural step is to move repair validation from this local scene interaction into richer mission data when each mission has distinct broken module nodes, replacement assets, and narrative completion beats.
+Move repair validation into mission data once each mission has distinct broken module nodes, replacement assets, and completion events.