Expand demo seed data with realistic multi-tracker showcase

[panteLx]

Summary

• Rewrites scripts/seed.ts to generate a realistic, English demo dataset covering every tracker feature, for use as showcase data (e.g. screenshots/Reddit).
• Five trackers, each demonstrating something different:
  • Personal Finances — solo tracker, ~20 months of history (salary, rent, groceries, travel, freelance income, savings transfers)
  • Shared Apartment — multi-member tracker exercising all four permission levels (owner/admin/write/read)
  • Community Fundraiser — public tracker (isPublic: true) with donation and event-expense patterns
  • Freelance Business — USD currency, Discord webhook configured (placeholder URL)
  • Road Trip 2023 — archived + hidden tracker with a short fixed transaction history
• Schedules on every active tracker across all three frequency types (monthly/yearly/custom_days), with a mix of overdue/due/upcoming due dates and backfilled history correctly linked via scheduleId/source: "schedule".
• Transaction amounts/dates are generated with a small seeded PRNG for organic-looking but reproducible data, and the whole script stays idempotent (safe to re-run against an already-seeded DB).
• Also ignores the local .ads notes folder in .gitignore.

Test plan

• npx tsc --noEmit passes
• Ran scripts/seed.ts against a throwaway copy of the dev database and verified: schedules span all frequency types with overdue/due/upcoming statuses, transaction counts/date ranges per tracker, source='schedule' linkage, tracker flags (is_public/is_hidden/discord_webhook_url/currency), and permission levels per member
• Re-ran the script a second time against the same copy to confirm idempotency (no duplicate rows)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 9 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 21baa146-5df7-4526-bb7a-f026fddf69c5

📥 Commits

Reviewing files that changed from the base of the PR and between 4da2ea0 and 72a9b6a.

📒 Files selected for processing (2)

• .gitignore
• scripts/seed.ts

---

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.}