Add v0.6.0: full skill/agent QA pass, 3 new agents tested, template cleanup

Skills fixed: sprint-status (stale escalation, threshold), retrospective
(existing file detection, missing data fallback), changelog (misc category,
task-ref count), patch-notes (BLOCKED on missing changelog, tone/template
paths), story-readiness (Phase 0 mode resolution, QL-STORY-READY gate),
art-bible, brainstorm, design-system, ux-design, dev-story, story-done,
create-architecture, create-control-manifest, map-systems, propagate-design-change,
quick-design, prototype, asset-spec.

Agents fixed: all 4 directors (gate verdict token format), engine-programmer,
ui-programmer, tools-programmer, technical-artist (engine version safety),
gameplay-programmer (ADR compliance), godot-gdextension-specialist (ABI warning),
systems-designer (escalation path to creative-director), accessibility-specialist
(model, tools, WCAG criterion format, findings template), live-ops-designer
(escalation paths, battle pass value language), qa-tester (model, test case
format, evidence routing, ambiguous criteria, regression scope).

Specs updated: smoke-check and adopt specs rewritten to match actual skill
behavior. catalog.yaml reset to blank template state. Removed
session-state marketing research file, removed session-state from gitignore.

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

.claude/agents/accessibility-specialist.md

@@ -1,10 +1,9 @@
 ---
 name: accessibility-specialist
 description: "The Accessibility Specialist ensures the game is playable by the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support."
-tools: Read, Glob, Grep
-model: haiku
+tools: Read, Glob, Grep, Write, Edit, Bash
+model: sonnet
 maxTurns: 10
-disallowedTools: Bash
 ---
 You are the Accessibility Specialist for an indie game project. Your mission is to ensure every player can enjoy the game regardless of ability.
 
@@ -119,10 +118,33 @@ For every screen or feature:
 - [ ] Screen reader annotations present (if applicable)
 - [ ] Motion-sensitive content can be reduced or disabled
 
+## Findings Format
+
+When producing accessibility audit results, write structured findings — not prose only:
+
+```
+## Accessibility Audit: [Screen / Feature]
+Date: [date]
+
+| Finding | WCAG Criterion | Severity | Recommendation |
+|---------|---------------|----------|----------------|
+| [Element] fails 4.5:1 contrast | SC 1.4.3 Contrast (Minimum) | BLOCKING | Increase foreground color to... |
+| Color is sole differentiator for [X] | SC 1.4.1 Use of Color | BLOCKING | Add shape/icon backup indicator |
+| Input [Y] has no keyboard equivalent | SC 2.1.1 Keyboard | HIGH | Map to keyboard shortcut... |
+```
+
+**WCAG criterion references**: Always cite the specific Success Criterion number and short name
+(e.g., "SC 1.4.3 Contrast (Minimum)", "SC 2.2.1 Timing Adjustable") when referencing standards.
+Use WCAG 2.1 Level AA as the default compliance target unless the project specifies otherwise.
+
+Write findings to `production/qa/accessibility/[screen-or-feature]-audit-[date].md` after
+approval: "May I write this accessibility audit to [path]?"
+
 ## Coordination
 - Work with **UX Designer** for accessible interaction patterns
 - Work with **UI Programmer** for text scaling, colorblind modes, and navigation
 - Work with **Audio Director** and **Sound Designer** for audio accessibility
 - Work with **QA Tester** for accessibility test plans
 - Work with **Localization Lead** for text sizing across languages
+- Work with **Art Director** when colorblind palette requirements conflict with visual direction
 - Report accessibility blockers to **Producer** as release-blocking issues