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/setup-engine/references/8-verify.md

@@ -0,0 +1,61 @@
+# /setup-engine — Sections 8 and 8.5: Verify and Read Back
+
+> Part of `/setup-engine`. `SKILL.md` names when to read this file; the settings it
+> resolved and the rules under its later headings still apply here.
+
+## 8. Verify the CLAUDE.md Import
+
+**This import was already written in Section 4 — do not edit it again and do not
+ask again.** Section 4 sets it as part of the same CLAUDE.md write, anchored to
+the `ENGINE-REFERENCE-IMPORT` marker. This step only confirms the result.
+
+Read `CLAUDE.md` and confirm the line under the marker reads:
+
+```markdown
+@docs/engine-reference/<engine>/VERSION.md
+```
+
+with `<engine>` the engine just configured. If it still points at a different
+engine, Section 4 did not complete — go back and finish it rather than patching
+the line here.
+
+> **Why this is a check and not a second write.** Repeating the edit here with
+> its own approval prompt would ask the user twice for one change, and the second
+> ask would be for work already done. Locate the line by its marker, never by the
+> `## Engine Version Reference` heading — the marker exists precisely so the line
+> can still be found when the heading moves or is reworded.
+
+---
+
+## 8.5 Read Back What You Just Wrote
+
+This section exists because prose did not hold. Section 5.5.1's rendering/physics
+table already carries an emphatic, source-cited warning naming the two mistakes
+most often made here -- and it is still entirely possible to make **both** of
+them anyway, writing `Forward+` and `Jolt` for a 2D browser game. Section 3's
+`Installed at pin time` row is just as easy to drop silently, because a missing
+row leaves no trace.
+
+Neither is fixed by adding more instructions. They are fixed by verifying the
+files after writing them:
+
+```bash
+bash .claude/scripts/project-coherence.sh
+```
+
+It compares `project.yaml` against `docs/engine-reference/<engine>/VERSION.md`,
+against `project.godot`, and against the engine binary actually on PATH, and it
+checks that the files `commands.build` and `commands.test` name exist.
+
+**Report every `[DIFFERS]` line to the user and resolve it before finishing.**
+Each one means two files this skill just wrote disagree, or describe something
+that is not there.
+
+**`[NOT CHECKED]` is not a pass.** Each such line names why a comparison could
+not be made -- an absent binary, a missing `project.godot`. Say which ones
+applied. A comparison that could not run has not established agreement.
+
+The script emits observations and never a verdict, per the convention in
+CLAUDE.md. The judgement is yours and the user's.
+
+---