Better reviews for AI-written code

A two-agent, evidence-gated approach to reviewing AI-generated code while the implementation can still change.

The distillation spent most of its time with one role waiting on the other. Both roles now start together, the two-batch cap is enforced, and a waiting reviewer is told when to stop.

1.0.3 reached npm and stopped there, missing from the MCP registry and the releases page with nothing able to finish it. Also: the cache purge that failed every deploy.

A .reviewer/ folder holds what only your repository knows to ask. Published to npm, but not to the MCP registry or the releases page; 1.0.4 fixed that.

On wide displays the two-column layouts sat centred in a gutter that grew with the window, and at some widths the diff got less room than it had in one column.

Intent Documents are now written in points instead of paragraphs. Underneath: three ways the interview silently lost its answers.

A paged session spine, an interview the server can attest from both sides, and the schema fix that made every submission fail.

The flow died on exactly the changes big enough to deserve a document. Paged diffs, hunk-id anchors, a run handle that survives a restart.

Written during a tool call, they could not be dispatched until the next session — so agents simulated the split without the allowlist that enforces it.

The guide told agents to run a CLI that could not detect their client, so they wrote subagent files into whatever repository they happened to be in.

Two releases had broken on cross-file invariants no generator owns. Separately: why npx-based servers show as not connected in GUI editors, with no error.

server.json had drifted two versions behind npm, and the registry could not verify the package was ours.

The npm README listed five tools where the server registers ten, and never mentioned that half the product is a GitHub App. The privacy claim was overstated too.

npm i -g npm@latest made every release depend on whatever npm shipped that hour.

git tag creates a lightweight tag; git push --follow-tags only pushes annotated ones.

npm version inside a workspace package bumps package.json and silently does nothing in git.

Three files carried a version and the release bumped one, so 0.2.2 shipped a server that reported itself as 0.2.1.

The publish workflow depended on a secret that was never set, and never attached the .mcpb the README links to.

The format, the validator, the MCP server and the guided-review app — and the decision to retire the GitHub Action.