bf0fbe4888
* feat: skip authentication check for reschedule bookings with validation - Skip checkBookingRequiresAuthentication when rescheduleUid is present - Add validation to ensure rescheduleUid points to a real booking - Verify booking status is ACCEPTED (upcoming) - Verify booking uses the same event-type - Throw appropriate errors for invalid reschedule attempts Co-Authored-By: morgan@cal.com <morgan@cal.com> * refactor: move reschedule validation logic into checkBookingRequiresAuthentication - Refactor checkBookingRequiresAuthentication to accept optional rescheduleUid parameter - Move reschedule booking validation logic inside the method - Simplify createBooking method by removing duplicate validation code - Maintain same validation logic: check booking exists, is ACCEPTED, and uses same event-type Co-Authored-By: morgan@cal.com <morgan@cal.com> * fix: allow PENDING bookings to be rescheduled - Update status validation to allow both ACCEPTED and PENDING bookings - Change error message to reflect both allowed statuses - PENDING bookings can now be rescheduled without authentication check Co-Authored-By: morgan@cal.com <morgan@cal.com> * refactor: separate reschedule validation from auth check - Extract validateRescheduleBooking method to handle reschedule-specific validation - Keep checkBookingRequiresAuthentication strictly for auth checks - Use conditional logic in createBooking: validate reschedule OR check auth - Improves code clarity by separating concerns per lauris's feedback Co-Authored-By: morgan@cal.com <morgan@cal.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>