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/docs/context-management.md

@@ -32,13 +32,11 @@ The checkpoint holds: current task, next step, what it is blocked on, files in
 progress, open questions. Write it so a cold reader can resume without opening
 anything else.
 
-> **Why the split.** One append-only file doing both jobs grows without bound —
-> past 700 lines every consumer invents its own slice: a status line parsing a
-> STATUS block nothing writes, `pre-compact` injecting `head -100` (12.7 KB, at
-> the moment context is scarcest), `session-start` previewing `tail -20` — the
-> opposite end. None was wrong, because nothing defined where
-> the recoverable state lived. Now every consumer reads the named region, and
-> the cost is fixed no matter how long the narrative grows.
+> **Why the split.** One append-only file doing both jobs grows without bound,
+> and every consumer then reads a different slice of it: the top, the bottom, or
+> a block nothing writes. None of them is wrong, because nothing defines where
+> the recoverable state lives. With a named region, every consumer reads the
+> same part, and the cost is fixed no matter how long the narrative grows.
 
 **Rotation.** When the narrative passes ~200 lines, move it into
 `production/session-logs/`:
@@ -125,7 +123,7 @@ Current helpers:
 - **`review-scope.sh`** — which GDDs changed since the last cross-review, plus
   their declared dependencies. Replaces reasoning through git history.
 
-Two rules when adding one:
+Two rules for helpers:
 
 1. **Grant it the way `.claude/docs/config-resolution.md` shows.** `allowed-tools`
    pre-approves commands; it does not restrict them — a skill without the grant