cut-release: version and tag move together, or not at all

A release is a claim: "this tag is this code." The failure mode this skill kills is drift — the version file says one thing, the Releases page another, and the changelog a third. (It's a real failure: a tag once lagged the code by ten days and three minor versions before anyone noticed.) The ritual keeps all three in lockstep.

Step 1 — verify live state (never from memory)

git fetch origin
git ls-remote --tags origin                    # what's actually tagged
git log --oneline <last-tag>..origin/main      # the pack since the last tag
git show origin/main:package.json | grep version   # or your version file