Fetch valid enumeration values used as filters across Loki.

Use this to discover the allowed values for status/type/category/fulfilled_by filters before calling the search tools.

Search logistics hubs. Use this first to find a hub's id (a Mongo ObjectId string) when you only know its name/code -- order and task search require hub_id.

Note on hub kinds: pharmacy delivery hubs are business_client="pharmacy" (types like RETAIL); diagnostics phlebo centers (PACs) are business_client="droplet", type="PAC". A "Sec-14 Gurgaon PAC" is therefore a droplet/PAC hub, not the same as the "sec_14_ggn_retail" pharmacy hub.

IMPORTANT: the server DEFAULTS business_client to "pharmacy" when it is omitted, so a search for a diagnostics/phlebo hub returns nothing unless you pass business_client="droplet". query is a substring match over both name AND code, so short numeric queries (e.g. "14") also match hub codes.

Get full detail for a single hub by its id (Mongo ObjectId string).

Get full detail for a single order.

IMPORTANT: this takes the order's internal numeric id (the id field returned by loki_search_orders, e.g. "29879321"), NOT the human-facing order_id / PO string (e.g. "PO17026268570467"). If you only have a PO string, run loki_search_orders (order_id=) first and read its id.

Get the status/event timeline for an order -- the chronological history of state changes. Useful for debugging "why is this order stuck/late".

IMPORTANT: takes the order's internal numeric id (the id field from loki_search_orders, e.g. 29879321), NOT the PO… order_id string.

Get full detail for a single task by its id.

Search riders (delivery agents / phlebos).

Use loki_reference_data('rider_statuses' | 'rider_types') for valid values.

Get full detail for a single rider by numeric id.

List the riders attached to one or more hubs (optionally filtered by type). Useful to see who is available to fulfil orders at a hub.

Daily summary KPIs for one phlebo/rider on a given date: Total Assigned, Completed, Cancelled, Total Distance (planned/actual), SLA Breach, Time, and Sequence edits. The fast "how did this rider's day go" snapshot.

The chronological day timeline for one phlebo/rider: shift start, login, and each task in expected sequence with status, group, SLA status and order timestamps. Use to debug a rider's route/sequence on a specific day.

The planned route for a phlebo/rider on a date: ordered [lng,lat] waypoints plus order/home/hub locations. Compare with loki_get_phlebo_actual_route to spot route deviations.

The actual GPS location history for a phlebo/rider on a date: timestamped lat/long pings with speed, battery % and coolbox temperature. Use to verify where a rider actually went and device/coolbox health.

List all phlebos/riders working a hub on a date with their live day-tracking row: status, availability, battery, lat/long, last_seen, tasks_assigned, orders_completed, attendance_status, coolbox temperature, idle/offline time. This is the "Track Phlebos" board for a hub+day.

Attendance roll-up for one or more hubs on a date: total_present / total_absent.

A rider's day-by-day attendance for a month: per-date attendance_status (present/absent) and hours worked.