feat(booking): acknowledge offline bookings before verification (backport #388)

[harshtandiya]

What changed

Manual backport of #388 to main. The automated backport could not cherry-pick it: main predates Buzz Team Settings, so the booking email code it touches reads its defaults from the Buzz Settings single instead.

Same behaviour as #388 — an offline booking now sends an acknowledgement the moment it is created (booking reference, event and participant details, offline method and amount, and a plain statement that the tickets are not confirmed yet and a separate confirmation will follow), and guests see a pending panel instead of the success panel claiming their tickets were sent. Includes the ticket-type title fix and the post-review tidy-ups from the same PR.

Adapted for this branch:

• send_booking_confirmation_email falls back to Buzz Settings.default_booking_confirmation_email_template, and get_booking_email_args reads Buzz Settings.support_email, in place of get_event_team_settings.
• TestOfflineAcknowledgementEmail configures Buzz Settings rather than team settings, matching the sibling TestBookingConfirmationEmail on this branch.
• Buzz Event's type annotations gain only the fields this branch's DocType actually has.

Everything else is the merge commit verbatim.

Demo

Same as #388 — no UI change beyond what that PR shipped.

Testing

• yarn test:unit green (43 tests) on this branch.
• Python suite is left to CI here: the local sites carry the develop schema, so a run against them would not prove anything about this branch.

[greptile-apps]

Greptile Summary

This backport adds an immediate acknowledgement email and a distinct pending UI state for offline bookings while retaining confirmation and ticket issuance for the later approval step.

• Adds event-level offline acknowledgement template configuration and a built-in email template.
• Refactors booking email recipient, template rendering, and attendee-summary construction into shared helpers.
• Routes guest offline responses to an inline pending panel and keeps signed-in users on the booking-detail path.
• Adds backend and dashboard tests for acknowledgement behavior, template rendering, and success-action selection.

Confidence Score: 4/5

The unconditional promise of a later email should be corrected before merging because events with booking emails disabled will never send it.

The pending guest UI diverges from the backend email toggle, while the new acknowledgement also presents inconsistent participant and subtotal amounts for partially applied free-ticket coupons.

Files Needing Attention: dashboard/src/components/BookingForm.vue; buzz/ticketing/doctype/event_booking/event_booking.py; buzz/templates/emails/offline_booking_acknowledgement.html

Important Files Changed

Filename	Overview
buzz/api/booking/services.py	Sends a best-effort acknowledgement after an offline booking is saved in its pending-verification state.
buzz/ticketing/doctype/event_booking/event_booking.py	Introduces shared booking-email helpers, but free-ticket coupon rows use a different discount basis from the acknowledgement subtotal.
buzz/templates/emails/offline_booking_acknowledgement.html	Adds the pending-payment receipt with event, attendee, payment, and support details; partial free-ticket discounts can produce inconsistent line totals.
buzz/events/doctype/buzz_event/buzz_event.json	Adds event-level acknowledgement-template configuration under the existing booking-email toggle.
dashboard/src/components/BookingForm.vue	Adds the guest pending panel, but promises a later email even when event configuration suppresses booking emails.
dashboard/src/utils/bookingSuccessRedirect.ts	Extends guest-inline actions with the offline pending-verification state while preserving gateway and explicit redirect priority.

Prompt To Fix All With AI

### Issue 1
dashboard/src/components/BookingForm.vue:80-82
**Disabled emails still promised**

When `send_booking_confirmation_email` is disabled, this panel still tells an offline guest that an email will arrive after verification, while the backend suppresses both acknowledgement and confirmation emails. The guest therefore waits for a message that will never be sent.

### Issue 2
buzz/ticketing/doctype/event_booking/event_booking.py:261
**Coupon totals mix bases**

For a partially discounted free-ticket booking, these participant amounts use the coupon-mutated attendee prices while the acknowledgement labels the unchanged pre-coupon `net_amount` as its subtotal. The participant lines consequently do not add up to the displayed subtotal, making the emailed payment breakdown inconsistent.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "feat(booking): acknowledge offline booki..." | Re-trigger Greptile}

[greptile-apps]

Disabled emails still promised

When send_booking_confirmation_email is disabled, this panel still tells an offline guest that an email will arrive after verification, while the backend suppresses both acknowledgement and confirmation emails. The guest therefore waits for a message that will never be sent.

Knowledge Base Used:

• Booking checkout and payment collection
• Dashboard booking experience

Prompt To Fix With AI

This is a comment left during a code review.
Path: dashboard/src/components/BookingForm.vue
Line: 80-82

Comment:
**Disabled emails still promised**

When `send_booking_confirmation_email` is disabled, this panel still tells an offline guest that an email will arrive after verification, while the backend suppresses both acknowledgement and confirmation emails. The guest therefore waits for a message that will never be sent.

**Knowledge Base Used:**
- [Booking checkout and payment collection](https://app.greptile.com/bwh-tech/-/custom-context/knowledge-base/bwhtech/buzz/-/docs/booking-checkout.md)
- [Dashboard booking experience](https://app.greptile.com/bwh-tech/-/custom-context/knowledge-base/bwhtech/buzz/-/docs/dashboard-booking-experience.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Coupon totals mix bases

For a partially discounted free-ticket booking, these participant amounts use the coupon-mutated attendee prices while the acknowledgement labels the unchanged pre-coupon net_amount as its subtotal. The participant lines consequently do not add up to the displayed subtotal, making the emailed payment breakdown inconsistent.

Knowledge Base Used: Booking checkout and payment collection

Prompt To Fix With AI

This is a comment left during a code review.
Path: buzz/ticketing/doctype/event_booking/event_booking.py
Line: 261

Comment:
**Coupon totals mix bases**

For a partially discounted free-ticket booking, these participant amounts use the coupon-mutated attendee prices while the acknowledgement labels the unchanged pre-coupon `net_amount` as its subtotal. The participant lines consequently do not add up to the displayed subtotal, making the emailed payment breakdown inconsistent.

**Knowledge Base Used:** [Booking checkout and payment collection](https://app.greptile.com/bwh-tech/-/custom-context/knowledge-base/bwhtech/buzz/-/docs/booking-checkout.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.