To address the issue where a booker can reschedule and cancel unconfirmed events directly from the email, it's crucial to implement a series of checks and updates in the application's logic. Here's a concise plan to resolve this bug:

1. Verify Event Confirmation Status: Ensure actions are only allowed for events with the appropriate confirmation status.
2. Check User Permissions: Confirm that the user has the necessary permissions to perform the action.
3. Respect Event Type Rules: Adhere to specific rules related to the event type, especially for events requiring confirmation or involving round-robin scheduling.
4. Handle Round-Robin Scheduling: Properly manage events that could be reassigned to a different host upon rescheduling.
5. Update External Calendar Events: Make sure any changes are reflected in linked external calendars.
6. Send Appropriate Notifications: Notify all relevant parties about the rescheduling or cancellation.
7. Log Actions: Keep a record of all actions for auditing and debugging purposes.

For implementation, you might need to review and update the logic in the following parts of the repository:

• Rescheduling logic in packages/app-store/vital/lib/reschedule.ts
• Rescheduling tests in packages/features/bookings/lib/handleNewBooking/test/reschedule.test.ts

This approach ensures that the application consistently enforces rules for unconfirmed events across both the app and email interactions, aligning with the expected behavior.

To continue the conversation, mention @dosu.