git-wrapup

---

name: git-wrapup description: > Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to main, no publish: the release-and-publish skill merges, tags, and ships from here. metadata: author: cyanheads version: "1.30" audience: external type: workflow

When to use

Working-tree or staged changes are ready to ship as a new version. This skill lands them as a stack of logical commits — the work grouped by concern, topped by a release commit (version + changelog + tree). It does NOT tag, push to main, or publish — release-and-publish does all three.

Common triggers:

• Feature work, bug fixes, or dependency updates are done and tested
• A maintenance or polish pass left changes in the working tree
• An orchestrator says "wrapup this project"

Release PR mode

A project can route every release through a pull request — one PR per version, for the audit trail and a stable review target. The mode is declared in the project's CLAUDE.md/AGENTS.md or in the caller's brief; when neither says anything, there is no release PR and the stack lands on main directly.

Mode	Wrapup ends at	Then
(none — default)	commit stack on main, tree clean	release-and-publish tags HEAD and ships
gated	commit stack on release/<version>, branch pushed, PR open	a review pass on the PR (release-pr-review skill), then a separate release-and-publish run fast-forwards main, tags, and ships
straight-through	same as gated	the same agent continues straight into release-and-publish

The branch is created at wrapup time, never before — its name carries the version, so it cannot exist until step 2 has settled one. The moment that number is known, the uncommitted tree moves to release/<version> (end of step 2), and every commit in the run lands there. No commit in these two modes ever reaches main, including the first one: a stack committed on main and then branched is a rewrite to undo, and once it is pushed there is no undo, because force-push is banned. The commit stack, the release commit, and the tag format are identical in every mode — the PR adds an artifact around them, it does not change them.

Pre-wrapup gate checklist

Every item must be true before starting wrapup. Committing means releasing — a commit only happens when the work is ready to ship, not just "the edits are done." Each item is a goal to verify.

• Changes exist — uncommitted files or commits since the last tag
• Work is complete — no half-finished features, no "I'll add the test later," no TODO placeholders. The diff represents a shippable unit.
• Code simplified — if the diff spans more than ~50 changed lines or touches 3+ source files, the code-simplifier skill has been run across the changes
• bun run devcheck is clean — exit-0 AND zero warnings. Biome/lint warnings exit 0 (non-blocking to the tool) but are a HARD BLOCK to shipping — pre-existing warnings in untouched code included: fix them behavior-preserving, or get the maintainer's explicit waiver in the maintainer's own words — never your own adjudication. A documented alternative remedy in a skill (lint:mcp's "or verify by hand that format() renders it") is a way to UNDERSTAND a warning, never a licence to ship it; hand-verifying it and filing a follow-up issue is still shipping dirty. Nor is a pinned version a reason to defer the real fix: when the correct fix crosses the minor floor, the VERSION yields, not the gate — take the minor and say so. Two things that look dirty but aren't: (1) info is not warning — Biome's unsafe-fix suggestions ("Skipped N suggested fixes", useLiteralKeys and friends) print at info severity with the step still ✅; not the block. (2) The Security Audit step's transitive warn — a DIRECT-dep advisory is a hard failure, an all-transitive one is ⚠️ WARNING with the run still ✅; confirm from the bun audit dependency path (pkg › child = transitive), then ship it. Never force a gate green with a resolutions/overrides hack, and never run audit:refresh to silence it (it re-resolves the ^-ranged framework pin off its hold). The exception is a deliberate, maintainer-directed overrides block as its own dependency-hygiene pass — mcp-ts-core carries one as of 0.11.0: leave it in place, pre-authorize it by name in implement/release briefs (or agents burn a phase chasing it), pin entries to the lowest patched version inside the consumer's existing major, and verify the installed tree rather than assuming a pin applied (bun skips resolutions its range can't satisfy). Read the severity label and the failing step before calling a green run dirty — filtering devcheck's output strips exactly the context that separates the tiers.
• bun run rebuild succeeds — full clean build from scratch
• All tests pass — bun run test:all (or bun run test), plus bun run test:package where the project defines one: it guards the public-export manifest and is not part of test:all. New tests and regression tests added as needed for the changes being shipped.
• Fixes verified — bug fixes validated, generally via bun run rebuild and field-testing. Not just written — confirmed to resolve the described behavior.
• No known regressions — the changes don't break existing functionality
• GH issues updated — issues addressed by this work commented with what landed and any follow-ups needed. Concise. Backlinked as needed.
• Docs updated — surgical updates to existing docs as needed. New docs for new features. No large rewrites for documentation that's still accurate.

