docs: reconcile spec inconsistencies across all documentation

- Fix incursion start day: 5→20 in GAME_BRIEFING.md (matches code constant)
- Fix fabricator discipline count: 2→5 in AGENTS.md
- Fix discipline counts: elemental.ts 22→21, advanced-regen.ts 14→15
- Fix equipment count: 50→43, remove shields, fix catalysts count
- Fix prestige upgrade count: add missing manaWell, manaFlow, pactBinding, pactInterferenceMitigation
- Remove x3 victory multiplier (no victory condition defined yet)
- Update pact persistence: pacts do NOT persist through prestige
- Update elemental matchup tables to match ultimate truth
- Update room type frequencies to match spire-climbing-spec
- Update guardian data tables to use formulas
- Update Tier 3 guardian elements to match guardian-data.ts code
- Add pactBinding + pactInterferenceMitigation to PRESTIGE_DEF constants
- Wire pactInterferenceMitigation into useGameDerived.ts
- Update spire-combat-spec.md Known Gaps table (DoT implemented, melee bypass bug)
- Update invoker-spec.md known issues (all resolved)
- Update golemancy-spec.md status (undergoing redesign)
- Update PrestigeTab test to expect 15 upgrades
- Create Gitea issues #285 (melee defense bypass), #286 (DoT verified), #287 (mana conversion gap)

docs/specs/attunements/fabricator/systems/golemancy-spec.md

@@ -4,9 +4,10 @@
 > configuration, summoning lifecycle, maintenance costs, room duration, combat
 > behavior, and discipline interactions.
 >
-> **⚠ Spec-defined, implementation pending.** This spec is based on
-> `docs/specs/spire-combat-spec.md` §9 and represents the intended design.
-> The current code has golem data defined but disconnected from the combat pipeline.
+> **⚠ Undergoing full redesign (see issue #268).** The golemancy system is being
+> redesigned from predefined golem types to a component-based construction system
+> (Core + Frame + Mind Circuit + Enchantments). The current data definitions exist
+> but are disconnected from the combat pipeline.
 
 ---
 

docs/specs/attunements/invoker/invoker-spec.md

@@ -190,10 +190,10 @@ The following inconsistencies exist in the codebase:
 
 | Issue | Description |
 |---|---|
-| `pactBinding` upgrade | Referenced in `prestigeStore.doPrestige` but **not defined** in `PRESTIGE_DEF` constants |
-| UI vs store mismatch | UI displays `prestigeUpgrades.pactCapacity` but store logic checks `pactBinding` |
-| Pact persistence | `signedPacts` is persisted but also reset to `[]` on `startNewLoop` — pacts don't survive loops in current implementation |
-| `pactInterferenceMitigation` | Used in `pact-utils.ts` but no prestige upgrade defines it |
+| `pactBinding` upgrade | ✅ **RESOLVED** — Added to `PRESTIGE_DEF` in `prestige.ts` |
+| UI vs store mismatch | ✅ **RESOLVED** — `pactBinding` is now the canonical ID used everywhere |
+| Pact persistence | ✅ **RESOLVED BY DESIGN** — Pacts intentionally do NOT persist through prestige (reset each loop). This is the correct behavior per design intent. |
+| `pactInterferenceMitigation` | ✅ **RESOLVED** — Added to `PRESTIGE_DEF` in `prestige.ts`; `useGameDerived.ts` now passes it from prestige store |
 
 ---