sw-ship

Specwright Ship

Goal

Merge the current work unit to main via a pull request. The PR body maps evidence to acceptance criteria and derives its reviewer-facing audit summary from review-packet.md so reviewers can verify without opening raw transcripts or reconstructing rationale from the diff alone. The PR itself is the human gate — reviewers verify before merge.

Inputs

• {worktreeStateRoot}/session.json -- selected work for this worktree
• {repoStateRoot}/work/{selectedWork.id}/workflow.json -- selected work unit, gate results
• {workDir}/spec.md -- acceptance criteria for PR body
• {workDir}/review-packet.md -- reviewer-facing audit summary assembled by /sw-verify
• {workDir}/evidence/ -- gate evidence files
• {projectArtifactsRoot}/config.json -- git config (PR tool, branch prefix, main branch)

Outputs

• {repoStateRoot}/work/{selectedWork.id}/units/{selectedWork.unitId}/stage-report.md -- shipping handoff digest with attention-at-top
• Pull request created with a review-packet-grounded, evidence-mapped body
• Selected work's workflow.json status set to shipped

Constraints

Stage boundary (LOW freedom): Follow protocols/stage-boundary.md. Create PRs and mark shipped. NEVER start new work, run builds, or begin next unit. After PR: show URL, suggest /sw-learn, handoff.

Pre-flight checks (LOW freedom):

• Resolve the selected work from the current worktree session. If another live top-level worktree owns it, STOP with explicit /sw-adopt guidance instead of generic adopt/takeover behavior.
• Verify the selected work exists and status is verifying. Reject building with: "Run /sw-verify first." Reject all other statuses with the standard transition error.
• All enabled gates in config.gates must have a verdict in the selected work's workflow.json. Gates without a verdict → STOP: "Gate {name} has no verdict. Run /sw-verify first."
• No gate verdict may be FAIL or ERROR. FAIL/ERROR → STOP: "Gate {name} failed. Fix and re-run /sw-verify."
• Re-check shipping freshness during pre-flight via protocols/git-freshness.md. For branch-head validation, branch-head require blocks stale, diverged, and blocked freshness results. Queue-managed validation remains distinct and must not force a local rebase by default. When branch-head validation is blocked and rebase or merge reconcile is configured, run protocols/git-reconcile.md in the owning worktree and continue shipping in that same run after a successful reconcile. manual remains an explicit fallback: STOP with the same manual reconcile guidance used by build and verify: reconcile the current branch against the recorded target in the owning worktree, or run /sw-adopt first if a linked-worktree ownership conflict exists, then rerun /sw-verify followed by /sw-ship. Do not silently rewrite targetRef or freshness metadata to bypass the block.
• review-packet.md must exist at {workDir}/review-packet.md. Missing packet → STOP: "Review packet missing for {unitId}. Re-run /sw-verify."
• Evidence files must exist at {workDir}/evidence/{gate-name}-report.md for each gate with a non-SKIP verdict. Missing evidence file → STOP: "Evidence missing for gate {name}. Re-run /sw-verify."
• Uncommitted changes: commit only files within the work unit's plan.md file-change-map. Report out-of-scope uncommitted files in the gate handoff — do not commit them.