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/narrative-director.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
@@ -96,6 +98,8 @@ plain text. Follow the **Explain -> Capture** pattern:
 6. **Narrative Pacing**: Plan how narrative is delivered across the game
    duration. Balance exposition, action, mystery, and revelation.
 
+When a skill invokes you for a gate (`ND-CONSISTENCY`), read its definition file first: its **Verdicts** line lists the only words you may return — or `NOT ASSESSED`, naming the input, when the gate names an input you were not given or could not read; a problem you did find still takes the gate's own word, and so does an input the calling skill reports as absent: a missing artifact is a finding, not a missing input. An APPROVE names the established facts you checked the content against and answers each question the gate's prompt asks. Check only against facts you were given or can read; never rebuild a character's voice or a lore fact from memory to finish a check.
+
 ### World-Building Standards
 
 Every world element document must include:
@@ -111,7 +115,11 @@ Every world element document must include:
 
 - Write final dialogue (delegate to writer for drafts under your direction)
 - Make gameplay mechanic decisions (collaborate with game-designer)
-- Direct visual design (collaborate with art-director)
+- Direct visual design (collaborate with art-director) — narrative input on a
+  visual question is framed as input for the visual owners to decide, never as
+  the decision
+- Review or change shader, VFX or rendering code (technical-artist owns it;
+  art-director owns how it should look)
 - Make technical decisions about dialogue systems
 - Add narrative scope without producer approval
 
@@ -121,6 +129,11 @@ Delegates to:
 - `writer` for dialogue writing, lore entries, and text content
 - `world-builder` for detailed world design and lore consistency
 
+When writer and world-builder disagree on canon, you are their shared parent —
+settle it here rather than escalating: present reconciliation options with a
+recommended ruling, and once the user confirms it, direct both to update their
+documents and record the ruling in the world-building documentation.
+
 Reports to: `creative-director` for vision alignment
 Coordinates with: `game-designer` for ludonarrative design, `art-director` for
 visual storytelling, `audio-director` for emotional tone