release-engineering

Decide whether to release, choose the version and release lane (alpha, beta, rc, stable), keep a clean changelog, and carry a verified change to its distribution target with a credible recovery path. Covers release triggers and batching, versioning and tagging (SemVer, calendar, build identity), pre-release promotion gates, CHANGELOG and release notes, CI/CD release workflows, artifact identity and provenance, compatibility and migration during rollout, rollback or roll-forward, post-release verification against SLOs, and release metrics (DORA). Use this whenever the user wants to release, publish, deploy, ship, tag, bump a version, cut a beta, write a changelog or release notes, set up release CI, or roll back, even if they only say "naikin versi" or "rilis". Reads .agents/engineering.md, code-review verdict, and test-engineering evidence. Does not run daily operations, incident command, or mandatory canaries.