feat: dist tracing 4

[Udit-takkar]

What does this PR do?

Follow up to #25092

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• N/A I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
• N/A I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

---

Summary by cubic

Adds distributed tracing across booking confirmation, webhook dispatch, mandatory reminders, seat handling, and payment webhook flows (Stripe, PayPal, HitPay, BTCPayServer, Alby) to improve observability and structured error logging. Trace context is created at payment webhooks and confirm handler, propagated end-to-end, and spans are added for handle_confirmation, webhook_trigger, and schedule_mandatory_reminder.

• New Features
  • Propagate TraceContext through RegularBookingService, TRPC confirm handler, seats, payments, handleConfirmation, handleWebhookTrigger, and reminder scheduler.
  • Initialize trace in Stripe, PayPal, HitPay, BTCPayServer, and Alby webhooks; update trace with booking/payment metadata during payment handlers.
  • Replace direct logger calls with tracingLogger to capture errors within span context.

^{Written for commit 2e66cb2. Summary will update automatically on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
cal-companion	Ready	Preview	Comment	Dec 10, 2025 8:35am

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
cal	Ignored			Dec 10, 2025 8:35am
cal-eu	Ignored			Dec 10, 2025 8:35am

[hariombalhara]

Left a few suggestions

[hariombalhara]

LGTM !!

[CLAassistant]

All committers have signed the CLA.

[cubic-dev-ai]

No issues found across 15 files

[alishaz-polymath]

@volnei A quick bless from the foundation please? 🙏

[volnei]

In general it looks good to me but I'd go with a more homogeneous traces

payment.webhook.stripe
payment.webhook.other-provider
booking.confirm

specially avoiding names like handler.
The idea is to create a hierarchy of tracings and avoid things like

stripe.handler
alby.payment.confirm
test.confirm.handler

Approved, but I strongly recommend a tracing name revision and a documentation on how tracing names are structured.