Doormile AI: make the numbers trustworthy, then composable

Data-layer work on the assistant, in the order it mattered.

Correctness first:

- getBookingsPage keeps the envelope's `total`/`page`. getBookings threw
  them away, so no caller could tell a full result from a truncated one.
- Every booking read now drains pages up to a budget instead of taking page
  one at the API's 1000-row cap. Past 1000 lifetime bookings, every count
  and sum in this file silently under-reported while the source line beside
  it still read "complete". Row order is detected per call, so a backend
  that stops returning newest-first degrades to a full scan rather than to
  a wrong answer.
- A capped scan now says "At least N", appends what it scanned versus the
  total, and marks its source call as failed.
- Revenue excludes cancelled orders, sums every service option rather than
  the first, and is labelled estimated — it is a quote, not settled money.
- A strong order reference that isn't found is answered "I couldn't find
  it" instead of falling through to a broader intent, which used to answer
  "142 orders created today" to a question about one order.

Then agreement with the Orders page:

- utils/orderStatusGroups.js is now the single definition of which raw
  booking enums make up each status; orders.js builds its tabs from it and
  the assistant matches against it. The assistant had been using api.js's
  Deliveries taxonomy, which keeps miler_assigned on `pending`, so the
  Orders page showed 19 Assigned while the bot answered 0. The two
  taxonomies stay separate on purpose — Orders tracks the operator's
  action, Deliveries tracks the rider's.
- A status question with no date named is no longer scoped to today. "How
  many orders are assigned" describes the queue right now, which is what
  the Orders page's tabs show; they apply no date filter either.
- The Orders header said "Today" over counts that were never date-filtered.
  Corrected the label rather than adding a filter, since filtering would
  hide currently-visible rows — a product decision, not a bug fix.

Then capability:

- delayedOrders answers "which orders are delayed" from the promised
  delivery time. deliveries.js and Dispatch.js both rejected that field for
  batch bucketing because an ETA is not the wave an order belongs to; that
  reasoning does not carry over to lateness, where a promise that never
  gets re-stamped is exactly the right baseline. If no order carries an
  ETA it says so rather than reporting a reassuring "0 delayed".
- orderQuery composes status x batch x tenant x rider, plus rankings. It
  claims a question only when two or more of those are present, so
  single-dimension questions keep their proven intents. A date is not
  counted as a dimension — counting it re-routed four working questions.
- An unresolved tenant/rider name falls through instead of having its
  filter silently dropped, which was the original defect.
- orderLookup resolves the rider's name and reads the tracking trail
  defensively, since that endpoint's response shape is undocumented.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/utils/orderStatusGroups.js

@@ -0,0 +1,67 @@
+// ============================================================================
+// Order status groups — which RAW `GET /admin/bookings` enums make up each
+// operator-facing status the Orders page shows as a tab.
+//
+// Extracted from orders.js's ORDERS_STATUS_TABS so the Doormile AI assistant
+// can answer "how many assigned orders" with the SAME match set the Orders
+// page counts, instead of growing a second definition that drifts. Same reason
+// utils/batchBucket.js exists.
+//
+// ⚠ This is deliberately NOT the same taxonomy as api.js's
+// BOOKING_STATUS_TO_DELIVERY_STATUS, and the two must not be merged:
+//
+//   • Orders page (this file)  — tracks the OPERATOR's workflow. "Assigned"
+//     means the operator picked a rider, the moment assign-miler succeeds, so
+//     miler_assigned counts as Assigned.
+//   • Deliveries page (api.js) — tracks the RIDER's engagement. Its "Accepted"
+//     means the rider accepted, a deliberately later and narrower bar, so it
+//     keeps miler_assigned on 'pending'.
+//
+// That split is explicit product direction (see the long comment above
+// ORDERS_STATUS_TABS in orders.js — it was unified once and reverted). The
+// assistant answers order-status questions with the ORDERS taxonomy, because
+// that is the screen an operator is comparing its answers against.
+// ============================================================================
+
+export const ORDER_STATUS_GROUPS = {
+  pending: ['pending_pickup'],
+  assigned: ['converted_to_consignment', 'miler_assigned', 'pickup_scheduled'],
+  // The Orders page has no tab for this one — a booking that is out for
+  // delivery has left the operator's queue. The assistant still needs it so
+  // "how many orders are in transit" resolves, and so statusBreakdown's
+  // totals account for every row rather than silently dropping some.
+  active: ['out_for_delivery'],
+  delivered: ['delivered'],
+  cancelled: ['cancelled']
+};
+
+export const ORDER_STATUS_LABELS = {
+  pending: 'Pending',
+  assigned: 'Assigned',
+  active: 'Out for delivery',
+  delivered: 'Delivered',
+  cancelled: 'Cancelled'
+};
+
+// Display order — matches the lifecycle, and the order the Orders page's tabs
+// appear in.
+export const ORDER_STATUS_ORDER = ['pending', 'assigned', 'active', 'delivered', 'cancelled'];
+
+const RAW_TO_GROUP = Object.entries(ORDER_STATUS_GROUPS).reduce((acc, [group, raws]) => {
+  raws.forEach((raw) => {
+    acc[raw] = group;
+  });
+  return acc;
+}, {});
+
+export const statusesInGroup = (group) => ORDER_STATUS_GROUPS[group] || [];
+
+// Raw booking enum → group key. Returns the lowercased raw value itself for an
+// enum this map has never seen, so an unmapped backend status stays visible in
+// a breakdown rather than vanishing from the totals.
+export const groupForBookingStatus = (raw) => {
+  const key = String(raw || '').toLowerCase();
+  return RAW_TO_GROUP[key] || key;
+};
+
+export const isInGroup = (raw, group) => statusesInGroup(group).includes(String(raw || '').toLowerCase());