Gate required evaluation cases - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
required: truesupport for individual gate cases.Rationale
Current AI-agent telemetry points to validation and human review as the bottleneck. Aggregate pass rates can hide a failed critical journey, so PMs need a release control for must-pass workflows like checkout, compliance, safety escalation, or executive-demo paths.
Evidence:
Validation
python3 -m pytest tests/test_evaluator.py -q- PASS, 14 passed.python3 -m pytest -q- PASS, 30 passed.python3 -m ruff check .- PASS, all checks passed.python3 -m mypy src- PASS, no issues found in 5 source files.python3 -m build- PASS, builtagent_release_gate-0.1.0.tar.gzandagent_release_gate-0.1.0-py3-none-any.whl.PYTHONPATH=src python3 -m agent_release_gate.cli evaluate --spec examples/spec.yaml --results examples/results.json --output /tmp/argate-required-pass.json --markdown /tmp/argate-required-pass.md- PASS, exit 0 withgate_passed: trueandrequired: trueonrefund_status.PYTHONPATH=src python3 -c 'import json, subprocess, sys, tempfile; from pathlib import Path; d = Path(tempfile.mkdtemp()); spec = d / "spec.yaml"; results = d / "results.json"; spec.write_text("global:\n minimum_pass_rate: 0.5\ncases:\n - id: critical_checkout\n expected_all: [\"approved\"]\n required: true\n - id: optional_status\n expected_all: [\"status\"]\n", encoding="utf-8"); results.write_text(json.dumps({"cases": [{"id": "critical_checkout", "response": "manual review needed"}, {"id": "optional_status", "response": "status ready"}]}), encoding="utf-8"); completed = subprocess.run([sys.executable, "-m", "agent_release_gate.cli", "evaluate", "--spec", str(spec), "--results", str(results)], capture_output=True, text=True); print(completed.stdout); print(completed.stderr); ok = completed.returncode == 1 and "Required cases failed: critical_checkout" in completed.stdout; sys.exit(0 if ok else 1)'- PASS, outer smoke exits 0 after confirming the CLI hard-fails the required case.node /Users/bwise/.openclaw/workspace/projects/humanizer/src/cli.js score -f README.md --ignore-code- PASS, 1/100.git diff --check- PASS.Note: an initial source-tree smoke without
PYTHONPATH=srcfailed withModuleNotFoundErrorbecause the package was not installed in that shell. The source-tree smoke commands above are the corrected validation path.