Checkwright

Checkwright v0.33.0

2026-10-24

Checkwright catches reproducible classes of unsupported claims in coding-agent delivery before merge, and this release lets you install the checks for yourself on a project that does not adopt Checkwright, and adds a workflow profile carrying the stage machine without the document checks.

In brief

Section Entries Who acts
New and tightened gates 0 everyone: these may red on upgrade
Knob changes 0 if you set knobs
Gate-authoring changes 0 if you write or shadow gates
Platforms 0 if you install on a listed platform
Behavior changes 2 if you depend on a listed behavior
  • On a project that does not adopt Checkwright, checkwright init --personal installs the checks for you alone: the files stay untracked, listed in your clone’s .git/info/exclude, and nothing is committed to the project.
  • A new workflow profile gives you the stage machine and the recorded test runs without the document and site checks.
  • Nothing to reconcile on upgrade: no gate is new or stricter, and no knob moved.

New and tightened gates

None.

Knob changes

None.

Gate-authoring changes

None.

Platforms

None.

Behavior changes

  • installer init --personal — new flag on init and update: installs the checks for this clone alone. It writes what init writes, untracked, lists every recorded path and checkwright.lock in a marker-bounded block in the clone’s info/exclude, and stages and commits nothing; a bare re-run keeps the mode. It takes starter or prose, refusing a profile whose kits commit a process record, a planned path the index tracks, and --no-commit beside it. No CI workflow is seeded, prove refuses there and its help names the personal install, and uninstall removes the files and the block, committing nothing. Nothing to do unless you install for yourself on a project that does not adopt Checkwright.
  • installer --profile workflow — new profile: starter plus lifecycle-kit and evidence-kit, the stage machine and the recorded test runs without the document and site checks, the least on which prove catches a done claim. delegation now builds on workflow, its kit set unchanged. Nothing to do; move to it with init --profile workflow.

Upgrading

Replace the vendored kit directories wholesale at v0.33.0, or run checkwright update. Regenerate your generated artifacts; each freshness gate that reds prints its own regen command. Then run the full battery.

No allowed reds.

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.