Deliver changes
Authorize the specific outward action after implementation is inspectable.
Make the delivery request concrete
Ask for the action you want: push a branch, open a pull request, merge, or publish. An execution request alone does not authorize these actions.
Push the implemented branch and open a pull request against this machine's
recorded base branch. Include the checks that actually ran.Resolve source and target
The agent reads real Git state and the CLI's base_branch report. A stacked run delivers the final chain end for each repository, including predecessor changes. The shared default_branch is only the fallback when no local base exists.
Leave a reviewable result
The description explains the problem, final behavior, checks, and remaining limitations. Base drift and conflicts are reported without automatically rebasing or launching an independent review.
Records are committed separately
Committing workspace records is not code delivery. When approval, completion, or archiving leaves records uncommitted, the agent asks whether to commit and push them, or commit only, and pushes only the workspace's base branch to its upstream. A push refused because the remote moved on is brought up to date with git pull --rebase: an ID file conflict keeps the union of both sides, any other conflict goes to you with the rebase left in progress, and nothing is force-pushed. Code delivery never rebases automatically.
Delivery does not stamp completion. After the work lands, request completion and reconciliation.