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/1-detect.md

@@ -0,0 +1,45 @@
+# /adopt — Phase 1: Detect Project State
+
+> 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 1: Detect Project State
+
+Emit one line before reading: `"Scanning project artifacts..."` — this confirms the
+skill is running during the silent read phase.
+
+Then read silently before presenting anything else.
+
+### Existence check
+- `project.stage` in `project.yaml` (fallback `production/stage.txt`) — if either is present, use that value (authoritative phase)
+- `design/gdd/game-concept.md` (or, at the minimal tier, `design/game-brief.md`) — concept exists?
+- `design/gdd/systems-index.md` — systems index exists?
+- Count GDD files: `design/gdd/*.md` (excluding game-concept.md and systems-index.md)
+- Count ADR files: `docs/architecture/adr-*.md`
+- Count story files: `production/epics/**/*.md` (excluding EPIC.md)
+- `project.yaml` (`engine.name`) / `.claude/docs/technical-preferences.md` — engine configured?
+- `docs/engine-reference/` — engine reference docs present?
+- Glob `docs/adoption-plan-*.md` — note the filename of the most recent prior plan if any exist
+
+### Infer phase (if no project.stage / stage.txt)
+Use the same heuristic as `/project-stage-detect`:
+- 10+ source files in the code root → Production
+- Stories in `production/epics/` → Pre-Production
+- ADRs exist → Technical Setup
+- systems-index.md exists → Systems Design
+- game-concept.md (or `design/game-brief.md`) exists → Concept
+- Nothing → Fresh (not a brownfield project — suggest `/start`)
+
+If the project appears fresh (no artifacts at all), use `AskUserQuestion`:
+- "This looks like a fresh project — no existing artifacts found. `/adopt` is for
+  projects with work to migrate. What would you like to do?"
+  - "Run `/start` — begin guided first-time onboarding"
+  - "My artifacts are in a non-standard location — help me find them"
+  - "Cancel"
+
+Then stop — do not proceed with the audit regardless of which option the user picks
+(each option leads to a different skill or manual investigation).
+
+Report: "Detected phase: [phase]. Found: [N] GDDs, [M] ADRs, [P] stories."
+
+---