release

# Release (project-local) Creates a CalVer tagged release with a hand-written narrative prepended to the body CI generates via `scripts/package.js`. Overrides the global `/release` skill for this repo. ## Purpose - Push CalVer tag → CI (`release.yml`) runs `scripts/package.js` to build ZIPs + produce `dist/release-notes.md`, then `gh release create --draft --notes-file` attaches it - Prepend a hand-written narrative block to the script-generated body so the release surfaces "why this release matters" before the commit list - Leave publish (draft → published) to the user for manual review ## Preconditions - Working tree clean, on `main` (or user-specified branch) - `gh` authenticated with push access to the target remote (fork or upstream) - Node 22+ on PATH (packaging requires `zlib.crc32`) ## Flow ### Phase 1: Tag decision - Previous tag: `git describe --tags --abbrev=0` (excludes drafts, gives last tagged commit) - Today: derive `YYYY.MM.DD` from current date - Candidate tag: `v{YYYY.MM.DD}`, or `v{YYYY.MM.DD}.{N+1}` if same-day tag exists - If latest tag is already today's and is Draft (not published), ask whether to re-tag (delete + recreate) or increment `.N` ### Phase 2: Tag push - `git tag <tag>` - `git push origin <tag>` → triggers `release.yml` ### Phase 3: Wait for CI draft - Poll `gh run list --workflow=release.yml --limit 1 --json status,conclusion,databaseId` every 5s, max 12 attempts (60s total) - When `status=completed` and `conclusion=success`, fet...