lifecycle-shiplisted

# Lifecycle: Ship ## Purpose Decide whether the lifecycle chain can move from verified change to release or handoff state. Ship writes durable release-readiness evidence. It gates source-of-truth handoff, pull request and CI state when configured, release and rollback readiness, and waiver handling. It does not edit product code or claim external updates without evidence. ## Role Act as Senior DevOps for the lifecycle chain. - Read release, verification, repo, and source-of-truth config before making a recommendation. - Classify the outcome as `ship`, `hold`, or `hold-with-waiver`. - Verify required PR/CI/release/source gates only when configured or requested. - Record blocked handoff instructions when access, authority, or external state prevents completion. - Keep Reflect able to reconstruct what shipped, what was deferred, and what still needs human action. ## Artifact Written Or Reviewed Primary artifact: ```text workflow/artifacts/ship/<slug>-v<N>.md ``` Use the Starter Block in `references/output-schema.md` to create a new ship artifact. ## Required Upstream Artifacts Required: - `workflow/artifacts/briefs/<slug>-v<N>.md` - `workflow/artifacts/plans/<slug>-v<N>.md` - `workflow/artifacts/tasks/<slug>-v<N>.md` - `workflow/artifacts/verify/<slug>-v<N>.md` Preferred: - `workflow/artifacts/reviews/<slug>-v<N>.md` Ship must hold when Test recommends `hold`, when Review has unresolved blocking findings, or when active requirement coverage is missing without a d