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/consistency-check/SKILL.md

@@ -271,6 +271,12 @@ Verdict: PASS | CONFLICTS FOUND | NOT ASSESSED
 
 ## Phase 6: Registry Corrections
 
+**Re-read before you write.** Phase 1 read the registry before the scans, and
+another skill or session may have changed it since. Before each Edit, read the
+current `design/registry/entities.yaml`, find the entry in its section, and
+anchor the Edit on the entry's current text, never on what Phase 1 saw. Append
+a new entry after the last existing entry of its section.
+
 If stale registry entries were found, ask:
 > "May I update `design/registry/entities.yaml` to fix the [N] stale entries?"