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/skills/estimate/SKILL.md

@@ -24,7 +24,10 @@ Identify files and modules that would need to change:
 - Assess complexity (size, dependency count, cyclomatic complexity)
 - Identify integration points with other systems
 - Check for existing test coverage in the affected areas
-- Read past sprint data from `production/sprints/` for similar completed tasks and historical velocity
+- Read past sprint data from `production/sprints/` for similar completed tasks and historical velocity.
+  **If there is none**, say so under Notes and Assumptions — "No sprint history found;
+  this estimate is not calibrated to the team's velocity" — and treat that as a risk
+  in the confidence level, not as a silent padding of the figures.
 
 ---
 
@@ -130,3 +133,4 @@ This skill is read-only — no files are written. Verdict: **COMPLETE** — esti
 - The recommended budget should be the expected estimate, not the optimistic one
 - Round to half-day increments — estimating in hours implies false precision for tasks longer than a day
 - Do not pad estimates silently — call out risk explicitly so the team can decide
+- Confidence is Low whenever the approach is undecided or the core requirements are still TBD — a range built on an unmade decision is a guess