v0.27.0 — a check after an action is judged

This release closes a way a step could pass on the agent's word alone. Steps that act and then check are judged differently, which is why this is a minor.

A step that acts and then checks has its check judged

A step like "save the transaction by clicking "Add" and verify the first transaction has payee "Home Depot"" could end with the agent answering done after the click. The step then closed on the agent's own sentence about the page, and nobody judged it. On a real budgeting app's suite, 4 of 61 such steps closed this way, and on the demo app 5 of 35 on gpt-6-luna (#172).

A check verb after and, then, a comma or a semicolon now makes that done a claim the judge decides, as for an assertion. After the change, every such step was judged. The budgeting app's suite still passed 21 of 21, and the run cost about the same number of calls.

Upgrade note: a step of this shape that passed before only because nobody checked it can now fail. That failure is the point.

Reliability, measured again

The README's table was measured again on this change: no false FAIL and no false PASS on either reference model. The one false FAIL Haiku had on 0.26.0 did not recur.

Documentation

• An editable data grid needs one cell per step. The README shows a grid test written one cell per step in keyboard order. Written as one step, the same test failed 3 runs in 3; written this way, it passed 3 in 3 (#67).
• Jev measured as a judge. TypeSafe AI's decision model was replayed on the judge corpus (#174). Corrected after release: these notes first reported 34 of 41 cases right and 6 false PASSes. That run gave Jev the step without the [redacted NAME] rewrite and without the label check every LLM verdict gets. Measured with both, it got 40 of 41 and no false PASS. It writes no reason for a failed step, which the agent's retry reads, so it is not a drop-in judge. The write-up has the numbers and a script to measure a later version for about a cent.

Full entry in the CHANGELOG.