M33: enforce booking readiness workflow
This commit is contained in:
@@ -2750,3 +2750,15 @@ evidence yet."
|
||||
all five scenarios ready; the last action after reset was the read-only Hub proof.
|
||||
- Exact next action: none for the requested scope; keep the public synthetic demo online
|
||||
and monitor its existing health, backup and integration evidence surfaces.
|
||||
|
||||
## M33 — explicit booking readiness and Brussels-safe planning (2026-08-10)
|
||||
|
||||
- New reservations now default to incomplete requirements. Checkout remains unavailable
|
||||
until an operator records a deliberate requirements confirmation; that transition and
|
||||
its bounded evidence are persisted in the audit trail.
|
||||
- Booking creation and availability use Europe/Brussels wall-clock conversion independent
|
||||
of the visitor's browser timezone. Customer and vehicle searches cancel stale requests,
|
||||
use a bounded timeout and expose server-side vehicle filtering up to 50 results.
|
||||
- Validation: isolated booking API suite **12 passed**; backend Ruff clean; frontend
|
||||
TypeScript lint and production build passed.
|
||||
- Exact next action: add database invariants/indexes and harden the shared public demo reset.
|
||||
|
||||
Reference in New Issue
Block a user