import { Icon } from '../shared/Icon'; const METRICS = [ { label: 'Flow Paths', value: '11', icon: 'route', color: '#7b59e6' }, { label: 'Status Mappings', value: '12', icon: 'swap_horiz', color: '#06b6d4' }, { label: 'BullMQ Jobs', value: '6', icon: 'schedule', color: '#a855f7' }, { label: 'Feature Flags', value: '3', icon: 'flag', color: '#f59e0b' }, ]; const KEY_POINTS = [ 'Syncs internal trip status changes to a rider/driver-facing booking_status field on the Trip schema', 'Uses optimistic locking (updateOne with status guard) to prevent race conditions', 'All side effects (notifications, DAC, cleanup) are fire-and-forget — never block the response', 'Feature flags control rollout: ENABLE_BOOKING_JOBS, ENABLE_PRE_TRIP_RIDER_CONFIRMATION, ENABLE_DRIVER_CONFIRMATION', 'Two entry points: rider endpoint (PUT /rider/trips/:tripId/booking-status) and driver endpoint (PUT /b2c/driver/trips/:tripId/booking-status)', ]; export function ExecutiveSummarySection() { return (
The Scheduled Ride Booking Status Sync feature maintains a parallel booking_status field
on the Trip schema that reflects the lifecycle of a scheduled (booked) ride. When internal trip statuses change
(e.g., driver assigned, trip started, rider cancelled), the middleware automatically maps these to
booking-specific statuses that the mobile apps consume.