Defined in cli/commands/merge-path.ts. Answers one question: may this branch be the head of a pull request into develop? It skips the wrapper's AWS gate and needs no login.

ds merge-path check#

ds merge-path check --head <branch> --base develop [--labels a,b] [--config <path>]

Prints one line, ALLOWED or BLOCKED with the reason, and exits 0, 1, or 2 for a usage or config error. It is the same checker the required merge-path check runs on every pull request into develop, and the one the merge guard consults before a merge. The rules are mergePath.allowedHeadPatterns in .claude/ds-config.json: an epic integration branch, the release train or the snapshot a release cuts from it, a master-into-develop sync, a release or hotfix branch, or a Dependabot update. Anything else needs the merge-path-override label — an infrastructure one-off, or an epic branch from before the epic- marker.

Why it exists. develop reaches production at the next release, so only branches that have been through a full review may merge into it. Running the check locally tells you before you open the pull request, instead of from a red check after.