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

@@ -7,7 +7,7 @@ allowed-tools: Read, Glob, Grep, Write, Bash, AskUserQuestion, Bash(bash "*/.cla
 model: sonnet
 ---
 
-!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation`
+!`bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level`
 
 
 
@@ -66,7 +66,7 @@ If a matching file is found, use `AskUserQuestion`:
   - `[B] Start fresh — generate a new retrospective (archive the old one)`
 
 If [A]: read the existing file and carry its content forward, revising sections with new data.
-If [B]: continue to Phase 2 with a blank slate. Before writing the new file, rename the existing one with a `-archived-[date]` suffix.
+If [B]: continue to Phase 2 with a blank slate. Before writing the new file, rename the existing one with a `-archived-[date]` suffix. That rename is a write too: it happens in Phase 5, only once the ask there — which names it — is approved.
 
 ---
 
@@ -81,17 +81,28 @@ Read the sprint or milestone plan from the appropriate location:
 
 **If the file does not exist or is empty**, output:
 
-> "No sprint data found for [sprint/milestone]. Run `/sprint-status` to generate
-> sprint data first, or provide the sprint details manually."
+> "No sprint data found for [sprint/milestone]. Run `/sprint-plan new` to create a
+> sprint (`/sprint-status` only reads one), or provide the sprint details manually."
 
-Then use `AskUserQuestion` to present two options:
+At `workflow: minimal` (resolved above) there are no sprints: offer to look back over the stories
+closed so far instead (`production/epics/*/story-*.md` with `Status: Complete`).
+At `qa.level: minimal` (resolved above) tests are waived, so a story closed
+without one is not a finding; a Visual/Feel or UI story closed without its
+retained screenshot still is.
+
+Then use `AskUserQuestion` to present these options ([C] only at `workflow: minimal`):
 
 - **[A] Provide data manually** — ask the user to paste or describe the sprint
   tasks, dates, and outcomes; use that as the source of truth for the retrospective.
 - **[B] Stop** — abort the skill. Verdict: **BLOCKED** — no sprint data available.
+- **[C] Look back over the closed stories** — use the stories with
+  `Status: Complete` as the record of what was done.
 
 If the user chooses [A], collect the data and continue to Phase 3 using what they provide.
 If the user chooses [B], stop here.
+If the user chooses [C], read those stories and continue to Phase 3. Sections that
+need sprint data (planned vs actual, velocity, carryover, estimation accuracy)
+are `NOT ASSESSED — NO DATA`.
 
 Extract: planned tasks, estimated effort, owners, and goals.
 
@@ -115,6 +126,10 @@ Scan for completed and incomplete tasks by comparing the plan against actual del
 - Tasks added mid-sprint (unplanned work)
 - Tasks removed or descoped
 
+Every story with `status: blocked` in `production/sprint-status.yaml` goes under
+Blockers Encountered, with its `blocker` field as the Blocker, and gets an action
+item in Action Items for Next Iteration.
+
 Scan the codebase for TODO/FIXME trends:
 
 - Count current TODO/FIXME/HACK comments
@@ -127,6 +142,10 @@ Read previous retrospectives (if any) from `production/retrospectives/` to check
 - Are the same problems recurring?
 - How has velocity trended?
 
+With no earlier sprint or retrospective, Velocity Trend keeps only the current
+sprint's row and reads `NOT ASSESSED — NO DATA`, and Previous Action Items
+Follow-Up is that one line — no invented earlier rows, no empty table.
+
 ---
 
 ## Phase 4: Generate the Retrospective
@@ -156,7 +175,7 @@ Generated: [Date]
 | [N-1] | [X] | [Y] | [Z%] |
 | [N] (current) | [X] | [Y] | [Z%] |
 
-**Trend**: [Increasing / Stable / Decreasing]
+**Trend**: [Increasing / Stable / Decreasing — or `NOT ASSESSED — NO DATA` with no earlier sprint to compare]
 [One sentence explaining the trend]
 
 ### What Went Well
@@ -231,6 +250,10 @@ Present the retrospective and top findings to the user (completion rate, velocit
 
 Ask: "May I write this to `production/retrospectives/retro-sprint-[N]-[date].md`?" (or `production/retrospectives/retro-[milestone-name]-[date].md` for milestone retrospectives)
 
+After Start fresh in Phase 1b, the same ask also names the rename: "…and rename
+`[old file]` to `[old file name]-archived-[date].md`?" On yes, rename first, then
+write; on no, neither happens.
+
 If yes, write the file, creating the `production/retrospectives/` directory if needed. Verdict: **COMPLETE** — retrospective saved.
 
 If no, stop here. Verdict: **BLOCKED** — user declined write.