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/coding-standards.md

@@ -69,8 +69,7 @@ falling back to the defaults above when it is absent.
 > **Exception — `/smoke-check`.** The ADVISORY default for **Config/Data** above
 > applies to *per-story evidence* gates. `/smoke-check` is a build-health gate,
 > not a per-story evidence gate, so its own unset default for
-> `testing.strict.config` is **BLOCKING**. This divergence is intentional and is
-> documented at both sites; do not reconcile one to the other.
+> `testing.strict.config` is **BLOCKING**. The two defaults differ on purpose.
 
 ## Automated Test Rules