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/skill-improve/SKILL.md

@@ -49,6 +49,10 @@ Static baseline:   [N] failures, [M] warnings
 Failing: Check 4 (no ask-before-write), Check 5 (no handoff)
 ```
 
+If the static result is **NOT ASSESSED** (the skill file could not be read or
+parsed), stop and report it with its reason: there is no score to improve, and
+0 FAILs from a file nobody could read is not a clean result.
+
 If baseline is 0 FAILs and 0 WARNs, note it and proceed to Phase 2b.
 
 ### Phase 2b: Category Baseline
@@ -69,7 +73,12 @@ Display to the user:
 Category baseline: [N] failures, [M] warnings  ([category] rubric)
 ```
 
-If BOTH static and category baselines are 0 FAILs and 0 WARNs, stop:
+A category result of **NOT ASSESSED** (a rubric section the skill-test could not
+find or apply) is reported with its reason and is not a zero: the category
+dimension is then excluded from "already passes" below.
+
+If BOTH static and category baselines are 0 FAILs and 0 WARNs — and neither is
+NOT ASSESSED — stop:
 "This skill already passes all static and category checks. No improvements needed."
 
 ---
@@ -90,8 +99,9 @@ For each failing or warning **static** check, identify the exact gap:
 
 For each failing or warning **category** check (if category was assigned in Phase 2b),
 identify the exact gap in the skill's text. For example:
-- If G2 fails (gate mode, full directors not spawned): skill body never references all 4
-  PHASE-GATE director prompts
+- If G2 fails (gate mode, director panel width): skill body does not size the
+  PHASE-GATE panel from `modes.workflow` (PR at `minimal`, TD + PR at `standard`,
+  all 4 at `full`)
 - If A2 fails (authoring, no per-section May-I-write): skill asks once at the end, not
   before each section write
 - If T3 fails (team, BLOCKED not surfaced): skill doesn't halt dependent work on blocked agent
@@ -114,25 +124,32 @@ If the user says no, stop here.
 
 ## Phase 5: Write and Retest
 
-Record the current content of the skill file (for revert if needed).
+Record the current content of the skill file — the exact text, kept in this
+conversation — so Phase 6 can restore it.
 
 Write the improved skill to `.claude/skills/[name]/SKILL.md`.
 
-Re-run `/skill-test static [name]` and record the new static score.
+Re-run `/skill-test static [name]` and record the new static score — measured by that run, never stated from the edit.
 If a category was assigned, also re-run `/skill-test category [name]` and record the new category score.
 
 Display the comparison:
 ```
 Static:   Before [N] failures, [M] warnings  →  After [N'] failures, [M'] warnings
 Category: Before [N] failures, [M] warnings  →  After [N'] failures, [M'] warnings  (if applicable)
-Combined change: improved / no change / worse
+Combined: [before] → [after] (improved / no change / worse)
 ```
 
+`[before]` and `[after]` are the Phase 6 combined counts — failures plus
+warnings, both dimensions — e.g. `Combined: 3 → 0 (improved)`.
+
 ---
 
 ## Phase 6: Verdict
 
 Count the combined failure total: static FAILs + category FAILs + static WARNs + category WARNs.
+**A re-test that comes back NOT ASSESSED** (for example, the edit broke the
+frontmatter so the file no longer parses) is never an improvement, whatever its
+counts: take the "did not improve" branch below.
 
 **If combined score improved (combined failure count is lower than baseline):**
 Report: "Score improved. Changes kept."
@@ -141,8 +158,10 @@ Show a summary of what was fixed in each dimension.
 **If combined score is the same or worse:**
 Report: "Combined score did not improve."
 Show what changed and why it may not have helped.
-Ask: "May I revert `.claude/skills/[name]/SKILL.md` using git checkout?"
-If yes: run `git checkout -- .claude/skills/[name]/SKILL.md`
+Ask: "May I restore `.claude/skills/[name]/SKILL.md` to the content it had before this run?"
+If yes: write the content recorded in Phase 5 back to the file with Write; if no, leave the file as written. Never
+`git checkout` it — that returns the last *committed* version and discards any edits
+made before this run that were not yet committed.
 
 ---