testing
- The secret filter made my security test pass
A guard test passed on the old code in one agent. Its secret mask had eaten the marker that meant 'ran'. Then the fix passed for a different wrong reason.
- The fix was in five agents. The sixth never called it.
A guard fix was unit-tested in both implementations and probed on one agent. Per-agent end-to-end cases found the one agent whose hook never ran it.
- Tests that could not fail
I broke my agent guard on purpose so its 'ask' meant 'allow'. Two new tests still passed on another layer's say-so; a third passed on the old code too.
- My unit tests never typed `; echo`
Fixing a guard's false positives exposed a hole, and the tighter rule passed every unit case. Then four agents failed one near miss: the command had a tail.
- My guard blocked bash -c. Models write bash -lc.
A regex guard for auto-approved coding agents denied bash -c 'rm -rf build' and allowed bash -lc. The end-to-end case had used the first spelling.
- Bun's fetch had no way to skip the proxy
With HTTP_PROXY set, my agents found no local models: fetch sent the LAN request to the proxy. Bun 1.3.10 had no per-request way out, and end() lost the reply.
- An exception in one layer deleted a block in another
Letting my agents delete extraction folders made a config generator drop a deny glob. That glob had been the only thing stopping $(echo rm) -rf in one agent.
- The proxy said unloaded. The model was loading.
A context probe gave up on four models loading behind my LLM proxy: its status was a snapshot up to 30 s old. Then a 336 ms stream timed at 120 s.
- The model that only says RUN
A fake model drove six coding-agent harnesses through dangerous commands. One block I had credited to a deny rule came from print mode having nobody to ask.
- A directory-only diff is not an empty directory
Verified-restore archiving lost two test fixtures: a global *.log ignore hid them from git, and the diff showing their missing directory was read as empty.