Restaurant Order Acceptance Failure Leading to Rider Inactivity

Description:
Users have identified a significant issue within the platform's order processing system. Specifically, when a restaurant accepts an order from a customer but fails to pass it on to the rider for delivery, the rider remains inactive and does not receive any orders. This breakdown in communication and order management disrupts the delivery process, potentially resulting in delayed or unfulfilled orders and a frustrating experience for both customers and riders.

Steps to Reproduce:

A customer places an order through the platform.
The restaurant receives and acknowledges the order.
The restaurant fails to pass the order details to the rider for delivery.
The rider, expecting incoming orders, remains inactive and does not receive any orders.
Expected Result:
When a restaurant accepts an order, it should promptly pass on the order details to the assigned rider for delivery. The rider should then receive the order and proceed with the delivery, ensuring a smooth and timely experience for customers.

Actual Result:
In instances where a restaurant acknowledges an order but fails to communicate it to the rider, the rider remains inactive and does not receive any orders. This results in a breakdown of the delivery process and potential customer dissatisfaction.

Impact:
This issue has a significant negative impact on the overall efficiency and reliability of the platform's order delivery system. Customers may experience delays or non-delivery of their orders, while riders may remain idle, affecting their earnings and job satisfaction.

The issue names no files, tests, or entry points. Start by tracing the restaurant-acceptance flow through the repository and identify where rider assignment or order notification is handled. Reproduce the accepted-order case, then verify that the assigned rider receives the order and becomes active without breaking customer or restaurant status.

Written by the indexing model from the issue text.