Deploy AIOS web (React glide grid + FastAPI slice)

RELEASES.json

@@ -1,5 +1,5 @@
 {
- "current": "2de35b7",
+ "current": "4c54929",
  "releases": [
   {
    "version": "v29",

VERSION

@@ -1 +1 @@
-2de35b7
+4c54929

web/src/customer-grid/ViewSidebar.tsx

@@ -288,12 +288,30 @@ interface ViewSidebarProps {
   agentPanel?: ReactNode;
   agentOpen?: boolean;
   onToggleAgent?: () => void;
+  /** ⭐⭐ OWNER, 2026-08-19 — the grid chat's launcher lives in THIS row, beside the minimize
+   *  control, exactly as the view agent's does. It was a text pill floating in the gap between
+   *  this rail and the grid; the owner called it *"ugly as hell"* and named where it belongs:
+   *  *"the same Navigation as the View navigation just beside its minimize icon"*.
+   *  ⚠ Optional, and ABSENT rather than disabled when the surface has no database to chat about
+   *  (embedded and Query bindings) — the same posture `onToggleAgent` takes one line up. */
+  chatOpen?: boolean;
+  /** ⛔ RENDERED AFTER the minimize toggle, never before it. W35-T28 made that control this
+   *  row's FIRST child on purpose and `verify_grid_ux.py`'s views-rail scan asserts the ordering,
+   *  so adding beside it is the instruction and re-ordering it would undo a shipped owner item to
+   *  satisfy a new one — the same rule the view-agent robot follows.
+   *  ⚠ IT IS AN ICON, NOT A LABEL. This row is a 26px control strip; the text pill is precisely
+   *  what made the old launcher read as bolted on. The sentence it used to show ("Ask about this
+   *  data") is now the `aria-label` AND the `title`, so nothing is lost to a screen reader or to
+   *  a hover — moving a control must not quietly cost its name. */
+  onToggleChat?: () => void;
 }
 
 export default function ViewSidebar({
   agentPanel = null,
   agentOpen = false,
   onToggleAgent,
+  chatOpen = false,
+  onToggleChat,
   views,
   activeViewId,
   saveState,
@@ -812,6 +830,27 @@ export default function ViewSidebar({
             </svg>
           </button>
         )}
+        {/* ⭐⭐ OWNER 2026-08-19 — the chat launcher. AFTER the toggle, same rule as the robot.
+            Rationale is on the `onToggleChat` prop; kept short here because this row's source
+            region carries a 2,400-char cap that `verify_grid_ux.py`'s views-rail scan enforces. */}
+        {onToggleChat && (
+          <button
+            type="button"
+            className={"cg-chat-toggle" + (chatOpen ? " is-on" : "")}
+            aria-label={chatOpen ? "Close the chat about this data"
+                                 : "Ask about this data"}
+            aria-expanded={chatOpen}
+            title={chatOpen ? "Close the chat about this data" : "Ask about this data"}
+            onClick={onToggleChat}
+          >
+            <svg width="16" height="16" viewBox="0 0 16 16" fill="none" aria-hidden="true">
+              <path d="M13.4 9.2c0 1.5-1.3 2.7-2.9 2.7H6.9l-3 2.1v-2.3a2.8 2.8 0 0 1-1.3-2.3V5.1c0-1.5 1.3-2.7 2.9-2.7h5c1.6 0 2.9 1.2 2.9 2.7z"
+                    stroke="currentColor" strokeWidth="1.3" strokeLinejoin="round" />
+              <path d="M5.9 7.2h4.2" stroke="currentColor" strokeWidth="1.3"
+                    strokeLinecap="round" />
+            </svg>
+          </button>
+        )}
         {/* ⛔⛔ THE DATABASE'S OWN TOTAL IS DELETED FROM THIS ROW (W35-T27, owner item 9 / R4).
             Owner, verbatim: *"remove [the important count] anywhere else but the View itself."*
             W33-T16 put a summed badge here and W34-T20 stripped its label; item 9 removes the

web/src/customer-grid/chatDock.css

@@ -1,52 +1,48 @@
-/* customer-grid/chatDock.css — W37-T29 (contract C6 + C8): the chat's DOCK and its LAUNCHER.
- *
- * ⛔ A SEPARATE SHEET FROM E's `gridChat.css` ON PURPOSE, and the split is the contract rather
- * than taste. C8 hands `index.css` to lane A alone and tells every other lane to add styles in its
- * own per-surface sheet; E owns how the PANEL looks and this file owns where the HOST puts it and
- * how a person opens it. Two lanes editing one sheet is the collision C8 exists to prevent.
- *
- * ⛔⛔ THE LAUNCHER IS THE WHOLE REASON THIS FILE EXISTS. A panel with no control that opens it is
- * mounted-but-never-offered, which is this repo's most repeated defect: one wave shipped five whole,
- * correct, unreachable features past every gate. E's sheet cannot carry the launcher, because the
- * launcher is not part of the panel.
- * ⚠ Tokens only, never fresh hexes (DESIGN.md: navy #1F4E78 + gold #C8A24B). No emojis, no
- * ALL-CAPS chrome.
- */
-
-/* The dock: a flex child of `.cg-shell`, seated between the views rail and the grid, so the panel
-   reads as part of the workspace rather than as an overlay floating on top of it. E's `.cg-chat`
-   brings its own width floor, ceiling and left border; this wrapper only owns the seat. */
-.cg-chat-dock {
-  display: flex;
-  min-height: 0;
-  align-self: stretch;
-}
-
-/* The launcher. A rail-height strip rather than a floating bubble: a bubble would sit over the
-   grid's own rows, which is the one place a person is trying to read. */
-.cg-chat-open {
-  display: flex;
-  align-items: center;
-  gap: 6px;
-  align-self: flex-start;
-  margin: 8px 0 0 8px;
-  padding: 6px 10px;
-  border: 1px solid var(--lp-border, #e4e7ec);
-  border-radius: 6px;
-  background: var(--lp-surface, #ffffff);
-  color: var(--lp-ink, #1f2937);
-  font-size: var(--lp-fs-xs);
-  line-height: 1.2;
-  cursor: pointer;
-  white-space: nowrap;
-}
-
-.cg-chat-open:hover {
-  border-color: var(--lp-navy, #1f4e78);
-  color: var(--lp-navy, #1f4e78);
-}
-
-.cg-chat-open:focus-visible {
-  outline: 2px solid var(--lp-gold, #c8a24b);
-  outline-offset: 1px;
-}
+/* customer-grid/chatDock.css — W37-T29 (contract C6 + C8): the chat's DOCK and its LAUNCHER.
+ *
+ * ⛔ A SEPARATE SHEET FROM E's `gridChat.css` ON PURPOSE, and the split is the contract rather
+ * than taste. C8 hands `index.css` to lane A alone and tells every other lane to add styles in its
+ * own per-surface sheet; E owns how the PANEL looks and this file owns where the HOST puts it and
+ * how a person opens it. Two lanes editing one sheet is the collision C8 exists to prevent.
+ *
+ * ⛔⛔ THE LAUNCHER IS THE WHOLE REASON THIS FILE EXISTS. A panel with no control that opens it is
+ * mounted-but-never-offered, which is this repo's most repeated defect: one wave shipped five whole,
+ * correct, unreachable features past every gate. E's sheet cannot carry the launcher, because the
+ * launcher is not part of the panel.
+ * ⚠ Tokens only, never fresh hexes (DESIGN.md: navy #1F4E78 + gold #C8A24B). No emojis, no
+ * ALL-CAPS chrome.
+ */
+
+/* The dock: a flex child of `.cg-shell`, seated between the views rail and the grid, so the panel
+   reads as part of the workspace rather than as an overlay floating on top of it. E's `.cg-chat`
+   brings its own width floor, ceiling and left border; this wrapper only owns the seat. */
+.cg-chat-dock {
+  display: flex;
+  min-height: 0;
+  align-self: stretch;
+}
+
+/* ⭐⭐ THE LAUNCHER, MOVED 2026-08-19 ON THE OWNER'S INSTRUCTION.
+   It was `.cg-chat-open`: a text pill reading "Ask about this data", floating in the gap between
+   the views rail and the grid with a `margin: 8px 0 0 8px`. The owner called it *"ugly as hell"*
+   and said where it belongs — *"the same Navigation as the View navigation just beside its
+   minimize icon"*. It is now a 26px icon button INSIDE `.cg-views-top`, and these rules match
+   `.cg-agent-open` (scriptView.css) exactly, because the two controls sit side by side in one
+   26px strip and a launcher that is 2px taller than its neighbour is what reads as bolted on.
+   ⚠ The old class is GONE rather than left orphaned: a dead rule for a removed node is how a
+   later reader concludes the feature still has two entry points. */
+.cg-chat-toggle {
+  display: inline-flex;
+  align-items: center;
+  justify-content: center;
+  width: 26px;
+  height: 26px;
+  border: 0;
+  border-radius: 6px;
+  background: transparent;
+  color: var(--lp-text-muted, #667085);
+  cursor: pointer;
+}
+.cg-chat-toggle:hover { background: var(--lp-surface-sunken, #f2f4f7); }
+.cg-chat-toggle.is-on { background: var(--lp-surface-sunken, #f2f4f7); color: var(--lp-navy, #1f4e78); }
+.cg-chat-toggle:focus-visible { outline: 2px solid var(--lp-gold, #c8a24b); outline-offset: 1px; }