feat(results): materialize per-test task bundles#1330
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
AgentV runs can now carry a native, per-test task bundle beside each result row. Instead of a parallel run-source schema, each completed result can point from
index.jsonltotask/EVAL.yaml,task/targets.yaml, copied input files, and copied grader assets, giving future audit/rerun flows a normal AgentV eval contract to consume.This hard-deprecates the unreleased
run-source.jsonsurface rather than preserving a compatibility reader. Historical runs still load without task metadata; new bundle-capable runs expose focused index links (artifact_dir,task_dir,eval_path,targets_path,files_path,graders_path) and Dashboard file APIs can traverse those task paths.Key design choices:
task/folder, not run-level source/recipe JSONEVAL.yamlplus selectedtargets.yaml${{ ENV_VAR }}placeholders; redact literal secret-looking values and secret files.agentv/resultsunder the test artifact folder ortask/task/EVAL.yamlpreserves the selected target nameVerification
bun test apps/cli/test/commands/eval/task-bundle.test.ts apps/cli/test/commands/eval/artifact-writer.test.ts apps/cli/test/commands/results/serve.test.ts apps/cli/test/commands/results/combine.test.ts(128 pass)bun --filter agentv typecheckbun --filter @agentv/core typecheck && bun --filter @agentv/phoenix-adapter typecheck && bun --filter agentv typecheck, thenbiome check .Red/Green UAT
Used the same dry-run eval with
input_filesonorigin/mainand this branch. The dry-run quality score was the same on both sides; the checked behavior was artifact materialization.origin/main)index.jsonlhad notask_dir; notask/EVAL.yaml; no copied task file (/tmp/agentv-red-uat.nlqOYC)index.jsonlincludedtask_dir,eval_path,targets_path, andfiles_path;task/EVAL.yamlpreservedtarget: mock-target; the fixture was copied undertask/files/external/...; no nested.agentv/results(/tmp/agentv-green-uat.SKAgFt)