feat(dashboard): identify result rows by eval path

[christso]

Summary

Dashboard run tables now use repo-relative eval_path as the visible Eval identity while preserving suite only as a legacy fallback for old run artifacts. Result drill-down links carry result_dir when available, falling back to eval-path-scoped identity so duplicate test_id rows from different eval files continue to open the correct artifact.

This keeps Experiments and Recent Runs centered on eval source identity without renaming unrelated benchmark concepts or the existing compatibility suite routes.

Validation

• bun test apps/dashboard/src/lib/result-table.test.ts apps/dashboard/src/lib/navigation.test.ts apps/dashboard/src/lib/run-detail-context.test.ts
• cd apps/dashboard && bun run build
• bun test apps/cli/test/commands/results/serve.test.ts
• bun --filter agentv typecheck
• bunx biome check ...touched dashboard/CLI files...
• git diff --check

Review Notes

• Spawned a code-review subagent before PR. It found duplicate-test-id sidebar active/link issues; this PR includes the follow-up fix so sidebar links and active states use result_dir/eval_path identity instead of bare test_id.

Post-Deploy Monitoring & Validation

• No runtime migration or service monitoring required. This is local Dashboard read-model/navigation behavior with legacy suite fallback retained for old artifacts.

Refs EntityProcess/agentv-beads#16 and bead av-504.4.

---

[cloudflare-workers-and-pages]

Deploying agentv with    Cloudflare Pages

Latest commit:	2007054
Status:	✅  Deploy successful!
Preview URL:	https://84347d1b.agentv.pages.dev
Branch Preview URL:	https://dashboard-eval-path-after-re.agentv.pages.dev

View logs