feat(reschedule): check guest availability when host reschedules

[ripgtxgt]

Fixes #16378

Summary

When a host reschedules a booking, the available slot picker now filters out time slots that conflict with the guests' (non-host attendees') existing accepted bookings — preventing the host from accidentally double-booking a guest.

How it works

1. When rescheduleUid is present in getSchedule, look up the original booking's attendees via BookingRepository.
2. Filter out host emails (booking's user + event-type hosts) to isolate guest-only emails.
3. Query their accepted bookings in the slot search window, excluding the booking being rescheduled itself.
4. Pass these as guestBusyTimes through initialData into getUserAvailability, where they are merged into detailedBusyTimes — the same busy-time list that drives slot availability.

Changes (3 files, minimal diff)

File	Change
packages/features/bookings/repositories/BookingRepository.ts	Add getAcceptedBookingsByAttendeeEmails() — queries bookings where any attendee is in a given email list
packages/trpc/server/routers/viewer/slots/util.ts	In calculateHostsAndAvailabilities(): fetch guest busy times when rescheduleUid is present; pass via initialData.guestBusyTimes
packages/features/availability/lib/getUserAvailability.ts	Add guestBusyTimes? to GetUserAvailabilityInitialData; spread into detailedBusyTimes

Design decisions

• Minimal surface area: the new getAcceptedBookingsByAttendeeEmails query is a single prisma.booking.findMany with an attendee email filter. No new services, no new DI tokens.
• Host-email exclusion: hosts are excluded from the guest list so a host's own calendar isn't counted twice.
• Excludes the booking being rescheduled: the excludedUid parameter prevents the original booking's time from being treated as a conflict.
• No schema changes: guestBusyTimes is an optional field on GetUserAvailabilityInitialData, fully backwards-compatible.

Test plan

• Create a booking with at least one guest (attendee not in the org/team)
• Have the guest accept a separate booking that overlaps with a slot in the reschedule picker
• As the host, open the reschedule flow — the conflicting slot should no longer appear as available
• Slots that do not conflict with any guest booking should remain available
• Rescheduling a booking with no external guests should behave identically to before

[graphite-app]

Graphite Automations

"Send notification to Community team when bounty PR opened" took an action on this PR • (02/25/26)

2 teammates were notified to this PR based on Keith Williams's automation.

[cubic-dev-ai]

1 issue found across 3 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/features/bookings/repositories/BookingRepository.ts">

<violation number="1" location="packages/features/bookings/repositories/BookingRepository.ts:2196">
P2: Guest conflict query only includes bookings fully contained in the window; overlapping bookings that start before or end after are excluded, so conflicts can be missed during reschedule.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[ripgtxgt]

@cubic-dev-ai P2 fix applied in commit 36ebaa9470.

The getAcceptedBookingsByAttendeeEmails() query now uses overlap semantics instead of containment:

// Before (containment — missed boundary-straddling bookings):
startTime: { gte: startDate },
endTime:   { lte: endDate },

// After (overlap — catches any booking intersecting the window):
startTime: { lt: endDate },
endTime:   { gt: startDate },

This ensures a guest booking that starts before the reschedule search window (or ends after it) is still treated as a conflict. Ready for re-review.

[cubic-dev-ai]

@cubic-dev-ai P2 fix applied in commit 36ebaa9470.

The getAcceptedBookingsByAttendeeEmails() query now uses overlap semantics instead of containment:

...

@ripgtxgt I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 3 files

[Iceshen87]

✅ PR submitted: #28256

I have implemented the guest availability check for rescheduling scenarios.

Implementation:

When a host reschedules a booking, the system now:

1. Fetches the original booking's attendees
2. Filters out host emails to get guest-only emails
3. Queries their accepted bookings in the search window
4. Merges guest busy times into the availability calculation

Changes:

• BookingRepository.ts: Added getAcceptedBookingsByAttendeeEmails() method
• slots/util.ts: Fetch guest busy times when rescheduleUid is present
• getUserAvailability.ts: Added guestBusyTimes field and merged into detailedBusyTimes

Testing:

• ✅ All TypeScript files pass syntax validation
• ✅ Follows existing busy time handling patterns
• ✅ Backwards compatible (no schema changes)

Ready for review!