No-show follow-up sent only after no-show status is explicitly set on the booking record

A cron job that sends follow-up emails to all bookings where start_time < now AND status = 'confirmed' will send follow-ups to every completed booking that was never explicitly marked as completed — which in many booking systems is the majority. ISO 25010 functional-suitability.functional-correctness requires that no-show follow-ups fire only on verified no-shows, not on a time-based proxy. Without an explicit NO_SHOW status in the booking state machine, operators have no way to distinguish a completed appointment from a no-show, and any automation built on that distinction will misfire. Automated no-show detection without host confirmation also creates legal exposure if follow-up communications are construed as accusations.

Add NO_SHOW to the booking status enum and expose an explicit host-action endpoint that sets it. Trigger the follow-up email from the status-change handler, not from a time-based cron:

// prisma/schema.prisma
enum BookingStatus {
  PENDING
  CONFIRMED
  COMPLETED
  NO_SHOW
  CANCELLED
}

// src/app/api/bookings/[id]/no-show/route.ts
export async function POST(req: Request, { params }: { params: { id: string } }) {
  const booking = await db.bookings.update({
    where: { id: params.id },
    data: { status: 'NO_SHOW', marked_no_show_at: new Date() },
  })
  await emailQueue.add('send-no-show-followup', {
    bookingId: booking.id,
    customerEmail: booking.customer_email,
    hostEmail: booking.host_email,
  })
  return Response.json({ ok: true })
}

Remove any cron job that infers no-show status from appointment time alone.