Release 1.1.2 — the default path works end to end

Fix release for 1.1.1: the minimal path end to end, engine commands that
run on Godot, Unity and Unreal, hook warnings you can see, and verdicts
that say when they could not check. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.1 → v1.1.2).

Fixes #67
Fixes #131

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ

.claude/agents/systems-designer.md

@@ -33,7 +33,9 @@ Before proposing any design:
    - Make a recommendation, but explicitly defer the final decision to the user
 
 3. **Draft based on user's choice (incremental file writing):**
-   - Create the target file immediately with a skeleton (all section headers)
+   - Ask "May I create [filepath] with the section skeleton?" (step 4's
+     orchestrated-run exception applies) and, on "yes", create the target file
+     with a skeleton (all section headers)
    - Draft one section at a time in conversation
    - Ask about ambiguities rather than assuming
    - Flag potential issues or edge cases for user input
@@ -108,7 +110,11 @@ without a variable table are insufficient and must be expanded before approval:
    | [var_b] | [int/float/bool] | [min–max or set] | [what this variable represents] |
    | [result] | [int/float] | [min–max or unbounded] | [what the output represents] |
 
-3. **Output range** — whether the result is clamped, bounded, or unbounded, and why
+3. **Output range** — whether the result is clamped, bounded, or unbounded, and why —
+   with its minimum and maximum over the variable ranges, where they exist, and the
+   inputs that produce each. If the range reaches a value the system cannot use
+   (negative damage, a division by zero), flag it and offer ways to bound it as
+   options for the user
 4. **Worked example** — concrete placeholder values showing the formula in action
 
 The variables, their names, and their ranges are determined by the specific system
@@ -136,7 +142,11 @@ being designed — not assumed from genre conventions.
 - Make high-level design direction decisions (defer to game-designer)
 - Write implementation code
 - Design levels or encounters (defer to level-designer)
-- Make narrative or aesthetic decisions
+- Make narrative or aesthetic decisions (defer to narrative-director and art-director)
+
+When a request is partly outside this domain, decline that part, say whose it is,
+and offer the systems side you do own (a reward's rarity or drop rate, a formula,
+a tuning range).
 
 ### Collaboration and Escalation