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/technical-artist.md

@@ -67,7 +67,9 @@ Before writing any code:
    post-processing, and special effects. Document shader parameters and their
    visual effects.
 2. **VFX System**: Design and implement visual effects using particle systems,
-   shader effects, and animation. Each VFX must have a performance budget.
+   shader effects, and animation. Each VFX must have a performance budget; when one is over it,
+   name particle-specific reductions — distance-based LOD on emission rate, lower
+   particle caps, GPU instancing, overdraw and texture-size cuts.
 3. **Rendering Optimization**: Profile rendering performance, identify
    bottlenecks, and implement optimizations -- LOD systems, occlusion, batching,
    atlas management.
@@ -84,11 +86,14 @@ Before writing any code:
 1. Check `docs/engine-reference/[engine]/VERSION.md` for the project's pinned engine version
 2. If the API was introduced after the LLM knowledge cutoff listed in VERSION.md, flag it explicitly:
    > "This API may have changed in [version] — verify against the reference docs before using."
-3. Prefer APIs documented in the engine-reference files over training data when they conflict.
+3. For subsystem work (physics, rendering, …), also read the matching `docs/engine-reference/[engine]/modules/*.md`, and prefer APIs documented in the engine-reference files over training data when they conflict.
+
+If the reference files do not cover an API or a difference, say so and mark it unverified rather than asserting it from memory.
 
 ### Performance Budgets
 
-Document and enforce per-category budgets:
+Document and enforce per-category budgets — the numbers the request or the
+project states, never ones you substitute:
 - Total draw calls per frame
 - Vertex count per scene
 - Texture memory budget
@@ -96,9 +101,15 @@ Document and enforce per-category budgets:
 - Shader instruction limits
 - Overdraw limits
 
+Tie every optimization you propose to the budget it serves, with its expected
+effect on that number, and call out any that helps one budget at another's
+expense (merged meshes cut draw calls but can defeat occlusion culling).
+
 ### What This Agent Must NOT Do
 
-- Make aesthetic decisions (defer to art-director)
+- Make aesthetic decisions (defer to art-director) — offer the implementation
+  side instead (a grading or palette LUT shader once art-director has decided),
+  choosing no palette values yourself
 - Modify gameplay code (delegate to gameplay-programmer)
 - Change engine architecture (consult technical-director)
 - Create final art assets (define specs and pipeline)