fix(results): publish runs at results branch root#1620
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
44f8b0c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://70bda53d.agentv.pages.dev |
| Branch Preview URL: | https://feat-results-branch-root-lay.agentv.pages.dev |
christso
force-pushed
the
feat/results-branch-root-layout
branch
from
b95da6e to
3a8d744
Compare
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
Published Git results now land directly at the
agentv/results/v1branch root as<run_id>/instead of under an extraruns/<run_id>/wrapper. Branch readers, cache indexing, WIP checkpoints, sidecar artifact keys, sync safety checks, and Dashboard sync copy now use that branch-root layout while preserving ADR-0017 run-bundle internals when present, including<run_id>/.internal/index.jsonland.indexes/*.jsonl.Mutable
metadata/runs/<run_id>/tags.jsonoverlays were removed from the published branch path. Tags are treated as read-only run metadata fromsummary.jsonand index rows.Related: av-i3zw
Validation
bun test apps/dashboard/src/lib/project-sync-status.test.ts packages/core/test/evaluation/results-repo.test.ts packages/core/src/evaluation/results-repo-cache.test.ts-> 81 pass.bun run build-> passed afterbun installpopulated this worktree's dependencies.git diff --check-> passed.Dogfood
Attempted one-case live eval publishing to a temporary local results repo at
/tmp/agentv-results-root-dogfood-ybAouK/results-repowith--results-branch agentv/results/v1 --no-results-push. The run published locally toagentv/results/v1:dogfood-results-root-layout;git ls-treeshowed branch-root layout with top-level.gitattributesanddogfood-results-root-layout/, with noruns/wrapper.Live provider dogfood did not complete because the copied primary
.envhasOPENAI_API_KEY=dummy; the CLI failed withHTTP 401 Incorrect API key provided: dummy. The publishing path still ran and produced the branch-root evidence above.Post-Deploy Monitoring & Validation
No additional production monitoring required; this is local/CI Git results publishing behavior. After merge, validate with the next real eval publish by checking that
agentv/results/v1contains<run_id>/summary.json, noruns/<run_id>/wrapper, and nometadata/runs/<run_id>/tags.jsonoverlay.