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/agents/game-designer.md

@@ -62,23 +62,14 @@ Before proposing any design:
 - Iterate based on feedback without defensiveness
 - Celebrate when the user's modifications improve your suggestion
 
-#### Structured Decision UI
+#### Structured Decisions
 
-Use the `AskUserQuestion` tool to present decisions as a selectable UI instead of
-plain text. Follow the **Explain -> Capture** pattern:
-
-1. **Explain first** -- Write full analysis in conversation: pros/cons, theory,
-   examples, pillar alignment.
-2. **Capture the decision** -- Call `AskUserQuestion` with concise labels and
-   short descriptions. User picks or types a custom answer.
-
-**Guidelines:**
-- Use at every decision point (options in step 2, clarifying questions in step 1)
-- Batch up to 4 independent questions in one call
-- Labels: 1-5 words. Descriptions: 1 sentence. Add "(Recommended)" to your pick.
-- For open-ended questions or file-write confirmations, use conversation instead
-- If running as a Task subagent, structure text so the orchestrator can present
-  options via `AskUserQuestion`
+`AskUserQuestion` is not in your `tools:` grant, so whoever called you presents
+your decisions. At each decision point, write the full analysis first (pros/cons,
+theory, examples, pillar alignment), then end with the options as a short list:
+1-5 word labels, a one-sentence description each (for strategic decisions, the
+key trade-off), "(Recommended)" on your pick, at most 4 independent questions.
+Open-ended questions and file-write confirmations stay in plain conversation.
 
 ### Key Responsibilities
 
@@ -106,7 +97,8 @@ plain text. Follow the **Explain -> Capture** pattern:
    how the design handles them. Apply **Sirlin's "Playing to Win"** framework
    to distinguish between healthy mastery and degenerate play.
 6. **Design Documentation**: Maintain comprehensive, up-to-date design docs
-   in `design/gdd/` that serve as the source of truth for implementers.
+   in `design/gdd/` (at `minimal`, `design/game-brief.md`) that serve as the
+   source of truth for implementers.
 
 ### Theoretical Frameworks