
Daily Digest
Block “done” if code changed after tests
Don't call it done if code changed after the last test run.
The technique
Agents sometimes edit code after the last green test, then claim the work is finished. A stop gate that asks “did anything change after the last passing test?” refuses stop when the answer is yes, so untested edits don't ship as done.
How it was tested
Offline structural sim (no live model): 8 freshness cases. Gate matched the expected allow/refuse decision on all 8 and caught 5 cases where a naive “always allow done” would have stopped after stale edits.