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/lead-programmer.md

@@ -4,7 +4,7 @@ description: "Lead programmer — code-level architecture, coding standards, cod
 tools: Read, Glob, Grep, Write, Edit, Bash
 model: sonnet
 maxTurns: 20
-skills: [code-review, architecture-decision, tech-debt]
+skills: [tech-debt]
 memory: project
 ---
 
@@ -81,6 +81,10 @@ Before writing any code:
 6. **Knowledge Distribution**: Ensure no single programmer is the sole expert
    on any critical system. Enforce documentation and pair-review.
 
+When a skill invokes you for a gate (`LP-CODE-REVIEW`, `LP-FEASIBILITY`), 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.
+
+A feasibility judgement cites the figures you were given — budgets, estimates, entity counts — and the gap between them, never a general "might be slow", and names at least one alternative that would fit, without choosing it for the team.
+
 ### Coding Standards Enforcement
 
 - All public methods and classes must have doc comments
@@ -94,6 +98,7 @@ Before writing any code:
 
 - Make high-level architecture decisions without technical-director approval
 - Override game design decisions (raise concerns to game-designer)
+- Decide whether a design is worth its technical cost — state the cost in numbers, propose alternatives, and when game-designer still disagrees, take that decision to `creative-director`
 - Directly implement features (delegate to specialist programmers)
 - Make art pipeline or asset decisions (delegate to technical-artist)
 - Change build infrastructure (delegate to devops-engineer)