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

CCGS Skill Testing Framework/agents/specialists/ui-programmer.md

@@ -2,8 +2,7 @@
 
 ## Agent Summary
 Domain: Menu screens, HUDs, inventory screens, dialogue boxes, UI framework code, and data binding.
-Does NOT own: UX flow design (ux-designer), visual style direction (art-director / technical-artist).
-Model tier: Sonnet (default).
+Does NOT own: UX flow and interaction design, including UI animation timing (ux-designer), visual style direction (art-director).
 No gate IDs assigned.
 
 ---
@@ -11,8 +10,8 @@ No gate IDs assigned.
 ## Static Assertions (Structural)
 
 - [ ] `description:` field is present and domain-specific (references menus / HUDs / UI framework / data binding)
-- [ ] `allowed-tools:` list includes Read, Write, Edit, Bash, Glob, Grep
-- [ ] Model tier is Sonnet (default for specialists)
+- [ ] `tools:` list includes Read, Write, Edit, Bash, Glob, Grep
+- [ ] Model tier is `inherit` — frontmatter `model:` reads exactly `inherit` (tiers: `.claude/docs/model-tiers.md`)
 - [ ] Agent definition does not claim authority over UX flow design or visual art direction
 
 ---
@@ -20,11 +19,11 @@ No gate IDs assigned.
 ## Test Cases
 
 ### Case 1: In-domain request — appropriate output
-**Input:** "Implement the inventory screen from the UX spec in `design/ux/inventory-flow.md`."
+**Input:** The UX spec at `design/ux/inventory-flow.md` defines five slot states: default, hover, selected, empty-slot, locked-slot. Request: "Implement the inventory screen from the UX spec in `design/ux/inventory-flow.md`."
 **Expected behavior:**
 - Reads the UX spec before producing any code
 - Produces implementation using the project's configured UI framework (UI Toolkit, UGUI, UMG, or Godot Control nodes)
-- Implements all states defined in the spec (default, hover, selected, empty-slot, locked-slot)
+- Implements every state the spec defines (default, hover, selected, empty-slot, locked-slot) — none dropped, none invented
 - Binds inventory data to UI elements via the project's data model, not hardcoded values
 - Includes doc comments on public UI API per coding standards
 
@@ -39,10 +38,10 @@ No gate IDs assigned.
 ### Case 3: Custom animation coordination
 **Input:** "The item selection in the inventory needs a custom bounce animation when selected."
 **Expected behavior:**
-- Recognizes that defining the animation curve and feel is within technical-artist territory
-- Does NOT invent animation parameters (timing, easing) without a spec
-- Coordinates with `technical-artist` for an animation spec (duration, easing curve, overshoot amount)
-- Once the spec is provided, produces the implementation binding the animation to the selection state
+- Recognizes that the bounce's feel (duration, easing curve, overshoot) is UI interaction and visual design, which it implements but does not design
+- Checks the UX spec it is implementing for those values first; does NOT invent them if they are absent
+- Asks the spec owner — `ux-designer` for interaction timing, `art-director` for visual style — for the missing values
+- Once the values are provided, binds the animation to the selection state, skippable and respecting the player's motion preference
 
 ### Case 4: Ambiguous UX spec — flags back
 **Input:** The UX spec states "show item details on selection" but does not define what happens when an empty slot is selected.
@@ -50,7 +49,7 @@ No gate IDs assigned.
 - Identifies the ambiguity in the spec (empty slot selection state is undefined)
 - Does NOT make an arbitrary implementation decision for the undefined state
 - Flags the ambiguity back to `ux-designer` with the specific question: "What should the detail panel show when an empty inventory slot is selected?"
-- May propose two common options (hide panel / show placeholder) to help ux-designer decide quickly
+- Any options it offers (e.g., hide the panel / show a placeholder) go to ux-designer as part of the question — none is implemented before the answer
 
 ### Case 5: Context pass — engine UI toolkit
 **Input:** Engine context provided: project uses Godot 4.6 with Control node UI. Request: "Implement a scrollable item list for the inventory."
@@ -66,14 +65,15 @@ No gate IDs assigned.
 
 - [ ] Stays within declared domain (menus, HUDs, UI framework, data binding)
 - [ ] Redirects UX flow design to ux-designer
-- [ ] Coordinates with technical-artist for animation specs before implementing animations
+- [ ] Takes animation timing and easing from ux-designer / art-director specs rather than inventing them, and makes every animation skippable and motion-preference aware
 - [ ] Flags ambiguous UX specs back to ux-designer rather than making arbitrary implementation decisions
 - [ ] Returns structured output (implementation code, data binding patterns, state machine for UI states)
 - [ ] Uses the correct engine UI toolkit for the project — never cross-engine code
+- [ ] Asks "May I write this to [filepath]?" naming the file before writing
 
 ---
 
 ## Coverage Notes
-- Inventory implementation (Case 1) should have a UI interaction test or manual walkthrough doc in `production/qa/evidence/`
+- Inventory implementation (Case 1) should have a retained screenshot of each screen touched in `production/qa/evidence/`
 - Animation coordination (Case 3) confirms the agent does not invent feel parameters without a spec
 - Ambiguous spec (Case 4) verifies the agent routes spec gaps back to the authoring agent rather than guessing