Deploy AIOS web (React glide grid + FastAPI slice)

RELEASES.json

@@ -1,6 +1,12 @@
 {
- "current": "v51 (5740d20)",
+ "current": "v52 (8263493)",
  "releases": [
+  {
+   "version": "v52",
+   "sha": "8263493",
+   "date": "2026-08-23",
+   "subject": "release v52"
+  },
   {
    "version": "v51",
    "sha": "5740d20",

VERSION

@@ -1 +1 @@
-v51 (5740d20)
+v52 (8263493)

web/src/customer-grid/useGridColumns.ts

@@ -1,391 +1,422 @@
-import { useCallback, useMemo } from "react";
-import type { GridColumn, Theme } from "@glideapps/glide-data-grid";
-import type { Field, FilterNode, ViewConfig } from "./types";
-import { isFilterGroup, isRuleActive, measureColumnIndex, ruleColumnKeys } from "./types";
-import { typeIconName } from "./iconShapes";
-import { fitHeaderTitle, headerLabelSpace, headerMarkSizes } from "./overlayPlacement";
-import { COLUMN_TONE_THEME, INVOLVED_HEADER_FONT, lightTheme } from "./theme";
-import type { ControlTone } from "./theme";
-
-const DEFAULT_WIDTH = 150;
-
-/**
- * Owner item 16 — measure header text in GLIDE'S OWN HEADER FONT.
- *
- * ⚠ NOT the cell font. Glide's `headerFontStyle` is "600 13px" and its `baseFontStyle` is
- * "13px" (`common/styles.js:73-75`); semibold is materially wider, so measuring with the cell
- * font under-measures, under-truncates, and leaves the label running under the (i) — the exact
- * defect this item is about, surviving a fix that looked correct in the diff.
- *
- * ⚠⚠ Wave-14 item 2 adds the SAME trap one weight up. An involved column paints its header at
- * **700** (`INVOLVED_HEADER_FONT`), so measuring every column at 600 would under-truncate
- * exactly the filtered/sorted/grouped columns — the ones the owner is looking at. Hence TWO
- * cached contexts, and both font strings are read off the theme layer rather than retyped here:
- * a literal in this file is a copy that can drift from the one glide actually paints with, which
- * is the whole failure mode above.
- *
- * ⚠ Wave-15 R5 gave each control its OWN hue, so there are now three involved-column themes
- * instead of one. They deliberately share `INVOLVED_HEADER_FONT`, so ONE bold context still
- * measures all three correctly — but the constant, not any one of the three theme objects, is
- * what this reads. Picking `COLUMN_TONE_THEME.filter.headerFontStyle` would have measured every
- * involved column against whichever tone happened to be listed first.
- *
- * One lazily-built offscreen context per weight, the same shape as CustomerGrid's
- * `measureCellText`. A context can legitimately be null (a headless canvas, a locked-down
- * embed); 0 then measures as "everything fits" and no title is truncated, which is the safe
- * direction to fail — a title that slightly overlaps beats one silently cut to "C…".
- */
-const _hdrCtx: Record<"base" | "bold", CanvasRenderingContext2D | null | undefined> = {
-  base: undefined,
-  bold: undefined,
-};
-function measureHeaderText(text: string, bold = false): number {
-  const slot = bold ? "bold" : "base";
-  if (_hdrCtx[slot] === undefined) {
-    const ctx = document.createElement("canvas").getContext("2d");
-    if (ctx) {
-      const style =
-        (bold ? INVOLVED_HEADER_FONT : lightTheme.headerFontStyle) ?? "600 13px";
-      ctx.font = `${style} ${lightTheme.fontFamily ?? "Inter, sans-serif"}`;
-    }
-    _hdrCtx[slot] = ctx;
-  }
-  const ctx = _hdrCtx[slot];
-  return ctx ? ctx.measureText(text).width : 0;
-}
-
-/** The (i) is drawn for exactly this condition — `CustomerGrid.drawGridHeader` resolves the
- *  same one from the same field, so the reserve and the mark can never disagree. */
-function hasInfoMark(field: Field): boolean {
-  return !!(field.note || field.description);
-}
-
-/** Every column key an ACTIVE filter rule names, anywhere in the tree. Inactive (half-typed)
- *  rules are skipped: a rule that is not narrowing anything must not tint a column as though
- *  it were — that is the same "it looks like it is working" lie the engine refuses to tell.
- *
- *  ⚠ Wave-20 item 2: the key a rule NAMES is not always the column it is ABOUT — a measure
- *  condition carries the MEASURE key. `ruleColumnKeys` is the one resolution (types.ts); it
- *  is what stopped a filtered-and-sorted measure column wearing the sort hue. */
-function filteredKeys(
-  nodes: FilterNode[],
-  out: Set<string>,
-  measureCols: Map<string, string[]>
-): void {
-  for (const node of nodes ?? []) {
-    if (isFilterGroup(node)) {
-      filteredKeys(node.children, out, measureCols);
-      continue;
-    }
-    if (isRuleActive(node)) for (const key of ruleColumnKeys(node, measureCols)) out.add(key);
-  }
-}
-
-/**
- * The column's theme override, or `undefined` — glide's fast path for "no override" is an absent
- * object, so an empty `{}` would cost a ~35-key theme merge per column per frame.
- *
- * ⚠ Wave-14 item 1 (R11): a user-created field contributes no theme. Its yellow header wash is
- * dead and its replacement is a painted DOT, not a background — so the only thing that can put a
- * themeOverride on a column is being INVOLVED in a control.
- *
- * ⚠ Wave-15 R5: the returned object is one of the three SHARED `COLUMN_TONE_THEME` references
- * (never a fresh object), which is what keeps glide's theme merge cache-friendly across frames.
- *
- * ⛔ Wave-29 R8 (2026-08-11): those three references now carry **HEADER keys only**. glide builds a
- * header theme from the column override alone and a cell theme from column → row ��� cell
- * (`data-grid-render.header.js:59`, `common/styles.js mergeAndRealizeTheme`), so the tone reaching
- * a column theme is exactly how a sort used to repaint record bodies. With no `bgCell` in the
- * table there is no longer a path from "this column is sorted" to a cell's background at all —
- * which is a property of what `COLUMN_TONE_THEME` CONTAINS, not of anything this function does.
- * A body wash belongs to `getRowThemeOverride` (status) or the cell itself (automation).
- */
-function columnTheme(tone: ControlTone | undefined): Partial<Theme> | undefined {
-  return tone ? COLUMN_TONE_THEME[tone] : undefined;
-}
-
-/**
- * Owner item 22 — key → which control involves it, or absent.
- *
- * ⚠ ONE tone per column, and the precedence is a decision, not an accident: **filter > sort >
- * group** (owner R6, wave 15). A filter changes WHICH ROWS you are looking at; when a column is
- * doing two jobs the header names the most consequential one. Blending two tints would produce a
- * third colour that matches no chip in the toolbar, which is worse than picking.
- *
- * ⚠ THE PRECEDENCE IS THE WRITE ORDER BELOW, and it reads backwards: later `set` calls WIN, so
- * the least important control is written FIRST. It was `sort, group, filter` — i.e. filter >
- * group > sort — until R6 named the order explicitly; getting this wrong is a one-line edit that
- * changes a colour on screen and nothing else, so it is stated here rather than left to be
- * re-derived from the sequence.
- */
-/* wave17 GRID — item 2 / owner R5. EXPORTED, and only since the row band died.
-   `activeControlTone` used to sit below this function and restate the same precedence for the
-   whole-table band; the band was its only consumer, so R5 took both. That left the surviving
-   precedence — the one that still paints — asserted by nothing, because `verify_icons` was
-   testing the twin. Exported so the gate can reach the function that is actually on screen. */
-export function columnTones(
-  config: ViewConfig,
-  /* wave20 item 2 — the FIELDS, because a measure condition names its measure and only the
-     field list can say which column displays it. Defaulted so the signature stays callable
-     with a config alone (the pre-wave-20 gate legs), and because a caller with no fields
-     legitimately has no measure columns to resolve. */
-  fields: Field[] = []
-): Map<string, ControlTone> {
-  const out = new Map<string, ControlTone>();
-  if (config.groupBy) out.set(config.groupBy, "group");
-  for (const s of config.sorts ?? []) out.set(s.colId, "sort");
-  const filtered = new Set<string>();
-  filteredKeys(config.filters ?? [], filtered, measureColumnIndex(fields));
-  for (const key of filtered) out.set(key, "filter");
-  return out;
-}
-
-/**
- * ⭐ WAVE 30 (owner item 2 scouting) — THE OVERLAY ARM IS GONE, and the arithmetic is the reason.
- *
- * This read `field.default !== false || field.source === "overlay"`. The second arm was written
- * when `overlay` meant "a column a user added here", and those columns have no `default` key at
- * all — so the arm was a belt-and-braces no-op for them. Then `user_tables._clean_field` started
- * stamping `source: "overlay"` on EVERY `ut_*` field, and every connected database became a `ut_*`
- * one: the exception quietly became the rule and swallowed the first arm entirely.
- *
- * ⛔ WHAT THAT COST, measured on the live orders grid: `odoo_relational.order_fields` declares
- * `default: False` on `odoo_id`, `state`, `customer_link` and `partner_id`, and every one of them
- * opened SHOWN. The grid arrives wide, and "Hide fields" reads inactive because
- * `shownCount === fields.length` — so the control that says "some columns are hidden" says the
- * opposite of what its own table declares. A second instance of [[fallback-that-became-the-rule]].
- *
- * ⚠ DROPPING THE ARM DOES NOT HIDE USER COLUMNS, and this is the check that matters before
- * believing the fix. A column somebody created carries no `default` key, `undefined !== false` is
- * true, and it stays visible. `_clean_field` also keeps `default` ONLY when it is `True`, so a
- * `ut_*` column can never arrive carrying `default: false` by accident — only a shipped field
- * CONTRACT (which is written straight into the store, bypassing that validator) can declare it.
- *
- * ⚠ THIS PREDICATE HAS A SERVER TWIN and the twin is the one that decides on first open:
- * `platform/aios_grid.py:_default_view_config` carries the same expression and builds the "All
- * records" system view the client pins as its landing default. Fixing one side alone changes
- * nothing a user sees — see `mailbox/F.md` F-1 ([[one-question-two-normalizers]] across two
- * languages).
- */
-function isDefaultVisible(field: Field): boolean {
-  return field.default !== false;
-}
-
-export function defaultViewConfig(fields: Field[]): ViewConfig {
-  const shown = fields.filter(isDefaultVisible).map((field) => field.key);
-  const hidden = fields.filter((field) => !isDefaultVisible(field)).map((field) => field.key);
-  return {
-    filters: [],
-    filterConj: "and",
-    sorts: [],
-    groupBy: null,
-    colorBy: null,
-    rowHeightMode: "short",
-    order: [...shown, ...hidden],
-    visible: shown,
-    widths: {},
-    memberPids: [],
-  };
-}
-
-function reconcileOrder(order: string[], fields: Field[]): string[] {
-  const valid = new Set(fields.map((field) => field.key));
-  const kept = order.filter((key, index) => valid.has(key) && order.indexOf(key) === index);
-  for (const field of fields) if (!kept.includes(field.key)) kept.push(field.key);
-  const locked = fields.find((field) => field.pinned)?.key ?? fields[0]?.key;
-  if (locked && kept[0] !== locked) {
-    const without = kept.filter((key) => key !== locked);
-    return [locked, ...without];
-  }
-  return kept;
-}
-
-function reconcileVisible(visible: string[], fields: Field[], lockedKey: string): Set<string> {
-  const valid = new Set(fields.map((field) => field.key));
-  const out = new Set(visible.filter((key) => valid.has(key)));
-  if (out.size === 0) {
-    for (const field of fields) if (isDefaultVisible(field)) out.add(field.key);
-  }
-  if (lockedKey) out.add(lockedKey);
-  return out;
-}
-
-export interface GridColumnsApi {
-  visibleCols: GridColumn[];
-  fieldByKey: Map<string, Field>;
-  order: string[];
-  visible: Set<string>;
-  widths: Record<string, number>;
-  lockedKey: string;
-  onColumnResize: (col: GridColumn, newSize: number) => void;
-  onColumnMoved: (from: number, to: number) => void;
-  onColumnProposeMove: (from: number, to: number) => boolean;
-  setColumnVisible: (key: string, show: boolean) => void;
-  insertColumn: (key: string, anchorKey: string | null, side: "left" | "right" | "end") => void;
-}
-
-/**
- * Controlled column adapter. ViewConfig is the durable source of truth, so
- * choosing a saved view is one atomic state change instead of a chain of hook
- * setters that can flash or overwrite one another.
- */
-export function useGridColumns(
-  fields: Field[],
-  config: ViewConfig,
-  onConfig: (next: ViewConfig) => void
-): GridColumnsApi {
-  const fieldByKey = useMemo(
-    () => new Map(fields.map((field) => [field.key, field])),
-    [fields]
-  );
-  const lockedKey = useMemo(
-    () => fields.find((field) => field.pinned)?.key ?? fields[0]?.key ?? "",
-    [fields]
-  );
-  const order = useMemo(() => reconcileOrder(config.order, fields), [config.order, fields]);
-  const visible = useMemo(
-    () => reconcileVisible(config.visible, fields, lockedKey),
-    [config.visible, fields, lockedKey]
-  );
-
-  // Item 22 — recomputed only when the three controls move, not on every width drag.
-  // Wave-20 item 2 adds `fields`: a measure condition can only be resolved to the column that
-  // displays it, and a new measure column must re-tint without waiting for a control to move.
-  const tones = useMemo(
-    () => columnTones(config, fields),
-    [config.filters, config.sorts, config.groupBy, fields]  // eslint-disable-line react-hooks/exhaustive-deps
-  );
-
-  const visibleCols = useMemo<GridColumn[]>(
-    () =>
-      order
-        .filter((key) => visible.has(key))
-        .map((key) => {
-          const field = fieldByKey.get(key)!;
-          const width = config.widths[key] ?? DEFAULT_WIDTH;
-          // Wave-14 item 2 — an INVOLVED column's header paints at 700, so it must be MEASURED
-          // at 700. `tones` is already a dep of this memo, so this costs nothing.
-          const involved = tones.has(key);
-          // R11 — the marks this header carries, in the strip's canonical order. Both this
-          // reserve and `CustomerGrid.drawGridHeader`'s painting read `headerMarkSizes`, so a
-          // column can never reserve room for one mark and then be given two.
-          const marks = headerMarkSizes(hasInfoMark(field), field.source === "overlay");
-          return {
-            id: key,
-            // Owner item 16 — ELLIPSISED so the title can never run under the (i). Glide
-            // truncates nothing: `drawHeaderInner` calls `fillText(c.title, …)` with no clip
-            // and no max width, so on a narrow column the name simply painted through the
-            // mark. Shortening the title glide is given is the whole fix — the alternative,
-            // clipping inside `drawHeader`, cuts mid-glyph with no ellipsis to say it did.
-            // The FULL name stays reachable: CustomerGrid's header tip leads with it whenever
-            // this returns something shorter than `field.label`.
-            title: fitHeaderTitle(
-              field.label,
-              headerLabelSpace(width, marks),
-              (text) => measureHeaderText(text, involved)
-            ),
-            width,
-            hasMenu: true,
-            menuIcon: "dots",
-            // Wave-8 I20 — the field-TYPE mark leads every header, so the column says what
-            // KIND of thing it holds before you read a single cell (same geometry as the
-            // Fields panel's rows — icons.tsx).
-            icon: typeIconName(field.type),
-            // Wave-9 I3 — the (i) is NO LONGER `overlayIcon`. Glide draws an overlay at a
-            // hard-coded offset from the TYPE mark (drawHeaderInner: `drawX + 9`), i.e.
-            // pinned to the far LEFT of the header, and no prop moves it; the owner asked
-            // for it right-aligned and centred with the field name. It is drawn instead by
-            // CustomerGrid's `drawHeader` callback, which resolves the same
-            // `field.note || field.description` condition from the field itself.
-            // The hover text is still CustomerGrid's floating tip (pointer-events: none —
-            // a tooltip must never swallow the next click, [[ui-invisible-to-assertions]]).
-            // Wave-14 R4 — being INVOLVED in a filter/sort/group is the only thing that tints a
-            // column now, and all three tint it the same faint warm grey; the hue that says
-            // WHICH control lives on the toolbar chip. User-created ownership moved out of the
-            // theme entirely and is the dot drawn in the mark strip (R11).
-            themeOverride: columnTheme(tones.get(key)),
-          };
-        }),
-    [order, visible, config.widths, fieldByKey, tones]
-  );
-
-  const onColumnResize = useCallback(
-    (column: GridColumn, newSize: number) => {
-      if (!column.id) return;
-      onConfig({
-        ...config,
-        widths: { ...config.widths, [column.id]: Math.round(newSize) },
-      });
-    },
-    [config, onConfig]
-  );
-
-  const onColumnMoved = useCallback(
-    (from: number, to: number) => {
-      if (from === 0 || to === 0) return;
-      const visibleKeys = order.filter((key) => visible.has(key));
-      if (
-        from < 0 ||
-        from >= visibleKeys.length ||
-        to < 0 ||
-        to >= visibleKeys.length
-      )
-        return;
-      const movedKeys = visibleKeys.slice();
-      const [moved] = movedKeys.splice(from, 1);
-      movedKeys.splice(to, 0, moved);
-      let index = 0;
-      const nextOrder = order.map((key) =>
-        visible.has(key) ? movedKeys[index++] : key
-      );
-      onConfig({ ...config, order: nextOrder });
-    },
-    [config, onConfig, order, visible]
-  );
-
-  const onColumnProposeMove = useCallback(
-    (from: number, to: number) => from !== 0 && to !== 0,
-    []
-  );
-
-  const setColumnVisible = useCallback(
-    (key: string, show: boolean) => {
-      if (!show && key === lockedKey) return;
-      const next = new Set(visible);
-      if (show) next.add(key);
-      else next.delete(key);
-      onConfig({ ...config, visible: [...next] });
-    },
-    [config, lockedKey, onConfig, visible]
-  );
-
-  const insertColumn = useCallback(
-    (key: string, anchorKey: string | null, side: "left" | "right" | "end") => {
-      const nextOrder = order.filter((item) => item !== key);
-      if (side === "end" || !anchorKey) {
-        nextOrder.push(key);
-      } else {
-        const anchor = Math.max(0, nextOrder.indexOf(anchorKey));
-        nextOrder.splice(anchor + (side === "right" ? 1 : 0), 0, key);
-      }
-      const nextVisible = new Set(visible);
-      nextVisible.add(key);
-      onConfig({ ...config, order: nextOrder, visible: [...nextVisible] });
-    },
-    [config, onConfig, order, visible]
-  );
-
-  return {
-    visibleCols,
-    fieldByKey,
-    order,
-    visible,
-    widths: config.widths,
-    lockedKey,
-    onColumnResize,
-    onColumnMoved,
-    onColumnProposeMove,
-    setColumnVisible,
-    insertColumn,
-  };
-}
+import { useCallback, useMemo } from "react";
+import type { GridColumn, Theme } from "@glideapps/glide-data-grid";
+import type { Field, FilterNode, ViewConfig } from "./types";
+import { isFilterGroup, isRuleActive, measureColumnIndex, ruleColumnKeys } from "./types";
+import { typeIconName } from "./iconShapes";
+import { fitHeaderTitle, headerLabelSpace, headerMarkSizes } from "./overlayPlacement";
+import { COLUMN_TONE_THEME, INVOLVED_HEADER_FONT, lightTheme } from "./theme";
+import type { ControlTone } from "./theme";
+
+const DEFAULT_WIDTH = 150;
+
+/**
+ * Owner item 16 — measure header text in GLIDE'S OWN HEADER FONT.
+ *
+ * ⚠ NOT the cell font. Glide's `headerFontStyle` is "600 13px" and its `baseFontStyle` is
+ * "13px" (`common/styles.js:73-75`); semibold is materially wider, so measuring with the cell
+ * font under-measures, under-truncates, and leaves the label running under the (i) — the exact
+ * defect this item is about, surviving a fix that looked correct in the diff.
+ *
+ * ⚠⚠ Wave-14 item 2 adds the SAME trap one weight up. An involved column paints its header at
+ * **700** (`INVOLVED_HEADER_FONT`), so measuring every column at 600 would under-truncate
+ * exactly the filtered/sorted/grouped columns — the ones the owner is looking at. Hence TWO
+ * cached contexts, and both font strings are read off the theme layer rather than retyped here:
+ * a literal in this file is a copy that can drift from the one glide actually paints with, which
+ * is the whole failure mode above.
+ *
+ * ⚠ Wave-15 R5 gave each control its OWN hue, so there are now three involved-column themes
+ * instead of one. They deliberately share `INVOLVED_HEADER_FONT`, so ONE bold context still
+ * measures all three correctly — but the constant, not any one of the three theme objects, is
+ * what this reads. Picking `COLUMN_TONE_THEME.filter.headerFontStyle` would have measured every
+ * involved column against whichever tone happened to be listed first.
+ *
+ * One lazily-built offscreen context per weight, the same shape as CustomerGrid's
+ * `measureCellText`. A context can legitimately be null (a headless canvas, a locked-down
+ * embed); 0 then measures as "everything fits" and no title is truncated, which is the safe
+ * direction to fail — a title that slightly overlaps beats one silently cut to "C…".
+ */
+const _hdrCtx: Record<"base" | "bold", CanvasRenderingContext2D | null | undefined> = {
+  base: undefined,
+  bold: undefined,
+};
+function measureHeaderText(text: string, bold = false): number {
+  const slot = bold ? "bold" : "base";
+  if (_hdrCtx[slot] === undefined) {
+    const ctx = document.createElement("canvas").getContext("2d");
+    if (ctx) {
+      const style =
+        (bold ? INVOLVED_HEADER_FONT : lightTheme.headerFontStyle) ?? "600 13px";
+      ctx.font = `${style} ${lightTheme.fontFamily ?? "Inter, sans-serif"}`;
+    }
+    _hdrCtx[slot] = ctx;
+  }
+  const ctx = _hdrCtx[slot];
+  return ctx ? ctx.measureText(text).width : 0;
+}
+
+/** The (i) is drawn for exactly this condition — `CustomerGrid.drawGridHeader` resolves the
+ *  same one from the same field, so the reserve and the mark can never disagree. */
+function hasInfoMark(field: Field): boolean {
+  return !!(field.note || field.description);
+}
+
+/** Every column key an ACTIVE filter rule names, anywhere in the tree. Inactive (half-typed)
+ *  rules are skipped: a rule that is not narrowing anything must not tint a column as though
+ *  it were — that is the same "it looks like it is working" lie the engine refuses to tell.
+ *
+ *  ⚠ Wave-20 item 2: the key a rule NAMES is not always the column it is ABOUT — a measure
+ *  condition carries the MEASURE key. `ruleColumnKeys` is the one resolution (types.ts); it
+ *  is what stopped a filtered-and-sorted measure column wearing the sort hue. */
+function filteredKeys(
+  nodes: FilterNode[],
+  out: Set<string>,
+  measureCols: Map<string, string[]>
+): void {
+  for (const node of nodes ?? []) {
+    if (isFilterGroup(node)) {
+      filteredKeys(node.children, out, measureCols);
+      continue;
+    }
+    if (isRuleActive(node)) for (const key of ruleColumnKeys(node, measureCols)) out.add(key);
+  }
+}
+
+/**
+ * The column's theme override, or `undefined` — glide's fast path for "no override" is an absent
+ * object, so an empty `{}` would cost a ~35-key theme merge per column per frame.
+ *
+ * ⚠ Wave-14 item 1 (R11): a user-created field contributes no theme. Its yellow header wash is
+ * dead and its replacement is a painted DOT, not a background — so the only thing that can put a
+ * themeOverride on a column is being INVOLVED in a control.
+ *
+ * ⚠ Wave-15 R5: the returned object is one of the three SHARED `COLUMN_TONE_THEME` references
+ * (never a fresh object), which is what keeps glide's theme merge cache-friendly across frames.
+ *
+ * ⛔ Wave-29 R8 (2026-08-11): those three references now carry **HEADER keys only**. glide builds a
+ * header theme from the column override alone and a cell theme from column → row → cell
+ * (`data-grid-render.header.js:59`, `common/styles.js mergeAndRealizeTheme`), so the tone reaching
+ * a column theme is exactly how a sort used to repaint record bodies. With no `bgCell` in the
+ * table there is no longer a path from "this column is sorted" to a cell's background at all —
+ * which is a property of what `COLUMN_TONE_THEME` CONTAINS, not of anything this function does.
+ * A body wash belongs to `getRowThemeOverride` (status) or the cell itself (automation).
+ */
+function columnTheme(tone: ControlTone | undefined): Partial<Theme> | undefined {
+  return tone ? COLUMN_TONE_THEME[tone] : undefined;
+}
+
+/**
+ * Owner item 22 — key → which control involves it, or absent.
+ *
+ * ⚠ ONE tone per column, and the precedence is a decision, not an accident: **filter > sort >
+ * group** (owner R6, wave 15). A filter changes WHICH ROWS you are looking at; when a column is
+ * doing two jobs the header names the most consequential one. Blending two tints would produce a
+ * third colour that matches no chip in the toolbar, which is worse than picking.
+ *
+ * ⚠ THE PRECEDENCE IS THE WRITE ORDER BELOW, and it reads backwards: later `set` calls WIN, so
+ * the least important control is written FIRST. It was `sort, group, filter` — i.e. filter >
+ * group > sort — until R6 named the order explicitly; getting this wrong is a one-line edit that
+ * changes a colour on screen and nothing else, so it is stated here rather than left to be
+ * re-derived from the sequence.
+ */
+/* wave17 GRID — item 2 / owner R5. EXPORTED, and only since the row band died.
+   `activeControlTone` used to sit below this function and restate the same precedence for the
+   whole-table band; the band was its only consumer, so R5 took both. That left the surviving
+   precedence — the one that still paints — asserted by nothing, because `verify_icons` was
+   testing the twin. Exported so the gate can reach the function that is actually on screen. */
+export function columnTones(
+  config: ViewConfig,
+  /* wave20 item 2 — the FIELDS, because a measure condition names its measure and only the
+     field list can say which column displays it. Defaulted so the signature stays callable
+     with a config alone (the pre-wave-20 gate legs), and because a caller with no fields
+     legitimately has no measure columns to resolve. */
+  fields: Field[] = []
+): Map<string, ControlTone> {
+  const out = new Map<string, ControlTone>();
+  if (config.groupBy) out.set(config.groupBy, "group");
+  for (const s of config.sorts ?? []) out.set(s.colId, "sort");
+  const filtered = new Set<string>();
+  filteredKeys(config.filters ?? [], filtered, measureColumnIndex(fields));
+  for (const key of filtered) out.set(key, "filter");
+  return out;
+}
+
+/**
+ * ⭐ WAVE 30 (owner item 2 scouting) — THE OVERLAY ARM IS GONE, and the arithmetic is the reason.
+ *
+ * This read `field.default !== false || field.source === "overlay"`. The second arm was written
+ * when `overlay` meant "a column a user added here", and those columns have no `default` key at
+ * all — so the arm was a belt-and-braces no-op for them. Then `user_tables._clean_field` started
+ * stamping `source: "overlay"` on EVERY `ut_*` field, and every connected database became a `ut_*`
+ * one: the exception quietly became the rule and swallowed the first arm entirely.
+ *
+ * ⛔ WHAT THAT COST, measured on the live orders grid: `odoo_relational.order_fields` declares
+ * `default: False` on `odoo_id`, `state`, `customer_link` and `partner_id`, and every one of them
+ * opened SHOWN. The grid arrives wide, and "Hide fields" reads inactive because
+ * `shownCount === fields.length` — so the control that says "some columns are hidden" says the
+ * opposite of what its own table declares. A second instance of [[fallback-that-became-the-rule]].
+ *
+ * ⚠ DROPPING THE ARM DOES NOT HIDE USER COLUMNS, and this is the check that matters before
+ * believing the fix. A column somebody created carries no `default` key, `undefined !== false` is
+ * true, and it stays visible. `_clean_field` also keeps `default` ONLY when it is `True`, so a
+ * `ut_*` column can never arrive carrying `default: false` by accident — only a shipped field
+ * CONTRACT (which is written straight into the store, bypassing that validator) can declare it.
+ *
+ * ⚠ THIS PREDICATE HAS A SERVER TWIN and the twin is the one that decides on first open:
+ * `platform/aios_grid.py:_default_view_config` carries the same expression and builds the "All
+ * records" system view the client pins as its landing default. Fixing one side alone changes
+ * nothing a user sees — see `mailbox/F.md` F-1 ([[one-question-two-normalizers]] across two
+ * languages).
+ */
+function isDefaultVisible(field: Field): boolean {
+  if (field.default === false) return false;
+  /**
+   * ⭐⭐ OWNER, 2026-08-23 — A NEW VIEW SHOWS THE DATABASE'S OWN COLUMNS AND NOTHING ELSE.
+   *
+   * Owner: *"when any new View is created only shareable pre-set data should show. Shared to me
+   * or Shared to everyone should be auto hidden."*
+   *
+   * ⛔ `custom || shared` IS THE WHOLE PREDICATE, and it is chosen because it is exactly the
+   * membership test `FieldsHidePanel` already uses to draw its two SHARED sections:
+   *     "Shared with me"       (field.custom || field.shared) && fieldEditMode === "users"
+   *     "Shared with everyone" (field.custom || field.shared) && fieldEditMode === "collaborative"
+   * Both sections are subsets of `custom || shared`, so hiding on that flag hides both by
+   * construction rather than by keeping a second list of section names in step with the panel.
+   *
+   * ⚠ IT ALSO HIDES THE UNTITLED SECTION'S CREATED COLUMNS, and that is deliberate rather than
+   * over-reach. A route order carries `shared: true` with `edit: personal`, so it is filed under
+   * no heading at all — and 52 of them landed on the customer grid the same day this was asked
+   * for. The owner's first sentence is the rule ("ONLY pre-set data shows"); the second names the
+   * two headings, it does not bound the set.
+   *
+   * ⚠ MEASURED ON THE LIVE CUSTOMER GRID before it was written: of 105 fields, 77 opened SHOWN.
+   * 52 route columns, 14 collaborative `custom_*`, 3 `measure_*`, one legacy route and 7 plain
+   * Odoo columns. After this, the 7 remain — which is precisely what
+   * `aios_grid_fields.json` declares as `default: true`, i.e. the contract's own answer before
+   * anybody's columns piled on top of it.
+   *
+   * ⛔⛔ A STORED VIEW IS UNTOUCHED. `normalizeConfig` spreads the saved `config` OVER this
+   * base, so a view that already recorded its own `visible` keeps it. What moves is a view born
+   * without one: the "All records" system view, a new view, a cohort view.
+   */
+  if (field.custom === true || field.shared === true) return false;
+  return true;
+}
+
+export function defaultViewConfig(fields: Field[]): ViewConfig {
+  const shown = fields.filter(isDefaultVisible).map((field) => field.key);
+  const hidden = fields.filter((field) => !isDefaultVisible(field)).map((field) => field.key);
+  return {
+    filters: [],
+    filterConj: "and",
+    sorts: [],
+    groupBy: null,
+    colorBy: null,
+    rowHeightMode: "short",
+    order: [...shown, ...hidden],
+    visible: shown,
+    widths: {},
+    memberPids: [],
+  };
+}
+
+function reconcileOrder(order: string[], fields: Field[]): string[] {
+  const valid = new Set(fields.map((field) => field.key));
+  const kept = order.filter((key, index) => valid.has(key) && order.indexOf(key) === index);
+  for (const field of fields) if (!kept.includes(field.key)) kept.push(field.key);
+  const locked = fields.find((field) => field.pinned)?.key ?? fields[0]?.key;
+  if (locked && kept[0] !== locked) {
+    const without = kept.filter((key) => key !== locked);
+    return [locked, ...without];
+  }
+  return kept;
+}
+
+function reconcileVisible(visible: string[], fields: Field[], lockedKey: string): Set<string> {
+  const valid = new Set(fields.map((field) => field.key));
+  const out = new Set(visible.filter((key) => valid.has(key)));
+  if (out.size === 0) {
+    for (const field of fields) if (isDefaultVisible(field)) out.add(field.key);
+  }
+  if (lockedKey) out.add(lockedKey);
+  return out;
+}
+
+export interface GridColumnsApi {
+  visibleCols: GridColumn[];
+  fieldByKey: Map<string, Field>;
+  order: string[];
+  visible: Set<string>;
+  widths: Record<string, number>;
+  lockedKey: string;
+  onColumnResize: (col: GridColumn, newSize: number) => void;
+  onColumnMoved: (from: number, to: number) => void;
+  onColumnProposeMove: (from: number, to: number) => boolean;
+  setColumnVisible: (key: string, show: boolean) => void;
+  insertColumn: (key: string, anchorKey: string | null, side: "left" | "right" | "end") => void;
+}
+
+/**
+ * Controlled column adapter. ViewConfig is the durable source of truth, so
+ * choosing a saved view is one atomic state change instead of a chain of hook
+ * setters that can flash or overwrite one another.
+ */
+export function useGridColumns(
+  fields: Field[],
+  config: ViewConfig,
+  onConfig: (next: ViewConfig) => void
+): GridColumnsApi {
+  const fieldByKey = useMemo(
+    () => new Map(fields.map((field) => [field.key, field])),
+    [fields]
+  );
+  const lockedKey = useMemo(
+    () => fields.find((field) => field.pinned)?.key ?? fields[0]?.key ?? "",
+    [fields]
+  );
+  const order = useMemo(() => reconcileOrder(config.order, fields), [config.order, fields]);
+  const visible = useMemo(
+    () => reconcileVisible(config.visible, fields, lockedKey),
+    [config.visible, fields, lockedKey]
+  );
+
+  // Item 22 — recomputed only when the three controls move, not on every width drag.
+  // Wave-20 item 2 adds `fields`: a measure condition can only be resolved to the column that
+  // displays it, and a new measure column must re-tint without waiting for a control to move.
+  const tones = useMemo(
+    () => columnTones(config, fields),
+    [config.filters, config.sorts, config.groupBy, fields]  // eslint-disable-line react-hooks/exhaustive-deps
+  );
+
+  const visibleCols = useMemo<GridColumn[]>(
+    () =>
+      order
+        .filter((key) => visible.has(key))
+        .map((key) => {
+          const field = fieldByKey.get(key)!;
+          const width = config.widths[key] ?? DEFAULT_WIDTH;
+          // Wave-14 item 2 — an INVOLVED column's header paints at 700, so it must be MEASURED
+          // at 700. `tones` is already a dep of this memo, so this costs nothing.
+          const involved = tones.has(key);
+          // R11 — the marks this header carries, in the strip's canonical order. Both this
+          // reserve and `CustomerGrid.drawGridHeader`'s painting read `headerMarkSizes`, so a
+          // column can never reserve room for one mark and then be given two.
+          const marks = headerMarkSizes(hasInfoMark(field), field.source === "overlay");
+          return {
+            id: key,
+            // Owner item 16 — ELLIPSISED so the title can never run under the (i). Glide
+            // truncates nothing: `drawHeaderInner` calls `fillText(c.title, …)` with no clip
+            // and no max width, so on a narrow column the name simply painted through the
+            // mark. Shortening the title glide is given is the whole fix — the alternative,
+            // clipping inside `drawHeader`, cuts mid-glyph with no ellipsis to say it did.
+            // The FULL name stays reachable: CustomerGrid's header tip leads with it whenever
+            // this returns something shorter than `field.label`.
+            title: fitHeaderTitle(
+              field.label,
+              headerLabelSpace(width, marks),
+              (text) => measureHeaderText(text, involved)
+            ),
+            width,
+            hasMenu: true,
+            menuIcon: "dots",
+            // Wave-8 I20 — the field-TYPE mark leads every header, so the column says what
+            // KIND of thing it holds before you read a single cell (same geometry as the
+            // Fields panel's rows — icons.tsx).
+            icon: typeIconName(field.type),
+            // Wave-9 I3 — the (i) is NO LONGER `overlayIcon`. Glide draws an overlay at a
+            // hard-coded offset from the TYPE mark (drawHeaderInner: `drawX + 9`), i.e.
+            // pinned to the far LEFT of the header, and no prop moves it; the owner asked
+            // for it right-aligned and centred with the field name. It is drawn instead by
+            // CustomerGrid's `drawHeader` callback, which resolves the same
+            // `field.note || field.description` condition from the field itself.
+            // The hover text is still CustomerGrid's floating tip (pointer-events: none —
+            // a tooltip must never swallow the next click, [[ui-invisible-to-assertions]]).
+            // Wave-14 R4 — being INVOLVED in a filter/sort/group is the only thing that tints a
+            // column now, and all three tint it the same faint warm grey; the hue that says
+            // WHICH control lives on the toolbar chip. User-created ownership moved out of the
+            // theme entirely and is the dot drawn in the mark strip (R11).
+            themeOverride: columnTheme(tones.get(key)),
+          };
+        }),
+    [order, visible, config.widths, fieldByKey, tones]
+  );
+
+  const onColumnResize = useCallback(
+    (column: GridColumn, newSize: number) => {
+      if (!column.id) return;
+      onConfig({
+        ...config,
+        widths: { ...config.widths, [column.id]: Math.round(newSize) },
+      });
+    },
+    [config, onConfig]
+  );
+
+  const onColumnMoved = useCallback(
+    (from: number, to: number) => {
+      if (from === 0 || to === 0) return;
+      const visibleKeys = order.filter((key) => visible.has(key));
+      if (
+        from < 0 ||
+        from >= visibleKeys.length ||
+        to < 0 ||
+        to >= visibleKeys.length
+      )
+        return;
+      const movedKeys = visibleKeys.slice();
+      const [moved] = movedKeys.splice(from, 1);
+      movedKeys.splice(to, 0, moved);
+      let index = 0;
+      const nextOrder = order.map((key) =>
+        visible.has(key) ? movedKeys[index++] : key
+      );
+      onConfig({ ...config, order: nextOrder });
+    },
+    [config, onConfig, order, visible]
+  );
+
+  const onColumnProposeMove = useCallback(
+    (from: number, to: number) => from !== 0 && to !== 0,
+    []
+  );
+
+  const setColumnVisible = useCallback(
+    (key: string, show: boolean) => {
+      if (!show && key === lockedKey) return;
+      const next = new Set(visible);
+      if (show) next.add(key);
+      else next.delete(key);
+      onConfig({ ...config, visible: [...next] });
+    },
+    [config, lockedKey, onConfig, visible]
+  );
+
+  const insertColumn = useCallback(
+    (key: string, anchorKey: string | null, side: "left" | "right" | "end") => {
+      const nextOrder = order.filter((item) => item !== key);
+      if (side === "end" || !anchorKey) {
+        nextOrder.push(key);
+      } else {
+        const anchor = Math.max(0, nextOrder.indexOf(anchorKey));
+        nextOrder.splice(anchor + (side === "right" ? 1 : 0), 0, key);
+      }
+      const nextVisible = new Set(visible);
+      nextVisible.add(key);
+      onConfig({ ...config, order: nextOrder, visible: [...nextVisible] });
+    },
+    [config, onConfig, order, visible]
+  );
+
+  return {
+    visibleCols,
+    fieldByKey,
+    order,
+    visible,
+    widths: config.widths,
+    lockedKey,
+    onColumnResize,
+    onColumnMoved,
+    onColumnProposeMove,
+    setColumnVisible,
+    insertColumn,
+  };
+}