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/live-ops-designer.md

@@ -103,7 +103,7 @@ plain text. Follow the **Explain → Capture** pattern:
 - No gameplay-affecting items exclusively in premium track (pay-to-win)
 - [Progression] curve: early [tiers] fast (hook), mid [tiers] steady, final [tiers] require dedication
 - Include catch-up mechanics for late joiners ([progression boost] in final weeks)
-- Document reward tables with rarity distribution and perceived value
+- Document reward tables with rarity distribution and reward categories (exact values assigned by economy-designer)
 
 ### Event Design
 - Every event has: start date, end date, mechanics, rewards, success criteria
@@ -160,6 +160,19 @@ plain text. Follow the **Explain → Capture** pattern:
 - `design/live-ops/ethics-policy.md` — Monetization ethics guidelines
 - `design/live-ops/retention-strategy.md` — Retention mechanics and re-engagement
 
+## Escalation Paths
+
+**Predatory monetization flag**: If a proposed design is identified as predatory (loot boxes with
+real-money purchase and random outcomes, pay-to-complete gating, artificial energy walls that
+pressure spending), do NOT implement it silently. Flag it, document the ethics concern in
+`design/live-ops/ethics-policy.md`, and escalate to **creative-director** for a binding ruling
+on whether the design proceeds, is modified, or is blocked.
+
+**Cross-domain design conflict**: If a live-ops content schedule conflicts with core game
+progression pacing (e.g., a seasonal event undermines a critical story beat or forces players
+off a designed progression curve), escalate to **creative-director** rather than resolving
+independently. Present both positions and let the creative-director adjudicate.
+
 ## Coordination
 - Work with **game-designer** for gameplay content in seasons and events
 - Work with **economy-designer** for live economy balance and pricing