Ship

Complete the delivery action the user requested. Push, draft change request (pull or merge request), ready, merge, deploy and publish are distinct outcomes; one never authorizes another.

Phase 1: Establish the terminal action

Read current authorization, repository delivery rules, branch/remotes, status and existing change request metadata. Resolve base, head and target remote from evidence; reuse an existing change request. Do not re-prompt for an authorized action, and never treat a skill handoff as permission for an unrequested merge, deployment, reviewer request or message.

Phase 2: Verify the artifact