fix: exclude AWAITING_HOST from seed-insights random status selection

[eunjae-lee]

What does this PR do?

Fixes a bug in the seed-insights script where AWAITING_HOST status was randomly assigned to bookings along with a userId, which violates the correct behavior of instant meetings.

Problem:

• The seed script randomly picked from all 5 booking statuses (including AWAITING_HOST)
• When AWAITING_HOST was selected, the script still assigned a userId
• Real instant meetings with AWAITING_HOST status should have userId = NULL until a host joins
• This created incorrect test data that doesn't match production behavior

Solution:

• Filter out AWAITING_HOST from BookingStatus values using Object.values(BookingStatus).filter()
• This approach is more maintainable than listing valid statuses explicitly - if new statuses are added in the future, they will automatically be included
• Moved validStatusesForSeed to module level so it's calculated once at load time instead of on every shuffle call
• Added comments explaining why this status requires special handling

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - seed script only.
• I confirm automated tests are in place that prove my fix is effective or that my feature works. N/A - this is a seed script for test data generation.

How should this be tested?

1. Run the seed script: yarn seed-insights
2. Verify no AWAITING_HOST bookings are created with a userId:

SELECT COUNT(*) FROM "Booking" 
WHERE status = 'awaiting_host' AND "userId" IS NOT NULL 
AND "createdAt" > NOW() - INTERVAL '1 day';
-- Should return 0 for newly seeded data

3. Verify other statuses are still generated:

SELECT status, COUNT(*) FROM "Booking" 
WHERE "createdAt" > NOW() - INTERVAL '1 day' 
GROUP BY status;
-- Should show ACCEPTED, PENDING, CANCELLED, REJECTED (but not AWAITING_HOST)

Checklist

• I have read the contributing guide
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have checked if my changes generate no new warnings

---

Link to Devin run: https://app.devin.ai/sessions/08f634e7210d415982d71c8f687b4468
Requested by: [email protected] (@eunjae-lee)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[vercel]

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

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
cal	Ignored			Nov 26, 2025 4:14pm
cal-eu	Ignored			Nov 26, 2025 4:14pm

[cubic-dev-ai]

No issues found across 1 file

[github-actions]

E2E results are ready!

• Workflow #90318.1 latest results