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/skills/patch-notes/SKILL.md

@@ -20,11 +20,44 @@ If no version is provided, ask the user before proceeding.
 ## Phase 2: Gather Change Data
 
 - Read the internal changelog at `production/releases/[version]/changelog.md` if it exists
-- Run `git log` between the previous release tag and current tag/HEAD
+- Also check `docs/CHANGELOG.md` for the relevant version entry
+- Run `git log` between the previous release tag and current tag/HEAD as a fallback
 - Read sprint retrospectives in `production/sprints/` for context
 - Read any balance change documents in `design/balance/`
 - Read bug fix records from QA if available
 
+**If no changelog data is available** (neither `production/releases/[version]/changelog.md`
+nor a `docs/CHANGELOG.md` entry for this version exists, and git log is empty or unavailable):
+
+> "No changelog data found for [version]. Run `/changelog [version]` first to generate the
+> internal changelog, then re-run `/patch-notes [version]`."
+
+Verdict: **BLOCKED** — stop here without generating notes.
+
+---
+
+## Phase 2b: Detect Tone Guide and Template
+
+**Tone guide detection** — before drafting notes, check for writing style guidance:
+
+1. Check `.claude/docs/technical-preferences.md` for any "tone", "voice", or "style"
+   fields or sections.
+2. Check `docs/PATCH-NOTES-STYLE.md` if it exists.
+3. Check `design/community/tone-guide.md` if it exists.
+4. If any source contains tone/voice/style instructions, extract them and apply
+   them to the language and framing of the generated notes.
+5. If no tone guidance is found anywhere, default to:
+   player-friendly, non-technical language; enthusiastic but not hyperbolic;
+   focus on what the player experiences, not what the developer changed.
+
+**Template detection** — check whether a patch notes template exists:
+
+1. Glob for `docs/patch-notes-template.md` and `.claude/docs/templates/patch-notes-template.md`.
+2. If found at either location, read it and use it as the output structure for Phase 4
+   instead of the built-in style templates (Brief / Detailed / Full). Fill in the
+   template's sections with the categorized data.
+3. If not found, use the built-in style templates as defined in Phase 4.
+
 ---
 
 ## Phase 3: Categorize and Translate
@@ -137,9 +170,11 @@ Check the generated notes for:
 
 Present the completed patch notes to the user along with: a count of changes by category, and any internal changes that were excluded (for review).
 
-Ask: "May I write this to `production/releases/[version]/patch-notes.md`?"
+Ask: "May I write these patch notes to `docs/patch-notes/[version].md`?"
 
-If yes, write the file, creating the directory if needed.
+If yes, write the file to `docs/patch-notes/[version].md`, creating the directory
+if needed. Also write to `production/releases/[version]/patch-notes.md` as the
+internal archive copy.
 
 ---