feat(config): hard-break dashboard project schema

[christso]

Summary

Closes #1354.

• hard-breaks $AGENTV_HOME/config.yaml project entries to the new GitHub owner/name schema: repository, ref, results.repository, results.local_path, and results.sync.auto_push
• removes project-registry support for legacy source and project results.mode/repo/path/auto_push fields, with validation errors that point to the new fields
• maps internal camelCase project results into the existing results-repo sync internals and resolves project GitHub owner/name values to https://github.com/<owner>/<name>.git
• updates Dashboard docs with before/after migration examples

Testing

• bun test packages/core/test/projects.test.ts packages/core/test/project-sync.test.ts packages/core/test/evaluation/validation/config-validator.test.ts
• bun test apps/cli/test/commands/results/serve.test.ts
• bun run build
• bun run lint
• bun run typecheck
• bun run test

Red / Green UAT Evidence

• Red (origin/main): the global config validator test accepted project entries using legacy results.mode, results.repo, results.path, and results.auto_push; project sync tests expected source.url/source.ref.
• Green (this branch): validateConfigFile now rejects each removed project legacy field with migration guidance, and the new project schema round-trips through registry load/save while syncProject resolves EntityProcess/agentv to https://github.com/EntityProcess/agentv.git.

Review Notes

• Manual Tier 2 fallback review completed because no ce-code-review runner/subagent executable is installed in this harness. No actionable findings found.
• Beads tracker commands were unavailable in this session (bd where reported no active beads workspace / no BEADS_DIR), so tracker comments could not be recorded.

Post-Deploy Monitoring & Validation

• Log searches: source was removed, results.repo was removed, results.path was removed, results.auto_push was removed, no repository defined, no ref defined.
• Metrics/dashboards: watch Dashboard project sync success/error counts and remote results status responses for configured projects.
• Healthy signals: new-schema project configs validate cleanly; project sync clones from https://github.com/<owner>/<name>.git; remote result status remains configured: true for projects with results.repository.
• Failure signals: spike in config validation errors for new-schema files, projects unexpectedly reporting configured: false, or git clone failures from malformed GitHub URLs.
• Mitigation: migrate affected $AGENTV_HOME/config.yaml entries using the docs before/after mapping; rollback by reverting this PR if new-schema configs fail unexpectedly.
• Window/owner: monitor first 24 hours after deploy by the Dashboard/config owner.

[cloudflare-workers-and-pages]

Deploying agentv with    Cloudflare Pages

Latest commit:	d96c88d
Status:	✅  Deploy successful!
Preview URL:	https://d889a161.agentv.pages.dev
Branch Preview URL:	https://feat-1354.agentv.pages.dev

View logs