If any gate is red, fix it before proceeding. This skill re-verifies build + tests in step 7, but the work is committed by then — starting wrapup on a broken tree wastes the version number and turns the fix into an extra commit on a stack that should have been green.

Steps

1. Review the diff

Understand what's about to ship before touching version numbers:

git branch --show-current                 # empty output = detached HEAD
git status
git log v<latest-tag>..HEAD --oneline    # commits since last release
git diff HEAD --stat                      # every uncommitted change, staged or not
git diff HEAD                             # review the actual content
git ls-files --others --exclude-standard  # new files, which never appear in the diff

Check the branch first. Empty output from git branch --show-current means a detached HEAD: halt. In every mode the wrap-up starts on main; release PR mode moves to release/<version> in step 2.

Diff against HEAD, not the index: plain git diff omits staged changes entirely, so a group already staged before wrap-up began — a git mv from a migration step, a hook's output — shows up in git status as a line to scroll past and nowhere in the diff review. Whatever is staged is part of what ships and gets grouped in step 3 like everything else.

Read every untracked file in full. New files ship through git add like any other change, but no diff shows their content, and git status collapses a new directory to a single line.

Ship only finished work no one is still writing. Uncommitted changes outside the work being wrapped are candidates, not automatic exclusions: git records no author for them, so judge each from the evidence. A complete, safe change that has sat idle for hours folds in as its own commit. A change this run didn't make, modified in the last few minutes (check mtimes) or visibly half-done, may belong to a session still writing it: leave it uncommitted and report it, since committing it would ship work in progress and leave its writer editing on top of a released commit. Anything unsafe or secret-bearing stays out regardless.

If the working tree is clean AND there are no commits since the last tag, halt — nothing to wrap up.

2. Determine the new version — and, in release PR mode, create its branch

Read the current version from package.json. The version is the caller's to set, not this skill's to pick:

1. A version pinned in the caller's brief is binding — use it as given.
2. Otherwise apply the project's documented versioning policy (its CLAUDE.md/AGENTS.md), which may classify changes differently from plain semver.
3. Otherwise use semver:

Bump	When
patch	Backward-compatible fixes with no new functionality — bug fixes, dependency updates, metadata, docs
minor	Backward-compatible new functionality; below 1.0, also any breaking change
major	A breaking change to an existing contract (tool schemas, removed tools, incompatible config), once the project is at 1.0 or later

When the diff doesn't clearly settle which row applies, ask the caller rather than picking.

In gated or straight-through mode, create the branch now, before going on to step 3 — the version you just settled is its name, and step 3 opens by committing:

git branch --show-current                 # must be main
git switch -c release/<version>           # uncommitted work rides along

