Deploy AIOS web (React glide grid + FastAPI slice)

RELEASES.json

@@ -1,6 +1,12 @@
 {
- "current": "v47 (917f9a0)",
+ "current": "v48 (3c69fd9)",
  "releases": [
+  {
+   "version": "v48",
+   "sha": "3c69fd9",
+   "date": "2026-08-23",
+   "subject": "release v48"
+  },
   {
    "version": "v47",
    "sha": "917f9a0",

VERSION

@@ -1 +1 @@
-v47 (917f9a0)
+v48 (3c69fd9)

web/src/customer-grid/MapView.tsx

@@ -2039,114 +2039,15 @@ export function MapView({
                         ))}
                     </select>
                   </label>
-                  {/* ── ITEM 4: the hand-off links, ONE PER LINE, DIRECTLY under the visit order
-                      field ────────────────────────────────────────────────────────────────────
-                      They were a `flex-wrap` cluster of chips, unreadable the moment a route
-                      needs more than one Google leg. Stacked, each on its own row, the list reads
-                      as what it is: leg 1, then leg 2.
-                      ⚠ POSITION IS PART OF THE INSTRUCTION, not a detail. They sit between the
-                      select and its Save button rather than after the whole block, because the
-                      block's tail can carry a stale marker, a shared-orders note and two message
-                      rows, and "under the Visit order column" stops being true the moment three
-                      of those render between the two. */}
-                  {plan.links.length > 0 && (
-                    <div className="cg-map-google-links" aria-label="Google Maps route links">
-                      {plan.links.map((link) => (
-                        <a
-                          key={link.index}
-                          href={link.url}
-                          target="_blank"
-                          rel="noopener noreferrer"
-                          title={`Open Google Maps route ${link.index} in a new tab`}
-                        >
-                          Google Maps route {link.index}
-                        </a>
-                      ))}
-                    </div>
-                  )}
-                  {/* ── ITEMS 4 AND 5: "Save route", and it ASKS FOR THE NAME ─────────────────
-                      ⭐ ITEM 4 — the button read "Save visit order". Owner: *"Change the button
-                      called 'Save visit order' to 'Save route'."* The FIELD is still the visit
-                      order (that is what the numbers in it are); the ACT is saving a route.
-                      ⭐ ITEM 5 — a NEW field now opens a name box first, pre-filled with the
-                      server's next free "Route N". Updating a field that already exists does not
-                      prompt: it already has a name, and asking again would invite a rename
-                      through a door that re-solves numbers rather than through Edit field.
-                      ⛔ AN INLINE STEP, NOT A BROWSER `prompt()`. A modal dialog blocks the page
-                      and cannot be styled, read by the design system, or dismissed with Escape
-                      the way every other overlay here is. */}
-                  {naming && !saveTarget ? (
-                    <div className="cg-route-name" role="group" aria-label="Name this route">
-                      <input
-                        className="cg-input"
-                        autoFocus
-                        value={nameDraft}
-                        aria-label="Route name"
-                        placeholder={nextLabel || "Name this route"}
-                        maxLength={120}
-                        onChange={(e) => setNameDraft(e.target.value)}
-                        onKeyDown={(e) => {
-                          if (e.key === "Enter") { e.preventDefault(); void saveRouteOrder(nameDraft); }
-                          if (e.key === "Escape") { e.preventDefault(); setNaming(false); }
-                        }}
-                      />
-                      <span className="cg-route-name-actions">
-                        <button
-                          type="button"
-                          className="cg-btn cg-btn--primary"
-                          disabled={saveBusy || !nameDraft.trim()}
-                          onClick={() => void saveRouteOrder(nameDraft)}
-                          title="Save these visit numbers into a new field with this name"
-                        >
-                          {saveBusy ? "Saving" : "Save route"}
-                        </button>
-                        <button
-                          type="button"
-                          className="cg-btn"
-                          onClick={() => setNaming(false)}
-                          title="Do not save this route yet"
-                        >
-                          Cancel
-                        </button>
-                      </span>
-                    </div>
-                  ) : (
-                    <button
-                      type="button"
-                      className="cg-btn cg-btn--primary cg-route-cta"
-                      disabled={saveBusy}
-                      onClick={() => {
-                        if (saveTarget) { void saveRouteOrder(); return; }
-                        setNameDraft(nextLabel);
-                        setSaveErr(null);
-                        setSaveMsg(null);
-                        setNaming(true);
-                      }}
-                      title={
-                        saveTarget
-                          ? "Write these visit numbers into the saved field, for everyone it is shared with"
-                          : "Name this route and save these visit numbers as a new field"
-                      }
-                    >
-                      {saveBusy ? "Saving" : saveTarget ? "Update route" : "Save route"}
-                    </button>
-                  )}
-                  {/* ⛔ DERIVED, NEVER STORED. The saved field carries the fingerprint of the
-                      inputs it was solved from; this compares it against the cohort ON SCREEN
-                      NOW, so the marker cannot itself go out of date. */}
-                  {orderStale && (
-                    <span className="cg-map-route-note">
-                      Stale. The saved numbers were solved from different stops, so re-solving
-                      would change them.
-                    </span>
-                  )}
+                  {/* ⚠ THIS NOTE STAYS WITH THE SELECT, while items 8 and 9 send the Save
+                      button and the Google links to the foot. It is a statement about what
+                      the LIST ABOVE does not contain ("not listed above"), so it is the one
+                      line in the old block that would become false the moment it travelled. */}
                   {(routeCols || []).some((f) => !f.mine) && (
                     <span className="cg-map-route-note">
                       Shared orders you can read but not re-solve are not listed above.
                     </span>
                   )}
-                  {saveMsg && <span className="cg-map-route-note">{saveMsg}</span>}
-                  {saveErr && <span className="cg-cal-nodate">{saveErr}</span>}
                 </>
               )}
 
