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/day-one-patch/SKILL.md

@@ -261,4 +261,5 @@ Use `AskUserQuestion`:
 - **Rollback plan first, always** — a patch without a rollback plan is irresponsible
 - **Deferred is not forgotten** — every deferred bug is listed in the record's
   "Deferred to 1.1" table; run `/bug-triage` afterwards to schedule them into the 1.1 sprint
+  (if the project has no sprint plan, as on the default minimal workflow, into the brief's build order)
 - **Player communication is part of the patch** — `/patch-notes` is a required output, not optional