Deploy AIOS web (React glide grid + FastAPI slice)

RELEASES.json

@@ -1,5 +1,5 @@
 {
- "current": "80b80b9",
+ "current": "507c54b",
  "releases": [
   {
    "version": "v53",

VERSION

@@ -1 +1 @@
-80b80b9
+507c54b

web/src/customer-grid/CustomerGrid.tsx

@@ -4010,17 +4010,34 @@ function CustomerGridSurface({
   /* ═══ end W18-B VOID (geometry) ═══ */
 
   // The record drawer resolves positions against what the MODE paints: the display slice for
-  // grid/list (the cap is real there), the FULL pipeline for calendar/kanban/map (a month, a
-  // stack or a pin reaches past the cap by design — a drawer that refused those pids would
-  // close itself on a card the user can plainly see).
-  // ⭐ WAVE-27 item 8 (C3) — `swipe` belongs here for calendar/kanban/map's own reason: the deck
-  // is derived from `modeDataRows` (the FULL pipeline), so a card past the display cap is one
-  // the user can plainly see, and a drawer that refused its pid would close itself on open.
+  // grid/list (the cap is real there), the FULL pipeline for calendar/kanban (a month or a
+  // stack reaches past the cap by design — a drawer that refused those pids would close itself
+  // on a card the user can plainly see).
+  //
+  // Map has one deliberately narrower exception to that rule. A saved Route is read from the
+  // current scoped book so opening yesterday's route still shows its complete stop list even
+  // when today's View filters a stop out. `MapView` can therefore ask the ordinary drawer to
+  // open a pid that is not in `visibleRows`. Resolve Map's detail identity from that SAME
+  // `scopedRows` universe: it is already after the table, permission, BU, and Cohort walls, and
+  // is exactly what MapView receives as `allRows`. This is a drawer lookup only — it neither
+  // changes the View's rows nor selection, route membership, or route order.
+  const mapDetailRows = useMemo(
+    () => scopedRows.map((record) => ({ kind: "data" as const, record })),
+    [scopedRows]
+  );
+  const mapDetailPidToIndex = useMemo(
+    () => new Map(mapDetailRows.map((row, index) => [row.record.pid, index])),
+    [mapDetailRows]
+  );
+  // ⭐ WAVE-27 item 8 (C3) — `swipe` belongs here for calendar/kanban's own reason: the deck is
+  // derived from `modeDataRows` (the FULL pipeline), so a card past the display cap is one the
+  // user can plainly see, and a drawer that refused its pid would close itself on open. Map's
+  // saved-stop case is the explicit scoped branch above, not another spelling of this rule.
   const fullSetMode =
-    displayMode === "calendar" || displayMode === "kanban" || displayMode === "map" ||
-    displayMode === "swipe";
-  const detailRows = fullSetMode ? visibleRows : displayRows;
-  const detailIdxMap = fullSetMode ? pidToIndex : displayPidToIndex;
+    displayMode === "calendar" || displayMode === "kanban" || displayMode === "swipe";
+  const detailRows = displayMode === "map" ? mapDetailRows : fullSetMode ? visibleRows : displayRows;
+  const detailIdxMap = displayMode === "map" ? mapDetailPidToIndex
+    : fullSetMode ? pidToIndex : displayPidToIndex;
   const detailIndex = detailPid !== null ? detailIdxMap.get(detailPid) : undefined;
   useEffect(() => {
     if (detailPid !== null && detailIndex === undefined) setDetailPid(null);