docs(results): clarify remote sync CLI contract#1345
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
f2dc402
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://233aa1b4.agentv.pages.dev |
| Branch Preview URL: | https://feat-remote-results-cli-cont.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
The remote results contract is now explicit:
agentv resultsis for local run workspaces, while manual remote status/sync stays with Dashboard/API and eval auto-export covers the publisher path.This avoids adding a second CLI sync surface for project-scoped git behavior that already has a production API contract, while giving users concrete automation endpoints and a direct recovery escape hatch.
What changed
docs/plans/2026-06-10-remote-results-cli-contract.md.agentv results --helpwording to “local evaluation results” so the CLI surface matches the decision.Red/green evidence
bun apps/cli/src/cli.ts results --helpdescribed the command asInspect, export, and manage evaluation resultswhile listing only local subcommands.Inspect, export, and manage local evaluation resultsand still lists only local result artifact subcommands.Verification
bun apps/cli/src/cli.ts results --helpbun test ./test/commands/results/serve.test.ts ./test/commands/results/summary.test.tsfromapps/cli— 92 passbun --filter agentv test— 606 passbunx biome check apps/cli/src/commands/results/index.ts apps/web/src/content/docs/docs/tools/results.mdx apps/web/src/content/docs/docs/tools/dashboard.mdx docs/plans/2026-06-10-remote-results-cli-contract.mdbun --filter agentv typecheckbun run lintCode review: skipped (no Tier 1 tool; Tier 2 criteria not met for a small docs/CLI-help wording change).
Post-Deploy Monitoring & Validation
No additional operational monitoring required. This is a documentation and CLI help contract clarification; runtime remote sync behavior is unchanged.