fix(dashboard): show eval suite labels

[christso]

Summary

• Adds compact eval suite chips beside test IDs in the Dashboard All Evals table when a run contains multiple suites.
• Adds the same suite context to the eval-detail sidebar list for mixed-suite runs.
• Keeps single-suite runs quiet by suppressing repeated labels, and formats path-like suite names as compact file labels.

Validation

• bunx biome check apps/dashboard/src/components/EvalSuiteLabel.tsx apps/dashboard/src/components/RunDetail.tsx apps/dashboard/src/components/Sidebar.tsx apps/dashboard/src/lib/run-detail-context.ts apps/dashboard/src/lib/run-detail-context.test.ts
• bun test apps/dashboard/src/lib/run-detail-context.test.ts
• cd apps/dashboard && bun run build
• bun run build
• Push hook: package typechecks plus biome check .

Manual UAT

• Red on origin/main: same mixed-suite fixture showed All Evals test IDs without suite labels. Screenshot: /tmp/agentv-suite-labels-red-run-table.png
• Green on this branch: All Evals rows show compact github-actions / security-review suite chips. Screenshot: /tmp/agentv-suite-labels-run-table.png
• Green eval detail: sidebar list shows compact suite chips beside each eval. Screenshot: /tmp/agentv-suite-labels-eval-sidebar.png

Fixture used for UAT: /tmp/agentv-suite-labels-workspace/.agentv/results/runs/github-actions::2026-06-17T05-55-30-000Z/index.jsonl.

Bead: av-2s7.13

[christso]

Reviewed PR #1397 against origin/main at 2aa062c.

No blocking findings.

Checked:

• Suite label visibility is gated by shouldShowSuiteLabels, suppresses single-suite runs, and shows mixed or partial suite metadata without rendering empty Uncategorized chips.
• Path-like suite formatting compacts labels while preserving the full raw value in the title.
• All Evals and eval-detail sidebar links preserve project-scoped and non-project route params.
• Screenshot evidence exists in the private evidence branch and covers red run table, green run table, and green eval sidebar states.

Verification:

• bun test apps/dashboard/src/lib/run-detail-context.test.ts passed: 8 tests.
• Initial Dashboard build failed because this worktree did not have dependencies installed: tsc: command not found. After bun install --frozen-lockfile, cd apps/dashboard && bun run build passed.
• GitHub CI check rollup is green.

Residual risk: there is no automated render/layout test for very long suite labels or narrow/mobile sidebar widths; current UX evidence is desktop screenshot coverage only.

[christso]

Follow-up verification after installing dependencies in the review worktree:

• Ran bun install from the worktree root: completed with no package changes.
• Ran bun test apps/dashboard/src/lib/run-detail-context.test.ts: passed, 8 tests / 15 expects.
• Ran cd apps/dashboard && bun run build: passed.
• Verified git status --short --branch: clean tracked worktree, still at PR head 2aa062c7.
• PR CI check rollup remains green.

The earlier tsc: command not found build failure was caused by missing node_modules in this review worktree, not by the PR. Code review outcome remains unchanged: no blocking findings. Residual UX risk remains limited to lack of automated render/layout coverage for very long suite labels or narrow/mobile sidebar widths.