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/dev-story/references/7-session-state.md

@@ -0,0 +1,40 @@
+# /dev-story — Phase 7: Update Session State
+
+> Part of `/dev-story`. `SKILL.md` names when to read this file; the settings it
+> resolved and the rules under its later headings still apply here.
+
+## Phase 7: Update Session State
+
+Silently update the checkpoint in `production/session-state/active.md` —
+**overwrite the `<!-- CHECKPOINT -->` … `<!-- /CHECKPOINT -->` block, never
+append** (schema: `.claude/docs/templates/session-state.md`). `session-start.sh`
+shows exactly that block when the next session opens, so it is what a cold
+resume starts from:
+
+```
+<!-- CHECKPOINT -->
+**Updated:** [date]
+**Branch:** `[current git branch]`
+**Current task:** /dev-story — [story-path] ([story title])
+**Next step:** /story-done [story-path] (at standard/full: /code-review [files] first)
+**Blocked on:** [nothing, or the blocker]
+**Files in progress:** [files changed, comma-separated; test file included]
+**Run result:** [the Phase 6 `Run result:` line, verbatim — `/story-done` reads it here]
+**Open questions:** [none, or one line each]
+<!-- /CHECKPOINT -->
+```
+
+**Next step** follows the Phase 6 result — the line above is the Implementation
+Complete one. On **INCOMPLETE** write
+`**Next step:** /dev-story [story-path] — resume: [the breakage Phase 6 named]`.
+On **BLOCKED** (Phase 2) write the unblocking action instead —
+`/architecture-decision accept ADR-NNNN`, the dependency story to finish, the
+manifest diff to review — and fill **Blocked on**. `/help` reads this line: a
+checkpoint that says `/story-done` tells it the work is written.
+
+If `active.md` does not exist, create it from the template. If it exists with no
+markers (a file from before the schema), insert the template's STATUS and
+CHECKPOINT blocks at the top and leave the rest untouched. Confirm: "Session
+state updated."
+
+---