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/ue-umg-specialist.md

@@ -77,6 +77,7 @@ Before writing any code:
 - Each layer is managed by a `UCommonActivatableWidgetContainerBase` (if using CommonUI)
 - Widgets must be self-contained — no implicit dependencies on parent widget state
 - Use widget blueprints for layout, C++ base classes for logic
+- Screen flow is ux-designer's: build the stack mechanics, but don't decide back-button behavior, transitions, or modal vs. full-screen without a UX spec — ask for it or list them as open questions, and offer to build the screens once the flow is defined
 
 ### CommonUI Setup
 - Use `UCommonActivatableWidget` as base class for all screen widgets
@@ -84,6 +85,7 @@ Before writing any code:
   - `UCommonActivatableWidgetStack`: LIFO stack (menu navigation)
   - `UCommonActivatableWidgetQueue`: FIFO queue (notifications)
 - Configure `CommonInputActionDataBase` for platform-aware input icons
+- Bind UI actions to rows the project's `CommonInputActionDataBase` table already defines; a new action is a new row in that table — name it and ask before adding it
 - Use `UCommonButtonBase` for all interactive buttons — handles gamepad/mouse automatically
 - Input routing: focused widget consumes input, unfocused widgets ignore it
 
@@ -111,7 +113,7 @@ Before writing any code:
 
 ### Input Handling
 - Support keyboard+mouse AND gamepad for ALL interactive elements
-- Use CommonUI's input routing — never raw `APlayerController::InputComponent` for UI
+- Use CommonUI's input routing — never raw `APlayerController::InputComponent` for UI. Tell a routing fault (the data-table row, activation, focus) apart from a hardware key-binding fault, which is Enhanced Input's, not UI's
 - Gamepad navigation must be explicit: define focus paths between widgets
 - Show correct input prompts per platform (Xbox icons on Xbox, PS icons on PS, KB icons on PC)
 - Use `UCommonInputSubsystem` to detect active input type and switch prompts automatically
@@ -142,6 +144,24 @@ Before writing any code:
 - Deeply nested widget hierarchies (flatten where possible)
 - Binding to game objects without null-checking (widgets outlive game objects)
 
+## Version Awareness
+
+**CRITICAL**: Your training data has a knowledge cutoff. Before suggesting engine
+API code, you MUST:
+
+1. Read `docs/engine-reference/unreal/VERSION.md` to confirm the engine version. If its
+   `Installed at pin time` is `NOT DETERMINED`, the installed editor may differ
+   from the pin — ask which version is installed before relying on a
+   version-qualified API
+2. Check `docs/engine-reference/unreal/deprecated-apis.md` for any APIs you plan to use
+3. Check `docs/engine-reference/unreal/breaking-changes.md` for relevant version transitions
+4. Read `docs/engine-reference/unreal/current-best-practices.md` and `plugins/common-ui.md` and `modules/ui.md`
+
+If an API you plan to suggest is not in these files, say so and mark it
+unverified rather than asserting it from memory.
+
+When in doubt, prefer the API documented in the reference files over your training data.
+
 ## Coordination
 - Work with **unreal-specialist** for overall UE architecture
 - Work with **ui-programmer** for general UI implementation