pre-merge

# pre-merge **The** CI gate. Runs after `eng --build` says a feature branch is done, and takes it to a PR open against `staging` with green checks and a human-approved preview. Absorbs the retired `/review` and `/test`. Each run is independent. ``` eng --build → /pre-merge → (fail → eng --build report=…, repeat) → PR feature→staging → post-merge --staging ``` ## Usage - `/pre-merge` — gate the current feature branch against `staging` - `/pre-merge --init` — run the one-time setup: detect tooling (incl. the `.github/workflows/` CI pipeline that runs the gate on PRs, unless `policies.github_actions.enabled` is `false` — then the missing workflow is a settled opt-out, not a gap, and no scaffold is offered) → interview → gated install/scaffold → write `devkit/policy.json` (no gate run); see `refs/protocol-init.md` - `/pre-merge --doctor` — **deprecated alias for one release**: runs `--init` and prints a deprecation note naming `--init`/`--update` - `/pre-merge --update` — reconcile the manifest with codebase reality (re-run preflight checks → diff `components[]` → approve the delta → apply `present`/`active_when`/new-component changes only; never re-grades user-set criticality or re-prompts settled opt-outs); see `refs/protocol-init.md` - `/pre-merge --prd <path>` — load a PRD; enables the `prd`-group components (`prd-consistency`, `manual-test-plan`) and feeds the `regression` component (repeatable) - `/pre-merge --prior-issues <path>` — load a prior verdict JSON t...