refactor(docs): rename docs/skills → project, retain academic uses (4/4)#1245
Merged
Conversation
2f530a0 to
56265a9
Compare
…ic uses
PR 4 of 4 in the benchmark → project rename. Aligns documentation and skill
cards with the rename that landed in PRs 1–3, and adds a naming-convention
note to AGENTS.md so the project/benchmark distinction is durable.
Renamed (registry/workspace concept → "project"):
- apps/web/src/content/docs/docs/tools/studio.mdx
- "## Benchmarks Dashboard" → "## Projects Dashboard"
- "### Registering Benchmarks" → "### Registering Projects"
- "### Removing a Benchmark" → "### Removing a Project"
- CLI flag descriptions ("Register a benchmark by path", etc.)
- All `~/.agentv/benchmarks.yaml` references → `projects.yaml`
- YAML example `benchmarks:` top-level key → `projects:`
- `/api/benchmarks` URLs → `/api/projects`
- "Add Benchmark" / "single-benchmark view" / "multi-benchmark" text
- apps/web/src/content/docs/docs/evaluation/running-evals.mdx
- `benchmarks.yaml` in the "Lightweight config and cache files" list → `projects.yaml`
- AGENTS.md (Wire Format Convention section)
- YAML file list updated to `projects.yaml`
- HTTP response field examples updated to `project_id`
- TypeScript boundary example: BenchmarkEntry/BenchmarkEntryYaml → ProjectEntry/ProjectEntryYaml
- "Reading back" pointer: `packages/core/src/benchmarks.ts` → `projects.ts`
Added (new):
- AGENTS.md "Naming Convention: Project vs Benchmark" section between
TypeScript Guidelines and Wire Format Convention. Codifies the
distinction so future contributors don't re-conflate the registry
concept with academic eval-suite terminology.
Intentionally kept (academic / artifact / verb usages):
- benchmark.json per-run artifact and all references to it
(Agent Skills compatibility — different concept, different rename if ever).
- examples/*-benchmark/ directory names (benchmark-tooling, multi-model-benchmark,
offline-grader-benchmark, bug-fix-benchmark) — they really are eval suites.
- "benchmark agents" / "benchmark datasets" / "grader benchmarks" usages
(verb / academic ML sense).
- "Snapshot MCP for benchmarks" reference in AGENTS.md (academic).
Stacks on refactor/rename-pr3-studio. With this PR landed, the codebase
consistently uses "project" for the registry/workspace concept and
"benchmark" only for eval-suite or per-run-artifact usages.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
bccc35d to
edcc9d2
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
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
PR 4 of 4 in the benchmark → project rename. Stacks on #1244 (PR 3). Aligns documentation with the rename and adds a durable naming-convention note to AGENTS.md.
Renames (registry/workspace → "project")
Added
Intentionally NOT renamed
Test plan
Cumulative state of the rename (PRs 1–4)
With this PR landed, the full rename is done:
🤖 Generated with Claude Code