Do not defer this to "just before the first commit". Step 3 is where committing starts, so a branch not created here is a branch created too late. If git branch --no-merged main --list 'release/*' prints a branch, a prior release PR was never merged — halt and report it rather than stacking a second release on top. A release/* branch already merged into main is a leftover from a finished release, not a blocker: delete it with git branch -d and continue.

Check the remote too, before creating the branch:

git ls-remote --heads origin release/<version>          # must print nothing
gh pr list --head release/<version> --state all         # must print nothing

A hit means an abandoned run already claimed this version: halt and report the branch and PR. Never force-push past it.

3. Commit the work — one commit per concern

Release PR mode: git branch --show-current must print release/<version> before you run the first git commit. If it prints main, step 2's branch step was skipped — go back and do it. The uncommitted tree moves with you, so nothing is lost by branching late, but a commit already on main has to be unwound.

The work is committed before the version is bumped. Work concerns routinely share a file with the version — a dependency refresh edits package.json, a doc edit lands in a CLAUDE.md/AGENTS.md that pins a version string — and the file is the atomic boundary, so whichever commit comes first takes the file whole. Committing the work first leaves the version hunk (step 4) as the only thing those files carry into the release commit.

Do NOT git add -A into one commit. Group the working tree into a handful of logical commits — never one blob. A feature spanning multiple layers splits by layer: runtime/logic, linter/tooling, docs/skills. Unrelated changes (two separate fixes, an incidental doc tweak) are their own commits. A dependency refresh is its own commit — chore(deps): … carrying package.json, the lockfile, and any pins it moved elsewhere. Work commits do not carry the version.

Stage each group explicitly, commit it by pathspec, then move to the next:

git add <paths-for-this-concern>
git commit --only <paths-for-this-concern> -m "<subject>" -m "<body>"
# repeat per concern

Commit by pathspec, never the bare index. A bare git commit commits everything staged, not the paths just added, so anything staged before wrap-up began — a git mv left by a migration step, a concurrent stage from a second session or a hook — rides into the first concern's commit. --only takes the named paths' working-tree content and disregards the rest of the index, so a pre-staged group never rides along; it stays staged, to be committed as its own concern (chore(skills): move the skill tree to framework-skills/) or reported. Anything still staged when the release commit lands then fails step 10's clean-tree check instead of shipping silently.

The file is the atomic boundary: NEVER split a single file's working-tree changes across commits, regardless of mechanism — not git add -p, not an index-only patch (git apply --cached), not editing the file between commits to remove-then-re-add a hunk. When one file serves two concerns, it ships whole in the commit of its dominant concern; a later commit may touch the file again only for changes made AFTER the first commit (the version bump applied in step 4).

Every commit builds and passes its tests on its own. When a concern changes an exported contract — a service method's return type, a shared helper's signature, a renamed export, a changed query or behavior a consumer's tests assert — the files that consume it AND their tests ride in the same commit, even when they also carry other concerns. Grouping the contract change into one commit and each consumer into its own later commit leaves pushed commits that fail typecheck or the suite alone, and pushed history is never rewritten to repair them. A snapshot can typecheck and still be red: before pushing, check out each work commit's tree (git stash is not the tool — extract it with git archive <sha> | tar -x -C <scratch>, symlink the project's node_modules into it) and run the test script there. Run it first on a snapshot of the commit the stack starts from: a test that fails in that baseline too, such as one that resolves paths through the symlinked node_modules, fails because of the snapshot method, not the group. Merge only groups whose snapshot fails where the baseline passes.

A dependency bump lands before the commits that use it. When any later commit in the stack uses something the new versions introduce — a new framework export, a new tool() option, a changed signature — chore(deps) is the first work commit. It builds on its own: package.json, the lockfile, and any source change the upgrade itself forces (a renamed import, a removed option) ride in it, so the commits above it compile against the versions they were written for. Ordered the other way, the adopting commit and every commit up to the bump fail typecheck at their own SHA. The exception is a package.json that also carries another concern's entry pointing at files a deps-first commit would not contain, such as a new exports subpath or files entry. That snapshot fails, so the dependency changes ride the commit that adds those files, and its body says so.

Subject format: Conventional Commits, no version in the subject — feat: hosted server endpoint, fix: handle empty SPARQL result sets, feat(linter): enrichment contract rules, docs: document the enrichment block, chore(deps): refresh dev dependencies.

Body: every commit has one, and it is one or two lines. Uniform across the stack — no commit ships subject-only, none ships a paragraph. One sentence stating the why or the load-bearing constraint, a second only if the first genuinely cannot carry it. Two lines is the hard ceiling.

fix: handle empty SPARQL result sets

Upstream returns 200 with an empty bindings array rather than 404.

Never put a closing keyword in a commit body. Fixes #N, Closes #N, Resolves #N and friends close the issue the moment the commit is pushed — before the close-out comment recording what shipped, so the issue closes with no account of the fix. Reference issues as bare (#N) backlinks in the subject or body; closing is a deliberate later step.

A body is too long the moment it:

• enumerates the files, subsystems, or symbols touched — that is git show --stat
• walks through how the implementation works — that is the code
• narrates a fix's mechanism across multiple sentences — that is the changelog entry
• runs to a second paragraph, ever

The changelog carries the depth, the tag carries the headline, the commit carries one line of why. When the body wants to grow, that pressure is telling you the content belongs in the changelog entry.

Rules:

• Plain -m flag only — no heredoc, no command substitution. Never put a backtick inside a double-quoted -m: the shell runs it as command substitution and the span silently disappears from a message that, once pushed, can't be rewritten
• No Co-authored-by or Generated with trailers
• No marketing adjectives ("comprehensive", "robust", "enhanced", "seamless", "improved")
• Each commit message stands alone for someone reading git log — no chat context, option numbers, or "as discussed"

Right-size it. "Group by concern" is not "always split." A genuinely single-concern change — one fix, a dependency bump, a small doc edit — is one work commit, with step 8's release commit on top of it. Only when the version bump is the whole change — a republish, a metadata-only patch with nothing else in the tree — is there no work commit to make, and step 8's release commit becomes the entire stack. The failure mode to prevent is the inverse: a large, multi-layer feature crammed into one commit alongside the release artifacts.

When every concern is committed, git status is clean, apart from changes step 1 left out and reported. That clean tree is what makes everything steps 4–6 touch a release artifact and nothing else — confirm it before moving on.

4. Bump version everywhere

Every file that declares a version must be updated. Skip any file that doesn't exist in the project. For @cyanheads/mcp-ts-core projects:

• package.json — version
• server.json — top-level version AND every packages[].version entry. lint:mcp flags a mismatch at either level
• manifest.json (if present) — version. Packaging validation fails on a mismatch, and on a scoped name (use bls-mcp-server, not @cyanheads/bls-mcp-server)
• .claude-plugin/plugin.json and .codex-plugin/plugin.json (if present) — version. Packaging validation fails on a mismatch; .codex-plugin/mcp.json is connection config and carries none
• README.md — version badge. Packaging validation fails on a mismatch with package.json; a literal - in a prerelease is escaped as -- (Version-0.14.0--rc.1-)
• CLAUDE.md / AGENTS.md — if they pin a version string
• Dockerfile — OCI labels if they pin the version

Catch stragglers (replace the placeholder with the actual current version string, e.g. 0.9.7):

grep -rnF "0.9.7" . --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=changelog --exclude=bun.lock

-F matches the string literally; without it each . matches any character, and 0.9.7 also hits 10.9.7, 0.9.70, and every dependency version in the lockfile that happens to match.

Resolve hits case by case — historical changelog entries are correct as-is; everything else should match the new version.

5. Author the changelog

Create changelog/<major.minor>.x/<version>.md. Use changelog/template.md as the format reference — never edit, rename, or move that file.

Frontmatter (required):

---
summary: "<one-line headline, ≤350 chars, no markdown>"
breaking: false    # true if consumers must change code to upgrade
security: false    # true ONLY for a security fix in this server's own source — NOT a dependency/transitive CVE bump (those go under ## Dependencies)
---

Write summary: LAST, derived from the body you just wrote — never independently. It is the line most readers see: changelog:build copies it verbatim into the CHANGELOG.md rollup, the entry file ships inside the npm tarball (changelog/ is in package.json files; the rollup is not), and in release PR mode it opens the PR body. Written from recollection rather than from the body, it reliably names a mechanism that was never built or a target that was never fixed, while the body beside it stays correct. After writing it, re-read the body and confirm every claim in the summary appears there. Derived-from-the-body means the facts come from the body — not that every body item appears: it is one headline, and comma-stitching every change into an inventory near the 350-char cap is the failure mode.

security: is a source-code signal — not a dependency-CVE signal. Set security: true only when this release fixes a vulnerability or adds hardening in code this server ships. A dependency or transitive CVE bump — even one that clears an advisory (bun audit going 1 → 0) — is routine maintenance: record it under ## Dependencies with the advisory ID and leave the flag false. The 🛡️ Security badge answers "does the server itself have a vuln"; a dep bump must not trip it.

Body: Section order follows Keep a Changelog — Added / Changed / Deprecated / Removed / Fixed / Security. Include only sections with entries. Delete empty sections.

Tone: Terse, fact-dense. Bullet = symbol + what changed + at most one consumer-facing caveat; one sentence by default, two max — a bullet past ~40 words or three sentences is wrong. The linked issue carries the why and the commit diff the how; the changelog names what changed and what a consumer does about it. Cut: history/justification narration, design-rationale defense, "X unchanged" clauses (short parenthetical only where a misread is likely), edge-case inventories. Verified ≠ included — the diff-is-source-of-truth rule bounds the truth of what you write, never the amount. Model length on changelog/template.md's authoring guide, never on the previous entry (entries modeled on entries compound). agent-notes carries adoption steps only, never a second rendering of the body; a consequence shared by many bullets is stated once, not per bullet. Full conventions: the authoring guide in changelog/template.md.

Re-read the entry file after writing it, then sweep for harness markup: grep -rlF -e '</invoke>' -e '</content>' changelog/ must print nothing. The sweep covers the whole directory: a hit in an older entry gets deleted and ships in this release's commit, never left as out of scope, because every entry ships in every tarball. A stray closing tag at EOF is the authoring tool's own syntax bleeding into the file; changelog/ is in package.json files, so it ships inside the npm tarball, and changelog:check cannot catch it — the rollup drops the trailing line, so a clean CHANGELOG.md proves nothing about the entry.

6. Regenerate derived artifacts

bun run changelog:build    # rebuilds CHANGELOG.md rollup from per-version files
bun run tree               # regenerates docs/tree.md — run when files were added, removed, or moved in src/

Both scripts are idempotent — safe to run even if nothing changed.

7. Run the verification gate

The stack being shipped must pass verification. All must succeed:

bun run devcheck
bun run rebuild
bun run test:all           # or `bun run test` if no test:all script exists
bun run test:package       # only if the script exists — NOT part of test:all

If any fails, halt. Do not bypass verification to land the release commit.

The work is already committed by this point, so the fix is a new commit on top of the stack, under step 3's conventions — never git commit --amend, never a rebase, reset, or any other rewrite of a commit the stack already carries. Land the fix, then re-run this step. The same holds when the gate passes but leaves the tree dirty: devcheck auto-fixes as it runs, and a formatter fix to a file committed in step 3 is a follow-up commit of its own, not something to fold into the release commit.

Only the version bump, the changelog entry, and the regenerated artifacts may still be uncommitted when this step goes green.

8. Commit the release artifacts

One commit, on top of the work stack from step 3, carrying only what steps 4–6 produced: the version bumps (package.json, server.json, manifest.json, the plugin manifests, README badge, CLAUDE.md/AGENTS.md), the changelog entry, CHANGELOG.md, and docs/tree.md.

git add <release-artifact-paths>
git commit --only <release-artifact-paths> -m "chore(release): <version> — <theme>" -m "<body>"

Subject leads with the version: chore(release): 0.2.1 — empty SPARQL result handling. Step 3's conventions carry over unchanged — pathspec staging rather than the bare index, a one- or two-line body, no closing keywords, no trailers, no marketing adjectives.

Anything else still uncommitted at this point was made after step 3 — a formatter auto-fix, a gate fix. It is committed on its own first, and the release commit goes on top of it; it is never folded in.

9. Open the release PR (release PR mode only)

Skip this step entirely when the project has no release PR mode — go to step 10.

git push -u origin release/<version>
gh pr create --base main --head release/<version> --title "<release commit subject>" --assignee @me --body-file <path-to-body.md>

Title: the release commit's subject, verbatim — chore(release): <version> — <theme>.

Assignee: --assignee @me on every release PR, so it lands in the maintainer's assigned queue like a filed issue. A reviewer is not set: GitHub drops a review request aimed at the PR's own author and refuses a self-approval, so on a self-authored release PR the reviewer field stays empty by design — the review record is the summary comment release-pr-review leaves.

Body — always via --body-file, never an inline --body string (backticks inside a double-quoted argument are command substitution and silently vanish). Write the file to a scratch location, not into the repo.

The body is the release digest — the ## Changes bullets and changelog link the annotated tag will carry, under a theme line and above a gates record that both stay on the PR. The digest is written here, reviewed on the PR, and copied into the tag at release time, so it is the one place the release notes get reviewed before they become permanent. Format:

<theme — the changelog entry's summary: line, plain prose, one line. It opens the PR; the tag's subject is written fresh at release time and is not this line>

## Changes

- <notable user-facing change> (#N)
- <notable user-facing change> (#N)
- <ONE compact grouped line for the minor/internal changes — build config, repo hygiene, metadata>
- deps: `@cyanheads/mcp-ts-core` ^0.10.6 → ^0.10.14 (+ dev-dep bumps)

## Gates

- `bun run devcheck` — clean
- `bun run rebuild` — ok
- `bun run test:all` — <N> passed
- `bun run test:package` — <N> passed   (only where the project defines it)

[CHANGELOG v<version>](https://github.com/<OWNER>/<REPO>/blob/main/changelog/<major.minor>.x/<version>.md)

Rules:

• ## Changes follows the tag rules exactly (release-and-publish step 4): flat bullets, never Keep-a-Changelog section headers; complete at headline granularity — notable changes get their own bullet, minor/internal items share ONE grouped bullet; deps one line max, naming only what earns it; no narrative, no marketing adjectives. Depth lives in the changelog entry, which is in this PR's diff and linked on the last line.
• Every claim traces to the diff and to the changelog entry. The body is derived from the entry you authored in step 5, never written independently of it.
• ## Gates is the one release surface that carries gate results — the exact commands from step 7 with their outcomes. It never enters the tag.
• Issue references are bare (#N) backlinks — never a closing keyword (Closes #N, Fixes #N); the merge would close the issue before its close-out comment lands.
• Changelog link is the final line, same form as the tag, blank line above it.
• Length is earned — a theme, two bullets, gates, and the link is a complete body for a small patch.

If the review pass changes what ships, release-pr-review updates ## Changes and ## Gates to match; release-and-publish then lifts ## Changes plus the final link into the tag verbatim.

Gated mode: halt here. Report the PR URL, the branch, and the commit stack. Do not tag, do not merge, do not touch main. The review pass and release-and-publish run as separate steps after this one.

Straight-through mode: continue directly into release-and-publish.

10. Verify end state

git log --oneline -8              # confirm the commit stack: work commits + release commit on top
git status                        # clean, apart from step 1's reported exclusions
git tag --points-at HEAD          # must print nothing — tagging is release-and-publish's job
git branch --show-current         # main, or release/<version> in release PR mode
gh pr view --json number,url,state   # release PR mode: OPEN, head = the branch above

If the working tree holds anything beyond those exclusions, or the release commit isn't at HEAD, something went wrong — investigate before proceeding.

Do NOT tag, push main, or publish. This skill stops here. release-and-publish merges the release branch when there is one, creates the tag, pushes, and publishes.

Constraints

• No push to main, no tag, no publish. The only remote writes this skill makes are the release-branch push and the PR create in release PR mode
• Never stash. Not for quick checks, not for testing, not for any reason
• Never destructive. No git reset --hard, git restore ., git clean -f, git checkout -- ., no force-push
• Bash git only. Drive every git operation through the shell
• Never --no-verify. A failing hook is a red gate. When a pre-commit hook fails, the commit did not happen: fix the cause and commit again — never --amend, which would rewrite the previous commit. When a hook reformats files, re-stage those paths before retrying
• If v<version> already exists as a tag, halt and report the conflict — include the version string, existing tag SHA, and current HEAD SHA so the caller can resolve it. Do not delete or move tags without explicit authorization

Checklist

• Started on main, not a detached HEAD; release PR mode found no existing release/<version> branch or PR, local or remote
• Diff and every untracked file reviewed end-to-end before the first commit
• Unfinished changes this run didn't make left uncommitted and reported
• Version taken from the brief, the project's policy, or semver, in that order — asked when the row was unclear
• Work concerns committed before the version bump — a version-bearing file a work concern also touches ships whole in that concern's commit, so the release commit brings it the version hunk alone
• Version bumped in every declaring file (package.json, server.json, manifest.json, .claude-plugin/plugin.json, .codex-plugin/plugin.json, README badge, CLAUDE.md/AGENTS.md if they pin a version) — devcheck flags a mismatch in server.json (both levels), manifest.json, both plugin manifests, and the README badge; step 4's straggler grep covers the docs and Dockerfile labels
• GH issues addressed by this work commented with what landed (if working from GH issues)
• Docs updated for any new or changed features
• Changelog authored at changelog/<major.minor>.x/<version>.md
• CHANGELOG.md rollup regenerated (bun run changelog:build)
• docs/tree.md regenerated if structure changed (bun run tree)
• bun run devcheck passes
• bun run rebuild succeeds
• bun run test:all (or test) passes
• bun run test:package passes, when the project defines it — it guards the public-export manifest and test:all does not run it
• Release PR mode: stack committed on release/<version>, never on main
• Work grouped into logical commits (large features split by layer); release artifacts (version + changelog + tree) committed separately on top, subject leading with the version
• chore(deps) is the first work commit whenever a later commit uses what the new versions introduce, and it builds on its own — carrying package.json, the lockfile, and any source change the upgrade forces
• A gate failure after the work is committed landed as a new commit on the stack — nothing amended, rebased, or otherwise rewritten
• Every commit carries a body, and every body is one or two lines — none subject-only, none a paragraph
• Release PR mode: branch pushed, PR open — title = release commit subject; body = theme line, ## Changes in tag rules, ## Gates, changelog link last (via --body-file, no closing keywords)
• No hook bypassed with --no-verify
• Working tree clean, apart from step 1's reported exclusions
• No tag at HEAD, nothing pushed to main — release-and-publish owns both