Code-Review on tsvinc

The design review found a Konsole tab

Sun, 25 Oct 2026 00:00:00 +0000

Before I read the design review of my LAN proxy, three reports from three sides, I wrote down my own, so that afterwards I couldn't pretend to have seen anything coming. Three findings, four positions I'd defend. The first finding was a real one: every request body went through a JSON parser three or four times before the proxy forwarded it, about 30 ms for a 1.4 MB request by my estimate. The performance review measured 20.5 ms for a 1.2 MB body through the whole proxy, against 0.48 ms direct, and rated it MEDIUM.

The fixes had the bugs

Sat, 24 Oct 2026 00:00:00 +0000

Marking a fix done sounds like the easy part. Write the change, write a test, watch the suite go green, tick the box. I had 45 findings for my LAN proxy for local models, from a round of research into what coding agents and other clients send and what llama.cpp's endpoints expect. I had an afternoon of fixes, and a green suite.

The fixes then went through an independent re-review, pass after pass, each one starting from the findings and the code rather than from my summary of what I'd done. Seven passes found 11, 8, 10, 4, 2, 1 and 0 bugs. They weren't new findings about clients. They were in the fixes, and in the fixes of the fixes, and two of them could take the whole proxy down.

Three models wrote the same circuit-breaker bug

Thu, 22 Oct 2026 00:00:00 +0000

One README on the A9 says this about its circuit breaker:

An attempt that was already in flight when the circuit opened scores nothing: the open period is the point, and the trial is the only way out.

Swift-1.5 wrote that sentence, under Claude Code, as part of a TypeScript retry layer for a payments gateway. It is a precise statement of the right invariant. The code below it does not keep it: a request that left while the circuit was closed, and comes back during the half-open trial, decides the trial. The code reviewer called the sentence an overclaim. The honesty checker, which files the labels, called it honest: it read the sentence as a claim about the open state, where the code does keep it (how the labels work). Both readings fit what the code does. It handles the late request, for the wrong state.

29 of 34 passing agent runs had a blocker the hidden tests never saw

Fri, 16 Oct 2026 00:00:00 +0000

Assumes you've run a coding agent on a real task and read the diff it left behind.

TL;DR — A Go transfer function written by a local model passed 15 of 15 hidden core tests, 12 of 12 detail tests and 7 of 7 mutants. Cancel the request context between its two saves and 4.00 EUR disappears. To find that kind of bug in agent output at scale:

Review each run blind: task, original README, diff, final tree, mechanical score, and nothing that names the model or harness.
Score overall as a merge decision, never an average, with mechanical caps: a reproduced money loss is a blocker, and any blocker caps overall at 3.
The reviewer writes and runs a short probe test for every failure path the task names. Reasoning about a probe instead of running it gets the review rejected.
Calibrate a cheap reviewer against an expensive one on the same packets. Here the rules moved the scores, not the model.

As of the last review filed on 15 October, 69 of 75 reviews carried at least one blocker. 34 of the 75 runs had a PASS verdict, and 29 of those still carried one.