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/5-summary.md

@@ -0,0 +1,48 @@
+# /adopt — Phase 5: Present Summary and Ask to Write
+
+> 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 5: Present Summary and Ask to Write
+
+Present a compact summary before writing:
+
+```
+## Adoption Audit Summary
+Phase detected: [phase]
+Engine: [configured / NOT CONFIGURED]
+GDDs audited: [N] ([X] fully compliant, [Y] with gaps)
+ADRs audited: [N] ([X] fully compliant, [Y] with gaps)
+Stories audited: [N]
+
+Gap counts:
+  BLOCKING: [N] — template skills will malfunction without these fixes
+  HIGH:     [N] — unsafe to run /create-stories or /story-readiness
+  MEDIUM:   [N] — quality degradation
+  LOW:      [N] — optional improvements
+
+Estimated remediation: [X blocking items × ~Y min each = roughly Z hours]
+```
+
+Before asking to write, show a **Gap Preview**:
+- List every BLOCKING gap as a one-line bullet describing the actual problem
+  (e.g. `systems-index.md: 3 rows have parenthetical status values`,
+  `adr-0002.md: missing ## Status section`). No counts — show the actual items.
+- Show HIGH / MEDIUM / LOW as counts only (e.g. `HIGH: 4, MEDIUM: 2, LOW: 1`).
+
+This gives the user enough context to judge scope before committing to writing the file.
+
+If a prior adoption plan was detected in Phase 1, add a note:
+> "A previous plan exists at `docs/adoption-plan-[prior-date].md`. The new plan will
+> reflect current project state — it does not diff against the prior run."
+
+Use `AskUserQuestion`:
+- "Ready to write the migration plan?"
+  - "Yes — write `docs/adoption-plan-[date].md`"
+  - "Show me the full plan preview first (don't write yet)"
+  - "Cancel — I'll handle migration manually"
+
+If the user picks "Show me the full plan preview", output the complete plan as a
+fenced markdown block. Then ask again with the same three options.
+
+---