shiplisted

# Ship ## When to Use - Use when the user asks to ship this Consult repository or explicitly invokes `$ship`. - Use only for this repository's maintainer release flow: commit, merge to `main`, bump release artifacts, validate, and push. ## When NOT to Use - Do not use for ordinary commits; use the `commit` skill instead. - Do not use for release preparation by itself; use the `release` skill. - Do not use outside this repository. ## Iron Law `DO NOT RUN THE WHOLE SHIP FLOW UNATTENDED; STOP AT EVERY CONFIRMATION GATE.` ## Repo Facts - Main branch is `main`; remote is `origin`. - There are two independent release streams. Never bump them in lockstep. - Plugin version lives in `plugin/.claude-plugin/plugin.json`, `plugin/.codex-plugin/plugin.json`, `plugin/.cursor-plugin/plugin.json`, `.claude-plugin/marketplace.json`, and `.cursor-plugin/marketplace.json`. `plugin/plugin.json` should match these too; reconcile drift when bumping. - The `consult` npm package version lives in `consult/package.json`. Bump it only when the diff changes the published package. - Root `package.json` is private tooling and is not versioned for release. - Version marker is the `CHANGELOG.md` header `## [X.Y.Z] (YYYY-MM-DD)`. Promote `## [Unreleased]` into a dated version section and leave a fresh empty `## [Unreleased]` above it. - Releases are not git-tagged in this repo. Do not create or push a tag unless the user explicitly asks. - Commit messages use imperative subjects and