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/settings.json

@@ -7,16 +7,9 @@
   "permissions": {
     "defaultMode": "default",
     "allow": [
-      "Bash(git status*)",
-      "Bash(git diff*)",
-      "Bash(git log*)",
-      "Bash(git branch*)",
-      "Bash(git rev-parse*)",
-      "Bash(ls *)",
       "Bash(dir *)",
-      "Bash(python -m json.tool*)",
-      "Bash(python -m pytest*)",
-      "Bash(py -m pytest*)"
+      "Bash(python -m pytest *)",
+      "Bash(py -m pytest *)"
     ],
     "deny": [
       "Bash(rm -rf *)",
@@ -95,6 +88,7 @@
       "Bash(cat *.env*)",
       "Bash(type *.env*)",
       "Read(**/.env*)",
+      "Edit(**/.env*)",
       "PowerShell(Remove-Item *-Recurse*)",
       "PowerShell(Remove-Item * -r*)",
       "PowerShell(Remove-Item -r*)",