Release v0.33.0 · qualitymd/quality.md

v0.33.0 - 2026-07-15

Evaluation concurrency now comes from the selected evaluator transport rather
than host CPU count: harness and Codex default to four, while Claude remains
sequential. Workspace evaluation.concurrency stays the only configuration
override and is clamped by any evaluator maximum; no CLI flag is added.
Direct evaluator runs now create their immutable manifest with the selected
evaluator before issuing work and use a completion-driven bounded pool. Each
accepted result is persisted before its slot is refilled, so fast calls no
longer wait behind the slowest sibling and accepted work survives
interruption. Harness runs retain their bounded rolling request window.
evaluation.json advances to schema version 9 with structured dispatch
capabilities and concurrency provenance. In-flight version-8 runs must be
started again; completed historical artifacts remain historical records.

Harness evaluation may assign one self-contained outstanding request to each
native worker while the parent keeps graph, artifact, quality-control, and
retry authority. Progress distinguishes the runner's outstanding cap from
requests actually dispatched.

In-flight schema-version-8 evaluation runs cannot resume under v0.33.0 and
must be started again. Completed version-8 artifacts remain historical data;
there is no migration or dual reader.
Automatic evaluation concurrency no longer follows host CPU count. Harness
and Codex default to four; Claude is sequential even when a higher workspace
cap is configured. Set positive evaluation.concurrency in workspace
configuration when a lower explicit cap is required.

Compatibility: