Skip to content

feat: passenger-initiated ride request flow #1

@aspect-study

Description

@aspect-study

Inverts the current booking model — a passenger posts a ride request, a driver with an active ride can offer a seat, and the passenger accepts or declines.

New domain entities: RideRequest, SeatOffer
New events/notifications: request created, seat offered, accepted/declined
New bot flows: REQUEST_* BotFlow states for passenger request creation
Driver UI: "Ride Requests" button on active ride screen
Passenger UI: accept/decline callback actions
Terminal step: accepted offer creates a standard Booking via existing BookingService

Deferred - more complex than standard booking, planned for a future sprint.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions