Initial booking state is explicit

Skipping an explicit initial booking status causes payment-confirmation race conditions: if a booking defaults to 'confirmed' at insert time, a failed or pending payment leaves a confirmed reservation with no corresponding charge. Under CWE-841 (improper enforcement of behavioral workflow), the system's state machine collapses at the first edge case. Any downstream job that queries status = 'CONFIRMED' to send reminder emails or mark slots occupied will fire on unconfirmed bookings, producing phantom reservations, double-charges, or capacity miscounts that are extremely difficult to detect after the fact.

Set status explicitly in the create call inside your booking service (e.g., src/lib/bookings.ts). Never rely on a database column default for a field whose initial value determines the entire lifecycle state machine.

const booking = await prisma.booking.create({
  data: {
    customerId,
    slotId,
    providerId,
    status: 'PENDING', // explicit — never trust a DB default here
    startTime,
    endTime,
  }
});