How do you know the agent isn't quietly rotting your codebase?

Agent-written code passes review and still erodes a system. Four mechanisms in Kiwipow Agent that answer it with evidence rather than with trust.
Thoughts and ideas about architecture and programming

Agent-written code passes review and still erodes a system. Four mechanisms in Kiwipow Agent that answer it with evidence rather than with trust.
mount, flush, fakeServer and mountRouting. The four helpers that let an agent verify a page the way the app uses it, from vitest, without a server or a browser.
An MCP server that finds duplicated code by meaning, ranks it by what it costs to keep, and hands the worst of it to my AI agent.
A template that cannot resolve a path renders an empty string. For a human that is a blank spot on the page. For an agent it is a green test. Here is how the…
Plain custom elements, a synchronous lifecycle, nothing re-renders on its own, and typed events. Four rules, each chosen because a reviewer can check it by…
Documentation tells an agent how a library works. A skill tells it what it will get wrong from habit. Keeping the two apart is what makes either one useful.
Coding agents write better Vue and Angular than they will ever write for my library. I use the library anyway, and this is the honest version of why.
Live API specs for coding agents An agent writing frontend code has to know the backend's...
I love coding my own stuff, and my clients typically have lots of internal specifications and...
Have you created a class library for tests with XUnit and .NET standard? Doesn’t it work?