Release 1.1.2 — the default path works end to end

Fix release for 1.1.1: the minimal path end to end, engine commands that
run on Godot, Unity and Unreal, hook warnings you can see, and verdicts
that say when they could not check. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.1 → v1.1.2).

Fixes #67
Fixes #131

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ

.claude/skills/team-live-ops/SKILL.md

@@ -7,7 +7,7 @@ allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Agent, AskUserQuestion, Task
 model: sonnet
 ---
 **Argument check:** If no season name or event description is provided, output:
-> "Usage: `/team-live-ops [season name or event description]` — Provide the name or description of the season or live event to plan."
+> "Usage: `/team-live-ops [season name or event description] [--review full|lean|solo]` — Provide the name or description of the season or live event to plan."
 Then stop immediately without spawning any subagents or reading any files.
 
 When this skill is invoked with a valid argument, orchestrate the live-ops team through a structured planning pipeline.
@@ -29,19 +29,19 @@ in `autonomous` mode it runs end to end, recording each phase outcome via
 Resolved above — use as-is; `--review` overrides `review_mode`. No block →
 defaults in `.claude/docs/config-resolution.md`.
 
-`review_mode` sets gate depth:
-- `full` — spawn all director and lead gates as described
-- `lean` — skip director gates unless they are PHASE-GATE type (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)
-- `solo` — skip all director gate spawning entirely; run the skill without any agent gates
+`review_mode` sets director-gate depth, and this pipeline has no director gate:
+no phase below spawns CD-, TD-, PR- or AD-PHASE-GATE, at any `review_mode`. Its
+phase gates are the pipeline's own decision points (defined under `team.size`
+below), and the agents that work at them are team members, not director gates.
 
 `automation` drives the Decision Points note above. See the Decision Points note above and
 `.claude/docs/automation-modes.md` for how each mode changes pipeline behavior.
 
 **`team.size`**: which agents are active (orthogonal to review_mode gate-depth and workflow docs).
 - **`individual`** (default): `live-ops-designer` + `economy-designer`. Other agents consulted via these two, not spawned separately.
-- **`small`**: + `analytics-engineer` + `community-manager` (the full pipeline as documented).
-- **`studio`**: + `writer` + `narrative-director` + per-season reviews.
-Directors (CD/TD/PR) still spawn at phase gates regardless of size; a non-core agent needed at `individual` routes through the nearest active core agent with an informational note. **"Phase gate" means any phase that ends in an `AskUserQuestion` decision point before the pipeline advances** — not every phase. Apply the test literally: if the phase below has no decision point, it is not a gate, and an agent restricted to "phase gates only" is not spawned for it. This active-set scoping applies throughout the pipeline below: any phase that names an agent outside the active set routes through the nearest core agent rather than spawning it.
+- **`small`**: + `analytics-engineer` + `community-manager`.
+- **`studio`**: + `writer` + `narrative-director` (the full pipeline as documented).
+A non-core agent needed at `individual` routes through the nearest active core agent with an informational note. **"Phase gate" means any phase that ends in an `AskUserQuestion` decision point this pipeline itself lists** — a transition under Decision Points above, or a **Gate** step written into the pipeline below — **whatever the `automation` mode.** `guided` and `autonomous` change how a gate is passed (it auto-advances, or is recorded with `log_decision`), not whether it is one, so bounded-exception condition (3) below holds at it in every mode. An agent restricted to "phase gates only" is spawned at those points and no others. This active-set scoping applies throughout the pipeline below: any phase that names an agent outside the active set routes through the nearest core agent rather than spawning it.
 
 **Announce the active set before Phase 1 — never let the collapse be silent.**
 Before spawning anything, state in one line which agents this run will actually
@@ -56,10 +56,10 @@ Fill it from the `team.size` list directly above and the agents this file's own
 pipeline names — not from an example. Both sets differ per orchestrator.
 
 The pipeline below reads as a multi-agent fan-out and at the shipped default it
-is one or two agents — `team-release` names eight and runs one, `team-narrative`
+is one or two agents — `team-release` names ten and runs one, `team-narrative`
 names six across five phases and runs `writer` alone. **The collapse is correct**:
-`team.size` is rigor-fronted and the narrow default is the token lever, measured
-at roughly 10x. What was wrong is that nothing said so, so a reader could not
+`team.size` is rigor-fronted and the narrow default is the token lever.
+Without saying so, a reader cannot
 distinguish a correctly-collapsed run from a broken pipeline, and the per-agent
 "routes through the nearest core agent with an informational note" rule above
 fires at routing time and never states the shape of the run as a whole.
@@ -70,7 +70,7 @@ enforced.**
 
 ## Team Composition
 - **live-ops-designer** — Season structure, event cadence, retention mechanics, battle pass
-- **economy-designer** — Live economy balance, store rotation, currency pricing, pity timers
+- **economy-designer** — Live economy balance, store rotation contents and prices (live-ops-designer sets its cadence), currency pricing, pity timers
 - **analytics-engineer** — Success metrics, A/B test design, event tracking, dashboard specs
 - **community-manager** — Player-facing announcements, event descriptions, seasonal messaging
 - **narrative-director** — Seasonal narrative theme, story arc, world event framing
@@ -90,6 +90,24 @@ Use the `Agent` tool to spawn each team member as a subagent:
 
 **End every agent prompt with a return contract:** "Write your full output to `[path]` — that named path is your write authorisation under the bounded exception below, so write it without a separate approval prompt. Return **only** (1) the path written, (2) a ≤5-bullet summary of decisions, (3) any BLOCKED/CONCERNS items, one line each. Do not restate the documents you read." Without it, an agent returns everything it read back into this session.
 
