updated the sheet

lib/xpress/data/delivery_api.dart

@@ -107,7 +107,7 @@ class DeliveryApi {
   /// **ABSENT** — the generic status write the ported flow uses for every
   /// transition (accepted → active → arrived → delivered → skipped).
   ///
-  /// Was `queue.workolik.com/live/api/v1/deliveries/updatedelivery`. There is no
+  /// Was `deliveries/updatedelivery` on the retired backend. There is no
   /// single status-write route on Doormile; the transitions above are separate
   /// endpoints. Call sites that still post a bare status change land here and
   /// will 404 until either they are split or the route is built.
@@ -117,7 +117,7 @@ class DeliveryApi {
 
   /// **LIVE** — periodic location/telemetry log.
   ///
-  /// Was `queue.workolik.com/live/api/v2/partners/createriderlog`.
+  /// Was `partners/createriderlog` on the retired backend.
   static String get createRiderLog => url('/miler/logs');
 
   /// **LIVE** — read them back.
@@ -142,7 +142,7 @@ class DeliveryApi {
 
   /// **ABSENT** — per-delivery event log.
   ///
-  /// Was `queue.workolik.com/live/api/v2/deliveries/createdeliverylog`. The
+  /// Was `deliveries/createdeliverylog` on the retired backend. The
   /// closest real thing is consignment logs, which key on a consignmentid the
   /// delivery flow does not always hold.
   static String get createDeliveryLog => url('/miler/consignments/logs');