release

Multi-channel release orchestration is managed by generating drafts for X, Discord, YouTube, and Zenn, then executing public actions in a controlled order after explicit user confirmation. This draft-first approach removes the risk of publishing mistakes across platforms.

Preparing release notes and GitHub Release drafts is handled within a single guided flow that produces all candidate artifacts before any public posting. The process requires a version number and uses phase gating to ensure user confirmation prior to publication.

Posting to a Discord webhook and publishing a GitHub Release are executed as ordered public actions after the user manually publishes X content. The workflow enforces this sequence to maintain safe, controlled public release execution.

Draft creation for X posts, video assets via MulmoScript, and Zenn articles is fully supported without immediate publishing. The workflow generates all drafts first and applies phase gating with user checkpoints before any public action occurs.

A YAML-defined orchestration process is required to manage versioning, candidate verification, and release PR preparation. This configuration drives the phase gating and user confirmation steps throughout the end-to-end workflow.

The draft-first release workflow requires explicit user confirmation at each phase gate, meaning fully automated continuous deployment is not supported. The process intentionally pauses for manual verification before switching drafts to published and executing public posting.