Thesis: In agent tooling, a version boundary can matter as much as a feature addition when it changes how teams run and maintain evaluations. The release names import verifiers.v1 as vf and vf-* CLI entrypoints as the forward path; it also removes the Pool harness and built-in Lean taskset.
Mechanism: By removing the legacy implementation and aliases, the release concentrates imports and CLI use on v1 rather than preserving parallel paths. It also adds E2B, Podman, and Apptainer runtime providers, while describing episodes streaming turn by turn through environment serving into Platform runs. The change therefore combines a migration boundary with additions to the runtime and evaluation workflow, rather than documenting a single isolated feature. Why now: The published v0.4.0 release makes this transition actionable for teams deciding whether to upgrade and what their existing workflows depend on.
First implication: Teams using Verifiers should audit imports, CLI entrypoints, and reliance on removed components before upgrading. Evidence boundary: The release note documents interfaces, removals, and listed capabilities, but supplies no adoption data or comparative evidence about performance or evaluation quality. First watch condition: Watch whether subsequent documentation or releases clarify migration paths for projects that still depend on v0 aliases, the Pool harness, or the built-in Lean taskset. This record is distinct because no prior New Runtime analytical record was supplied for this release.