Release 1.1.3 — long skills keep their later steps

Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko

.claude/skills/setup-engine/references/12-output-summary.md

@@ -0,0 +1,48 @@
+# /setup-engine — Section 12: Output Summary
+
+> Part of `/setup-engine`. `SKILL.md` names when to read this file; the settings it
+> resolved and the rules under its later headings still apply here.
+
+## 12. Output Summary
+
+After setup is complete, output:
+
+```
+Engine Setup Complete
+=====================
+Engine:          [name] [version]
+Language:        [GDScript | C# | GDScript + C# | C# | C++ + Blueprint | Blueprint + C++]
+Knowledge Risk:  [LOW/MEDIUM/HIGH]
+Reference Docs:  [created/skipped]
+CLAUDE.md:       [updated]
+Tech Prefs:      [created/updated]
+project.yaml:    [created/updated]
+Agent Config:    [verified]
+
+Next Steps:
+1. Review docs/engine-reference/<engine>/VERSION.md
+```
+
+Then print **one** Next-Steps list, matching the resolved `workflow` tier:
+
+**`minimal` — the lean 4-step floor (you are on step 1):**
+```
+2. Run /brainstorm to produce your one-page design/game-brief.md (the lean-tier design artifact)
+3. Run /create-stories to turn the brief's MVP list into stories
+4. Run /dev-story — first line of game code
+```
+(No `/map-systems`, `/design-system`, `/prototype`, or `/sprint-plan` at
+`minimal` — the brief replaces the GDDs and its build order is the plan.)
+
+**`standard` / `full` — the full pipeline:**
+```
+2. [If from /brainstorm] Run /map-systems to decompose your concept into individual systems
+3. [If from /brainstorm] Run /design-system to author per-system GDDs (guided, section-by-section)
+4. [If from /brainstorm] Run /prototype [core-mechanic] to validate the core idea before writing GDDs
+5. [If fresh start] Run /brainstorm to discover your game concept
+6. Create your first milestone: /sprint-plan new
+```
+
+---
+
+Verdict: **COMPLETE** — engine configured and reference docs populated.