release: 0.17.0
Release prep for 0.17.0. No tag, GitHub release or npm publish in this pull request.
Version. 0.17.0, not 0.16.1. The two commits since v0.16.0 (1ff058b1 and db4216c8) add one capability to a shipped script: check-open-work.mjs reports a new group and a new resolvedLater field in its --json output. That is a new feature, not a bug fix, and earlier minor releases (0.14.0, 0.15.0, 0.16.0) were cut for the same kind of change. It breaks nothing: the exit code and every existing group are unchanged.
What changes.
CHANGELOG.md:## Unreleasedbecomes## 0.17.0 - 2026-10-17with an empty## Unreleasedabove it. The feature commit's entry and its fix (a commit made only of digits or letters) are one statement of final behavior, and it names the JSON field and the--repocondition for bare pull request numbers.package.json: 0.16.0 to 0.17.0.
Audits (release-batching.md).
- Accuracy audit: README, banners, overview image and its alt text, SECURITY.md and the docs. None of them names the open-work check, a version number or a count this release changes, and none of those files changed since the 0.16.0 audit (the diff since the tag touches the changelog, one skill's
SKILL.md, its script and its test). No stale claim found. - Changelog audit: every term in the new entry was checked against
check-open-work.mjs: the group label, theresolvedLaterfield, therecheck:condition, the five token kinds, the 8-line cutoff, the "commit" or "sha" rule, the--reporule, the plan-text-only run and the unchanged exit code. - Not changed:
rules/modifiers/plan-files.mdtells the reader to check items the script lists as "possibly finished or due for a re-check". It stays accurate and does not name the new group; I left a shipped rule's text alone in a release-prep change.
Checks run locally, all exit 0. oxfmt@0.70.0 --check ., oxlint@1.85.0 . (one existing warning), node --test test/*.test.mjs (182 pass, 7 skipped), bun test test/ (558 tests, 0 fail), npm run check:package -- --bun (237 files), bun test skills/ (369 pass).
Landing follows the standing exception for review bots, plus the Greptile check read by hand; CI still has to be green.
Summary by cubic
Prepares the 0.17.0 release by bumping the version in package.json and updating CHANGELOG.md. The changelog entry consolidates the new resolvedLater group and the commit-matching fix into one statement of final behavior. No tag, GitHub release, or npm publish happens in this PR.