deliver-change

name	deliver-change
description	Deliver one validated change through GitHub.
disable-model-invocation	true

Deliver change

Carry one validated commit through review and into the default branch.

Read standards/repository-lifecycle.md from the selected release before operating this transition.

1. Perform delivery preparation through this adapter. Record the caller's branch, head, index, and worktree content and treat that worktree as observation-only. Resolve the candidate commit, isolate it reversibly, enter that worktree, and prove its HEAD is the candidate. Resolve the normalized manifest contract, then execute canonical-validation.executable with its ordered arguments from its repository-relative working-directory. Use a process argument vector directly: never pass the declaration through a shell or perform quoting, expansion, globbing, redirects, or pipelines. Treat the result as a hard gate; only that isolated run is candidate evidence. Failure stops before push or pull-request mutation and returns unchanged work to implementation. Restore the exact caller state before stopping or reporting, including on failure. Push the head and reuse or create a ready pull request with an unambiguous non-closing tracked-work link.
2. Present one exact lifecycle proposal containing the pull request, prepared head, validation evidence, linked work, checks and review evidence, proposed squash merge, cleanup, warnings, and observed starting state. End preparation with Exact confirmation required: Confirm delivery of HEAD via PR, replacing HEAD and PR with the prepared commit and pull-request URL, then stop. Only that exact reply authorizes the proposal; a pull-request reference does not.
3. After exact confirmation, re-observe the proposal's starting state and reject stale evidence. A changed head invalidates confirmation; validate the new head as a hard gate before presenting its fresh proposal. Before merging, collect all current blockers from checks, submitted reviews, inline-thread resolution, mergeability, and merge policy; query thread resolution separately when the ordinary pull-request view omits it. Pending or failed gates and actionable feedback return unchanged work with their evidence.
4. After verifying the merge, apply the tracked-work reconciliation policy, safely clean up the branch, and report exact completed, failed, uncertain, and remaining work without rollback claims. Relevant state change or partial execution requires a fresh lifecycle proposal and human confirmation.

Implementation and standards adoption remain separate and must already have produced the validated commit. Delivery does not edit implementation work.