dispatchlisted

# /forged:dispatch Hand one reviewed native Bead to the Forged execution control plane. The lead agent remains the operator-facing controller; Forged freezes the execution record, runs provider adapters, gates the result, and stops at a reviewed draft pull request. This skill never merges the default branch. ## Select and verify Resolve the operator store and canonical target repository. If the operator did not name an id, query the native repository frontier directly: ```bash export ANVIL_HOME="${ANVIL_HOME:-$HOME/.anvil}" export BEADS_DIR="${BEADS_DIR:-$ANVIL_HOME/beads}" BD_BIN="${BD_BIN:-$(command -v bd)}" TARGET_REPO="$(cd "$(git rev-parse --show-toplevel)" && pwd -P)" env BEADS_DIR="$BEADS_DIR" "$BD_BIN" ready \ --metadata-field "repository=$TARGET_REPO" --json ``` Consider only records whose returned `metadata.repository` exactly matches that canonical repository. Read the selected Bead with explicit operator state: ```bash env BEADS_DIR="$BEADS_DIR" "$BD_BIN" show "$BEAD_ID" \ --long --include-comments --json ``` Verify: - complete `description`, `design`, `acceptance_criteria`, and `notes`; - exact canonical repository metadata; - no unchecked questions or unresolved critique CRUX; - no unmet dependency and actual presence on the ready frontier; - issue type is a reviewable code slice, not an epic or no-diff coordination record; - working tree safety and the repository's configured base branch. Do not dispatch a record merely because its status text s