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/gate-check/references/gate-polish.md

@@ -9,8 +9,8 @@
 - [ ] The code root has active code organized into subsystems
 - [ ] All core mechanics from GDD are implemented (cross-reference `design/gdd/` with the code root)
 - [ ] Main gameplay path is playable end-to-end
-- [ ] Test files exist in `tests/unit/` and `tests/integration/` covering Logic and Integration stories
-- [ ] All Logic stories from this sprint have corresponding unit test files in `tests/unit/`
+- [ ] Test files exist under the engine's test root — `tests/unit/` and `tests/integration/` (Godot), `Assets/Tests/EditMode/` and `Assets/Tests/PlayMode/` (Unity), `Source/<Module>/Private/Tests/` (Unreal) — covering Logic and Integration stories
+- [ ] All Logic stories from this sprint have corresponding unit test files in the engine's unit-test location (`tests/unit/`, `Assets/Tests/EditMode/` or `Source/<Module>/Private/Tests/`)
 - [ ] Smoke check has been run with a PASS or PASS WITH WARNINGS verdict — report exists in `production/qa/`
 - [ ] At least one QA plan exists in `production/qa/` (generated by `/qa-plan`) covering this sprint, the final production sprint, or this production phase — run `/qa-plan` if missing (CONCERNS — advisory, not blocking)
 - [ ] QA sign-off report exists in `production/qa/` (generated by `/team-qa`) with verdict APPROVED or APPROVED WITH CONDITIONS
@@ -20,7 +20,7 @@
 
 **Quality Checks:**
 - [ ] Tests are passing (run test suite via Bash)
-- [ ] No critical/blocker bugs in any bug tracker or known issues
+- [ ] No open S1 Critical bugs in any bug tracker or known issues
 - [ ] Core loop plays as designed (compare to GDD acceptance criteria)
 - [ ] Performance is within budget (check `performance.*` in `project.yaml`, else technical-preferences.md targets)
 - [ ] Playtest findings have been reviewed and critical fun issues addressed (not just documented)
@@ -37,11 +37,11 @@ reduction for the resolved tier; items not named keep their status above.
 Reductions only ever *relax* a requirement — `workflow_overrides` is the
 only thing that adds one.
 
-- **`full`** — core mechanics + Logic/Integration tests + smoke check (PASS) + QA sign-off + 3+ playtests all required
+- **`full`** — core mechanics + Logic/Integration tests + smoke check (PASS or PASS WITH WARNINGS) + QA sign-off + 3+ playtests all required
 - **`standard`** — QA sign-off + per-story test coverage → recommended;
   **core mechanics + smoke check + playable end-to-end + 1+ documented
-  playtest + no critical/blocker bugs** required
-- **`minimal`** — **smoke check + playable end-to-end + no critical/blocker
+  playtest + no open S1 Critical bugs** required
+- **`minimal`** — **smoke check + playable end-to-end + no open S1 Critical
   bugs** required; the core-mechanics cross-check → recommended; everything
   else **drops**. Reductions relax what must *exist*, never what must *work* —
   a gate that closes production on "it boots" alone has not asked whether the

.claude/skills/gate-check/references/gate-pre-production.md

@@ -12,7 +12,7 @@
 - [ ] At least 3 Architecture Decision Records in `docs/architecture/` covering
       Foundation-layer systems (scene management, event architecture, save/load)
 - [ ] Engine reference docs exist in `docs/engine-reference/[engine]/`
-- [ ] Test framework initialized: `tests/unit/` and `tests/integration/` directories exist
+- [ ] Test framework initialized: the engine's test root exists — `tests/unit/` and `tests/integration/` (Godot), `Assets/Tests/EditMode/` and `Assets/Tests/PlayMode/` (Unity), or `Source/<Module>/Private/Tests/` (Unreal); see `.claude/docs/directory-structure.md`
 - [ ] CI/CD test workflow exists at `.github/workflows/tests.yml` (or equivalent)
 - [ ] At least one example test file exists to confirm the framework is functional
 - [ ] Master architecture document exists at `docs/architecture/architecture.md`

.claude/skills/gate-check/references/gate-production.md

@@ -8,7 +8,7 @@
 **Required Artifacts:**
 - [ ] Vertical slice exists in `prototypes/` with a REPORT.md (run `/vertical-slice`) — **recommended, not blocking**; if absent, surface as CONCERNS
 - [ ] First sprint plan exists in `production/sprints/`
-- [ ] Art bible is complete (all 9 sections) and AD-ART-BIBLE sign-off verdict is recorded in `design/art/art-bible.md`
+- [ ] Art bible is complete (all 9 sections) and AD-ART-BIBLE sign-off verdict is recorded in `design/art/art-bible.md` — where `review_mode` skips that gate (`lean`, `solo`), a `SKIPPED` sign-off line `/art-bible` records stands in for it, and a header still reading `[Not yet reviewed]` on such a project reads "sign-off skipped — [mode] mode", never missing
 - [ ] Entity inventory exists at `design/assets/entity-inventory.md` (recommended — run `/asset-spec` with no arguments to generate collaboratively from GDDs + art bible)
 - [ ] All MVP-tier GDDs from systems index are complete
 - [ ] Master architecture document exists at `docs/architecture/architecture.md`
