Gated release execution + drafted notes
Release is where approval turns into action: a drafted plan, a human-approved gate, your own release command run in a clean checkout, and a record that cannot be edited after the fact.
How it works
DeployPlanAgent drafts the steps, checks, and rollback for a release from the work approved since the last one.
DeployController checks the deploy gate is still approved immediately before executing — an approval can't go stale and fire anyway.
The release command you configured runs in a fresh checkout — the same discipline as your CI, executed by DeployController rather than a human running it by hand.
Approvers, executor, command, and output are written to a release record that can't be edited after the fact.
ReleaseNotesAgent drafts a headline and highlights onto a successful release, from its acceptance criteria and merged proposals — best-effort, and it never touches a release that didn't go through the gate.
The agents behind it
Human control
Deploy gate — approval is required before execution, and the gate is checked again the instant before the release command runs.