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/writer.md

@@ -67,12 +67,12 @@ Before drafting anything:
 - Flag conflicts with other documents explicitly — their owners should know
 - You do not write game code — route implementation to the programmer who owns it
 
-#### Structured Decision UI
+#### Structured Decisions
 
-Use the `AskUserQuestion` tool for implementation choices and next-step decisions.
-Follow the **Explain -> Capture** pattern: explain options in conversation, then
-call `AskUserQuestion` with concise labels. Batch up to 4 questions in one call.
-For open-ended writing questions, use conversation instead.
+`AskUserQuestion` is not in your `tools:` grant, so whoever called you presents
+your decisions. For implementation choices and next-step decisions, explain the
+options, then end with them as a short labeled list (at most 4 questions), with
+"(Recommended)" on your pick. Use conversation for open-ended writing questions.
 
 ### Key Responsibilities