gm-finalize

To archive Godot game development documentation, you can finalize the current tag by snapshotting GDD, PLAN, and evaluation evidence into docs/tags/<Tag>/, generating a changelog, and creating a local git tag to seal the milestone.

Plan validation for GodotMaker tag readiness checks for a valid PLAN.md state, accepted plan events, final approval, and build consistency so broken tags are not archived during the game dev pipeline.

Reset pipeline runtime state by truncating stage.jsonl and metrics_current files after sealing the current tag, ensuring subsequent Godot game development iterations start from a clean baseline without stale artifacts.

Yes, you need a successful Godot build, evaluation approval status, and accept/decision events before archiving a game tag, because the finalization process validates these readiness checks to prevent broken tags.

The best way to bundle release metadata is to generate docs/tags/<Tag>/CHANGELOG.md and write .godotmaker/final_report.json while archiving per-tag deliverables, creating a traceable postmortem record for the Godot game tag.

You should not use automated tag finalization before release packaging, or if the PLAN.md tag state is invalid, because the workflow requires strict validation of document consistency and approval status before sealing the Godot project tag.