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/templates/architecture-decision-record.md

@@ -6,11 +6,10 @@
 
 > **Who may move this to `Accepted`: the user, or `technical-director` on the
 > user's explicit confirmation. No other agent, and no skill on its own.**
-> Stated here because every consumer of this field enforces the *consequences*
-> of acceptance (stories referencing a `Proposed` ADR are set `Blocked`; epics
-> require `Accepted`), so something has to say who may produce it. `technical-director` is the role `coordination-rules.md`
-> already escalates technical conflicts to, and an ADR is exactly that decision
-> made durable.
+> Why this is stated here: stories referencing a `Proposed` ADR are set `Blocked`,
+> and epics require `Accepted`, so the field needs a named owner.
+> `technical-director` is the role `coordination-rules.md` already escalates
+> technical conflicts to, and an ADR is that decision made durable.
 >
 > This does **not** relax the existing rule that `Status: Accepted` is never set
 > without explicit user confirmation — it narrows *which agent* may set it once
@@ -59,10 +58,9 @@ chosen approach.]
 > `/architecture-decision`, `/story-readiness`, `/propagate-design-change` and
 > `gate-pre-production.md`; a missing row counts as critical. At `standard`,
 > `/create-stories` **stops** for a missing critical ADR and only **warns** for a
-> non-critical one, so this row decides whether a run halts. Earlier revisions of
-> this template recorded no layer at all, leaving those sites to infer one from
-> the referencing epic — which gives the wrong answer whenever a Foundation-layer
-> ADR is referenced by a Core-layer epic, the common case.
+> non-critical one, so this row decides whether a run halts. Do not infer the
+> layer from the referencing epic: a Foundation-layer ADR is commonly referenced
+> by a Core-layer epic, which would give the wrong answer.
 >
 > The vocabulary is the same `Foundation / Core / Feature / Presentation` that
 > epics and stories already carry — do not invent a fifth value, and do not