Release v0.4.0: UX pipeline, game-dev improvements

## New Skills (9)
- /quick-design: lightweight spec path for small changes (bypasses full GDD pipeline)
- /story-readiness: validates stories are implementation-ready before pickup
- /story-done: end-of-story completion review (criteria verification, deviation check, status update)
- /sprint-status: fast 30-line sprint snapshot, read-only
- /ux-design: guided section-by-section UX spec authoring (screen/flow/HUD/patterns)
- /ux-review: UX spec validation with APPROVED/NEEDS REVISION/MAJOR REVISION verdict
- /architecture-review, /create-architecture, /create-control-manifest,
  /create-epics-stories, /propagate-design-change, /review-all-gdds (pipeline completion)

## New Templates (7)
- player-journey.md: 6-phase emotional arc, critical moments, retention hooks
- difficulty-curve.md: difficulty axes, onboarding ramp, cross-system interactions
- ux-spec.md: per-screen UX spec with states, interaction map, data requirements, events
- hud-design.md: whole-game HUD with philosophy, info architecture, element specs
- accessibility-requirements.md: project-wide accessibility tier commitment and audit
- interaction-pattern-library.md: 26 standard + game-specific patterns with full state specs
- architecture-traceability.md: GDD requirements to ADR coverage matrix

## Updated Skills & Templates
- gate-check: Vertical Slice hard gate, playtesting strengthened, UX artifacts required
- team-ui: full UX pipeline integration (/ux-design + /ux-review + accessibility-specialist)
- game-design-document: Game Feel section (input latency, animation frames, impact moments)
- implementation-agent-protocol: /story-done as explicit final step of every story
- architecture-decision, design-system: pipeline completion updates

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/docs/templates/architecture-traceability.md

@@ -0,0 +1,101 @@
+# Architecture Traceability Index
+
+<!-- Living document — updated by /architecture-review after each review run.
+     Do not edit manually unless correcting an error. -->
+
+## Document Status
+
+- **Last Updated**: [YYYY-MM-DD]
+- **Engine**: [e.g. Godot 4.6]
+- **GDDs Indexed**: [N]
+- **ADRs Indexed**: [M]
+- **Last Review**: [link to docs/architecture/architecture-review-[date].md]
+
+## Coverage Summary
+
+| Status | Count | Percentage |
+|--------|-------|-----------|
+| ✅ Covered | [X] | [%] |
+| ⚠️ Partial | [Y] | [%] |
+| ❌ Gap | [Z] | [%] |
+| **Total** | **[N]** | |
+
+---
+
+## Traceability Matrix
+
+<!-- One row per technical requirement extracted from a GDD.
+     A "technical requirement" is any GDD statement that implies a specific
+     architectural decision: data structures, performance constraints, engine
+     capabilities needed, cross-system communication, state persistence. -->
+
+| Req ID | GDD | System | Requirement Summary | ADR(s) | Status | Notes |
+|--------|-----|--------|---------------------|--------|--------|-------|
+| TR-[gdd]-001 | [filename] | [system name] | [one-line summary] | [ADR-NNNN] | ✅ | |
+| TR-[gdd]-002 | [filename] | [system name] | [one-line summary] | — | ❌ GAP | Needs `/architecture-decision [title]` |
+
+---
+
+## Known Gaps
+
+Requirements with no ADR coverage, prioritised by layer (Foundation first):
+
+### Foundation Layer Gaps (BLOCKING — must resolve before coding)
+- [ ] TR-[id]: [requirement] — GDD: [file] — Suggested ADR: "[title]"
+
+### Core Layer Gaps (must resolve before relevant system is built)
+- [ ] TR-[id]: [requirement] — GDD: [file] — Suggested ADR: "[title]"
+
+### Feature Layer Gaps (should resolve before feature sprint)
+- [ ] TR-[id]: [requirement] — GDD: [file] — Suggested ADR: "[title]"
+
+### Presentation Layer Gaps (can defer to implementation)
+- [ ] TR-[id]: [requirement] — GDD: [file] — Suggested ADR: "[title]"
+
+---
+
+## Cross-ADR Conflicts
+
+<!-- Pairs of ADRs that make contradictory claims. Must be resolved. -->
+
+| Conflict ID | ADR A | ADR B | Type | Status |
+|-------------|-------|-------|------|--------|
+| CONFLICT-001 | ADR-NNNN | ADR-MMMM | Data ownership | 🔴 Unresolved |
+
+---
+
+## ADR → GDD Coverage (Reverse Index)
+
+<!-- For each ADR, which GDD requirements does it address? -->
+
+| ADR | Title | GDD Requirements Addressed | Engine Risk |
+|-----|-------|---------------------------|-------------|
+| ADR-0001 | [title] | TR-combat-001, TR-combat-002 | HIGH |
+
+---
+
+## Superseded Requirements
+
+<!-- Requirements that existed in a GDD when an ADR was written, but the GDD
+     has since changed. The ADR may need updating. -->
+
+| Req ID | GDD | Change | Affected ADR | Status |
+|--------|-----|--------|-------------|--------|
+| TR-[id] | [file] | [what changed] | ADR-NNNN | 🔴 ADR needs update |
+
+---
+
+## How to Use This Document
+
+**When writing a new ADR**: Add it to the "ADR → GDD Coverage" table and mark
+the requirements it satisfies as ✅ in the matrix.
+
+**When approving a GDD change**: Scan the matrix for requirements from that GDD
+and check whether the change invalidates any existing ADR. Add to "Superseded
+Requirements" if so.
+
+**When running `/architecture-review`**: The skill will update this document
+automatically with the current state.
+
+**Gate check**: The Pre-Production gate requires this document to exist and to
+have zero Foundation Layer Gaps.