The lock's python cases assumed pytest was on the machine. On a runner without it the arbiter went red for a missing interpreter, four graded verdicts collapsed into no verdict at all, and the suite reported failures it had never measured. Each case now checks for the toolchain it needs, says which cases it did not judge, and refuses to print GREEN when it judged nothing.
A repair the arbiter could not grade the same way twice no longer writes REPAIR_OK. The screen already refused to certify it while the ledger recorded it as a success, so the held-repair counter included a coin flip. That run now carries its own event.