ship - Pull Request Stage

Invariants

Always advance the task to Ready To Ship in TASKS.md and re-read the tracker to confirm the row moved before handoff. A stale tracker blocks downstream and headless sessions.
Self-heal when intermediate stages were skipped: never abort because the task is not in Approved. Detect the current section, record a Skipped Stages list, and disclose it in the PR body and handoff text.
Run available pre-ship checks before creating a pull request.
Do not auto-merge.
Keep released-version work for the release stage.

Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is ship.