Everything an operator needs about one booking
Tapping any booking on the tee sheet lands here. The same surface is reused by the Customer profile, the Bay detail page, and the Payments page when they cross-reference a booking.
- Booking summary — date, time, bay, duration, activity, party size; the canonical "what was reserved".
- Customer — name, contact, plan tier, included-hours balance, prior visit count; link to the full customer profile.
- Payment — method, amount, refunds, payment status; link to the Stripe charge or counter receipt.
- Door + bay state — code issued, used/unused, automation runs (lights, sim) that fired for this session.
- Edit booking — change time, bay, duration, customer, party size; honors the same rules as creation (booking-group windows, rate card).
- Operator actions — cancel (with refund policy), comp this session, mark no-show, message customer, add operator note.
- Audit log — every state change with timestamp + actor (who created, who edited, who comped, when SMS went out).
Backend wiring pending. GET /operator/bookings/<id> in the live app; same shape regardless of how the operator landed here.