Skip to content

v2.2.1 — check-registry schema hotfix

Choose a tag to compare

View all tags
@lasswellt lasswellt released this 30 May 17:23
· 54 commits to main since this release
v2.2.1
1bc7867

[2.2.1] — 2026-05-30 · fix check-registry schema (v2.2.0 hotfix)

v2.2.0's LANE-1 re-laned 41 rows to lane: semantic but left detection.type: command and one verdict_authority: reject — which the check-registry-validate CI gate rejects (semantic rows must be detection.type: semantic + verdict_authority: advisory). The gate runs in CI only and was not run locally, so v2.2.0 shipped with a schema-invalid registry (red CI on main).

Fixed

  • check-registry.json — the 41 semantic design rows now carry detection.type: "semantic" (the npx impeccable detect command is retained on the row) and verdict_authority: "advisory" (design-low-contrast was reject). Registry passes hooks/scripts/check-registry-validate.sh (90 checks, derivation clean).
  • hooks/tests/design-pillar.bats — added two guards that run the CI schema validator + assert every semantic design row is type:semantic/advisory, so this class of drift fails locally (suite 57→59).
  • .github/workflows/{ci,publish}.yml — actions/checkout + actions/setup-node bumped v4 → v5 (Node 24 compat; silences the Node 20 deprecation warning).
Assets 2
Loading