fix: persist enchantment design state across tab navigation

- EnchantmentDesigner now reads selection state directly from useCraftingStore
  instead of receiving it as props, so state survives tab unmount/remount
- EnchanterSubTab no longer uses local useState for selectedEquipmentType,
  selectedEffects, designName, selectedDesign — all sourced from store
- Removed unused EnchantmentDesignerProps interface from types
- All 1158 existing tests pass, no new type errors introduced

Fixes #366

docs/circular-deps.txt

@@ -1,10 +1,11 @@
 # Circular Dependencies
-Generated: 2026-06-11T07:08:59.875Z
-Found: 3 circular chain(s) — these MUST be fixed before modifying involved files.
+Generated: 2026-06-11T09:37:23.110Z
+Found: 4 circular chain(s) — these MUST be fixed before modifying involved files.
 
-1. 1) stores/golem-combat-actions.ts > stores/golem-combat-helpers.ts
-2. 2) stores/attunementStore.ts > stores/combatStore.ts > stores/combat-descent-actions.ts
-3. 3) stores/attunementStore.ts > stores/combatStore.ts > stores/combat-descent-actions.ts > stores/non-combat-room-actions.ts
+1. 1) data/guardian-encounters.ts > data/guardian-procedural.ts
+2. 2) stores/golem-combat-actions.ts > stores/golem-combat-helpers.ts
+3. 3) stores/attunementStore.ts > stores/combatStore.ts > stores/combat-descent-actions.ts
+4. 4) stores/attunementStore.ts > stores/combatStore.ts > stores/combat-descent-actions.ts > stores/non-combat-room-actions.ts
 
 ## How to fix
 1. Identify which import in the chain can be extracted to a shared types/utils file.