fix: Make BOOKING_CANCELLED` webhook payload consistent for regular cancellation and request-reschedule flow

[alishaz-polymath]

What does this PR do?

Fixes inconsistencies in the BOOKING_CANCELLED webhook payload when triggered via the "Request Reschedule" flow vs regular cancellations.

Issues Fixed:

1. Missing organizer.id - The usersToPeopleType() function in requestReschedule.handler.ts was not including the id field when converting users to Person objects, causing intermittent organizer.id missing errors for webhook consumers.

2. Missing payload fields - The request reschedule cancellation webhook was missing several fields that are present in regular cancellation webhooks:

   • eventTypeId (Int)
   • length (Int)
   • iCalSequence (Int)
   • eventTitle (String)
   • status (String)

3. New requestReschedule field - Added a new boolean field to help webhook consumers distinguish between:

   • Regular cancellations (requestReschedule: false)
   • Cancellations triggered by a reschedule request (requestReschedule: true)

Changes:

• Updated requestReschedule.handler.ts to include id in organizer and pass additional fields
• Updated BookingWebhookFactory.ts to support new cancellation payload fields
• Updated handleCancelBooking.ts to include requestReschedule: false
• Updated cancelAttendeeSeat.ts to include requestReschedule: false
• Updated DI scaffolding (BookingWebhookService, BookingPayloadBuilder, DTOs, params)
• Updated webhook documentation (webhooks.mdx)

Note: This is a non-breaking change - only adds new fields to existing payloads.

Visual Demo (For contributors especially)

Before (Request Reschedule cancellation webhook - missing fields):

{
  "triggerEvent": "BOOKING_CANCELLED",
  "payload": {
    "organizer": {
      // "id" was MISSING
      "email": "organizer@example.com",
      "name": "Organizer Name"
    }
    // Missing: eventTypeId, length, iCalSequence, eventTitle, status, requestReschedule
  }
}

After (Request Reschedule cancellation webhook - complete):

{
  "triggerEvent": "BOOKING_CANCELLED",
  "payload": {
    "organizer": {
      "id": 1,
      "email": "organizer@example.com",
      "name": "Organizer Name"
    },
    ... other fields
    "eventTypeId": 100,
    "length": 30,
    "iCalSequence": 2,
    "eventTitle": "Strategy Session",
    "status": "CANCELLED",
    "requestReschedule": true
  }
}

Regular cancellation webhook (now includes new field):

{
  "triggerEvent": "BOOKING_CANCELLED",
  "payload": {
    ... other fields
    "requestReschedule": false
  }
}

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. Updated docs/developing/guides/automation/webhooks.mdx and packages/features/webhooks/WEBHOOK_PAYLOADS.md.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Test 1: Regular Cancellation

1. Create a booking
2. Cancel the booking as the host
3. Check the webhook payload includes:
   • organizer.id is present
   • requestReschedule: false

Test 2: Request Reschedule Cancellation

1. Create a booking
2. As the host, click "Request Reschedule"
3. Check the webhook payload includes:
   • organizer.id is present
   • eventTypeId, length, iCalSequence, eventTitle, status are all present
   • requestReschedule: true

Test 3: Seat Cancellation

1. Create a seated event booking with multiple attendees
2. Cancel one attendee's seat
3. Check the webhook payload includes requestReschedule: false

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

[cubic-dev-ai]

1 issue found across 11 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="packages/trpc/server/routers/viewer/bookings/requestReschedule.handler.ts">

<violation number="1" location="packages/trpc/server/routers/viewer/bookings/requestReschedule.handler.ts:280">
P2: `bookingToReschedule.iCalSequence` is never selected from the repository, so this line always computes `NaN`, causing the webhook to emit an invalid iCal sequence.</violation>
</file>

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

[github-actions]

Devin AI is addressing Cubic AI's review feedback

A Devin session has been created to address the issues identified by Cubic AI.

View Devin Session

[devin-ai-integration]

Reviewed the Cubic AI feedback regarding the iCalSequence issue at line 280.

The confidence score for this issue is 8/10 (found in the comment metadata), which is below the required threshold of 9/10 for automated fixes. Per the review guidelines, I'm skipping this issue.

If you'd like me to investigate and fix this issue regardless of the confidence score, please let me know.

[hariombalhara]

LGTM !!