merge-and-releaselisted

# Merge and Release Reference document for merge and release policy. The executable bash lives in `plugins/flow/commands/merge.md` and `plugins/flow/commands/release.md`. This skill describes **what those commands enforce and why**. Both merge and release are **Tier 3** — they always require explicit human confirmation, even in autonomous mode. This is non-negotiable. ## Iron Law **MERGE IS IRREVERSIBLE IN PRACTICE. Treat every merge as permanent. Every prerequisite must be verified with fresh evidence, not memory.** Reverting a merge is technically possible in git but disruptive in practice — downstream branches rebase off the merge, deploys propagate it, and history grows confusing. Prevention is the only reliable strategy. The Tier 3 confirmation requirement is the structural expression of that fact. ## Merge Prerequisites — The Five-Check Gate Before a merge proceeds, all five checks must pass. The runnable verification is in `plugins/flow/commands/merge.md` Phase 1. | # | Check | Requirement | What it protects against | |---|-------|-------------|--------------------------| | 1 | Approval | At least one approval, no outstanding requested changes | Merging code that no human has signed off on | | 2 | CI Checks | All status checks pass (`statusCheckRollup` all success) | Merging code that fails the project's automated tests | | 3 | Mergeable | No merge conflicts (`mergeable == "MERGEABLE"`) | Merging a PR whose content cannot cleanly land on the base branch | | 4 |