Claim class: Current truth for release eval gating (WDD-002 precursor). Requires: WDA-004 wired at HEAD.
Agent behavior changes that ship in a release must pass an offline eval gate covering prompt regression, conversational-quality, and repo-map benchmark corpora before the release workflow proceeds.
| Corpus | Module | Tests |
|---|---|---|
| Prompt regression | teaagent.prompt_regression |
3 default cases |
| Conversational quality | teaagent.eval_corpus |
4 axes: clarification, interruption, correction, long-context recall |
| Repo-map benchmark | teaagent.eval_corpus + teaagent.governance.repo_map_benchmark |
1 deterministic fixture corpus case; critical-category coverage is required |
# Green path (should exit 0)
python scripts/run_release_eval_gate.py --root .
# Verify gate blocks on seeded failure (should exit 1)
python scripts/run_release_eval_gate.py --root . --seed-failure
# Verify repo-map critical failure blocks the gate (should exit 1)
TEAAGENT_EVAL_SEED_REPO_MAP_FAILURE=1 python scripts/run_release_eval_gate.py --root .
# Unit tests
python -m pytest tests/test_release_eval_gate.py -q- Tag releases:
.github/workflows/release.ymlruns the gate before packaging. - Evidence bundle:
scripts/build_release_evidence_bundle.pyincludes the gate inreleaseprofile.
- Gate report JSON:
--report dist/evidence/release-eval-gate.json(release workflow) - Eval store:
.teaagent/eval/under workspace root (gitignored)
- The default CLI/release workflow path still uses offline replay for prompt and conversational tests unless a
model_runneris injected; those runs are disclosed as simulated/advisory. repo_map_benchmarkis now in the release corpus through a deterministic fixture benchmark, and release gating blocks if any configured critical category has zero enabled tests.