feat: add execution status classification to eval results (#431)#436
Merged
feat: add execution status classification to eval results (#431)#436
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…431) Add executionStatus, failureStage, failureReasonCode, and executionError assertions to representative existing tests: - Success path: assert executionStatus === 'ok' - Provider throw: assert execution_error with agent stage - Provider raw.error: assert execution_error with provider_error code - Setup script failure: assert execution_error with setup stage - Successful workspace scripts: assert ok status Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
New test file covering all executionStatus classification paths: - Provider throw -> execution_error with agent stage - High score (>=0.8) -> ok - Low score (<0.8) -> quality_failure - Backward compatibility: error field still set alongside executionError - Threshold boundary tests at exactly 0.8 and 0.79 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add required executionStatus: 'ok' to makeFullResult() in baseline.test.ts to match the updated EvaluationResult type which now requires this field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…egation - Extract 0.8 threshold into QUALITY_PASS_THRESHOLD constant with classifyQualityStatus helper to prevent threshold drift - Scope byFailureStage/byFailureReason aggregation to execution_error results only (was iterating all results) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Deploying agentv with
|
| Latest commit: |
015b77d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://34345a56.agentv.pages.dev |
| Branch Preview URL: | https://feat-execution-status-431.agentv.pages.dev |
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
1 participant
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
executionStatus: 'ok' | 'quality_failure' | 'execution_error'as a required field onEvaluationResult, with optionalfailureStage,failureReasonCode, andexecutionErrorfor structured error detailerrorfieldTest Plan
Follow-up Issues
--retry-errorsCLI flagfail_on_errortolerance config🤖 Generated with Claude Code
Closes #431