@@ -2273,23 +2174,149 @@ export function MapView({
                 </span>
               )}
 
-              {routeOn && (
-                <button
-                  type="button"
-                  className="cg-btn cg-btn--danger cg-route-cta"
-                  onClick={() => {
-                    setRouteOn(false);
-                    setRouteStartPid(null);
-                    setRouteOrder(null);
-                    setRoad(null);
-                    setRoadErr(null);
-                    setDepot(null);
-                  }}
-                  title="Drop this route and start again. The records stay selected."
-                >
-                  Clear route
-                </button>
+              {/* ══ OWNER ITEMS 8 AND 9 (2026-08-23) — THE COMMITTING CONTROLS LIVE AT THE FOOT ══
+                  Owner: *"the 'Google Map Route 1' etc. should still be located at the bottom
+                  just above clear route button. And the save route button should still be at
+                  the bottom too beside clear route button."*
+                  ⛔⛔ THIS OVERRULES THE OLDER "POSITION IS PART OF THE INSTRUCTION" NOTE, WHICH
+                  IS KEPT NOWHERE ELSE, SO IT IS RESTATED HERE RATHER THAN DELETED. Item 4 of the
+                  earlier pass put the Google links BETWEEN the visit-order select and its Save
+                  button, so that "under the Visit order column" stayed true; item 3b then moved
+                  that whole block above Start. The owner has now separated the two jobs: the
+                  select is SETUP and belongs at the top with Add a record, while saving and
+                  clearing are the two ways to FINISH and belong together at the bottom. The old
+                  argument was about keeping the links adjacent to something; they are now
+                  adjacent to the button that commits them, which serves it.
+                  ⚠ The Save button and Clear route share one row (item 9's "beside"), so
+                  `.cg-route-cta`'s full-width override is deliberately NOT applied to them —
+                  two full-width buttons cannot sit beside each other. */}
+              {plan && (
+                <>
+                  {/* ── ITEM 4: the hand-off links, ONE PER LINE ─────────────────────────
+                      They were a `flex-wrap` cluster of chips, unreadable the moment a route
+                      needs more than one Google leg. Stacked, each on its own row, the list
+                      reads as what it is: leg 1, then leg 2. Owner item 8 moved the stack down
+                      here, directly above the two buttons that finish the job. */}
+                  {plan.links.length > 0 && (
+                    <div className="cg-map-google-links" aria-label="Google Maps route links">
+                      {plan.links.map((link) => (
+                        <a
+                          key={link.index}
+                          href={link.url}
+                          target="_blank"
+                          rel="noopener noreferrer"
+                          title={`Open Google Maps route ${link.index} in a new tab`}
+                        >
+                          Google Maps route {link.index}
+                        </a>
+                      ))}
+                    </div>
+                  )}
+                  {/* ── ITEMS 4 AND 5: "Save route", and it ASKS FOR THE NAME ─────────────────
+                      ⭐ ITEM 4 — the button read "Save visit order". Owner: *"Change the button
+                      called 'Save visit order' to 'Save route'."* The FIELD is still the visit
+                      order (that is what the numbers in it are); the ACT is saving a route.
+                      ⭐ ITEM 5 — a NEW field now opens a name box first, pre-filled with the
+                      server's next free "Route N". Updating a field that already exists does not
+                      prompt: it already has a name, and asking again would invite a rename
+                      through a door that re-solves numbers rather than through Edit field.
+                      ⛔ AN INLINE STEP, NOT A BROWSER `prompt()`. A modal dialog blocks the page
+                      and cannot be styled, read by the design system, or dismissed with Escape
+                      the way every other overlay here is. */}
+                  {naming && !saveTarget && (
+                    <div className="cg-route-name" role="group" aria-label="Name this route">
+                      <input
+                        className="cg-input"
+                        autoFocus
+                        value={nameDraft}
+                        aria-label="Route name"
+                        placeholder={nextLabel || "Name this route"}
+                        maxLength={120}
+                        onChange={(e) => setNameDraft(e.target.value)}
+                        onKeyDown={(e) => {
+                          if (e.key === "Enter") { e.preventDefault(); void saveRouteOrder(nameDraft); }
+                          if (e.key === "Escape") { e.preventDefault(); setNaming(false); }
+                        }}
+                      />
+                      <span className="cg-route-name-actions">
+                        <button
+                          type="button"
+                          className="cg-btn cg-btn--primary"
+                          disabled={saveBusy || !nameDraft.trim()}
+                          onClick={() => void saveRouteOrder(nameDraft)}
+                          title="Save these visit numbers into a new field with this name"
+                        >
+                          {saveBusy ? "Saving" : "Save route"}
+                        </button>
+                        <button
+                          type="button"
+                          className="cg-btn"
+                          onClick={() => setNaming(false)}
+                          title="Do not save this route yet"
+                        >
+                          Cancel
+                        </button>
+                      </span>
+                    </div>
+                  )}
+                  {/* ⛔ DERIVED, NEVER STORED. The saved field carries the fingerprint of the
+                      inputs it was solved from; this compares it against the cohort ON SCREEN
+                      NOW, so the marker cannot itself go out of date. */}
+                  {orderStale && (
+                    <span className="cg-map-route-note">
+                      Stale. The saved numbers were solved from different stops, so re-solving
+                      would change them.
+                    </span>
+                  )}
+                  {saveMsg && <span className="cg-map-route-note">{saveMsg}</span>}
+                  {saveErr && <span className="cg-cal-nodate">{saveErr}</span>}
+                </>
               )}
+
+              <div className="cg-route-foot">
+                {/* ⚠ THE NAME BOX IS FULL WIDTH ABOVE THE ROW, NOT INSIDE IT. A text input, a
+                    Save and a Cancel cannot share a 338px row with Clear route without every
+                    one of them shrinking past reading width, so while it is open the row shows
+                    Clear route alone and the prompt owns the line above it. */}
+                {plan && !(naming && !saveTarget) && (
+                  <button
+                    type="button"
+                    className="cg-btn cg-btn--primary cg-route-foot-btn"
+                    disabled={saveBusy}
+                    onClick={() => {
+                      if (saveTarget) { void saveRouteOrder(); return; }
+                      setNameDraft(nextLabel);
+                      setSaveErr(null);
+                      setSaveMsg(null);
+                      setNaming(true);
+                    }}
+                    title={
+                      saveTarget
+                        ? "Write these visit numbers into the saved field, for everyone it is shared with"
+                        : "Name this route and save these visit numbers as a new field"
+                    }
+                  >
+                    {saveBusy ? "Saving" : saveTarget ? "Update route" : "Save route"}
+                  </button>
+                )}
+                {routeOn && (
+                  <button
+                    type="button"
+                    className="cg-btn cg-btn--danger cg-route-cta"
+                    onClick={() => {
+                      setRouteOn(false);
+                      setRouteStartPid(null);
+                      setRouteOrder(null);
+                      setRoad(null);
+                      setRoadErr(null);
+                      setDepot(null);
+                    }}
+                    title="Drop this route and start again. The records stay selected."
+                  >
+                    Clear route
+                  </button>
+                )}
+              </div>
             </div>
           </aside>
         )}

