Ordrivo RideFlow 7.2.54 addresses both reported findings.

1. Ride status, driver assignment, ETA replacement and customer ETA responses now use a shared per-ride database advisory lock. The code reads authoritative database status and current assignment after acquiring that lock, rejects stale transitions, preserves ride status during ordinary editor saves, and verifies status persistence before success. Closing or cancelling a ride closes any pending ETA response.

2. Customer, driver and dispatch safety alerts are created under the same per-ride lock. Each source may have one open alert, one accepted new alert per 60 seconds, and at most five per ride per site-local day. Customer and driver alerts remain separate and individually acknowledgeable. Delivered, completed and cancelled rides reject new alerts without creating a record or sending email; the response explains throttling and directs immediate emergencies to local emergency services.

The package includes updated version and changelog metadata, source regression assertions, and staging steps for the requested concurrent status, assignment, ETA and panic scenarios. PHP lint and live WordPress staging scenarios were not run in the packaging environment.
