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/create-stories/CONTRACT.md

@@ -16,6 +16,15 @@ and `/story-readiness` + `/dev-story`.
 | `docs/architecture/control-manifest.md` | Layer rules (required patterns, forbidden patterns, guardrails), `Manifest Version:` date in header | Yes |
 | `docs/architecture/tr-registry.yaml` | All TR-IDs for the epic's system, with stable `id` values | Yes |
 
+> **Tier.** The rows above are the `standard`/`full` inputs. At `workflow: minimal`
+> the only input is `design/game-brief.md`: the skill writes
+> `production/epics/<slug>/EPIC.md` itself from the brief (or uses one that already
+> exists there, never rewriting it), needs no `/create-epics`
+> run, and reads no GDD, ADR, control manifest or TR registry. Each story traces to
+> `Brief MVP feature N` instead of a TR-ID, and its ADR lines read
+> `N/A (minimal — no ADRs)` (SKILL.md, the `minimal` branch of Step 2 and the
+> `minimal` field mapping in Step 6).
+
 ### Preconditions
 - `/create-epics` has been run and the target `EPIC.md` has `Status: Ready`
 - The EPIC.md contains a populated `## GDD Requirements` table (not empty)
@@ -28,32 +37,33 @@ and `/story-readiness` + `/dev-story`.
 | File | Guaranteed Fields / Sections | Notes |
 |------|------------------------------|-------|
 | `production/epics/[epic-slug]/story-NNN-[slug].md` | `Epic:`, `Status:`, `Layer:`, `Type:`, `Manifest Version:`, `## Context` (GDD path + `TR-[system]-NNN` + ADR reference + ADR Decision Summary + Engine/Risk + Engine Notes + Control Manifest Rules), `## Acceptance Criteria`, `## Implementation Notes`, `## Out of Scope`, `## Test Evidence`, `## Dependencies` | Created per story |
-| `production/epics/[epic-slug]/EPIC.md` | `## Stories` table replacing the "Not yet created" placeholder | Updated in-place |
+| `production/epics/[epic-slug]/EPIC.md` | `## Stories` table replacing the "Not yet created" placeholder | Updated in-place; a return visit appends rows for new stories only. At `minimal`, when none exists yet, the skill creates it from the brief, after the write ask names it |
+| `production/epics/index.md` | The epic's `Stories` column set to `[N] stories` | Only when the index exists; otherwise the run prints `Epics index not updated: production/epics/index.md absent` |
 
 ### Output Guarantees
-- Every story file contains a `TR-[system]-NNN` reference in its `## Context` section (or `TR-[system]-???` with a warning if the registry has no match)
+- Every story file contains a `TR-[system]-NNN` reference in its `## Context` section (or `TR-[system]-???` with a warning if the registry has no match) — at `minimal`, `Brief MVP feature N` instead
 - Every story file contains an `ADR Governing Implementation:` line referencing at least one ADR, or an explicit `No ADR applies` note
-- Every story file has a `Status:` field — either `Ready` or `Blocked` (if the governing ADR is `Proposed`)
+- Every story file has a `Status:` field — either `Ready` or `Blocked` (if the governing ADR is `Proposed`, `Deprecated` or `Superseded`)
 - Every story file has a `Type:` field — one of: Logic, Integration, Visual/Feel, UI, Config/Data
-- Every story file has a `Manifest Version:` field matching the date from `docs/architecture/control-manifest.md`'s header at time of writing
+- Every story file has a `Manifest Version:` field matching the date from `docs/architecture/control-manifest.md`'s header at time of writing — at `minimal`, `N/A (minimal — no control manifest)`
 - Every story file has a `## Test Evidence` section stating the expected evidence location for its type
-- Every story file has a `## Acceptance Criteria` section with at least one checkbox item copied from the GDD
+- Every story file has a `## Acceptance Criteria` section with at least one checkbox item copied from the GDD — at `minimal`, derived from `design/game-brief.md` (its Player goal & fail state and the MVP feature the story implements)
 - Every story file has a `## Dependencies` section (may say "None" but is never omitted)
 - The EPIC.md `## Stories` table is updated with a row per story including `#`, `Story` title, `Type`, `Status`, and `ADR`
-- Stories with a `Proposed` ADR have `Status: Blocked` and a note: `BLOCKED: ADR-NNNN is Proposed — run /architecture-decision to advance it`
+- Stories with a `Proposed` ADR have `Status: Blocked` and a note: `BLOCKED: ADR-NNNN is Proposed — accept it with /architecture-decision accept ADR-NNNN once decided`; a `Deprecated` or `Superseded` ADR blocks the same way, naming its successor
 - Every story file has an `Engine` and a `Risk` field. `Risk` is taken from `docs/engine-reference/<engine>/VERSION.md`; when that file is missing or assigns no level, `Risk` is **`NOT ASSESSED (no VERSION.md risk rating)`** — never a guessed level
 - **`NOT ASSESSED` is an emittable value of the `Risk` field**, and downstream readers must handle it. `/dev-story` treats it as HIGH when deciding whether to spawn the engine specialist: an unknown risk is not a low one
 
 ## Immutability Rules
 - READS but does NOT modify: the epic's GDD, all ADR files, `docs/architecture/tr-registry.yaml`, `docs/architecture/control-manifest.md`
-- MODIFIES: `production/epics/[epic-slug]/story-NNN-[slug].md` (creates), `production/epics/[epic-slug]/EPIC.md` (updates Stories section only)
+- MODIFIES: `production/epics/[epic-slug]/story-NNN-[slug].md` (creates), `production/epics/[epic-slug]/EPIC.md` (updates Stories section only; created at `minimal` when none exists yet), `production/epics/index.md` (the epic's row, when the index exists) — all after one write ask that names them
 
 ## Hard Constraints (Never Violate)
 - Never start implementation — this skill stops at the story file level
-- Never invent acceptance criteria — all criteria must come from the GDD
+- Never invent acceptance criteria — all criteria must come from the GDD (from `design/game-brief.md` at `minimal`)
 - Never invent implementation notes — all guidance must come from the referenced ADR
 - Never write story files without presenting the full story list for approval first
-- Never mark a story `Status: Ready` if its governing ADR has `Status: Proposed`
+- Never mark a story `Status: Ready` if its governing ADR has `Status: Proposed`, `Deprecated` or `Superseded`
 - Never omit the `Manifest Version:` field — downstream readiness checks depend on it
 - Never reuse a story number (NNN) that already exists in the epic directory