Release Dispatch

The router behind /release. It owns one job: turn a subcommand into the right release action and delegate. It does not contain release logic of its own — CI gating + cut/PR live in release-pr-gates, semver + patch notes live in release, branch/worktree pruning lives in release-cleanup. Trunk-based throughout: releases are tags cut from the trunk; staging and production are deployment environments driven by CI/CD and tags, not branch promotions.

Contract

Inputs:

• A single argument string (may be empty) parsed into a mode. A bump token (patch / minor / major / vX.Y.Z) is forwarded verbatim to the cut engine.

Outputs: