You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: rename dataset to suite across codebase (#944)
* refactor: rename dataset to suite across codebase (#943)
An eval file is a test suite (lifecycle hooks, workspace setup/teardown,
execution config), not a dataset (passive input/output pairs). This
renames the `dataset` field to `suite` everywhere:
- Core types: EvalTest.suite, EvaluationResult.suite
- Wire format: JSONL results write `suite` field
- CLI: --group-by suite, --suite flag, trace/trend/pipeline commands
- Studio UI: routes /suite/, labels "Suites", API endpoints /suites
- OTel: agentv.suite attribute
- Example baseline JSONL files updated
- Documentation and plugin skill files updated
Hard deprecation — no backward-compat aliases for `dataset`.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix(test): use platform-agnostic paths in pi-coding-agent tests
The tests used hardcoded Windows backslash paths which fail on Linux.
Use path.join and path.sep for cross-platform compatibility.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* docs: add Suites section to eval files documentation
Explains the suite concept as requested in #943 comment.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* fix: address code review findings from dataset→suite rename
- Fix missed verbose log "JSONL Dataset:" → "JSONL Suite:" in jsonl-parser
- Clean up stale "legacy" comment in discover.ts
- Rename internal datasetFile/datasetFilePath vars in check-eval-baselines script
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0 commit comments