web/src/index.css

@@ -5086,6 +5086,20 @@ a.cg-map-ctl-b { text-decoration: none; }
   gap: 6px;
 }
 .cg-route-name-actions .cg-btn { flex: 1 1 0; justify-content: center; }
+/* ⭐ OWNER ITEMS 8 AND 9 (2026-08-23) — SAVE AND CLEAR SHARE THE LAST ROW. Owner: *"the save
+   route button should still be at the bottom too beside clear route button."* The Google links sit
+   directly above it (item 8), so the panel ends: how to hand this route to Google, then the two
+   ways to finish with it.
+   ⛔ `.cg-route-cta`'s `width: 100%` is OVERRIDDEN here rather than simply not applied, because
+   `Clear route` still carries that class from every other position it has ever had. Two full-width
+   buttons cannot sit beside each other, which is the whole of item 9. */
+.cg-route-foot {
+  display: flex;
+  gap: 6px;
+  width: 100%;
+  margin-top: 2px;
+}
+.cg-route-foot .cg-btn { flex: 1 1 0; width: auto; justify-content: center; text-align: center; }
 .cg-route-popover .cg-map-route-sum { white-space: normal; line-height: 1.45; }
 .cg-route-popover .cg-map-route-opt {
   align-items: stretch;
@@ -5195,6 +5209,18 @@ a.cg-map-ctl-b { text-decoration: none; }
   scrollbar-width: thin;
 }
 .cg-route-picker-opt {
+  /* ⛔⛔ OWNER ITEM 10 (2026-08-23) — `flex: 0 0 auto` IS THE WHOLE FIX, AND ITS ABSENCE IS WHY
+     THE RESULTS PILED ON TOP OF EACH OTHER. Owner: *"when i type search records for the route, the
+     dropdown overlays for both start and search database."* The list is a flex COLUMN with
+     `max-height: 168px`, and a flex item's default `flex-shrink: 1` lets the browser squash it
+     below its content height to fit — so 40 results in a 168px box became 40 four-pixel rows,
+     each one's text spilling over its neighbour's. REPRODUCED before it was fixed: 662 matches
+     for "flow", the panel painting an unreadable stack of half-overlapping names.
+     ⚠ The `overflow-y: auto` on the list was never the problem and is not the fix: a scroller
+     only scrolls what it is allowed to leave at full height. It could not, so it never scrolled.
+     ⚠ Applies to BOTH pickers by construction (Start and Add a record are one component), which
+     is what the owner's "for both" describes. */
+  flex: 0 0 auto;
   padding: 5px 6px;
   border: 0;
   border-radius: 4px;