Skip to content

v0.2.0 — 2026-04-27

Added

  • Shared reference docs mechanism (skills/core/_shared/) — cross-skill reference docs (worker-dispatch.md, verifier-dispatch.md, reviewer-dispatch.md, analyst-dispatch.md) live as a single source of truth and are reverse-deployed by publish_shared_refs() into each consumer's references/ with an <!-- AUTO-GENERATED --> header. Schema and authoring rules in docs/contributing/shared-refs.md.
  • Per-scene visual targets — /gm-asset Step 3 generates references/scene_*.png per SCENES.md entry; /gm-evaluate Phase 3 invokes the visual-qa skill with Static / Dynamic templates to compare running screenshots against these targets. Frame sequences for animated scenes live under per-scene subdirs e2e/screenshots/scene_{name}/frame_*.png.

Changed

  • Pipeline split into 9 role-based skills — replaced the monolithic /orchestrator skill with /gm-scaffold, /gm-gdd, /gm-asset, /gm-build, /gm-verify, /gm-evaluate, /gm-fixgap, /gm-accept, /gm-finalize. Each role owns a single phase and a write-permission scope; .godotmaker/current_role enforces the lock at hook level. Role transitions are recorded in .godotmaker/stage.jsonl (was stage.json).
  • Hook rewrite for the role model — check_stage_prerequisites.py keys off PREREQ_ROLE (build requires gdd; fixgap requires evaluate); stage_reminder.py validates per-role outputs from config/stage_schemas.json whose keys are role names instead of stage numbers; on_subagent_stop.py serialises log_subagent + check_worker_report to avoid the metrics_current.jsonl parallel-write race.
  • Wiki rewrote for end-users — 28 user-facing pages across getting-started / concepts / skills / troubleshooting / tools / configuration / contributing / reference, replacing the previous engineer-oriented layout. Landing page and mkdocs.yml nav synced.

Fixed

  • Cleared all ruff lint debt (24 errors across hooks/, tools/, tests/) and a real NameError in tools/rembg_matting.py (bg_color referenced before assignment in --preview branch).
  • Aligned pyproject.toml version with VERSION file (was 0.4.0).

Removed

  • harness/ code and docs migrated out of this repository into the separate external automation host. The framework is now the only thing shipped from this repo.

Upgrading from v0.1.x

In-place migration from v0.1.x is not supported. The v0.2.0 release reshapes the runtime contract — role-based skills, current_role lock, stage.jsonl, and per-role hook permissions — and there is no migrations/0.1_to_0.2/ script for it. If you have a project on v0.1, run a clean redeploy:

python tools/publish.py --force <target_dir>

--force rewrites the framework-managed surface (.claude/skills/, .claude/settings.json, .godotmaker/hooks/, templates, tools) while preserving your game code, CLAUDE.md, and godotmaker.yaml. Migrations resume incremental support starting from the v0.2.x line.