feat(results): restructure AgentV run artifacts#1513
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
c799beb
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://62dff0da.agentv.pages.dev |
| Branch Preview URL: | https://strict-vercel-results.agentv.pages.dev |
christso
changed the title
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
AgentV run bundles now use
index.jsonlas the discovery anchor and rootsummary.jsonas the run-level aggregate. The old rootbenchmark.jsonfile is no longer written or read; local discovery, git-backed remote discovery, CI gating, exports, comparison/reporting, Dashboard loading, and WIP resume metadata now use the summary/index contract.The layout keeps AgentV-specific value where it belongs: per-case
summary.jsonremains, eachrun-N/keepsresult.json,grading.json, metrics, timing, transcripts, and outputs, and repeat-run rows remain inspectable in the Dashboard. The Dashboard table also preserves the intendedTarget,Suite,Scoreorder and renders repeat-run detail rows.Results publishing now treats existing checkout remotes as user-owned state. AgentV writes result refs through the configured remote name, defaulting to
origin, but does not add or rewrite remotes in an existing checkout.Validation
bun test packages/core/test/evaluation/results-repo.test.tsbun test apps/cli/test/commands/results/serve.test.tsbun test apps/dashboard/src/lib/result-table.test.tsbun --filter @agentv/core typecheckbun --filter agentv typecheckbun run lintcd apps/dashboard && bun run buildStatus, Expand, Test ID, Target, Suite, Scoreand repeat detail content forrun-1/run-2.