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

CCGS Skill Testing Framework/skills/utility/setup-engine.md

@@ -246,6 +246,29 @@ None. `/setup-engine` is a technical configuration skill. No director gates appl
 
 ---
 
+### Case 8: A skipped question is not an answer
+
+**Fixture:**
+- Fresh project: no engine configured, no `project.yaml` engine block
+- The engine question comes back skipped: the user closes it, or a headless run
+  returns every question as skipped
+
+**Input:** `/setup-engine`
+
+**Expected behavior:**
+1. The skill does not choose an engine, language or version itself
+2. It asks again in plain text, saying what is waiting on the answer, and waits
+3. Nothing is written to `CLAUDE.md`, `project.yaml`, `technical-preferences.md`
+   or `VERSION.md` before the user answers
+4. In a run where nobody can answer, it stops and reports what is waiting
+
+**Assertions:**
+- [ ] No engine, language or version is picked on the user's behalf
+- [ ] The question is asked again in plain text
+- [ ] No file is written before an answer arrives
+
+---
+
 ## Protocol Compliance
 
 - [ ] Presents draft configuration before asking to write