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/engine/godot/godot-gdextension-specialist.md

@@ -3,7 +3,6 @@
 ## Agent Summary
 Domain: GDExtension API, godot-cpp C++ bindings, godot-rust bindings, native library integration, and native performance optimization.
 Does NOT own: GDScript code (gdscript-specialist), shader code (godot-shader-specialist).
-Model tier: Sonnet (default).
 No gate IDs assigned.
 
 ---
@@ -11,8 +10,8 @@ No gate IDs assigned.
 ## Static Assertions (Structural)
 
 - [ ] `description:` field is present and domain-specific (references GDExtension / godot-cpp / native bindings)
-- [ ] `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 `sonnet` — frontmatter `model:` reads exactly `sonnet` (tiers: `.claude/docs/model-tiers.md`)
 - [ ] Agent definition does not claim authority over GDScript or shader authoring
 
 ---
@@ -26,7 +25,7 @@ No gate IDs assigned.
   - Class inheriting from `godot::Object` or an appropriate Godot base class
   - `GDCLASS` macro registration
   - `_bind_methods()` implementation exposing the physics API to GDScript
-  - `GDExtension` entry point (`gdextension_init`) setup
+  - Module entry point: `initialize_module` in `register_types.cpp` registers the class with `ClassDB::register_class<T>()` at `MODULE_INITIALIZATION_LEVEL_SCENE`, reached from the exported init function named by the manifest's `entry_symbol`
 - Notes the `.gdextension` manifest file format required
 - Does NOT produce the GDScript usage code (that belongs to gdscript-specialist)
 
@@ -36,16 +35,16 @@ No gate IDs assigned.
 - Does NOT produce GDScript code
 - Explicitly states that GDScript authoring belongs to `godot-gdscript-specialist`
 - Redirects to `godot-gdscript-specialist`
-- May describe the API surface the GDScript should call (method names, parameter types) as a handoff spec
+- Any hand-off it offers is the extension's bound API surface (method names, parameter and return types) — not GDScript that calls it
 
 ### Case 3: ABI compatibility risk — minor version update
 **Input:** "We're upgrading from Godot 4.5 to 4.6. Will our existing GDExtension still work?"
 **Expected behavior:**
-- Flags the ABI compatibility concern: GDExtension binaries may not be ABI-compatible across minor versions
+- States the compatibility direction: an extension built for 4.5 should load in 4.6, but not the reverse — so it may keep working, yet it must be re-tested, and rebuilt against 4.6 to use newer APIs
 - Directs to check the 4.5→4.6 migration guide for GDExtension API changes
-- Recommends recompiling the extension against the 4.6 godot-cpp headers rather than assuming binary compatibility
+- Recommends rebuilding against the 4.6 godot-cpp headers rather than treating "should load" as tested
 - Notes that the `.gdextension` manifest may need a `compatibility_minimum` version update
-- Provides the recompilation checklist
+- Lays out the rebuild as a checklist: rebuild debug and release (`scons ... target=template_debug` / `template_release`, or `cargo build` / `cargo build --release`) for every target platform, update `compatibility_minimum`, then re-test in the 4.6 editor before shipping
 
 ### Case 4: Memory management — RAII for Godot objects
 **Input:** "How should we manage the lifecycle of Godot objects created inside C++ GDExtension code?"
@@ -55,14 +54,14 @@ No gate IDs assigned.
   - `memnew()` / `memdelete()` for non-reference-counted objects
   - Warning: do NOT use `new`/`delete` for Godot objects — undefined behavior
 - Notes object ownership rules: who is responsible for freeing a node added to the scene tree
-- Provides a concrete example managing a `CollisionShape3D` created in C++
+- Its concrete example (e.g., a `CollisionShape3D` created in C++) applies both rules: the node is created with `memnew()` and handed to the scene tree with `add_child()`, after which the tree frees it (no `memdelete()`); its shape resource is held in a `Ref<>`; `memdelete()` is only for a node that never enters the tree
 
 ### Case 5: Context pass — Godot 4.6 GDExtension API check
 **Input:** Engine version context: Godot 4.6 (upgrading from 4.5). Request: "Check if any GDExtension APIs changed from 4.5 to 4.6."
 **Expected behavior:**
 - References the 4.5→4.6 migration guide from the VERSION.md verified sources list
-- Reports on any documented GDExtension API changes in the 4.6 release
-- If no breaking changes are documented for GDExtension in 4.6, states that explicitly with the caveat to verify against the official changelog
+- Reads the 4.5 → 4.6 table in `docs/engine-reference/godot/breaking-changes.md` and states explicitly that it has no GDExtension-specific row, with the caveat to verify against the official changelog
+- Still surfaces the listed 4.6 changes that reach native code: `Quaternion` now initializes to identity (it was zero)
 - Flags the D3D12 default on Windows (4.6 change) as potentially relevant for GDExtension rendering code
 - Provides a checklist of what to verify after upgrading
 
@@ -74,9 +73,10 @@ No gate IDs assigned.
 - [ ] Redirects GDScript authoring to godot-gdscript-specialist
 - [ ] Redirects shader authoring to godot-shader-specialist
 - [ ] Returns structured output (binding patterns, RAII examples, ABI checklists)
-- [ ] Flags ABI compatibility risks on minor version upgrades — never assumes binary compatibility
+- [ ] States that compatibility runs forward only (older build → newer Godot) and requires a re-test after an upgrade — never treats "should load" as tested
 - [ ] Uses Godot-specific memory management (`memnew`/`memdelete`, `Ref<T>`) not raw C++ new/delete
 - [ ] Checks engine version reference for GDExtension API changes before confirming compatibility
+- [ ] Asks "May I write this to [filepath]?" naming the file before writing
 
 ---