auto-shiplisted

# Auto ship Chain the post-plan pipeline in a single run. Every step has a stop condition. State is always recoverable on stop: code lives on the branch, review output on disk, plan still linked. ## Guards - All `.canon/plans/` and `.canon/review/` reads resolve at the main worktree root, not the current worktree. Resolve that root the way `session-worktree` does. - Derive `<slug>` per `${CLAUDE_SKILL_DIR}/../../standards/slug.md`. This skill takes the stop rather than the `latest` fallback, since it commits and opens a pull request. If empty, stop: `❌ Detached HEAD. Checkout the feature branch first.` This slug is provisional. It is superseded once `session-worktree` runs, whether at Step 0 or before this chain began. Every later step keys its output on the slug that run resolves, being the worktree, the review receipt, and the branch, regardless of which plan Step 1 reads. - Resolve `<plan>` in Step 1, ahead of any other read. - If the working tree has uncommitted changes unrelated to the plan, stop: `❌ Uncommitted changes outside the plan. Commit or stash before autoshipping.` ## Diff baseline Step 6 classifies the changed-file list to decide whether review runs. Resolve the base ref once: ```bash git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main 2>/dev/null ``` Prefer `origin/main` over local `main`, since a local `main` trailing the remote pulls other people's merged commits into the list. The baseline is unusable when no merge base resolves