kit 5.20.0
Added
kit reviewis a structured verdict, not console output. The meta-runner
was print-and-return-bool:--jsonemitted four concatenated sub-documents
(the ADR stage ignored the flag entirely), and nothing machine-readable
described the audit as a whole.collectReviewnow runs every stage's shared
gate — check (via the newrunCheckGatecollection core), design
(runDesignGate), standards (runStandardsGate), ADR (runAdrGate) — and
returns oneReviewReport { ok, failed, stages: [{ stage, ok, summary, findings }] }. The CLI is a renderer on top;kit review --jsonemits ONE
document and exits 1 on red. Same discipline ascomputeCheckVerdict: the
collection can no longer fork between surfaces.kit reviewis now a pure
read —kit checkkeeps its CLI extras (PAL sync, attestation, hints,
scanner self-heal).kit_reviewMCP tool — the full audit for shell-less agents, serializing
the samecollectReviewreport.concise: truedrops pass/skip rows while
per-stage summary counts keep totals honest (nothing silently truncated).
Deprecated
kit_standardsleaves the MCP surface in kit 6.0 —kit_reviewruns
that gate as its standards stage; scoped runs (--category) go via
kit_run. With the five existing deprecations the surface lands at 10 tools
after 6.0. Both docs↔surface drift gates updated to pin the six.
Fixed
- The hook-skip sentinel's STAMPING half is now tracked. 5.19.0 shipped the
post-commit detector, but the pre-commit block that writes the sentinel it
reads existed only machine-locally (viakit fix) — so a fresh clone logged
a falsesentinel-missingskip on every commit (the 5.18.0 release commit is
a recorded example). Both halves now travel with the repo. Plus gitignore
hardening: kit's local state files (.kit-skipped-commits.jsonl,
.kit-audit.pending,.env.local.*),.opencode/alongside the other
agent-harness dirs, and.toml/extensionless-hook variants of the cloud-sync
conflict-copy patterns.
Full changelog: https://github.com/sandstream/kit/blob/v5.20.0/CHANGELOG.md
Verify this release:
git tag -v v5.20.0
npm audit signatures