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/docs/error-recovery-protocol.md

@@ -4,7 +4,7 @@ Shared procedure for any skill that spawns agents via the `Agent` tool. Referenc
 `## Error Recovery Protocol` section of each orchestration/review skill. Those
 skills keep the two load-bearing imperatives (surface immediately, produce a
 partial report) inline, and keep their own **Common blockers** list inline —
-those are skill-specific. This file holds the full four-step procedure.
+those are skill-specific. This file holds the full procedure.
 
 ## Trigger 0 — verify the artifact before reading the response
 
@@ -40,20 +40,25 @@ When the path is missing:
    over re-spawning — the context is usually still there, and a re-spawn pays
    for the whole investigation again.
 3. If the second attempt also produces nothing, treat it as BLOCKED and apply
-   steps 1–4 below.
+   steps 1–5 below.
 
 ---
 
 If any spawned agent returns BLOCKED, errors, or cannot complete:
 
 1. **Surface immediately** — report "[AgentName]: BLOCKED — [reason]" to the user
-   before continuing to dependent phases.
+   before continuing to dependent phases. The reason names what is missing and
+   where it was expected (the path or the input), so the user can supply it.
 2. **Assess dependencies** — check whether the blocked agent's output is required
    by subsequent phases. If yes, do not proceed past that dependency point without
    user input.
 3. **Offer options** via `AskUserQuestion`:
-   - Skip this agent and note the gap in the final report
+   - Skip this agent and note the gap in the final report — never fill the skipped agent's section with content of your own
    - Retry with narrower scope
    - Stop here and resolve the blocker first
 4. **Always produce a partial report** — output whatever was completed. Never
    discard work because one agent blocked.
+5. **A skip does not clear the block.** In a `/team-*` pipeline, choosing "skip
+   this agent and note the gap" lets the remaining phases run, but the skipped
+   agent's work is missing from what the pipeline delivers: the final verdict is
+   BLOCKED, naming the skipped agent and its gap — never COMPLETE.