Checkwright v0.14.0

2026-07-25

Checkwright is the verification layer under agent orchestration, and this release moves the lead’s model-tiering unit from the stage to the batch and adds the per-delta work-class label that makes a batch tierable — so an all-mechanical batch can be downgraded to a cheaper model while any design-bearing batch stays on the judgment tier. No gate lands or tightens; the change is in what the /spec and lead templates ask their sessions to do.

Tightened gates

None. No gate landed new or got stricter this release.

Renamed knobs

None. No knob was added, renamed, or removed.

Behavior changes

• lifecycle-kit/templates/skills/spec.md — /spec’s output contract now requires every delta in an amendment’s What changes section to carry a work-class tag (mechanical or design-bearing), applying delegation-kit’s unit-shape doctrine at authoring time. The label’s reader is the lead’s per-batch tier decision below. What a consumer reconciles: a copied-out /spec skill carries the old output contract with no work-class label — re-sync it, and begin tagging each delta so the lead binding has a batch’s work class to read.
• lifecycle-kit/templates/lead.md §Economics — the model-tiering unit moves from the stage to the batch: “Tier each stage to its work class” becomes “Tier each batch”, the lead reading a batch’s deltas’ work-class labels and downgrading an all-mechanical batch while keeping any design-bearing batch on the judgment tier. This resolves the prior self-contradiction with the “per-batch model tiering is the dominant window lever” bullet above it. What a consumer reconciles: a copied-out lead template carries the per-stage phrasing — re-sync to the per-batch unit, which reads the /spec work-class label above.

Upgrading

Replace the vendored kit directories wholesale at v0.14.0, then regenerate the generated artifacts — the pre-commit hook and the graph projection. Then run the full battery.

No allowed reds. This release tightens no gate, so a clean upgrade turns nothing red; the behavior changes above are template-level and reconciled by reading, not by a battery red.

The behavior changes above are declared for reading, not a mechanical scan. If a gate reds that this note does not name, the upgrade smoke was supposed to catch it first — open an issue, because that is a defect in the release rather than work for you.