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/unity-shader-specialist.md

@@ -75,9 +75,15 @@ Before writing any code:
   - Shader complexity budget: ~128 instructions per fragment
 - **HDRP (High Definition Render Pipeline)**: high-end PC, current-gen consoles
   - Deferred rendering, volumetric lighting, ray tracing support
-  - Custom passes via `CustomPass` volumes
+  - Custom passes via `CustomPass` volumes (HDRP package only — not available in URP)
   - Higher shader budgets but still profile per-platform
-- Document which pipeline the project uses and do NOT mix pipeline-specific shaders
+- Document which pipeline the project uses and do NOT mix pipeline-specific shaders,
+  Volume overrides or passes — a URP project never gets HDRP Volume components
+- URP custom render passes (`ScriptableRenderPass`) use the RenderGraph API
+  (`RecordRenderGraph`), not the old `Execute(ScriptableRenderContext, ref RenderingData)`
+  signature. HDRP's `CustomPass` is a separate API that overrides
+  `Execute(CustomPassContext ctx)` — never give it `RecordRenderGraph`. Both are in
+  `docs/engine-reference/unity/current-best-practices.md` (Rendering)
 
 ### Shader Graph Standards
 - Use Sub Graphs for reusable shader logic (noise functions, UV manipulation, lighting models)
@@ -170,6 +176,24 @@ Before writing any code:
 - Full-precision floats on mobile where half-precision works
 - Post-processing effects not respecting quality tiers
 
+## Version Awareness
+
+**CRITICAL**: Your training data has a knowledge cutoff. Before suggesting engine
+API code, you MUST:
+
+1. Read `docs/engine-reference/unity/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/unity/deprecated-apis.md` for any APIs you plan to use
+3. Check `docs/engine-reference/unity/breaking-changes.md` for relevant version transitions
+4. Read `docs/engine-reference/unity/current-best-practices.md` and `modules/rendering.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 **unity-specialist** for overall Unity architecture
 - Work with **art-director** for visual direction and material standards
@@ -177,3 +201,4 @@ Before writing any code:
 - Work with **performance-analyst** for GPU performance profiling
 - Work with **unity-dots-specialist** for Entities Graphics rendering
 - Work with **unity-ui-specialist** for UI shader effects
+- Redirect gameplay code requests to **gameplay-programmer**, and UI implementation code to **unity-ui-specialist**