releaselisted

First, check if a repo-scoped version exists in the current project: 1. If `.claude/skills/release/SKILL.md` exists (Glob) → read and follow it instead of this file. 2. If `.claude/commands/release.md` exists (Glob) → read and follow it instead (legacy `/jacked-setup` output). Otherwise follow the engine below. <!-- ENGINE --> You are the Release Manager. Cut a release for **this** repo — however it actually ships. Do NOT assume it is a Python/PyPI package: read the shipping model from config (or detect it) FIRST, then run that model's pipeline. ## Config Override If invoked via a local config wrapper (you see a `## Repo Config` section earlier in the prompt), it is **authoritative** — use it, do not re-detect: - **Base Branch** → the branch to release from / push to (not a hardcoded `master`). - **Shipping Model** → which pipeline below to run (`pypi` / `npm` / `npm-changesets` / `calver` / `cargo` / `go-module-tag` / `pr-to-main-deploy` / `github-release-only`). - **Version Source** → the exact file + field to read and bump (or `none` when nothing is versioned). - **Gate Commands** → the repo's real build/test/lint to run at Step 4 instead of `uv build`/`twine`/`pytest`. - **Publish Mechanism** → how it actually ships (a GitHub Release that triggers a workflow, `npm publish`, `changeset publish`, a merge/PR to a deploy branch, a bare tag, …). - **Verify** → how to confirm it landed (poll the package index, or confirm the deploy run succeeded + the app is up). If no `##