Host receives a separate notification for each new booking

If the host does not get a per-booking notification, bookings go unnoticed until the customer shows up to an empty room. Digest-only notifications fail the moment a booking is made less than 24 hours out — the host reads the digest the next morning, after the appointment slot. Host-side awareness is the difference between a booking system and a calendar-shaped black hole. No-show rates for hosts are just as business-critical as customer no-shows and they break trust with paying customers permanently.

Dispatch a host notification inside the same confirmation handler as the customer notification — same code path, same transaction boundary, queued not cron'd. Include at minimum customer name, service, date, time, and timezone in the payload so the host can act without opening the dashboard. Edit src/lib/bookings.ts:

await emailQueue.add('send-host-notification', {
  bookingId,
  hostEmail: booking.host_email,
  customerName: booking.customer_name,
  service: booking.service_name,
  dateTime: booking.start_time,
  timezone: booking.timezone,
})