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/authoring/create-architecture.md

@@ -8,7 +8,7 @@ a prerequisite is missing: the engine reference docs (no engine → `/setup-engi
 `design/gdd/systems-index.md` (absent at `standard`/`full` → `/map-systems`),
 and `design/gdd/game-concept.md` (absent → `/brainstorm`; at `minimal` the
 one-page `design/game-brief.md` stands in). It extracts a Technical Requirements
-Baseline (`TR-[gdd-slug]-[NNN]`) from the requirement-bearing sections of every
+Baseline (`TR-[system]-[NNN]`) from the requirement-bearing sections of every
 GDD, inventories existing ADRs from their headers, and shows an Engine Knowledge
 Gap Inventory with an `AskUserQuestion` before authoring.
 
@@ -94,7 +94,7 @@ skipped — Solo mode."
 9. Phase 8 writes a summary to `production/session-state/active.md` and prints the handoff with the headings "Architecture Complete", "Run These ADRs Next", "Gate-Check Readiness"; its **Then:** line names `/architecture-review`, then `/create-control-manifest` once the review passes, and the readiness block names `/gate-check pre-production`
 
 **Assertions:**
-- [ ] The baseline uses `TR-[gdd-slug]-[NNN]` IDs and is built from the scanned GDD sections, not whole-file reads
+- [ ] The baseline uses `TR-[system]-[NNN]` IDs and is built from the scanned GDD sections, not whole-file reads
 - [ ] The knowledge gap inventory and its three-option `AskUserQuestion` come before Phase 1
 - [ ] Each section is shown before its approval is asked
 - [ ] The master document is written only after the Phase 7 `AskUserQuestion` approval