Request Booking

Phase 0+1 — facility booking creation is PARKED.

Auditor item 1 (Phase 0+1): "Facility booking must not disappear after restart. Choose A or B. Preferred: disable POST /book with HTTP 503 until facility_bookings is aligned. Keep facility browse/detail read-only."

We pick A. The booking write would otherwise either:

• write to a schema that may not match across environments (constraint violation), or
• write to the in-memory dict only and silently disappear on backend restart.

Both are unacceptable. So we 503 with an explicit message. The auth + facility lookup still run — we want the access signal in logs even when the action is parked. This unblocks Phase 0.5 (the facility schema audit + repair chapter) where POST /book becomes durable.