LLMKube 0.9.19 shipped this morning, and it is the strangest release we have cut. About half of it exists because we caught our own agent pipeline lying to us, in four different ways at once. The other half was written by that same pipeline, after we fixed it. This is the honest version of how that went, because the interesting product is not the features, it is the compounding: every release since 0.8.0 has made this system measurably harder to fool, and this is the release where that loop visibly closed on itself.
Nine files, full test coverage, zero callers
It started with a routine backlog triage. Twenty-five issues were sitting open with merged PRs attached, each honestly labeled "not wired into a running pipeline yet." When I checked what that actually meant, the answer was worse than a stale backlog: nine files on main, each fully unit-tested, each with zero production callers. Verdict rails, audit collectors, a staleness detector. Written, reviewed, merged, and completely inert.
The uncomfortable part is why nothing caught it. Go does not warn about unused package-level functions. Our linter's unused checker treats a function as used if tests reference it, and these files had excellent tests. A thoroughly-tested dead function is invisible to every standard gate. The tests are what hid the bodies.
