feat: prefer the Weekly valuation + streams report starter template

[sweetmantech]

Part of #1850 (video/experience parity, item 3 — starter template includes valuation).

What

• lib/home/findStarterTemplate.ts: the homepage starter task's preference chain is now "Weekly valuation + streams report" → "Weekly Performance Dashboard" → any Report-tagged template → hidden. The previously preferred dashboard template has no valuation in its prompt (platform stats only), so the starter task never matched the video's valuation-report flow.
• TDD: new preference test added RED first, then the implementation (4/4 tests in lib/home/__tests__/findStarterTemplate.test.ts).

Template data (already live)

The new /agents template was created in production via POST https://chat.recoupable.dev/api/agent-templates:

• id ad0a233b-5f6d-4b91-89a6-90a1a8ecfd94, title "Weekly valuation + streams report", tags ["Report"], is_private: false
• Prompt asks for (a) current estimated catalog valuation with low–high range + week-over-week change, (b) top-track streaming numbers with week-over-week deltas, (c) every cited number linked to its source (house rule for task emails).
• Verified publicly listed via GET /api/agent-templates.

Verification

• pnpm vitest run — 33 files / 127 tests pass
• pnpm exec tsc --noEmit — 8 errors, identical to the pre-existing main baseline (none in touched files)
• Pending: fresh-account live verification of the full starter flow is still blocked by the Privy test-app cap on preview deployments (known pending check from Valuation-first homepage (Catalog HQ): surface catalog value + task runs on chat home; fix the .dev cross-domain auth regression #1850).

Siblings

Cross-repo valuation derivation guard (item 2 of #1850): recoupable/api#765 and recoupable/marketing#44 share a byte-identical golden fixture.

🤖 Generated with Claude Code

---

Summary by cubic

Make the homepage starter task prefer the "Weekly valuation + streams report" template, with fallbacks to "Weekly Performance Dashboard" and then any "Report"-tagged template. Aligns the starter flow with the valuation report experience from #1850 while keeping the card visible during rollout.

• New Features
  • Implemented new preference chain in lib/home/findStarterTemplate.ts.
  • Added tests for top preference and dashboard fallback in lib/home/__tests__/findStarterTemplate.test.ts.

^{Written for commit 33b29d6. Summary will update on new commits.}

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat	Ready	Preview	Jul 7, 2026 11:08pm

[coderabbitai]

Warning

Review limit reached

@sweetmantech, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 94ad1dda-fcb4-420d-b99b-6bee05b7f7c0

📥 Commits

Reviewing files that changed from the base of the PR and between 8474780 and 33b29d6.

⛔ Files ignored due to path filters (1)

• lib/home/__tests__/findStarterTemplate.test.ts is excluded by !**/*.test.* and included by lib/**

📒 Files selected for processing (1)

• lib/home/findStarterTemplate.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/starter-valuation-template

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Changes the preferred starter template order in a small, isolated function with updated tests. Low risk: only affects template selection for the homepage starter task.

Re-trigger cubic</sub>