v0.5.2
TLDR. CI now lints every pull request against the conventions this template has always asked for but never enforced: the head branch must be <type>/<issue#>-<slug>, the body must close exactly one issue in this repository, that issue must exist, be open and be an issue (not a PR), and the branch's number must match the body's. A PR that submits the template's Closes #<!-- issue number --> as-is, or an empty Closes #, fails the required ci check and the failure names the line. Bot PRs are exempt by author (dependabot, github-actions) or by release-please's autorelease: pending label — never by branch name, which a fork author chooses. The logic is scripts/pr-lint.js (ADR-0008, same shape as the labeler), tested on every make check by scripts/pr-lint.test.js; the body is stripped of code fences, code spans and HTML comments before the Closes line is read, so an example in a fenced block cannot link an issue by accident.
The version is a patch, not a minor, on purpose: the gate landed as ci:, a hidden type, so this release exists only because the follow-up docs PR carried Release-As: 0.5.2 — and the docs it carries explain that rule (hidden types ship no release; when one is needed, Release-As is always the current version plus one patch). One consequence is visible right below: the changelog lists the docs PR that carried the footer, not the CI gate — release-please always renders the commit carrying Release-As, whatever its type, and omits the other hidden-type commits. The lint itself is #69.
If you upgrade: take .github/workflows/ci.yml (the Lint the pull request step and the widened on.pull_request.types), scripts/pr-lint.js, scripts/pr-lint.test.js, and scripts/check-node-tests.sh, which replaces scripts/check-issue-labeler.sh and now runs every scripts/*.test.js (delete the old script and update the check: line in the Makefile). Two things will bite if skipped: scripts/pr-lint.test.js asserts that the type list in AGENTS.md's Branch step equals the eight types the linter accepts (feat, fix, docs, chore, refactor, ci, test, perf), so that line must be updated with the kit; and any open PR whose branch or body does not follow the convention goes red on its next push or edit — fix the body (no push needed; edited re-runs the check) or rename the branch.