shiplisted

# Ship Close the SpecStudio pipeline for a single Feature: enforce the spec-aware release gates, hand the deploy off to a project-configured delegate skill, and record the outcome. Ship **gates, records, and dispatches once** — it never deploys, sequences, retries, rolls back, or orchestrates. The high-blast-radius deploy execution lives in a tool the project already trusts. Implements the [Ship Skill Feature](../../spec/features/skills/ship/README.md). ## When to Use - A single Feature at `spec/features/<feature-slug>/README.md` is `**Status:** Implementing`, its ACs have all been verified green, its latest recap shows no contradictions, and the user wants to release it. - The user wants to run the spec-aware release gates for one Feature and (when a delegate is configured) dispatch the deploy. **Refuse and redirect when:** - The invocation does not name exactly one Feature slug → print a usage error and exit non-zero. Ship operates on one Feature per invocation. (AC: `rejects-non-feature-input`) - The Feature's `**Status:**` is not `Implementing` → print the current Status and recommend the appropriate prior step (`Implementing` is the only status from which `Stable` is reachable). Write nothing; exit non-zero. (AC: `refuses-non-implementing-status`) - The Feature's latest verify report is missing or not all-green → recommend `specstudio:verify <feature-slug>`. Write nothing; exit non-zero. (AC: `refuses-when-verify-not-green`) - The Feature's latest recap report is m