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/release-checklist/SKILL.md

@@ -6,7 +6,7 @@ user-invocable: true
 allowed-tools: Read, Glob, Grep, Write, Bash(bash "*/.claude/skills/release-checklist/../../hooks/yaml-helper.sh" resolve_config *)
 model: sonnet
 ---
-!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys rigor,project.stage,cert_tier,automation`
+!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys rigor,workflow,project.stage,cert_tier,automation`
 
 **Automation mode**: Resolve `modes.automation` (`project.local.yaml` →
 `project.yaml` → default `collaborative`). Every `AskUserQuestion` call and
@@ -30,8 +30,9 @@ trains the reader to skip the list, which defeats the gate:
   **`NOT ASSESSED — cert tier unknown`**. **Unset is not `none`:** `none` is a
   decision, unset is a missing one, and they must not produce the same output.
   Branch on the **four values this key takes** — `none | itch | steam | console` —
-  and not on platform names; `.claude/docs/effects-map.md` holds the full
-  requirement table and is the source, so read it rather than restating it.
+  and not on platform names. The full requirement table is the `## platform.cert_tier`
+  section of `.claude/docs/effects-map.md` — read **only that section** (Grep its
+  heading, then a bounded Read); the file as a whole is not a runtime input.
   - `none` — **emit no certification section at all.** Internal release, alpha or
     jam game. Say the section was omitted and why; do not leave it blank.
   - `itch` — itch.io upload requirements only: build size, page setup, age tags.
@@ -78,6 +79,7 @@ certification track.
 
 - Read `CLAUDE.md` for project context, version information, and platform targets.
 - Read the current milestone from `production/milestones/` to understand what features and content should be included in this release.
+- Read the open bugs from `production/qa/bugs/`: grep the `**Severity**` and `**Status**` lines of `production/qa/bugs/*.md`, as `/bug-triage` does. A bug is open unless its Status is `Closed` or `Verified Fixed`. The bug items use the thresholds `/gate-check release` applies for the resolved `workflow`: at `full` an open S1, S2 or S3 bug fails its item; at `standard` and `minimal` only an open S1 does, and an open S2 or S3 is listed in the Rationale as a risk. Each failing bug is named in the Rationale as a blocking item. **No bug files in `production/qa/bugs/`** → the bug items read `NOT ASSESSED — no bug records` — never zero and never ticked, since an absent record and a clean one must not produce the same checklist; bugs are filed with `/bug-report`.
 
 ---
 
@@ -86,9 +88,12 @@ certification track.
 > **State the denominator with every count.** These scans look for something bad,
 > so `0` means either "searched and found none" or "there was nothing to search",
 > and on a release gate those are opposite findings. Report
-> `scanned [N] source files: [M] TODO, [M] FIXME, [M] HACK` — or, when `src/` is
-> absent or holds no source files,
-> **`NOT ASSESSED — no source files found to scan`**. A bare `0` is not a result.
+> `scanned [N] source files: [M] TODO, [M] FIXME, [M] HACK` — or, when the code
+> root (`src/`, `Assets/` or `Source/`; resolve per
+> `.claude/docs/code-root-resolution.md`) is unresolved,
+> **`NOT ASSESSED — code root unresolved`**, and when it is absent or holds no
+> source files, **`NOT ASSESSED — no source files found to scan`**. A bare `0` is
+> not a result.
 >
 > `/launch-checklist` scans the same way and is most often run beside this one.
 > Keep the two consistent: changing the rule in one and not the other leaves a
@@ -115,6 +120,7 @@ passing one must not produce the same release checklist.
 Generated: [Date]
 
 ### Codebase Health
+- Scanned: [N] source files (or `NOT ASSESSED — [reason]`, per Phase 3)
 - TODO count: [N] ([list top 5 if many])
 - FIXME count: [N] ([list all -- these are potential blockers])
 - HACK count: [N] ([list all -- these need review])
@@ -128,8 +134,9 @@ Generated: [Date]
 - [ ] Build is reproducible from tagged commit
 
 ### Quality Gates
-- [ ] Zero S1 (Critical) bugs
-- [ ] Zero S2 (Major) bugs -- or documented exceptions with producer approval
+- Open bugs (`production/qa/bugs/`): [N] S1, [N] S2, [N] S3 -- or `NOT ASSESSED — no bug records`
+- [ ] Zero open S1 (Critical) bugs
+- [ ] Zero open S2 (High) and S3 (Medium) bugs, no exceptions -- this row at `workflow: full` only; at `standard`/`minimal` open S2/S3 bugs go in the Rationale as risks
 - [ ] All critical path features tested and signed off by QA
 - [ ] Performance within budgets:
   - [ ] Target FPS met on minimum spec hardware
@@ -283,7 +290,12 @@ emitting every track; if it cannot be determined, emit
 - [ ] Support team briefed on known issues and FAQ
 - [ ] Rollback plan documented (if critical issues found post-launch)
 
-### Go / No-Go: [READY / NOT READY]
+### Go / No-Go: [READY / NOT ASSESSED / NOT READY]
+
+First match wins: **NOT READY** if any blocking item fails; else **NOT ASSESSED**
+if any section or item came out `NOT ASSESSED` (name each one); else **READY**. NOT
+ASSESSED outranks READY — an unassessed section is not a passed one — and ranks
+below NOT READY, so a known blocker is never buried behind it.
 
 **Rationale:**
 [Summary of readiness assessment. List any blocking items that must be
@@ -311,5 +323,6 @@ If yes, write the file, creating the directory if needed.
 
 ## Phase 6: Next Steps
 
-- Run `/gate-check` for a formal phase gate verdict before proceeding to release.
-- Coordinate final sign-offs via `/team-release`.
+- Draft the changelog or patch notes (`/changelog`, `/patch-notes`) if not done — the release gate checks them.
+- Run `/gate-check release` — the Polish → Release gate reads this checklist.
+- After a PASS: `/launch-checklist`, then coordinate the release via `/team-release`.