testing
- My drift check said 0 differences. It checked 4 arrays.
My Go checker read a bash model config without running it and said 0 differences. It compared 4 arrays. The fail-closed rewrite found a missing output cap.
- In opencode 1.19.5, my workaround protected nothing
I renamed model keys so opencode wouldn't force top_p on my local models. In 1.19.5 it matches the id I sent anyway, and the qwen rule is gone.
- Another guard's test list found holes in mine
114 example commands from a separately built shell-parsing guard went through my regex guard. Most held. The worst gap was a guard that could quietly vanish.
- Five languages, two reps: the round-two ranking
Five local models in six setups, 144 coding-agent runs on one 128 GB box. Flash-Next leads in both quants, and the bugs line up by ticket.
- Nine accusations, one lie: re-reading round two's judges
137 reviewed local-model agent runs, 14 "false" verdicts from two judges. On the raw sessions 9 fell, 4 were about docs, and 1 was a lie.
- The race detector saw my requests in order
A mutant removed a lock in my Go proxy and survived -race. The test sent its requests one after another, and that order hid the unlocked read.
- My isolation guard checked itself
A guard meant to prove my Go tests couldn't reach the live proxy compared a path with the env var it guarded, and passed on any shell that had set it.
- The mutant was killed after it switched a real GPU
A hand-written mutant made my Go CLI skip -proxy. Its test failed on cue, after a real model load that then kept a benchmark off a GPU for almost half an hour.
- The lock map deleted a mutex someone was waiting on
A Go transfer by Flash-Next Q2_0 scored 100 and passed 6 of 6 failure-path tests. One cleanup line let a retried key move the money twice.
- The test rig was the unsafe part
A suite that tells six coding agents to run rm -rf and docker system prune had a throwaway HOME and bwrap --unshare-net. Neither isolated what it needed to.