@@ -51,6 +51,10 @@
 > **Verdict rules for Vertical Slice:**
 > - **Slice was built AND any validation item is NO** → verdict is automatically FAIL. A broken
 >   or unfun vertical slice should not advance to Production.
+> - **Slice was built but its report says NOT ASSESSED** (nobody has played it) → it is not a
+>   PROCEED, and its validation items were not checked (they are not NO): the Vertical Slice
+>   Validation block does not run, so the FAIL rule above does not apply. The gate item is NOT
+>   ASSESSED, never passed — and a "not yet" to "a human has played it" means the same.
 > - **Slice was not built (skipped)** → downgrade to CONCERNS only, not FAIL. Surface the risk
 >   clearly: "Advancing without a validated Vertical Slice increases the risk of late-stage design
 >   pivots. Recommended before committing full production scope." The user decides.
@@ -63,16 +67,20 @@ reduction for the resolved tier; items not named keep their status above.
 Reductions only ever *relax* a requirement — `workflow_overrides` is the
 only thing that adds one.
 
-- **`full`** — sprint plan + complete (9-section) art bible + epics + 3+ playtests + UX specs + control manifest all required; **Vertical Slice keeps its Section 2 status** (see note)
-- **`standard`** — **1+ playtest** required (not 3); epics + sprint plan required; art bible complete + UX specs + control manifest → recommended
-- **`minimal`** — only **sprint plan** required (the minimal floor); epics, playtests, art bible, UX, control manifest all **drop**
+- **`full`** — sprint plan + complete (9-section) art bible + epics + UX specs + control manifest all required; **Vertical Slice keeps its Section 2 status** (see note) — its playtest is recommended, 1 documented session with 3+ better
+- **`standard`** — epics + sprint plan required; art bible complete + UX specs + control manifest → recommended; **Vertical Slice keeps its Section 2 status**
+- **`minimal`** — the minimal floor only: a filled **`design/game-brief.md`** with its build order, and **stories** under `production/epics/` (`workflow-modes.md` — the brief's build order is the plan, so there is **no sprint plan**); everything else **drops** — sprint plan, epics, playtests, art bible, entity inventory, MVP GDDs, the master architecture document, both ADR items, control manifest, the UX items (key screen specs, HUD document, `/ux-review`), and the Vertical Slice items (the slice, its playtest, and the Vertical Slice Validation block) — the two current-build checks below replace them
+  **Quality checks at `minimal`:** every check that reads a dropped artifact drops with it — the sprint-plan, architecture, both ADR, GDD-coherence, UX and accessibility checks, and the Player Fantasy check (no GDD holds one). Two still apply, to the current build instead of a slice: **the core loop is fun** (ask the user, or read a playtest note if one exists) and **it runs end to end** — one complete start → challenge → resolution cycle. A "no" to either is FAIL, as a NO on a built slice is at the other tiers; a "not yet" to the fun question means nobody has played the build — NOT ASSESSED.
 
-> **The Vertical Slice keeps its Section 2 status at every tier.** The
+> **The Vertical Slice keeps its Section 2 status at `full` and `standard`.** The
 > Pre-Production → Production "prototype/Vertical Slice" floor is NOT upgraded to
 > blocking by the tier table — the Vertical Slice artifacts stay *recommended,
 > not blocking* (absent → CONCERNS, not FAIL) exactly as Section 2 defines, at
-> `full`, `standard`, and `minimal` alike. The genuinely-required floor item at
-> this gate is the **sprint plan**. The one hard rule that binds at every tier:
-> if a Vertical Slice *was built* and any of its validation items is NO, the
-> verdict is FAIL regardless of tier — tier reductions relax what must *exist*,
-> never what must *work*.
+> `full` and `standard` alike. At `minimal` they drop — the minimal route never
+> builds a slice — and the two current-build checks replace them. The
+> genuinely-required floor item at this gate is the **sprint plan** at `standard`
+> and `full`, and the **brief's build order plus stories** at `minimal`. The one
+> hard rule that binds at every tier: if a Vertical Slice *was built* and any of
+> its validation items is NO (at `minimal`, if the current build fails either of
+> its two checks), the verdict is FAIL regardless of tier — tier reductions relax
+> what must *exist*, never what must *work*.

.claude/skills/gate-check/references/gate-release.md

@@ -11,11 +11,11 @@
 - [ ] Localization strings are externalized (no hardcoded player-facing text in the code root)
 - [ ] QA test plan exists (`/qa-plan` output in `production/qa/`)
 - [ ] QA sign-off report exists (`/team-qa` output — APPROVED or APPROVED WITH CONDITIONS)
-- [ ] All Must Have story test evidence is present (Logic/Integration: test files pass; Visual/Feel/UI: sign-off docs in `production/qa/evidence/`)
+- [ ] All Must Have story test evidence is present (Logic/Integration: test files pass; UI: retained screenshots of each screen touched; Visual/Feel: retained screenshots plus lead sign-off — both in `production/qa/evidence/`, and no `qa.level` waives either)
 - [ ] Smoke check passes cleanly (PASS verdict) on the release candidate build
 - [ ] No test regressions from previous sprint (test suite passes fully)
 - [ ] Balance data has been reviewed (`/balance-check` run)
-- [ ] Release checklist completed (`/release-checklist` or `/launch-checklist` run)
+- [ ] Release checklist completed (`/release-checklist` run)
 - [ ] Store metadata prepared (if applicable)
 - [ ] Changelog / patch notes drafted
 
@@ -23,9 +23,10 @@
 - [ ] Full QA pass signed off by `qa-lead`
 - [ ] All tests passing
 - [ ] Performance targets met across all target platforms
-- [ ] No known critical, high, or medium-severity bugs
+- [ ] No known open S1 Critical, S2 High or S3 Medium bugs
+- [ ] No open CRITICAL or HIGH findings in the newest `production/security/security-audit-*.md` whose **Scope** is `full`, as updated by any later `quick` report (the re-run `/security-audit` prescribes after remediation). A later `network`, `save` or `input` report adds its open findings but never clears a category it did not scan — any open CRITICAL or HIGH finding means not ready (a blocker). No `full`-scope audit report means the check could not run: this item is NOT ASSESSED, never passed. A report whose release recommendation is itself NOT ASSESSED makes this item NOT ASSESSED too
 - [ ] Accessibility basics covered (remapping, text scaling if applicable)
-- [ ] Localization verified for all target languages
+- [ ] Localization verified for all target languages — every translated locale being shipped has a `/localize qa` verdict of PASS or PASS WITH CONDITIONS (`production/localization/loc-qa-[locale]-[date].md`). A FAIL blocks that locale; the others may still ship. A locale with no QA report, or whose QA reported NOT ASSESSED (nobody has played it), has not been verified: this item is NOT ASSESSED, never passed. The source locale (`en`, per `/localize`) is not a target language and needs no `/localize qa` report; a game that ships only its source locale marks this item N/A and says so
 - [ ] Legal requirements met (EULA, privacy policy, age ratings if applicable)
 - [ ] Build compiles and packages cleanly
 
@@ -36,6 +37,6 @@ reduction for the resolved tier; items not named keep their status above.
 Reductions only ever *relax* a requirement — `workflow_overrides` is the
 only thing that adds one.
 
-- **`full`** — all features + content complete + localization + QA sign-off + smoke (PASS) + no critical bugs all required
-- **`standard`** — content-complete audit + QA sign-off + localization → recommended; **all features + smoke + no critical bugs** required
-- **`minimal`** — only **smoke + no critical bugs** required; everything else **drops**
+- **`full`** — all features + content complete + localization + QA sign-off + smoke (PASS) + no open S1–S3 bugs all required
+- **`standard`** — content-complete audit + QA sign-off + localization → recommended; **all features + smoke + no open S1 Critical bugs** required; open S2 High and S3 Medium bugs → recommended
+- **`minimal`** — only **smoke + no open S1 Critical bugs** required; everything else **drops**

.claude/skills/gate-check/references/gate-technical-setup.md

@@ -12,7 +12,7 @@
 
 **Quality Checks:**
 - [ ] All MVP GDDs pass individual design review (8 required sections, no MAJOR REVISION NEEDED verdict)
-- [ ] `/review-all-gdds` verdict is not FAIL (cross-GDD consistency and design theory checks pass)
+- [ ] `/review-all-gdds` verdict is not FAIL (cross-GDD consistency and design theory checks pass). A NOT ASSESSED verdict does not satisfy this: that review could not compare the GDDs, so this item is NOT ASSESSED for the gate
 - [ ] All cross-GDD consistency issues flagged by `/review-all-gdds` are resolved or explicitly accepted
 - [ ] System dependencies are mapped in the systems index and are bidirectionally consistent
 - [ ] MVP priority tier is defined
@@ -33,4 +33,6 @@ only thing that adds one.
 > has no meaning at `minimal` (no GDDs exist by design). Return a PASS verdict
 > with the note: *"No design gate at minimal workflow — minimal skips the
 > Systems Design phase; advancing brief → code."* The Section 6 stage write still
-> applies on user confirmation. Do NOT flag absent GDDs as blockers.
+> applies on user confirmation. Do NOT flag absent GDDs as blockers. This is the
+> named exception to Section 2b's rule that a gate with no required artifacts left
+> may not PASS; the director panel does not run for it.