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/scripts/migrate-v1-config.sh

@@ -569,7 +569,7 @@ fi
   echo "schema_version: 1"
   echo ""
   echo "framework:"
-  echo "  version: 1.1.2"
+  echo "  version: 1.1.3"
   echo ""
   # Emit `project:` only when there is a stage to put in it -- same rule as the
   # `modes:` block below. Writing `stage: null` produced a file that FAILED THIS