+**Substitute a real path for `[path]`.** Working artifacts go under
+`production/live-ops/[season-slug]/`, where `[season-slug]` is the argument as a
+slug — lowercase, spaces → hyphens. One file per agent, so the parallel phases
+never share one:
+
+| Phase / agent | Writes to |
+|---|---|
+| 1 live-ops-designer | `production/live-ops/[season-slug]/brief.md` |
+| 2 narrative-director | `production/live-ops/[season-slug]/narrative.md` |
+| 3 economy-designer | `production/live-ops/[season-slug]/economy.md` |
+| 4 analytics-engineer | `production/live-ops/[season-slug]/analytics.md` |
+| 5 narrative-director | `production/live-ops/[season-slug]/narrative-text.md` |
+| 5 writer | `production/live-ops/[season-slug]/copy.md` |
+| 6 community-manager | `production/live-ops/[season-slug]/comms.md` |
+
+These are working drafts; the final documents under `design/live-ops/seasons/`
+are compiled from them (Output Documents).
+
 > **Why this does not violate the Collaboration Protocol.** `CLAUDE.md` requires an agent to ask "May I write this to [filepath]?" before Write/Edit. A subagent spawned here writes **without** asking, and that is a deliberate, bounded exception rather than an oversight — the same call already made for `consistency-check` appending to `active.md`. The exception holds only when all three are true: (1) the path is one **you** named in the prompt, so the user approved the destination when they approved the phase; (2) it is a new artifact under `production/`, `docs/` or `tests/`, never an edit to existing source or config; (3) the phase that produced it is itself gated by an `AskUserQuestion` before the pipeline advances. Outside those three, the agent must ask. **Do not "fix" this by asking per subagent** — a prompt per agent per phase makes an orchestrator unusable, which is why the exception exists.
 
 Launch independent agents in parallel where the pipeline allows it (Phases 3 and 4 can run simultaneously).
@@ -112,11 +130,11 @@ Delegate to **narrative-director**:
 - Identify which existing lore threads this season can advance
 - Output: narrative framing document (theme, story hook, lore connections)
 
-### Phase 3: Economy Design (parallel with Phase 2 if theme is clear)
+### Phase 3: Economy Design (parallel with Phase 4)
 Delegate to **economy-designer**:
 - Read the season brief and existing economy rules from `design/live-ops/economy-rules.md`
 - Design the reward track: free tier progression, premium tier value proposition
-- Plan the in-season economy: seasonal currency, store rotation, pricing
+- Plan the in-season economy: seasonal currency, store rotation contents, pricing
 - Define pity timer mechanics and bad-luck protection for any random elements
 - Verify no pay-to-win items in premium track
 - Output: economy design doc with reward tables, pricing, and currency flow
@@ -130,7 +148,7 @@ Delegate to **analytics-engineer**:
 - Output: analytics plan with success criteria and instrumentation requirements
 
 ### Phase 5: Content Writing (parallel)
-Delegate in parallel:
+Start only after both Phase 3 and Phase 4 results are collected. Delegate in parallel:
 - **narrative-director** (if needed): Write any in-game narrative text (cutscene scripts, NPC dialogue, world event descriptions) for the season
 - **writer**: Write all player-facing text — event names, reward item descriptions, challenge objective text, seasonal flavor text
 - Both should read the narrative framing doc from Phase 2
@@ -191,19 +209,20 @@ usually still there.
 
 If any spawned agent returns BLOCKED, errors, or cannot complete: **surface it
 immediately, don't proceed past a dependency it blocks, and always produce a
-partial report.** Full procedure: `.claude/docs/error-recovery-protocol.md`.
+partial report.** A skipped agent's section stays a named gap — never fill it with content of your own. Full procedure: `.claude/docs/error-recovery-protocol.md`.
 
 If a BLOCKED state is unresolvable, end with Verdict: **BLOCKED** instead of COMPLETE.
 
 ## File Write Protocol
 
-All file writes (season design docs, analytics plans, communication calendars) are
-delegated to sub-agents spawned via `Agent`. Those writes follow the **bounded
-exception** documented above under "Why this does not violate the Collaboration
-Protocol" — the path is one you named, the artifact is new under `production/`,
-`docs/` or `tests/`, and the phase is gated by an `AskUserQuestion`. A sub-agent
-does **not** prompt per write inside those bounds; outside them it must ask.
-This orchestrator does not write files directly.
+Sub-agents write their working artifacts under `production/`, following the
+**bounded exception** documented above under "Why this does not violate the
+Collaboration Protocol" — the path is one you named, the artifact is new under
+`production/`, `docs/` or `tests/`, and the phase is gated by an `AskUserQuestion`.
+A sub-agent does **not** prompt per write inside those bounds; outside them it must
+ask. The **final documents under `design/live-ops/`** — season design, analytics
+plan, communication calendar — are the exception: the orchestrator compiles and
+writes them itself after its own "May I write …?" prompt (Output Documents above).
 
 ## Output
 
@@ -216,3 +235,6 @@ Verdict: **COMPLETE** — season plan produced and handed off for production.
 - Run `/design-review` on the season design document for consistency validation.
 - Run `/sprint-plan` to schedule content creation work for the season.
 - Run `/team-release` when the season content is ready to deploy.
+- If the run ended **BLOCKED** on an ethics flag: revise the economy design against
+  `design/live-ops/ethics-policy.md` and re-run `/team-live-ops`; the three steps
+  above wait for a COMPLETE plan.