Problem
The release workflow runs the full test suite serially, including timing-sensitive perf tests, inside a 15-minute budget shared with qualification checks, audits, signing, and artifact work. CI already separates correctness tests from performance tests and uses parallel execution.
A release candidate should fail for deterministic correctness evidence, not shared-runner timing noise, and its timeout should come from a rehearsal measurement rather than an estimate.
Acceptance criteria
Related
Problem
The release workflow runs the full test suite serially, including timing-sensitive
perftests, inside a 15-minute budget shared with qualification checks, audits, signing, and artifact work. CI already separates correctness tests from performance tests and uses parallel execution.A release candidate should fail for deterministic correctness evidence, not shared-runner timing noise, and its timeout should come from a rehearsal measurement rather than an estimate.
Acceptance criteria
-n auto).perf-marked tests; CI remains the merge-time enforcement point for latency budgets.Related