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/adopt/references/3-classify.md

@@ -0,0 +1,29 @@
+# /adopt — Phase 3: Classify and Prioritise Gaps
+
+> Part of `/adopt`. `SKILL.md` names when to read this file; the settings it
+> resolved and the rules under its later headings still apply here.
+
+## Phase 3: Classify and Prioritise Gaps
+
+Organise every gap found across all audits into four severity tiers:
+
+**BLOCKING** — Will cause template skills to silently produce wrong results *right now*.
+Examples: ADR missing Status field, systems-index parenthetical status values,
+engine not configured when ADRs exist.
+
+**HIGH** — Will cause stories to be generated with missing safety checks, or
+infrastructure bootstrapping will fail.
+Examples: ADRs missing Engine Compatibility, GDDs missing Acceptance Criteria
+(stories can't be generated from them), tr-registry.yaml missing.
+
+**MEDIUM** — Degrades quality and pipeline tracking but does not break functionality.
+Examples: GDDs missing Tuning Knobs or Formulas sections, stories missing TR-IDs,
+sprint-status.yaml missing.
+
+**LOW** — Retroactive improvements that are nice-to-have but not urgent.
+Examples: Stories missing Manifest Version stamps, GDDs missing Open Questions section.
+
+Count totals per tier. If zero BLOCKING and zero HIGH gaps: report that the project
+is template-compatible and only advisory improvements remain.
+
+---