[christso]

Summary

Dashboard no longer pretends it can serve arbitrary run folders or index.jsonl files as first-class sources. Passing a noncanonical direct source now fails at startup with actionable guidance to use the project's configured .agentv/results/runs/ source, --dir <project-dir>, or results: config, while one-off bundles are redirected to agentv results report.

The fix stays local to Dashboard source resolution: supported project auto-discovery and configured remote-results discovery still work, but the legacy positional source path is now treated as unsupported instead of being normalized into a manifest path. The CLI help text and Dashboard docs now describe that canonical run-source contract, and regression coverage exercises both direct run-directory and direct index.jsonl inputs with a WTG-style noncanonical fixture plus CLI-level failure assertions.

Test Plan

• bun test apps/cli/test/commands/results/serve.test.ts
• bun --filter agentv typecheck
• bun x biome check apps/cli/src/commands/results/serve.ts apps/cli/test/commands/results/serve.test.ts apps/web/src/content/docs/docs/tools/dashboard.mdx
• bun --filter @agentv/web build

Evidence

• Red (HEAD, direct run dir): Serving 1 result(s) from /tmp/.../wtg-dogfood-noncanonical-run/index.jsonl
• Green (this branch, same run dir): Error: Unsupported Dashboard source: /tmp/.../wtg-dogfood-noncanonical-run
• Red (HEAD, direct index.jsonl): Serving 1 result(s) from /tmp/.../wtg-dogfood-noncanonical-run/index.jsonl
• Green (this branch, same index.jsonl): Error: Unsupported Dashboard source: /tmp/.../wtg-dogfood-noncanonical-run/index.jsonl

---