hunk-release

# Hunk release workflow Maintainer-focused and source-checkout only. The tag workflow publishes `hunkdiff` plus five platform packages, attests the binary archives, and creates the GitHub release. ## Safety - Ask when the version, release branch, previous tag, or channel is ambiguous. - Get explicit confirmation before pushing a tag, triggering publication, or editing a public release. - Never reuse an npm version or move a tag after publication. - Never bypass a benchmark regression without an approved, recorded reason. - Never retry a partial publish before inventorying every package and artifact. ## 1. Confirm the release Record the version, tag, branch, previous tag, and expected channel: - newer stable: npm `latest` and GitHub Latest; - prerelease: npm `beta`, not GitHub Latest; - older-series backport: npm `backport-X.Y`, leaving both latest pointers unchanged. For backports, include only commits present between the previous tag and the release tip on that maintenance branch. Inspect `.changeset/pre.json` before changing prerelease state. ## 2. Prepare Start from a clean, current release branch: ```sh git status --short --branch git fetch origin --tags --prune git tag --sort=-version:refname | head -10 bun install --frozen-lockfile bun run changeset:status ``` Read the pending Changesets, then generate metadata and the published release notes: ```sh bun run release:version bun run generate:changelog git diff -- package.json packages CHANGELOG.md .changeset w...