From a5154e696942199b1db7964439c4d69a699eea68 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 26 Oct 2026 20:06:37 +0000
Subject: [PATCH 1/4] refactor(plugin-grid): move ObjectGrid's module-level
 helpers into sibling modules (slice 1)

Move-only: the query helpers, column helpers and emit types, the link cell,
the fallback translations, the display defaults and the row-version helpers
leave ObjectGrid.tsx verbatim for six sibling modules. ObjectGrid.tsx imports
them back and re-exports every name it exported before.

Claude-Session: https://claude.ai/code/session_01Bdrd2yH4eqnz2QobtN3haE
Co-authored-by: Claude <noreply@anthropic.com>
---
 ui/packages/plugin-grid/src/ObjectGrid.tsx    | 983 +-----------------
 .../plugin-grid/src/objectGridColumns.ts      | 304 ++++++
 .../plugin-grid/src/objectGridDefaults.ts     | 207 ++++
 .../plugin-grid/src/objectGridLinkCell.tsx    | 197 ++++
 .../plugin-grid/src/objectGridQuery.ts        | 150 +++
 .../plugin-grid/src/objectGridRowVersion.ts   |  65 ++
 .../plugin-grid/src/objectGridTranslations.ts |  93 ++
 7 files changed, 1029 insertions(+), 970 deletions(-)
 create mode 100644 ui/packages/plugin-grid/src/objectGridColumns.ts
 create mode 100644 ui/packages/plugin-grid/src/objectGridDefaults.ts
 create mode 100644 ui/packages/plugin-grid/src/objectGridLinkCell.tsx
 create mode 100644 ui/packages/plugin-grid/src/objectGridQuery.ts
 create mode 100644 ui/packages/plugin-grid/src/objectGridRowVersion.ts
 create mode 100644 ui/packages/plugin-grid/src/objectGridTranslations.ts

diff --git a/ui/packages/plugin-grid/src/ObjectGrid.tsx b/ui/packages/plugin-grid/src/ObjectGrid.tsx
index aafaa39eb4a..3a2a15c7e08 100644
--- a/ui/packages/plugin-grid/src/ObjectGrid.tsx
+++ b/ui/packages/plugin-grid/src/ObjectGrid.tsx
@@ -22,12 +22,10 @@
  */
 
 import React, { useEffect, useState, useCallback, useMemo } from 'react';
-import type { ObjectGridSchema, DataSource, DependsOnInput, ListColumn, TableColumn, ViewData, TableSortItem, DataTableSchema, ListViewExportFormat, RecordNavigateAction } from '@object-ui/types';
+import type { ObjectGridSchema, DataSource, DependsOnInput, ListColumn, TableSortItem, DataTableSchema, ListViewExportFormat, RecordNavigateAction } from '@object-ui/types';
 import { isSystemManagedField, normalizeTableColumnType } from '@object-ui/types';
-import type { I18nLabel } from '@objectstack/spec/ui';
 import { parseFilterAST, resolveFieldScale, type FilterCondition } from '@objectstack/spec/data';
-import { SchemaRenderer, useDataScope, useNavigationOverlay, useAction, useSafeFieldLabel, usePredicateScope, useCapabilityGate, useRelatedRecordActions, RelatedRecordActionsProvider, useDataInvalidation, notifyDataChanged, useFilterScope, useMetadata, isSameAuthoredFilter } from '@object-ui/react';
-import { createSafeTranslation } from '@object-ui/i18n';
+import { SchemaRenderer, useDataScope, useNavigationOverlay, useAction, useSafeFieldLabel, usePredicateScope, useCapabilityGate, useDataInvalidation, notifyDataChanged, useFilterScope, useMetadata } from '@object-ui/react';
 // objectui#8920 — the grid reaches a cell renderer through THIS module and
 // nowhere else. `getCellRenderer` / `resolveCellRendererType` are deliberately
 // NOT imported here: six sites spelling the resolve three different ways is
@@ -35,9 +33,8 @@ import { createSafeTranslation } from '@object-ui/i18n';
 // what stops a seventh site picking a convention of its own.
 import { resolveGridCellRendering, gridCellRendererForFixedKey, linkCellRenderer, BADGE_PREFIX_RENDERER_KEY } from './cellRendererResolution';
 import { isMaskedGridColumn, isWithheldGridColumn } from './maskedColumn';
-import { formatCurrency, formatCompactCurrency, formatDate, formatDateTime, formatRelativeDate, formatPercent, percentCellScale, humanizeLabel, getBadgeColorClasses, getBadgeHexAppearance, FieldEditWidget, hasFieldEditWidget, DISCRETE_EDIT_TYPES, coerceToSafeValue, MaskedCellRenderer, withKnownObjects, RICH_TEXT_FIELD_TYPES, resolveRecordPointer } from '@object-ui/fields';
-import { RecordPointerCell, type RecordPointerSource } from './RecordPointerCell';
-import { useLocalization, useDisplayLocale, resolveFieldCurrency, pickLocalized } from '@object-ui/i18n';
+import { formatCurrency, formatCompactCurrency, formatDate, formatDateTime, formatRelativeDate, formatPercent, percentCellScale, humanizeLabel, getBadgeColorClasses, getBadgeHexAppearance, FieldEditWidget, hasFieldEditWidget, DISCRETE_EDIT_TYPES, coerceToSafeValue, MaskedCellRenderer, withKnownObjects, RICH_TEXT_FIELD_TYPES } from '@object-ui/fields';
+import { useLocalization, useDisplayLocale, resolveFieldCurrency } from '@object-ui/i18n';
 // Two resolvers, two vocabularies — the repo spells the distinction into the
 // NAMES (objectui#4167). `resolveInlineI18nLabel` is the spec's own
 // `resolveI18nLabel`: it resolves the INLINE per-locale map
@@ -48,7 +45,7 @@ import { useLocalization, useDisplayLocale, resolveFieldCurrency, pickLocalized
 // `string | I18nLabel` form `BaseSchema` has carried since objectui#4580: the
 // two reads below put the label in STRING positions, so a map-valued label used
 // to reach them as an object and the compiler could not say so.
-import { resolveI18nLabel as resolveInlineI18nLabel, PaginationConfigSchema } from '@objectstack/spec/ui';
+import { resolveI18nLabel as resolveInlineI18nLabel } from '@objectstack/spec/ui';
 import { stateMachineNextValues, isFieldInlineEditable } from './inline-edit-options';
 import {
   Badge, Button, NavigationOverlay, EmptyValue,
@@ -61,7 +58,7 @@ import {
   toast,
 } from '@object-ui/components';
 import { usePullToRefresh } from '@object-ui/mobile';
-import { resolveConditionalFormatting, resolveDependsOnFields, isDeadlineSettled, leadWithNameField, declaredNameField, buildExpandFields, buildExportFileName, columnIdentity, collectPredicateFieldRefs, collectGroupingFieldRefs, listViewPredicates, resolveAffordance, resolveFieldAffordance, type SchemaLike, isProjectableField, isExpandableFieldType, isUnmaterializedFieldType, readObjectSortability, isPlatformSortableField, filterPlatformSortableSort, toFilterNodeSafely, filterRefusalSubject, FilterOperatorError, convertSortToQueryParams, normalizeSortEntries, type QuerySortEntry, ROW_HEIGHT_TO_DENSITY_MODE, resolveRecordSourceConfig, resolveRecordSourceObjectName, resolveFilterPlaceholders, partitionRowsByPredicate, buildCategoryOrder, buildCategoryRank, toDisplayDate, type FilterTokenScope } from '@object-ui/core';
+import { resolveConditionalFormatting, resolveDependsOnFields, isDeadlineSettled, leadWithNameField, declaredNameField, buildExpandFields, buildExportFileName, columnIdentity, collectPredicateFieldRefs, collectGroupingFieldRefs, listViewPredicates, resolveAffordance, resolveFieldAffordance, type SchemaLike, isProjectableField, isExpandableFieldType, isUnmaterializedFieldType, readObjectSortability, isPlatformSortableField, filterPlatformSortableSort, toFilterNodeSafely, filterRefusalSubject, FilterOperatorError, convertSortToQueryParams, normalizeSortEntries, type QuerySortEntry, resolveRecordSourceObjectName, partitionRowsByPredicate, buildCategoryOrder, buildCategoryRank, toDisplayDate } from '@object-ui/core';
 import { usePermissions } from '@object-ui/permissions';
 import {
   RECORD_OVERLAY_DEFAULT_WIDTH,
@@ -90,80 +87,13 @@ import { BulkActionBar } from './components/BulkActionBar';
 import { BulkActionDialog } from './components/BulkActionDialog';
 import type { BulkResult } from './hooks/useBulkExecutor';
 import type { BulkActionDef } from '@object-ui/types';
-
-/**
- * The node's own authored filter: the canonical `filter`. Its deprecated alias
- * `defaultFilters` is not read: `@objectstack/spec` 18 retired it as a
- * tombstone that refuses by name (objectstack#11509), and the alias read went
- * with it (objectui#12030).
- */
-interface AuthoredGridFilters {
-  filter: ObjectGridSchema['filter'];
-}
-
-/** One resolution, remembered with the inputs it was computed from. */
-interface HeldGridFilters {
-  authored: AuthoredGridFilters;
-  currentUserId: FilterTokenScope['currentUserId'];
-  currentOrgId: FilterTokenScope['currentOrgId'];
-  recordId: FilterTokenScope['recordId'];
-  onUnresolved: FilterTokenScope['onUnresolved'];
-  resolved: AuthoredGridFilters;
-}
-
-function resolveGridFilters(authored: AuthoredGridFilters, scope: FilterTokenScope): HeldGridFilters {
-  return {
-    authored,
-    currentUserId: scope.currentUserId,
-    currentOrgId: scope.currentOrgId,
-    recordId: scope.recordId,
-    onUnresolved: scope.onUnresolved,
-    resolved: resolveFilterPlaceholders(authored, scope),
-  };
-}
-
-/**
- * objectui#10607 — resolve the node's own filter ONCE, through
- * `@object-ui/core`'s shared `resolveFilterPlaceholders`, against the session
- * scope the host provides (`useFilterScope`). Before this, a directly authored
- * `object-grid` with `filter: [['owner', '=', '{current_user_id}']]` sent the
- * literal token on `$filter`. `object-view` already resolves the filters it
- * hands this grid (objectui#10506); resolving that value again changes
- * nothing, because a resolved id no longer matches the whole-token pattern.
- *
- * ⛔ Not a second resolver, and no fallback: a token the scope cannot resolve
- * is whatever `resolveFilterPlaceholders` makes of it (left intact, with one
- * warning naming it).
- *
- * The result is HELD against its inputs, the shape `plugin-view`'s
- * `useResolvedFilterSegments` uses. The load effect keys on the filter this
- * grid lowers, so a resolved copy minted on every render would refetch on
- * every render; and a date macro such as `{now}` resolves to a new value at
- * every call, so comparing OUTPUTS cannot stop that. The key is the authored
- * filters, compared by structure (a host that rebuilds an equal filter inline
- * must not re-query), plus each scope member read one by one (`recordId`
- * among them, objectui#7297), never the scope object's identity (AGENTS.md
- * #10). The held pair lives in state,
- * so the value handed out is always the one React committed.
- */
-function useResolvedGridFilters(authored: AuthoredGridFilters, scope: FilterTokenScope): AuthoredGridFilters {
-  const [held, setHeld] = useState(() => resolveGridFilters(authored, scope));
-  if (
-    held.currentUserId !== scope.currentUserId
-    || held.currentOrgId !== scope.currentOrgId
-    || held.recordId !== scope.recordId
-    || held.onUnresolved !== scope.onUnresolved
-    || !isSameAuthoredFilter(held.authored, authored)
-  ) {
-    // React's documented "information from previous renders" shape: a set
-    // during render re-renders this component at once, before any child sees
-    // the discarded pass, and the re-render finds the inputs equal.
-    const next = resolveGridFilters(authored, scope);
-    setHeld(next);
-    return next.resolved;
-  }
-  return held.resolved;
-}
+import { findParamsSignature, getDataConfig, useResolvedGridFilters } from './objectGridQuery';
+import { type ObjectGridColumn, type ObjectGridColumnDraft, isChipFieldType, normalizeColumns, resolveColumnLabel } from './objectGridColumns';
+import { LinkCell, recordPointerFace, rowRecordId } from './objectGridLinkCell';
+import { useGridTranslation } from './objectGridTranslations';
+import { DEFAULT_DISPLAY_PAGE_SIZE, DEFAULT_FETCH_BATCH_SIZE, DEFAULT_SELECTION_TYPE, NO_GROUPING_REFUSAL, type RowHeightMode, describeNonPositivePageSize, resolvePageSize, resolveRowHeightMode } from './objectGridDefaults';
+import { type BatchSaveOutcome, OCC_TOKEN_FIELD, type RowConflictChoice, type WrittenRowVersion, rowVersionOf, rowVersionToSend } from './objectGridRowVersion';
+export type { RetiredListColumnKey, ObjectGridColumnHolds, ObjectGridColumnDraft, ObjectGridColumn } from './objectGridColumns';
 
 /**
  * A declared `sort` → the `"field order"` join string THIS block sends as
@@ -242,310 +172,6 @@ export function parseSchemaSort(sort: unknown): TableSortItem[] {
   return items;
 }
 
-/**
- * The class list both faces of {@link LinkCell} wear — the anchor is a visual
- * no-op against the span it upgrades, so a list does not change appearance
- * depending on whether its host publishes record URLs.
- */
-/**
- * The field types whose grid cell draws chips: the ones `@object-ui/fields`
- * maps to `SelectCellRenderer` (a badge per selected option). Their column
- * carries `chips`, so `data-table` floors it at its widest drawn chip and a
- * single-word value is never ellipsized (objectui#12708).
- */
-const CHIP_FIELD_TYPES: ReadonlySet<string> = new Set(['select', 'status', 'multiselect', 'radio', 'checkboxes', 'tags']);
-
-function isChipFieldType(type: unknown): boolean {
-  return typeof type === 'string' && CHIP_FIELD_TYPES.has(type);
-}
-
-const LINK_CELL_CLASS =
-  'text-primary font-medium underline-offset-4 hover:underline cursor-pointer truncate block max-w-full';
-
-/**
- * The same list with the one-line clamp swapped for wrapping — what a cell in a
- * column carrying an authored `wrap: true` wears (objectui#6650).
- *
- * ⭐ DERIVED from {@link LINK_CELL_CLASS} rather than written out, so the two
- * cannot drift: every future edit to the link cell's appearance lands in both
- * faces of both variants, and the no-wrap variant stays byte-identical to what
- * `ObjectGrid.linkCellAnchor.test.tsx` pins as full markup.
- *
- * ⚠️ Why this exists at all — the outer read in `data-table.tsx` is NOT enough
- * on its own. `data-table` puts the wrap/truncate decision on the cell BODY it
- * owns, but a link column's content is this component, and its own `truncate`
- * clamps the text back to one line INSIDE a body that is willing to wrap. So
- * `wrap: true` on the record-link column — column one of almost every grid —
- * would have rendered as silently nothing: the very failure mode this card
- * exists to end, reproduced one element deeper. Measured, not reasoned: the
- * end-to-end pin in `ObjectGrid.columnWrapForward.test.tsx` failed on exactly
- * this, reading back `…cursor-pointer truncate block max-w-full` from a column
- * authored `wrap: true`.
- */
-const LINK_CELL_CLASS_WRAP = LINK_CELL_CLASS.replace('truncate', 'whitespace-normal break-words');
-
-/**
- * A row's primary key — the value the host's record-URL builder addresses.
- * Mirrors what `useNavigationOverlay.handleClick` reads off the same row, so
- * the anchor's href and the click path can never point at different records.
- */
-function rowRecordId(row: unknown): string | number | undefined {
-  const rec = row as Record<string, unknown> | null | undefined;
-  const id = rec?.id ?? rec?._id;
-  return typeof id === 'string' || typeof id === 'number' ? id : undefined;
-}
-
-// Clickable text cell that can safely contain other interactive content
-// (e.g., EmailCellRenderer's copy button). Using <button> here would
-// produce an invalid <button> > <button> nesting (hydration error +
-// breaks the inner copy click). role="link" + tabIndex + keyboard
-// handlers preserves accessibility while allowing arbitrary children.
-//
-// objectui#4490 — that span was the whole cell, so the list's link column had
-// none of a link's native affordances: no middle-click / ⌘-click open-in-new-
-// tab, no "copy link address", no hover status-bar URL, and `role="link"` with
-// no `href` is a weaker contract for assistive tech than a real anchor. PR
-// #4489 had just given detail-page and related-list lookup VALUES real anchors,
-// which left the list — the surface users open records from — as the weakest of
-// the three.
-//
-// So when the host publishes a record URL this renders a real `<a href>`, with
-// the split #4489 established:
-//   - plain left click → `preventDefault()` + the existing `onActivate`, so SPA
-//     navigation (drawer / modal / page, whatever the view configured) is
-//     completely unchanged;
-//   - modifier / non-primary click → NOT prevented, so the browser does what it
-//     does with any link.
-//
-// **The URL is not built here.** This package has no router and no business
-// knowing what a record route looks like; the host publishes its own builder
-// through `RelatedRecordActionsContext.recordHref` — the same seam #4489 used,
-// and for the console list surface the same builder its "open in new window"
-// action already navigates with. No host, or a host that cannot route to this
-// object, renders EXACTLY the span below: same markup, same behavior, nothing
-// to un-learn (the Studio designer, embedded renderers, standalone grids).
-const LinkCell: React.FC<{
-  testId: string;
-  onActivate: () => void;
-  /** Object whose record this row is — passed to the host's URL builder. */
-  objectName?: string;
-  /** This row's primary key. Absent (a row with no id) ⇒ no anchor. */
-  recordId?: string | number | null;
-  /**
-   * The column's authored `wrap` (objectui#6650). `true` ⇒ this cell drops its
-   * one-line clamp so long link text flows onto further lines, matching what
-   * `data-table` does to the body around it. Absent / `false` ⇒ unchanged.
-   */
-  wrap?: boolean;
-  children: React.ReactNode;
-}> = ({ testId, onActivate, objectName, recordId, wrap, children }) => {
-  const host = useRelatedRecordActions();
-  const cellClass = wrap ? LINK_CELL_CLASS_WRAP : LINK_CELL_CLASS;
-  const href =
-    objectName && recordId != null && recordId !== '' && host?.recordHref
-      ? host.recordHref(objectName, recordId)
-      : null;
-
-  if (href && host) {
-    // objectui#11817 — no anchor inside this anchor. A reference value in the
-    // cell (`LookupCellRenderer`'s `ReferencedRecordLink`) draws its own `a`
-    // whenever the host answers `recordHref` for the referenced object, so the
-    // children are rendered under the same host with no record destination:
-    // "the host cannot route to that object", which the context documents as
-    // render the plain value. The self-linking faces (`mailto:`, URL, `tel:`)
-    // never ask the host; the cell is handed their text face instead
-    // (`linkCellRenderer` in `./cellRendererResolution`).
-    const unlinkedHost = { ...host, recordHref: undefined, openRecord: undefined };
-    return (
-      <a
-        href={href}
-        data-testid={testId}
-        className={cellClass}
-        onClick={(e) => {
-          // The row underneath carries its own click handler (open the record,
-          // and on a modifier click open it in a new tab). Following this link
-          // must never ALSO fire that — on a modifier click that would open two
-          // tabs, one from the anchor and one from the row.
-          e.stopPropagation();
-          // Modifier and non-primary clicks belong to the browser (new tab, new
-          // window) — that is the entire point of rendering a real href.
-          if (e.metaKey || e.ctrlKey || e.shiftKey || e.altKey || e.button !== 0) return;
-          e.preventDefault();
-          onActivate();
-        }}
-        onKeyDown={(e) => {
-          // Enter is the anchor's OWN activation: the browser fires a click for
-          // it, which the handler above turns into the SPA path. Handling it
-          // here too would activate twice. Space is the one the span had that a
-          // link does not do natively, so it is carried over explicitly.
-          if (e.key === ' ') {
-            e.preventDefault();
-            e.stopPropagation();
-            onActivate();
-          }
-        }}
-      >
-        <RelatedRecordActionsProvider value={unlinkedHost}>{children}</RelatedRecordActionsProvider>
-      </a>
-    );
-  }
-
-  return (
-    <span
-      role="link"
-      tabIndex={0}
-      data-testid={testId}
-      className={cellClass}
-      onClick={(e) => {
-        e.stopPropagation();
-        onActivate();
-      }}
-      onKeyDown={(e) => {
-        if (e.key === 'Enter' || e.key === ' ') {
-          e.preventDefault();
-          e.stopPropagation();
-          onActivate();
-        }
-      }}
-    >
-      {children}
-    </span>
-  );
-};
-
-
-/**
- * objectui#12608 — the face a `referenceVia` pointer column draws its rows
- * with, or `null` when the field declares no pointer pair.
- *
- * The pair is resolved per row by `resolveRecordPointer` (`@object-ui/fields`),
- * the one rule the record details grid asks too; `referenceVia` is read off the
- * OBJECT field, where the spec declares it, and the type is the column's
- * declared one, so a view that re-types the column keeps its own face. A row
- * the rule answers `null` for (a half-addressed pair) is drawn by the column's
- * ordinary face: the returned function answers `null` and the caller falls
- * through to it. Inside a link cell the face is drawn under `LinkCell`'s
- * unlinked host, so it draws the name without a second anchor.
- */
-function recordPointerFace(
-  fieldName: string,
-  declaredType: string | null,
-  fieldDef: { referenceVia?: unknown } | null | undefined,
-  dataSource: RecordPointerSource | null | undefined,
-): ((row: any) => React.ReactElement | null) | null {
-  const referenceVia = fieldDef?.referenceVia;
-  if (typeof referenceVia !== 'string' || referenceVia === '') return null;
-  return (row: any) => {
-    const pointer = resolveRecordPointer({ name: fieldName, type: declaredType, referenceVia }, row);
-    return pointer ? <RecordPointerCell pointer={pointer} dataSource={dataSource} /> : null;
-  };
-}
-
-// Default English fallback translations for the grid
-const GRID_DEFAULT_TRANSLATIONS: Record<string, string> = {
-  'grid.actions': 'Actions',
-  'grid.edit': 'Edit',
-  'grid.delete': 'Delete',
-  'grid.export': 'Export',
-  'grid.exportAs': 'Export as {{format}}',
-  'grid.loading': 'Loading grid…',
-  'grid.errorLoading': 'Error loading grid',
-  // objectui#9050 — the malformed-filter state, shared with `RelatedList`
-  // and `LineItemsPanel` because it is one sentence about one authored
-  // value, not three. Byte-identical to the `en` pack, which
-  // `defaults-maps-mirror-en-pack` enforces.
-  'view.malformedFilter': 'This view’s filter is malformed, so no records are shown: the {{subject}} condition cannot be applied.',
-  'grid.pullToRefresh': 'Pull to refresh',
-  'grid.refreshing': 'Refreshing…',
-  'grid.openRecord': 'Open record',
-  'grid.empty': 'Empty',
-  'grid.yes': 'Yes',
-  'grid.no': 'No',
-  'grid.systemFields': 'System',
-  // The grouped grid's refusal over a data source that cannot answer the
-  // group header query (objectui#10881, ruling F). It must exist HERE as well
-  // as in the locale packs: a provider-less host (a standalone grid, this
-  // package's own tests) never reaches them, and it is the only thing such a
-  // grid draws.
-  'grid.grouping.needsHeaderQuery':
-    'This view is grouped, but its data source does not implement queryGroupHeaders, so the groups cannot be counted. Remove the grouping to show the records.',
-  // …and over rows a host handed in while declaring them one page of more.
-  'grid.grouping.needsWholeRows':
-    'Grouping needs every record, but this grid was handed one page of them, so the groups cannot be counted. Hand in every record, or let the grid fetch them from a data source that implements queryGroupHeaders.',
-  // Reused by the grouped-view pager (falls back here when no I18nProvider).
-  'table.rowsPerPage': 'Rows per page',
-  'table.pageInfo': 'Page {{current}} of {{total}}',
-  // The grouped-view pager's four icon buttons are named by these
-  // (objectui#12143): the `data-table` pager's own keys, objectui#12124.
-  'table.firstPage': 'First page',
-  'table.previousPage': 'Previous page',
-  'table.nextPage': 'Next page',
-  'table.lastPage': 'Last page',
-  // The default inline-edit saves' success toast (objectui#12303), counted in
-  // the rows the server accepted — the `table.modified` unit the table's
-  // "Save All" bar counts in.
-  'table.saved': '{{count}} row saved',
-  'table.saved_one': '{{count}} row saved',
-  'table.saved_other': '{{count}} rows saved',
-  // The heading of an authored `emptyState` that declares no `title`
-  // (objectui#11068): the words the table's own empty row shows, so leaving the
-  // member out changes nothing a user reads.
-  'table.noResults': 'No results found',
-  // The empty state an empty grid draws when no authored `emptyState` and no
-  // search term are in force (objectui#13142). Borrowed from the `list.*`
-  // namespace `ListEmptyState` reads, so a grid and a list say the same thing
-  // about the same empty object; the rows exist HERE too for a provider-less
-  // host.
-  'list.firstRunTitle': 'Nothing here yet',
-  'list.firstRunMessage': 'Create your first record to get started.',
-  'list.noMatches': 'No matching records',
-  'list.viewFilterNoMatchesMessage': 'No records match this view’s filter.',
-  // objectstack#25898 — a grid filtered to the signed-in user, and an
-  // unfiltered grid for a caller who may not create (`ListEmptyState` says
-  // both in the same words).
-  'list.ownedNoneTitle': 'Nothing of yours yet',
-  'list.ownedNoneMessage': 'This view lists only records that are yours, and you don’t have any yet.',
-  'list.noneVisibleTitle': 'No records you can see',
-  'list.noneVisibleMessage': 'There are no records here that you have access to. If you expected to see some, ask your administrator for access.',
-  // Heading of the record-detail overlay this grid opens on row click
-  // (objectui#3426). Borrowed from the `detail.*` namespace rather than minted
-  // as `grid.recordDetail`: `NavigationOverlay` already resolves
-  // `detail.recordDetail` for hosts that pass no title, and one heading on one
-  // control should not get two translations that can drift apart. Both entries
-  // must exist HERE too — a provider-less host (a standalone grid, this
-  // package's own tests) never reaches the locale packs.
-  'detail.recordDetail': 'Record Detail',
-  'detail.recordDetailWithLabel': '{{label}} Detail',
-};
-
-/**
- * Safe wrapper for useObjectTranslation that falls back to English defaults
- * when I18nProvider is not available (e.g., standalone usage).
- *
- * Delegates to `@object-ui/i18n`'s `createSafeTranslation`; the local copy this
- * replaced wrapped the hook in try/catch (rules-of-hooks, objectui#2879).
- */
-const useGridTranslation = createSafeTranslation(GRID_DEFAULT_TRANSLATIONS, 'grid.actions');
-
-/**
- * Resolve a column header `label` (`ListColumnSchema.label`, the spec's
- * `I18nLabel`) to the string the header prints, in the viewer's `language`.
- *
- * A plain string passes through unchanged. An inline locale map
- * (`{ en: 'Amount', 'zh-CN': '金额' }`) is picked by `pickLocalized` — the one
- * locale pick the console uses for `I18nLabel`, with its own floor when the
- * viewer's locale is absent — rather than a second implementation here.
- * objectui#12358: this used to keep only a plain string and answer `undefined`
- * for a map, so an authored map header silently fell back to the field label.
- * A map with no usable entry still answers `undefined`, so the field-label
- * fallback at the call site applies exactly as for an absent label.
- */
-function resolveColumnLabel(label: string | I18nLabel | undefined, language: string | undefined): string | undefined {
-  if (label == null) return undefined;
-  if (typeof label === 'string') return label;
-  return pickLocalized(label, language) || undefined;
-}
-
 /**
  * The column layout ObjectGrid persists and reports back — the merged result of
  * a resize and a reorder, not either event on its own. Named so the state hook
@@ -837,55 +463,6 @@ export interface ObjectGridComponentProps extends ObjectGridExternalPaginationPr
   onAddRecord?: () => void;
 }
 
-/**
- * Helper to get data configuration from schema.
- *
- * The ruled three-rung ladder itself (`data`, then `staticData`, then
- * `objectName`) is `resolveRecordSourceConfig` in `@object-ui/core` — ONE
- * implementation of a contract published on both faces (`77cb489b4`), which
- * this file used to hand-copy (`ce2aaefe1`).
- *
- * What used to stay here was the head above it: the bare-array `data`
- * shorthand, which lifted `data: [...]` to `{ provider: 'value', items }`.
- * ⛔ IT IS GONE (objectui#8348, decision batch #83, maintainer verbatim
- * 「8348 以协议为准」 — the contract decides).
- *
- * MEASURED on `@objectstack/spec` 17.4.0:
- * `ComponentPropsMap['object-grid'].data` is the `ViewData` union, and its own
- * description names the refusal — *"Static inline rows live at
- * `{ provider: 'value', items: [...] }`; the bare-array shortcut is refused —
- * see migration `object-grid-data-view-data-converged`"*. This block's own
- * registration publishes the same arm (`{ name: 'data', type: 'object' }` in
- * `index.tsx`), and `gridDataInputContract.test.ts` has pinned that declaration
- * since objectui#5090. The head was the last carrier of a spelling every one of
- * those faces refuses, so `data` is honoured here on the OBJECT arm only and
- * the shared rung is passed `'view-data'`.
- *
- * ⛔ WHAT THIS REACHES, measured per CARRIER — do NOT read it as "the array is
- * gone". An authored `data` array reaches this component TWICE: as
- * `schema.data`, which this function used to lift, and as the `data` PROP,
- * because `SchemaRenderer` spreads every non-metadata node key and
- * `index.tsx` forwards `{...rest}`. That prop is `passedData` below, and it
- * lifts an array to `{ provider: 'value', items }` at HIGHER priority than this
- * ladder — it is the channel a host such as `ListView` uses to hand down rows it
- * already fetched, and it is indistinguishable here from an authored key.
- *
- * ⇒ at the ladder the array is no longer a record source; through
- * `SchemaRenderer` an authored `data: [ …rows… ]` still draws, from the props
- * channel. Both halves are pinned in
- * `__tests__/gridBareArrayDataRefused-8348.test.tsx`, which had to correct its
- * own first draft on exactly this point. Collapsing the two carriers would take
- * the host path with it and is outside objectui#8348's scope — reported on the
- * card, not changed in passing.
- *
- * The declared spelling for inline rows is
- * `data: { provider: 'value', items: [...] }`, and the deprecated `staticData`
- * array still works as before.
- */
-function getDataConfig(schema: ObjectGridSchema): ViewData | null {
-  return resolveRecordSourceConfig(schema, 'view-data');
-}
-
 /**
  * The relational copy set and `applyRelationalMeta` moved to
  * `./relationalMetaKeys` for objectui#6875. The list there is DERIVED from a
@@ -903,285 +480,6 @@ function getDataConfig(schema: ObjectGridSchema): ViewData | null {
  * Measured in `__tests__/lookupPickerKeys-7154.test.tsx` (objectui#7154).
  */
 
-/**
- * Content signature of a host's find-params, used as the query-change signal for
- * the cross-page escalation (objectui#4501 clause 2).
- *
- * CONTENT and not identity: a host re-render that rebuilds an equal params
- * object must not drop an escalation the user just made, and identity is the
- * one thing a host cannot be relied on to keep stable. Top-level keys are
- * sorted so key ORDER — which differs between the host's literal and this
- * grid's own loader — never reads as a query change.
- */
-function findParamsSignature(params: Record<string, unknown> | null | undefined): string | null {
-  if (!params) return null;
-  return JSON.stringify(
-    Object.keys(params).sort().map((k) => [k, params[k] ?? null]),
-  );
-}
-
-/**
- * Helper to normalize columns configuration
- * Handles both string[] and ListColumn[] formats
- */
-function normalizeColumns(
-  columns: string[] | ListColumn[] | undefined
-): ListColumn[] | string[] | undefined {
-  if (!columns || columns.length === 0) return undefined;
-  
-  // Already in ListColumn format - check for object type with optional chaining
-  if (typeof columns[0] === 'object' && columns[0] !== null) {
-    return columns as ListColumn[];
-  }
-  
-  // String array format
-  return columns as string[];
-}
-
-/**
- * ⭐ WHAT THIS GRID'S COLUMN PRODUCER IS ALLOWED TO EMIT (objectui#6004).
- *
- * `generateColumns()` below builds the column array this component hands to
- * `data-table`, whose slot is `DataTableSchema.columns: TableColumn[]`. It had
- * no return annotation, so its four emit paths were inferred structurally and
- * nothing ever compared them to the slot's declaration — and all four call
- * sites re-widened to `any` on the way out, so even an annotation would have
- * been discarded one hop later.
- *
- * ## ⭐ Why this is not just `: TableColumn[]`
- *
- * objectui#6373 measured, at the sibling producer in `plugin-dashboard`, that a
- * bare `TableColumn` annotation raises no error on a `{ ...spread }` emit,
- * because TypeScript's excess-property check is a FRESHNESS check on the
- * properties an object literal WRITES OUT and spread properties are exempt.
- *
- * Measured again HERE before choosing this shape, because this seam is worse
- * than that one and the difference matters:
- *
- *   1. `generateColumns = useCallback((): TableColumn[] => {`, everything else
- *      unchanged  →  `tsc --noEmit` exit 0, ZERO diagnostics.
- *   2. Same, PLUS an undeclared key `wrapControl: true` WRITTEN OUT in the path-A
- *      column literal (not arriving through a spread)  →  exit 0, ZERO diagnostics.
- *
- * Run 2 is the one that fixes the mechanism. At objectui#6373's seam the object
- * literal sits in `enrich()`'s return position, so freshness still caught keys
- * written out longhand and only the spread escaped. Here every literal is the
- * return value of a `.map()` callback, so it is inferred into the callback's
- * return type FIRST and reaches the annotation as a non-fresh `X[]`. Freshness
- * is gone entirely: written-out keys escape too. A bare annotation at this seam
- * is not a weak instrument, it is an inert one — a green gate and no guard.
- *
- * The `?: never` members are what make the annotation able to fail. They are
- * ADR-0049 retirement tombstones — this repo's convention for a key that is
- * REFUSED rather than merely absent (`StaticTableColumn` in `@object-ui/types`)
- * — and they bite by ASSIGNABILITY, which survives `.map()` because it never
- * depended on freshness. Re-adding `...(col.summary && { summary: col.summary })`
- * to a column literal is a compile error naming `summary`.
- *
- * ## The rule (objectui#6373's, applied to this producer's key set)
- *
- * A producer may write into a `TableColumn[]` slot only keys the CONSUMER of
- * that slot reads, and the read set is MEASURED from the consumer's source,
- * never assumed. A key the consumer reads and `TableColumn` declares is
- * written; a key the consumer reads that `TableColumn` does not declare is HELD
- * where a ruling already holds it; a key nothing reads is RETIRED — never
- * declared, because declaring a key nothing reads is the same
- * `declared != enforced` defect facing the other way. Before retiring, prove
- * the value has a second road to its consumer.
- *
- * Consumers measured for THIS producer — two of them, because the array is read
- * twice before it reaches the slot:
- *
- *   - `data-table.tsx`, comments stripped, every `col.<key>` read — FOURTEEN:
- *     `accessorKey`, `width`, `align`, `header`, `className`, `cellClassName`,
- *     `sortable`, `resizable`, `editable`, `type`, `cell`, `headerIcon`,
- *     `fitContent`, `wrap`. ⚠️ It was THIRTEEN between objectui#7196 and
- *     objectui#6650, which added the `wrap` read this producer now feeds; it
- *     said fourteen before #7196 re-derived it:
- *     `name` was the fourteenth and was correct when written, but objectui#6963
- *     (2026-08-31) retired the `col.name` alias — the last undeclared spelling
- *     the adapter accepted — so the key left the consumer's read set that day.
- *   - THIS FILE's own downstream passes, which read the array before handing it
- *     on — TEN: `pinned` (the left/right reorder + the frozen-column verdict),
- *     `accessorKey`, `header`, `width`, `type`, `fitContent`, plus the four the
- *     chrome passes read in order to RE-EXPRESS them: `className` and
- *     `cellClassName` (`applyDensity`, and again in the right-pinned literal),
- *     `sortable` (`withSortability`), `cell` (the mobile card renderer).
- *     ⚠️ Those four were missing from this list from the day it was written —
- *     all three passes already existed at that commit — so this is an
- *     incompleteness, not drift. They change no verdict: each is declared on
- *     `TableColumn` and read by `data-table.tsx` as well. Recorded because a
- *     list presented as MEASURED has to be one.
- *     ⚠️ `col.wrap` is read ONE MORE TIME here since objectui#6650, at the
- *     `LinkCell` call sites, and that read is not a re-expression of the
- *     forward — it is a SECOND consumer of the same authored key. The record
- *     link wears its own `truncate`, so honouring `wrap` only downstream would
- *     have left column one of almost every grid wrapping its cell body around
- *     text still clamped to one line.
- *
- * Verdicts, each with the read-count behind it:
- *
- *   - `headerIcon` — DECLARED by `TableColumn`, so NOT held. Live:
- *     `data-table.tsx` renders it into the header cell (1 render site, 2
- *     syntactic reads), forwarded verbatim and never re-expressed. It WAS held
- *     here, on the "undeclared by `TableColumn`" premise; objectui#6615
- *     declared it and that premise expired with nothing going red at the moment
- *     of loss. objectui#6424 then removed the hold, MEASURED rather than
- *     derived: with the member deleted both emit types below are byte-identical
- *     (27 members, every member's resolved type unchanged), against a positive
- *     control that deleting `pinned` instead moves them to 26. Pinned in
- *     `columnHoldsExpiry-6424.test.ts` — which now also carries the claim the
- *     hold used to carry implicitly, that `TableColumn` DECLARES the key.
- *   - `pinned` — HELD. Live, and consumed BEFORE the slot: the reorder pass
- *     below reads it (5 reads in this file) and re-expresses it as the sticky
- *     `className` that `data-table` actually reads. `data-table` never reads
- *     `pinned` itself, and does not need to.
- *   - `wrap` — DECLARED by `TableColumn`, forwarded, and READ. This entry was
- *     "RETIRED (objectui#5453, 2026-08-28)" and the retirement was correct on
- *     its own measurement: `data-table.tsx` was then a two-way switch,
- *     `isFit ? 'w-full whitespace-nowrap' : 'truncate w-full'`, with a `title`
- *     tooltip as the only concession to overflow, so nothing read the key and
- *     the emit rule retired it. ⭐ What #5453 could not settle is what
- *     objectui#6650 escalated one level up: `@objectstack/spec` never stopped
- *     DECLARING `ListColumn.wrap`, and describes it to authors as "Allow text
- *     wrapping" — so retiring the forward left a promise made at authoring
- *     time and silently broken at render time. The maintainer ruled that
- *     promise is kept rather than withdrawn (2026-09-02, Option B): the
- *     consumer was BUILT, `TableColumn` now declares the key, and the forward
- *     returns WITH a reader. ⚠️ Note what moved and what did not — the emit
- *     rule is unchanged and still decided this: the key is written because the
- *     consumer reads it, which is the same test that retired it when the
- *     consumer did not exist.
- *   - `options` — RETIRED (see the enrichment pass below).
- *   - `type` — not adjudicated here; its VALUE set was settled by `fc62bb490`,
- *     whose fold still stands. It is the one member whose vocabulary differs between
- *     the two types below.
- *   - `name` — not emitted by this producer at all, so objectui#5120's alias
- *     never needed a hold here. Tombstoned only in the sense that nothing writes
- *     it — and since objectui#6963 (2026-08-31) nothing READS it either: the
- *     consumer-side alias is retired, so the key is absent from BOTH ends of
- *     this seam and the verdict now rests on two measurements, not one.
- *
- * `essential` is absent from both types on purpose: objectui#6004's suggested
- * key list named it, but it was READ off the authored column and turned into a
- * `className` — never emitted, and not a `ListColumn` member either. That read
- * is now RETIRED too (objectui#6458), so mobile visibility is decided purely
- * positionally (`colIndex === 0`) and nothing on either side of this producer
- * carries the key.
- */
-
-/**
- * The tombstoned keys — DERIVED from the authored input type, never hand-listed,
- * so a future `ListColumn` member is refused by default and has to be
- * adjudicated to escape.
- *
- * `ListColumn` is the right derivation source because it is where this
- * producer's drift comes from: every key the emit could wrongly grow is a key
- * the author wrote on the input and someone forwarded. `pinned` is the one that
- * escaped and stayed — adjudicated HELD above. `wrap` escaped too, was RETIRED
- * by objectui#5453, and has since been DECLARED on `TableColumn` by
- * objectui#6650, so the band lets it through again — ⭐ and it does so with no
- * edit to this line, which is the property that makes the derivation worth
- * having. The tombstone was never a carve-out to remember to remove; it was a
- * consequence of `TableColumn` not declaring the key, and it lifted the moment
- * that stopped being true. A key that never earns a declaration stays refused
- * by default, and re-adding its forward stays a compile error naming it.
- */
-export type RetiredListColumnKey = Exclude<keyof ListColumn, keyof TableColumn | 'pinned'>;
-
-/**
- * The undeclared-but-live keys this producer holds. See the docblock above.
- *
- * ⚠️ "Undeclared by `TableColumn`" is this interface's ENTRY CONDITION, and it
- * is a claim about ANOTHER package that can stop being true with nothing going
- * red here. So it is re-checked per key when the card owning that key closes,
- * never inherited: `headerIcon` sat here on exactly that premise until
- * objectui#6615 declared it on `TableColumn`, at which point the hold was
- * redundant rather than load-bearing, and objectui#6424 removed it.
- *
- * ⛔ A key whose ONLY declaration on the emit types is this interface is not in
- * that position — deleting it deletes the key from the emit. `pinned` is that
- * key today, which is why the two verdicts differ.
- */
-export interface ObjectGridColumnHolds {
-  /**
-   * HELD, load-bearing on BOTH counts — the pair that has to hold for a hold to
-   * be real, and the contrast that made `headerIcon`'s removal safe:
-   *
-   *   1. `TableColumn` does NOT declare it, and `RetiredListColumnKey` carves it
-   *      out of the derived tombstone band, so this member is its ONLY
-   *      declaration on both emit types. Deleting it drops the key from them
-   *      (measured: 27 members → 26).
-   *   2. It has a live consumer BEFORE the slot — this file's own reorder pass
-   *      reads it and re-expresses it as the sticky `className` that
-   *      `data-table` actually reads. That is the "second road" the emit rule
-   *      demands before a key may be retired. `wrap` failed it in 2026-08 and
-   *      was retired; objectui#6650 then BUILT its consumer rather than
-   *      reinstating a hold, which is why `wrap` is a plain declared key today
-   *      and `pinned` is still the only member here.
-   */
-  pinned?: 'left' | 'right';
-}
-
-/**
- * What `generateColumns()` returns: everything final EXCEPT `type`, which is
- * still the producer's raw inference vocabulary (`@objectstack/spec`'s
- * `FieldType`, 49 values) rather than the EIGHT-literal union `TableColumn`
- * declares (`TABLE_COLUMN_TYPES`: `text`, `number`, `date`, `datetime`,
- * `currency`, `percent`, `boolean`, `action`). `fc62bb490` folds it
- * downstream, in a pass that is deliberately separate from the enrichment map —
- * so the pre-fold shape needs a name, and this is it.
- *
- * ⚠️ This said "7-literal" until objectui#7196 re-derived it. `action` joined
- * the union at objectui#6370 on 2026-08-25 — a day BEFORE this docblock was
- * written, and that commit's own subject line reads "make the 8-literal union
- * the one canonical TableColumn.type" — so the count was never right here; it
- * was mis-copied, not drifted. Both numbers are now measured rather than
- * recited: `TABLE_COLUMN_TYPES` in `@object-ui/types` has 8 members and
- * `@objectstack/spec`'s `FieldType` enum has 49.
- */
-/**
- * ⭐ `options` — RETIRED at this emit (objectui#6004), and this explicit
- * tombstone is now the ONLY enforcement of that verdict. ⛔ Do not "tidy" it
- * away as redundant.
- *
- * Until objectui#6425 the key needed no tombstone: it was a member of NO part
- * of the emit types below, so TypeScript's excess-property check refused a
- * fresh literal writing it — refusal by non-membership. #6425's maintainer
- * ruling (2026-08-27) then declared `options` on `TableColumn` itself (the
- * `object-data-table` cell pipeline reads it off the AUTHORED column), which
- * made the key a member here through `Omit<TableColumn, …>` / `TableColumn`
- * and silently ended that enforcement. Nothing went red at the moment of
- * loss — the emit-boundary suite's directive merely turned TS2578-unused,
- * which is luck, not design. The general rule, recorded so the next seam can
- * check itself: **a pin enforced by a key's non-membership silently stops
- * enforcing the moment the key becomes a member.**
- *
- * objectui#6004's verdict itself is unchanged — nothing on either side of
- * THIS seam reads a column-level `options` (`data-table.tsx` has no such
- * read; `renderCellEditor` rebuilds the field from the object schema) — only
- * the refusal's mechanism moves, from freshness to assignability. It is
- * intersected into BOTH the pre-fold draft and the post-fold column, because
- * the retirement belongs to the seam, not to one of its two types; the key
- * cannot land in the DERIVED band (`RetiredListColumnKey`) because `options`
- * is not a `ListColumn` member, which is why this one is hand-written.
- */
-type ObjectGridRetiredOptionsTombstone = { options?: never };
-
-export type ObjectGridColumnDraft =
-  Omit<TableColumn, 'type'>
-  & { type?: string }
-  & ObjectGridColumnHolds
-  & ObjectGridRetiredOptionsTombstone
-  & { [K in RetiredListColumnKey]?: never };
-
-/** Post-fold: what actually reaches `DataTableSchema.columns: TableColumn[]`. */
-export type ObjectGridColumn =
-  TableColumn
-  & ObjectGridColumnHolds
-  & ObjectGridRetiredOptionsTombstone
-  & { [K in RetiredListColumnKey]?: never };
-
 /**
  * ⭐ THE SCHEMA SLOT THIS GRID FILLS (objectui#6459) — the receiver half of the
  * seam whose producer half #6004 typed. `dataTableSchema` below was
@@ -1388,261 +686,6 @@ export type ObjectGridDataTableSchemaHolds = {
 export type ObjectGridDataTableSchema =
   DeclaredDataTableSchema & ObjectGridDataTableSchemaHolds;
 
-/** The row heights this grid styles — the five `RowHeight` values the spec admits. */
-type RowHeightMode = 'compact' | 'short' | 'medium' | 'tall' | 'extra_tall';
-
-/**
- * The ONE answer this component gives for a `rowHeight` it does not recognize
- * (objectui#4443).
- *
- * The seed used to be `schema.rowHeight ?? 'compact'`, which made the component
- * answer the same question two ways: an ABSENT `rowHeight` landed on `compact`,
- * an OFF-SPEC one fell through the density ternaries below to their terminal
- * `else` — the `medium` styling. That is the absent-vs-off-spec split #4440
- * removed from `ListView`, and a third answer to a question `@object-ui/core`
- * (`rowHeightToDensityMode`, which abstains) and the `@object-ui/react` spec
- * bridge (#4352, which abstains) had already settled. One metadata-driven
- * system, one answer: off-spec renders exactly like absent.
- *
- * The ternary chains are deliberately NOT touched — `medium` is a real value
- * with its own arm, and a leaf renderer's terminal `else` is legitimate styling.
- * Narrowing happens here, at the boundary, so nothing off-spec ever reaches it.
- *
- * Membership is tested against `ROW_HEIGHT_TO_DENSITY_MODE` rather than a local
- * list so the admitted values have one definition in the repo; that table is
- * typed `Record<RowHeight, DensityMode>`, so the build fails if the spec grows a
- * sixth row height and this resolver is not taught about it.
- *
- * `hasOwnProperty`, not `in`: `in` walks the prototype chain, so `'toString'`
- * would come back admitted. That is not hypothetical here — the toolbar's icon
- * map is looked up by the same key, and a prototype member reached
- * `Object.prototype.toString` and rendered it as a React component, while a
- * plain off-spec value produced `undefined` and threw outright.
- */
-function resolveRowHeightMode(rowHeight: unknown): RowHeightMode {
-  if (typeof rowHeight !== 'string') return 'compact';
-  if (!Object.prototype.hasOwnProperty.call(ROW_HEIGHT_TO_DENSITY_MODE, rowHeight)) return 'compact';
-  return rowHeight as RowHeightMode;
-}
-
-/**
- * The page size every display surface of this component falls back to when the
- * author declared none (objectui#9853, rulings 5749197629 and 5824040487): the
- * flat table, the server-paged table, the grouped view's page of groups, and a
- * server-grouped leaf's page of rows. Wherever there is a pager, this is its
- * page.
- *
- * READ from `@objectstack/spec`, not restated. The protocol's pagination config
- * declares `pageSize` with a default, and that declaration is the one answer an
- * author can look up; a literal here would be a second answer free to drift
- * from it. Parsing an empty object is the spec's own way of saying what an
- * undeclared member means, so this is the value the schema would fill in.
- *
- * ⚠️ There is deliberately no local fallback number behind this read. If a
- * future `@objectstack/spec` stops declaring the default (the same principle
- * `packages/types` applies at its own import boundary is that a validator does
- * not write values), this throws at module load instead of quietly
- * substituting a number nobody declared. The spec version is locked, so that
- * can only surface on a spec upgrade, where the pin
- * `ObjectGrid.displayPageSizeDefault-9853.test.tsx` reddens first.
- */
-function readSpecDisplayPageSize(): number {
-  const declared: unknown = PaginationConfigSchema.parse({}).pageSize;
-  if (typeof declared !== 'number' || !Number.isInteger(declared) || declared <= 0) {
-    throw new Error(
-      '[ObjectUI] ObjectGrid: @objectstack/spec no longer declares a positive default '
-      + `for pagination.pageSize (read ${String(declared)}); the grid has no display `
-      + 'page size to fall back to.',
-    );
-  }
-  return declared;
-}
-const DEFAULT_DISPLAY_PAGE_SIZE = readSpecDisplayPageSize();
-
-/**
- * How many rows this grid FETCHES when it buckets a window into groups in the
- * browser and the author declared no page size (`bucketsFetchedWindow`). A
- * fetch batch, ⛔ not a page size: no display path reads it, and it does not
- * follow the display default (objectui#9853, ruling 5824040487, structure B).
- * Before ruling 5749197629 this number was named as a "server window" and also
- * sized the server-paged table's visible page, so one constant meant two
- * quantities.
- *
- * It stays a constant of this component rather than the protocol's value
- * because the protocol declares no fetch batch: it is how much of the result
- * set a client-grouped view holds, which is an implementation choice.
- */
-const DEFAULT_FETCH_BATCH_SIZE = 50;
-
-/**
- * The mode a `selection` object with no `type` member asks for (objectui#9837,
- * ruling A-prime: presence enables, an explicit off wins).
- *
- * ⚠️ Derived, not chosen freely. The ruling's first clause is that writing the
- * object turns selection ON, so the only values that satisfy it are the two
- * enabling ones — and `'multiple'` is already this renderer's own answer to
- * "selection is on, nothing said which kind": it is what the bulk-action
- * auto-enable arm resolves to, and what the legacy `selectable: true` means
- * (`packages/types/src/data-display.ts`, "boolean: Enable/disable selection
- * (true = multiple selection)"). `'single'` would be a third, unstated opinion.
- *
- * ⚠️ `@objectstack/spec`'s own `SelectionConfigSchema` declares `type` with
- * `.default('none')`, which this constant deliberately does NOT follow: honouring
- * it would make a written object mean OFF and contradict the ruling's first
- * clause outright. It is reachable only through a PARSE, and this repo's mirror
- * strips imported defaults at the import boundary
- * (`packages/types/src/zod/imported-defaults.ts`), so an omitted `type` stays
- * omitted on the way to this read — but metadata parsed by the spec bundle
- * itself arrives carrying `type: 'none'` and is then an EXPLICIT off here.
- * Handed back as a question on objectui#9837 rather than decided here.
- */
-const DEFAULT_SELECTION_TYPE = 'multiple' as const;
-
-/**
- * The ONE resolver for an authored page size, for the reason the `rowHeight`
- * resolver just above exists: one resolver at every entry is what keeps the
- * answer single (objectui#4443).
- *
- * Before objectui#9853 this value was spelled out separately at each of its
- * three read points, and the spellings disagreed about a non-positive number:
- * the flat site used `||`, so `0` was falsy and fell through to a default,
- * while both seeds used `??`, so `0` was not nullish and survived as a real
- * page size. It then divided the grouped pager and reached the wire as
- * `$top: 0`, so the grid asked the server for nothing and drew an empty table
- * — with no error, no warning and no empty state naming the cause.
- *
- * ## Why refusing `0` is not this renderer inventing a meaning
- *
- * `@objectstack/spec` has already answered what a `pageSize` of `0` means.
- * Its pagination config declares the member as a POSITIVE integer with a
- * default, and the spec's own suite pins that refusal under the names
- * `should reject zero pageSize` and `should reject negative pageSize`. The
- * `limit` that this block's `ElementDataSourceMapping` lowers
- * `pagination.pageSize` into is declared positive as well. So `0` is not a
- * spelling whose meaning a consumer may choose; it is a value the contract
- * refuses, and a renderer that quietly divides by it is the only party not
- * saying so.
- *
- * ⚠️ The refusal is FAIL-SOFT on purpose. Throwing would take out the whole
- * subtree for a declaration the flat path already tolerated, which is a worse
- * outcome than the defect. The value is dropped, the site's own default is
- * used, and `describeNonPositivePageSize` states it once through the channel
- * this component already uses for "you declared it, the renderer dropped it".
- *
- * Reads the canonical key first and the deprecated flat shorthand second, in
- * that precedence, with `??` so an explicit `0` is SEEN by the guard instead
- * of skipped by falsiness — that skipping is the defect, not the fix.
- */
-function readAuthoredPageSize(schema: {
-  pagination?: unknown;
-  pageSize?: unknown;
-}): unknown {
-  const fromObject = (schema.pagination as { pageSize?: unknown } | undefined)?.pageSize;
-  return fromObject ?? schema.pageSize;
-}
-
-function isUsablePageSize(value: unknown): value is number {
-  return typeof value === 'number' && Number.isInteger(value) && value > 0;
-}
-
-function resolvePageSize(
-  schema: { pagination?: unknown; pageSize?: unknown },
-  fallback: number,
-): number {
-  const authored = readAuthoredPageSize(schema);
-  return isUsablePageSize(authored) ? authored : fallback;
-}
-
-/**
- * The diagnostic half. `null` means "nothing to say" — an absent key is not a
- * mistake, and a usable page size is not either, so the message is CONDITIONAL
- * and a control asserting its silence is what keeps it from being an
- * always-on marker that states nothing.
- */
-function describeNonPositivePageSize(
-  schema: { pagination?: unknown; pageSize?: unknown },
-  context: { blockType?: unknown; objectName?: unknown },
-): string | null {
-  const authored = readAuthoredPageSize(schema);
-  if (authored === undefined || authored === null) return null;
-  if (isUsablePageSize(authored)) return null;
-  const where = [
-    typeof context.blockType === 'string' ? context.blockType : 'object-grid',
-    typeof context.objectName === 'string' ? context.objectName : undefined,
-  ]
-    .filter(Boolean)
-    .join(' on ');
-  return (
-    `[ObjectUI] ObjectGrid pagination: ${where} declared pageSize: ${String(authored)}, `
-    + 'which is not a positive integer. A page size must be a positive integer '
-    + '(the spec refuses zero and negative values), so it was ignored and this '
-    + 'grid fell back to its default page size.'
-  );
-}
-
-/**
- * The grouping-refusal signature when no entry is refused (objectui#10583,
- * objectui#10657): the authored grouping config is then handed on as it is.
- */
-const NO_GROUPING_REFUSAL = JSON.stringify({ refused: [], warned: [] });
-
-/**
- * The row key that carries a record's optimistic-concurrency token
- * (objectui#12292): `updated_at`, the key the record surfaces send as
- * `If-Match`.
- */
-const OCC_TOKEN_FIELD = 'updated_at';
-
-/**
- * The concurrency token a row carries, read exactly as the record surfaces read
- * it (`occVersionOf` in `plugin-form`, the save in `plugin-detail`'s
- * `InlineEditSaveBar`): a non-empty string `updated_at`. Anything else (a
- * backend without timestamps, a row read without the column) answers
- * `undefined`, and the write goes out unguarded, as it did before.
- */
-function rowVersionOf(row: unknown): string | undefined {
-  const v = (row as Record<string, unknown> | null | undefined)?.[OCC_TOKEN_FIELD];
-  return typeof v === 'string' && v.length > 0 ? v : undefined;
-}
-
-/** What this grid remembers about its last landed write to one record. */
-interface WrittenRowVersion {
-  /** The token the row carried when that write was made: the read it superseded. */
-  readVersion: string;
-  /** The token of the record the server answered that write with. */
-  version: string;
-}
-
-/**
- * The `ifMatch` a row save sends: the rule `plugin-form`'s `versionToSend`
- * applies to a form that stays open (objectui#10565), applied to a row.
- *
- * A saved row keeps the token it was READ with until the grid re-reads it, and
- * that token stopped being current the moment this grid's own write landed. So
- * while the row still carries the read a landed write superseded, the version
- * that write answered with is sent. A row carrying any other token is a newer
- * read, and its token wins. A row with no token stays unguarded.
- */
-function rowVersionToSend(
-  written: WrittenRowVersion | undefined,
-  readVersion: string | undefined,
-): string | undefined {
-  if (!readVersion) return undefined;
-  return written && written.readVersion === readVersion ? written.version : readVersion;
-}
-
-/** The three ways out of `ConcurrentUpdateDialog`, by its own button names. */
-type RowConflictChoice = 'reload' | 'overwrite' | 'cancel';
-
-/**
- * The per-row outcome the table's `onBatchSave` slot reads, derived from the
- * slot's declared return rather than restated here.
- */
-type BatchSaveOutcome = Exclude<
-  Awaited<ReturnType<NonNullable<DataTableSchema['onBatchSave']>>>,
-  void
->;
-
 /**
  * [objectui#12528] Reports the grid's column summaries to a host that draws
  * them in its own footer row (`onColumnSummaryChange`). Renders nothing.
diff --git a/ui/packages/plugin-grid/src/objectGridColumns.ts b/ui/packages/plugin-grid/src/objectGridColumns.ts
new file mode 100644
index 00000000000..909db822453
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridColumns.ts
@@ -0,0 +1,304 @@
+/**
+ * The column helpers and column emit types of `ObjectGrid` (`./ObjectGrid.tsx`):
+ * the chip field types, the header-label resolver, the column-list
+ * normaliser and the types `generateColumns()` emits into, moved out of that
+ * file verbatim (objectstack#25994, slice 1). `ObjectGrid.tsx` re-exports
+ * every name it exported before.
+ */
+
+import type { ListColumn, TableColumn } from '@object-ui/types';
+import type { I18nLabel } from '@objectstack/spec/ui';
+import { pickLocalized } from '@object-ui/i18n';
+
+/**
+ * The field types whose grid cell draws chips: the ones `@object-ui/fields`
+ * maps to `SelectCellRenderer` (a badge per selected option). Their column
+ * carries `chips`, so `data-table` floors it at its widest drawn chip and a
+ * single-word value is never ellipsized (objectui#12708).
+ */
+const CHIP_FIELD_TYPES: ReadonlySet<string> = new Set(['select', 'status', 'multiselect', 'radio', 'checkboxes', 'tags']);
+
+export function isChipFieldType(type: unknown): boolean {
+  return typeof type === 'string' && CHIP_FIELD_TYPES.has(type);
+}
+
+/**
+ * Resolve a column header `label` (`ListColumnSchema.label`, the spec's
+ * `I18nLabel`) to the string the header prints, in the viewer's `language`.
+ *
+ * A plain string passes through unchanged. An inline locale map
+ * (`{ en: 'Amount', 'zh-CN': '金额' }`) is picked by `pickLocalized` — the one
+ * locale pick the console uses for `I18nLabel`, with its own floor when the
+ * viewer's locale is absent — rather than a second implementation here.
+ * objectui#12358: this used to keep only a plain string and answer `undefined`
+ * for a map, so an authored map header silently fell back to the field label.
+ * A map with no usable entry still answers `undefined`, so the field-label
+ * fallback at the call site applies exactly as for an absent label.
+ */
+export function resolveColumnLabel(label: string | I18nLabel | undefined, language: string | undefined): string | undefined {
+  if (label == null) return undefined;
+  if (typeof label === 'string') return label;
+  return pickLocalized(label, language) || undefined;
+}
+
+/**
+ * Helper to normalize columns configuration
+ * Handles both string[] and ListColumn[] formats
+ */
+export function normalizeColumns(
+  columns: string[] | ListColumn[] | undefined
+): ListColumn[] | string[] | undefined {
+  if (!columns || columns.length === 0) return undefined;
+  
+  // Already in ListColumn format - check for object type with optional chaining
+  if (typeof columns[0] === 'object' && columns[0] !== null) {
+    return columns as ListColumn[];
+  }
+  
+  // String array format
+  return columns as string[];
+}
+
+/**
+ * ⭐ WHAT THIS GRID'S COLUMN PRODUCER IS ALLOWED TO EMIT (objectui#6004).
+ *
+ * `generateColumns()` below builds the column array this component hands to
+ * `data-table`, whose slot is `DataTableSchema.columns: TableColumn[]`. It had
+ * no return annotation, so its four emit paths were inferred structurally and
+ * nothing ever compared them to the slot's declaration — and all four call
+ * sites re-widened to `any` on the way out, so even an annotation would have
+ * been discarded one hop later.
+ *
+ * ## ⭐ Why this is not just `: TableColumn[]`
+ *
+ * objectui#6373 measured, at the sibling producer in `plugin-dashboard`, that a
+ * bare `TableColumn` annotation raises no error on a `{ ...spread }` emit,
+ * because TypeScript's excess-property check is a FRESHNESS check on the
+ * properties an object literal WRITES OUT and spread properties are exempt.
+ *
+ * Measured again HERE before choosing this shape, because this seam is worse
+ * than that one and the difference matters:
+ *
+ *   1. `generateColumns = useCallback((): TableColumn[] => {`, everything else
+ *      unchanged  →  `tsc --noEmit` exit 0, ZERO diagnostics.
+ *   2. Same, PLUS an undeclared key `wrapControl: true` WRITTEN OUT in the path-A
+ *      column literal (not arriving through a spread)  →  exit 0, ZERO diagnostics.
+ *
+ * Run 2 is the one that fixes the mechanism. At objectui#6373's seam the object
+ * literal sits in `enrich()`'s return position, so freshness still caught keys
+ * written out longhand and only the spread escaped. Here every literal is the
+ * return value of a `.map()` callback, so it is inferred into the callback's
+ * return type FIRST and reaches the annotation as a non-fresh `X[]`. Freshness
+ * is gone entirely: written-out keys escape too. A bare annotation at this seam
+ * is not a weak instrument, it is an inert one — a green gate and no guard.
+ *
+ * The `?: never` members are what make the annotation able to fail. They are
+ * ADR-0049 retirement tombstones — this repo's convention for a key that is
+ * REFUSED rather than merely absent (`StaticTableColumn` in `@object-ui/types`)
+ * — and they bite by ASSIGNABILITY, which survives `.map()` because it never
+ * depended on freshness. Re-adding `...(col.summary && { summary: col.summary })`
+ * to a column literal is a compile error naming `summary`.
+ *
+ * ## The rule (objectui#6373's, applied to this producer's key set)
+ *
+ * A producer may write into a `TableColumn[]` slot only keys the CONSUMER of
+ * that slot reads, and the read set is MEASURED from the consumer's source,
+ * never assumed. A key the consumer reads and `TableColumn` declares is
+ * written; a key the consumer reads that `TableColumn` does not declare is HELD
+ * where a ruling already holds it; a key nothing reads is RETIRED — never
+ * declared, because declaring a key nothing reads is the same
+ * `declared != enforced` defect facing the other way. Before retiring, prove
+ * the value has a second road to its consumer.
+ *
+ * Consumers measured for THIS producer — two of them, because the array is read
+ * twice before it reaches the slot:
+ *
+ *   - `data-table.tsx`, comments stripped, every `col.<key>` read — FOURTEEN:
+ *     `accessorKey`, `width`, `align`, `header`, `className`, `cellClassName`,
+ *     `sortable`, `resizable`, `editable`, `type`, `cell`, `headerIcon`,
+ *     `fitContent`, `wrap`. ⚠️ It was THIRTEEN between objectui#7196 and
+ *     objectui#6650, which added the `wrap` read this producer now feeds; it
+ *     said fourteen before #7196 re-derived it:
+ *     `name` was the fourteenth and was correct when written, but objectui#6963
+ *     (2026-08-31) retired the `col.name` alias — the last undeclared spelling
+ *     the adapter accepted — so the key left the consumer's read set that day.
+ *   - THIS FILE's own downstream passes, which read the array before handing it
+ *     on — TEN: `pinned` (the left/right reorder + the frozen-column verdict),
+ *     `accessorKey`, `header`, `width`, `type`, `fitContent`, plus the four the
+ *     chrome passes read in order to RE-EXPRESS them: `className` and
+ *     `cellClassName` (`applyDensity`, and again in the right-pinned literal),
+ *     `sortable` (`withSortability`), `cell` (the mobile card renderer).
+ *     ⚠️ Those four were missing from this list from the day it was written —
+ *     all three passes already existed at that commit — so this is an
+ *     incompleteness, not drift. They change no verdict: each is declared on
+ *     `TableColumn` and read by `data-table.tsx` as well. Recorded because a
+ *     list presented as MEASURED has to be one.
+ *     ⚠️ `col.wrap` is read ONE MORE TIME here since objectui#6650, at the
+ *     `LinkCell` call sites, and that read is not a re-expression of the
+ *     forward — it is a SECOND consumer of the same authored key. The record
+ *     link wears its own `truncate`, so honouring `wrap` only downstream would
+ *     have left column one of almost every grid wrapping its cell body around
+ *     text still clamped to one line.
+ *
+ * Verdicts, each with the read-count behind it:
+ *
+ *   - `headerIcon` — DECLARED by `TableColumn`, so NOT held. Live:
+ *     `data-table.tsx` renders it into the header cell (1 render site, 2
+ *     syntactic reads), forwarded verbatim and never re-expressed. It WAS held
+ *     here, on the "undeclared by `TableColumn`" premise; objectui#6615
+ *     declared it and that premise expired with nothing going red at the moment
+ *     of loss. objectui#6424 then removed the hold, MEASURED rather than
+ *     derived: with the member deleted both emit types below are byte-identical
+ *     (27 members, every member's resolved type unchanged), against a positive
+ *     control that deleting `pinned` instead moves them to 26. Pinned in
+ *     `columnHoldsExpiry-6424.test.ts` — which now also carries the claim the
+ *     hold used to carry implicitly, that `TableColumn` DECLARES the key.
+ *   - `pinned` — HELD. Live, and consumed BEFORE the slot: the reorder pass
+ *     below reads it (5 reads in this file) and re-expresses it as the sticky
+ *     `className` that `data-table` actually reads. `data-table` never reads
+ *     `pinned` itself, and does not need to.
+ *   - `wrap` — DECLARED by `TableColumn`, forwarded, and READ. This entry was
+ *     "RETIRED (objectui#5453, 2026-08-28)" and the retirement was correct on
+ *     its own measurement: `data-table.tsx` was then a two-way switch,
+ *     `isFit ? 'w-full whitespace-nowrap' : 'truncate w-full'`, with a `title`
+ *     tooltip as the only concession to overflow, so nothing read the key and
+ *     the emit rule retired it. ⭐ What #5453 could not settle is what
+ *     objectui#6650 escalated one level up: `@objectstack/spec` never stopped
+ *     DECLARING `ListColumn.wrap`, and describes it to authors as "Allow text
+ *     wrapping" — so retiring the forward left a promise made at authoring
+ *     time and silently broken at render time. The maintainer ruled that
+ *     promise is kept rather than withdrawn (2026-09-02, Option B): the
+ *     consumer was BUILT, `TableColumn` now declares the key, and the forward
+ *     returns WITH a reader. ⚠️ Note what moved and what did not — the emit
+ *     rule is unchanged and still decided this: the key is written because the
+ *     consumer reads it, which is the same test that retired it when the
+ *     consumer did not exist.
+ *   - `options` — RETIRED (see the enrichment pass below).
+ *   - `type` — not adjudicated here; its VALUE set was settled by `fc62bb490`,
+ *     whose fold still stands. It is the one member whose vocabulary differs between
+ *     the two types below.
+ *   - `name` — not emitted by this producer at all, so objectui#5120's alias
+ *     never needed a hold here. Tombstoned only in the sense that nothing writes
+ *     it — and since objectui#6963 (2026-08-31) nothing READS it either: the
+ *     consumer-side alias is retired, so the key is absent from BOTH ends of
+ *     this seam and the verdict now rests on two measurements, not one.
+ *
+ * `essential` is absent from both types on purpose: objectui#6004's suggested
+ * key list named it, but it was READ off the authored column and turned into a
+ * `className` — never emitted, and not a `ListColumn` member either. That read
+ * is now RETIRED too (objectui#6458), so mobile visibility is decided purely
+ * positionally (`colIndex === 0`) and nothing on either side of this producer
+ * carries the key.
+ */
+
+/**
+ * The tombstoned keys — DERIVED from the authored input type, never hand-listed,
+ * so a future `ListColumn` member is refused by default and has to be
+ * adjudicated to escape.
+ *
+ * `ListColumn` is the right derivation source because it is where this
+ * producer's drift comes from: every key the emit could wrongly grow is a key
+ * the author wrote on the input and someone forwarded. `pinned` is the one that
+ * escaped and stayed — adjudicated HELD above. `wrap` escaped too, was RETIRED
+ * by objectui#5453, and has since been DECLARED on `TableColumn` by
+ * objectui#6650, so the band lets it through again — ⭐ and it does so with no
+ * edit to this line, which is the property that makes the derivation worth
+ * having. The tombstone was never a carve-out to remember to remove; it was a
+ * consequence of `TableColumn` not declaring the key, and it lifted the moment
+ * that stopped being true. A key that never earns a declaration stays refused
+ * by default, and re-adding its forward stays a compile error naming it.
+ */
+export type RetiredListColumnKey = Exclude<keyof ListColumn, keyof TableColumn | 'pinned'>;
+
+/**
+ * The undeclared-but-live keys this producer holds. See the docblock above.
+ *
+ * ⚠️ "Undeclared by `TableColumn`" is this interface's ENTRY CONDITION, and it
+ * is a claim about ANOTHER package that can stop being true with nothing going
+ * red here. So it is re-checked per key when the card owning that key closes,
+ * never inherited: `headerIcon` sat here on exactly that premise until
+ * objectui#6615 declared it on `TableColumn`, at which point the hold was
+ * redundant rather than load-bearing, and objectui#6424 removed it.
+ *
+ * ⛔ A key whose ONLY declaration on the emit types is this interface is not in
+ * that position — deleting it deletes the key from the emit. `pinned` is that
+ * key today, which is why the two verdicts differ.
+ */
+export interface ObjectGridColumnHolds {
+  /**
+   * HELD, load-bearing on BOTH counts — the pair that has to hold for a hold to
+   * be real, and the contrast that made `headerIcon`'s removal safe:
+   *
+   *   1. `TableColumn` does NOT declare it, and `RetiredListColumnKey` carves it
+   *      out of the derived tombstone band, so this member is its ONLY
+   *      declaration on both emit types. Deleting it drops the key from them
+   *      (measured: 27 members → 26).
+   *   2. It has a live consumer BEFORE the slot — this file's own reorder pass
+   *      reads it and re-expresses it as the sticky `className` that
+   *      `data-table` actually reads. That is the "second road" the emit rule
+   *      demands before a key may be retired. `wrap` failed it in 2026-08 and
+   *      was retired; objectui#6650 then BUILT its consumer rather than
+   *      reinstating a hold, which is why `wrap` is a plain declared key today
+   *      and `pinned` is still the only member here.
+   */
+  pinned?: 'left' | 'right';
+}
+
+/**
+ * What `generateColumns()` returns: everything final EXCEPT `type`, which is
+ * still the producer's raw inference vocabulary (`@objectstack/spec`'s
+ * `FieldType`, 49 values) rather than the EIGHT-literal union `TableColumn`
+ * declares (`TABLE_COLUMN_TYPES`: `text`, `number`, `date`, `datetime`,
+ * `currency`, `percent`, `boolean`, `action`). `fc62bb490` folds it
+ * downstream, in a pass that is deliberately separate from the enrichment map —
+ * so the pre-fold shape needs a name, and this is it.
+ *
+ * ⚠️ This said "7-literal" until objectui#7196 re-derived it. `action` joined
+ * the union at objectui#6370 on 2026-08-25 — a day BEFORE this docblock was
+ * written, and that commit's own subject line reads "make the 8-literal union
+ * the one canonical TableColumn.type" — so the count was never right here; it
+ * was mis-copied, not drifted. Both numbers are now measured rather than
+ * recited: `TABLE_COLUMN_TYPES` in `@object-ui/types` has 8 members and
+ * `@objectstack/spec`'s `FieldType` enum has 49.
+ */
+/**
+ * ⭐ `options` — RETIRED at this emit (objectui#6004), and this explicit
+ * tombstone is now the ONLY enforcement of that verdict. ⛔ Do not "tidy" it
+ * away as redundant.
+ *
+ * Until objectui#6425 the key needed no tombstone: it was a member of NO part
+ * of the emit types below, so TypeScript's excess-property check refused a
+ * fresh literal writing it — refusal by non-membership. #6425's maintainer
+ * ruling (2026-08-27) then declared `options` on `TableColumn` itself (the
+ * `object-data-table` cell pipeline reads it off the AUTHORED column), which
+ * made the key a member here through `Omit<TableColumn, …>` / `TableColumn`
+ * and silently ended that enforcement. Nothing went red at the moment of
+ * loss — the emit-boundary suite's directive merely turned TS2578-unused,
+ * which is luck, not design. The general rule, recorded so the next seam can
+ * check itself: **a pin enforced by a key's non-membership silently stops
+ * enforcing the moment the key becomes a member.**
+ *
+ * objectui#6004's verdict itself is unchanged — nothing on either side of
+ * THIS seam reads a column-level `options` (`data-table.tsx` has no such
+ * read; `renderCellEditor` rebuilds the field from the object schema) — only
+ * the refusal's mechanism moves, from freshness to assignability. It is
+ * intersected into BOTH the pre-fold draft and the post-fold column, because
+ * the retirement belongs to the seam, not to one of its two types; the key
+ * cannot land in the DERIVED band (`RetiredListColumnKey`) because `options`
+ * is not a `ListColumn` member, which is why this one is hand-written.
+ */
+type ObjectGridRetiredOptionsTombstone = { options?: never };
+
+export type ObjectGridColumnDraft =
+  Omit<TableColumn, 'type'>
+  & { type?: string }
+  & ObjectGridColumnHolds
+  & ObjectGridRetiredOptionsTombstone
+  & { [K in RetiredListColumnKey]?: never };
+
+/** Post-fold: what actually reaches `DataTableSchema.columns: TableColumn[]`. */
+export type ObjectGridColumn =
+  TableColumn
+  & ObjectGridColumnHolds
+  & ObjectGridRetiredOptionsTombstone
+  & { [K in RetiredListColumnKey]?: never };
diff --git a/ui/packages/plugin-grid/src/objectGridDefaults.ts b/ui/packages/plugin-grid/src/objectGridDefaults.ts
new file mode 100644
index 00000000000..208cbc63102
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridDefaults.ts
@@ -0,0 +1,207 @@
+/**
+ * The display defaults of `ObjectGrid` (`./ObjectGrid.tsx`): the row-height
+ * resolver, the page sizes, the selection default and the no-refusal
+ * grouping signature, moved out of that file verbatim (objectstack#25994,
+ * slice 1).
+ */
+
+import { PaginationConfigSchema } from '@objectstack/spec/ui';
+import { ROW_HEIGHT_TO_DENSITY_MODE } from '@object-ui/core';
+
+/** The row heights this grid styles — the five `RowHeight` values the spec admits. */
+export type RowHeightMode = 'compact' | 'short' | 'medium' | 'tall' | 'extra_tall';
+
+/**
+ * The ONE answer this component gives for a `rowHeight` it does not recognize
+ * (objectui#4443).
+ *
+ * The seed used to be `schema.rowHeight ?? 'compact'`, which made the component
+ * answer the same question two ways: an ABSENT `rowHeight` landed on `compact`,
+ * an OFF-SPEC one fell through the density ternaries below to their terminal
+ * `else` — the `medium` styling. That is the absent-vs-off-spec split #4440
+ * removed from `ListView`, and a third answer to a question `@object-ui/core`
+ * (`rowHeightToDensityMode`, which abstains) and the `@object-ui/react` spec
+ * bridge (#4352, which abstains) had already settled. One metadata-driven
+ * system, one answer: off-spec renders exactly like absent.
+ *
+ * The ternary chains are deliberately NOT touched — `medium` is a real value
+ * with its own arm, and a leaf renderer's terminal `else` is legitimate styling.
+ * Narrowing happens here, at the boundary, so nothing off-spec ever reaches it.
+ *
+ * Membership is tested against `ROW_HEIGHT_TO_DENSITY_MODE` rather than a local
+ * list so the admitted values have one definition in the repo; that table is
+ * typed `Record<RowHeight, DensityMode>`, so the build fails if the spec grows a
+ * sixth row height and this resolver is not taught about it.
+ *
+ * `hasOwnProperty`, not `in`: `in` walks the prototype chain, so `'toString'`
+ * would come back admitted. That is not hypothetical here — the toolbar's icon
+ * map is looked up by the same key, and a prototype member reached
+ * `Object.prototype.toString` and rendered it as a React component, while a
+ * plain off-spec value produced `undefined` and threw outright.
+ */
+export function resolveRowHeightMode(rowHeight: unknown): RowHeightMode {
+  if (typeof rowHeight !== 'string') return 'compact';
+  if (!Object.prototype.hasOwnProperty.call(ROW_HEIGHT_TO_DENSITY_MODE, rowHeight)) return 'compact';
+  return rowHeight as RowHeightMode;
+}
+
+/**
+ * The page size every display surface of this component falls back to when the
+ * author declared none (objectui#9853, rulings 5749197629 and 5824040487): the
+ * flat table, the server-paged table, the grouped view's page of groups, and a
+ * server-grouped leaf's page of rows. Wherever there is a pager, this is its
+ * page.
+ *
+ * READ from `@objectstack/spec`, not restated. The protocol's pagination config
+ * declares `pageSize` with a default, and that declaration is the one answer an
+ * author can look up; a literal here would be a second answer free to drift
+ * from it. Parsing an empty object is the spec's own way of saying what an
+ * undeclared member means, so this is the value the schema would fill in.
+ *
+ * ⚠️ There is deliberately no local fallback number behind this read. If a
+ * future `@objectstack/spec` stops declaring the default (the same principle
+ * `packages/types` applies at its own import boundary is that a validator does
+ * not write values), this throws at module load instead of quietly
+ * substituting a number nobody declared. The spec version is locked, so that
+ * can only surface on a spec upgrade, where the pin
+ * `ObjectGrid.displayPageSizeDefault-9853.test.tsx` reddens first.
+ */
+function readSpecDisplayPageSize(): number {
+  const declared: unknown = PaginationConfigSchema.parse({}).pageSize;
+  if (typeof declared !== 'number' || !Number.isInteger(declared) || declared <= 0) {
+    throw new Error(
+      '[ObjectUI] ObjectGrid: @objectstack/spec no longer declares a positive default '
+      + `for pagination.pageSize (read ${String(declared)}); the grid has no display `
+      + 'page size to fall back to.',
+    );
+  }
+  return declared;
+}
+export const DEFAULT_DISPLAY_PAGE_SIZE = readSpecDisplayPageSize();
+
+/**
+ * How many rows this grid FETCHES when it buckets a window into groups in the
+ * browser and the author declared no page size (`bucketsFetchedWindow`). A
+ * fetch batch, ⛔ not a page size: no display path reads it, and it does not
+ * follow the display default (objectui#9853, ruling 5824040487, structure B).
+ * Before ruling 5749197629 this number was named as a "server window" and also
+ * sized the server-paged table's visible page, so one constant meant two
+ * quantities.
+ *
+ * It stays a constant of this component rather than the protocol's value
+ * because the protocol declares no fetch batch: it is how much of the result
+ * set a client-grouped view holds, which is an implementation choice.
+ */
+export const DEFAULT_FETCH_BATCH_SIZE = 50;
+
+/**
+ * The mode a `selection` object with no `type` member asks for (objectui#9837,
+ * ruling A-prime: presence enables, an explicit off wins).
+ *
+ * ⚠️ Derived, not chosen freely. The ruling's first clause is that writing the
+ * object turns selection ON, so the only values that satisfy it are the two
+ * enabling ones — and `'multiple'` is already this renderer's own answer to
+ * "selection is on, nothing said which kind": it is what the bulk-action
+ * auto-enable arm resolves to, and what the legacy `selectable: true` means
+ * (`packages/types/src/data-display.ts`, "boolean: Enable/disable selection
+ * (true = multiple selection)"). `'single'` would be a third, unstated opinion.
+ *
+ * ⚠️ `@objectstack/spec`'s own `SelectionConfigSchema` declares `type` with
+ * `.default('none')`, which this constant deliberately does NOT follow: honouring
+ * it would make a written object mean OFF and contradict the ruling's first
+ * clause outright. It is reachable only through a PARSE, and this repo's mirror
+ * strips imported defaults at the import boundary
+ * (`packages/types/src/zod/imported-defaults.ts`), so an omitted `type` stays
+ * omitted on the way to this read — but metadata parsed by the spec bundle
+ * itself arrives carrying `type: 'none'` and is then an EXPLICIT off here.
+ * Handed back as a question on objectui#9837 rather than decided here.
+ */
+export const DEFAULT_SELECTION_TYPE = 'multiple' as const;
+
+/**
+ * The ONE resolver for an authored page size, for the reason the `rowHeight`
+ * resolver just above exists: one resolver at every entry is what keeps the
+ * answer single (objectui#4443).
+ *
+ * Before objectui#9853 this value was spelled out separately at each of its
+ * three read points, and the spellings disagreed about a non-positive number:
+ * the flat site used `||`, so `0` was falsy and fell through to a default,
+ * while both seeds used `??`, so `0` was not nullish and survived as a real
+ * page size. It then divided the grouped pager and reached the wire as
+ * `$top: 0`, so the grid asked the server for nothing and drew an empty table
+ * — with no error, no warning and no empty state naming the cause.
+ *
+ * ## Why refusing `0` is not this renderer inventing a meaning
+ *
+ * `@objectstack/spec` has already answered what a `pageSize` of `0` means.
+ * Its pagination config declares the member as a POSITIVE integer with a
+ * default, and the spec's own suite pins that refusal under the names
+ * `should reject zero pageSize` and `should reject negative pageSize`. The
+ * `limit` that this block's `ElementDataSourceMapping` lowers
+ * `pagination.pageSize` into is declared positive as well. So `0` is not a
+ * spelling whose meaning a consumer may choose; it is a value the contract
+ * refuses, and a renderer that quietly divides by it is the only party not
+ * saying so.
+ *
+ * ⚠️ The refusal is FAIL-SOFT on purpose. Throwing would take out the whole
+ * subtree for a declaration the flat path already tolerated, which is a worse
+ * outcome than the defect. The value is dropped, the site's own default is
+ * used, and `describeNonPositivePageSize` states it once through the channel
+ * this component already uses for "you declared it, the renderer dropped it".
+ *
+ * Reads the canonical key first and the deprecated flat shorthand second, in
+ * that precedence, with `??` so an explicit `0` is SEEN by the guard instead
+ * of skipped by falsiness — that skipping is the defect, not the fix.
+ */
+function readAuthoredPageSize(schema: {
+  pagination?: unknown;
+  pageSize?: unknown;
+}): unknown {
+  const fromObject = (schema.pagination as { pageSize?: unknown } | undefined)?.pageSize;
+  return fromObject ?? schema.pageSize;
+}
+
+function isUsablePageSize(value: unknown): value is number {
+  return typeof value === 'number' && Number.isInteger(value) && value > 0;
+}
+
+export function resolvePageSize(
+  schema: { pagination?: unknown; pageSize?: unknown },
+  fallback: number,
+): number {
+  const authored = readAuthoredPageSize(schema);
+  return isUsablePageSize(authored) ? authored : fallback;
+}
+
+/**
+ * The diagnostic half. `null` means "nothing to say" — an absent key is not a
+ * mistake, and a usable page size is not either, so the message is CONDITIONAL
+ * and a control asserting its silence is what keeps it from being an
+ * always-on marker that states nothing.
+ */
+export function describeNonPositivePageSize(
+  schema: { pagination?: unknown; pageSize?: unknown },
+  context: { blockType?: unknown; objectName?: unknown },
+): string | null {
+  const authored = readAuthoredPageSize(schema);
+  if (authored === undefined || authored === null) return null;
+  if (isUsablePageSize(authored)) return null;
+  const where = [
+    typeof context.blockType === 'string' ? context.blockType : 'object-grid',
+    typeof context.objectName === 'string' ? context.objectName : undefined,
+  ]
+    .filter(Boolean)
+    .join(' on ');
+  return (
+    `[ObjectUI] ObjectGrid pagination: ${where} declared pageSize: ${String(authored)}, `
+    + 'which is not a positive integer. A page size must be a positive integer '
+    + '(the spec refuses zero and negative values), so it was ignored and this '
+    + 'grid fell back to its default page size.'
+  );
+}
+
+/**
+ * The grouping-refusal signature when no entry is refused (objectui#10583,
+ * objectui#10657): the authored grouping config is then handed on as it is.
+ */
+export const NO_GROUPING_REFUSAL = JSON.stringify({ refused: [], warned: [] });
diff --git a/ui/packages/plugin-grid/src/objectGridLinkCell.tsx b/ui/packages/plugin-grid/src/objectGridLinkCell.tsx
new file mode 100644
index 00000000000..d7cdeabbe01
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridLinkCell.tsx
@@ -0,0 +1,197 @@
+/**
+ * The record-link cell of `ObjectGrid` (`./ObjectGrid.tsx`): its class lists,
+ * the row's primary key, `LinkCell` and the `referenceVia` pointer face,
+ * moved out of that file verbatim (objectstack#25994, slice 1).
+ */
+
+import React from 'react';
+import { useRelatedRecordActions, RelatedRecordActionsProvider } from '@object-ui/react';
+import { resolveRecordPointer } from '@object-ui/fields';
+import { RecordPointerCell, type RecordPointerSource } from './RecordPointerCell';
+
+/**
+ * The class list both faces of {@link LinkCell} wear — the anchor is a visual
+ * no-op against the span it upgrades, so a list does not change appearance
+ * depending on whether its host publishes record URLs.
+ */
+
+const LINK_CELL_CLASS =
+  'text-primary font-medium underline-offset-4 hover:underline cursor-pointer truncate block max-w-full';
+
+/**
+ * The same list with the one-line clamp swapped for wrapping — what a cell in a
+ * column carrying an authored `wrap: true` wears (objectui#6650).
+ *
+ * ⭐ DERIVED from {@link LINK_CELL_CLASS} rather than written out, so the two
+ * cannot drift: every future edit to the link cell's appearance lands in both
+ * faces of both variants, and the no-wrap variant stays byte-identical to what
+ * `ObjectGrid.linkCellAnchor.test.tsx` pins as full markup.
+ *
+ * ⚠️ Why this exists at all — the outer read in `data-table.tsx` is NOT enough
+ * on its own. `data-table` puts the wrap/truncate decision on the cell BODY it
+ * owns, but a link column's content is this component, and its own `truncate`
+ * clamps the text back to one line INSIDE a body that is willing to wrap. So
+ * `wrap: true` on the record-link column — column one of almost every grid —
+ * would have rendered as silently nothing: the very failure mode this card
+ * exists to end, reproduced one element deeper. Measured, not reasoned: the
+ * end-to-end pin in `ObjectGrid.columnWrapForward.test.tsx` failed on exactly
+ * this, reading back `…cursor-pointer truncate block max-w-full` from a column
+ * authored `wrap: true`.
+ */
+const LINK_CELL_CLASS_WRAP = LINK_CELL_CLASS.replace('truncate', 'whitespace-normal break-words');
+
+/**
+ * A row's primary key — the value the host's record-URL builder addresses.
+ * Mirrors what `useNavigationOverlay.handleClick` reads off the same row, so
+ * the anchor's href and the click path can never point at different records.
+ */
+export function rowRecordId(row: unknown): string | number | undefined {
+  const rec = row as Record<string, unknown> | null | undefined;
+  const id = rec?.id ?? rec?._id;
+  return typeof id === 'string' || typeof id === 'number' ? id : undefined;
+}
+
+// Clickable text cell that can safely contain other interactive content
+// (e.g., EmailCellRenderer's copy button). Using <button> here would
+// produce an invalid <button> > <button> nesting (hydration error +
+// breaks the inner copy click). role="link" + tabIndex + keyboard
+// handlers preserves accessibility while allowing arbitrary children.
+//
+// objectui#4490 — that span was the whole cell, so the list's link column had
+// none of a link's native affordances: no middle-click / ⌘-click open-in-new-
+// tab, no "copy link address", no hover status-bar URL, and `role="link"` with
+// no `href` is a weaker contract for assistive tech than a real anchor. PR
+// #4489 had just given detail-page and related-list lookup VALUES real anchors,
+// which left the list — the surface users open records from — as the weakest of
+// the three.
+//
+// So when the host publishes a record URL this renders a real `<a href>`, with
+// the split #4489 established:
+//   - plain left click → `preventDefault()` + the existing `onActivate`, so SPA
+//     navigation (drawer / modal / page, whatever the view configured) is
+//     completely unchanged;
+//   - modifier / non-primary click → NOT prevented, so the browser does what it
+//     does with any link.
+//
+// **The URL is not built here.** This package has no router and no business
+// knowing what a record route looks like; the host publishes its own builder
+// through `RelatedRecordActionsContext.recordHref` — the same seam #4489 used,
+// and for the console list surface the same builder its "open in new window"
+// action already navigates with. No host, or a host that cannot route to this
+// object, renders EXACTLY the span below: same markup, same behavior, nothing
+// to un-learn (the Studio designer, embedded renderers, standalone grids).
+export const LinkCell: React.FC<{
+  testId: string;
+  onActivate: () => void;
+  /** Object whose record this row is — passed to the host's URL builder. */
+  objectName?: string;
+  /** This row's primary key. Absent (a row with no id) ⇒ no anchor. */
+  recordId?: string | number | null;
+  /**
+   * The column's authored `wrap` (objectui#6650). `true` ⇒ this cell drops its
+   * one-line clamp so long link text flows onto further lines, matching what
+   * `data-table` does to the body around it. Absent / `false` ⇒ unchanged.
+   */
+  wrap?: boolean;
+  children: React.ReactNode;
+}> = ({ testId, onActivate, objectName, recordId, wrap, children }) => {
+  const host = useRelatedRecordActions();
+  const cellClass = wrap ? LINK_CELL_CLASS_WRAP : LINK_CELL_CLASS;
+  const href =
+    objectName && recordId != null && recordId !== '' && host?.recordHref
+      ? host.recordHref(objectName, recordId)
+      : null;
+
+  if (href && host) {
+    // objectui#11817 — no anchor inside this anchor. A reference value in the
+    // cell (`LookupCellRenderer`'s `ReferencedRecordLink`) draws its own `a`
+    // whenever the host answers `recordHref` for the referenced object, so the
+    // children are rendered under the same host with no record destination:
+    // "the host cannot route to that object", which the context documents as
+    // render the plain value. The self-linking faces (`mailto:`, URL, `tel:`)
+    // never ask the host; the cell is handed their text face instead
+    // (`linkCellRenderer` in `./cellRendererResolution`).
+    const unlinkedHost = { ...host, recordHref: undefined, openRecord: undefined };
+    return (
+      <a
+        href={href}
+        data-testid={testId}
+        className={cellClass}
+        onClick={(e) => {
+          // The row underneath carries its own click handler (open the record,
+          // and on a modifier click open it in a new tab). Following this link
+          // must never ALSO fire that — on a modifier click that would open two
+          // tabs, one from the anchor and one from the row.
+          e.stopPropagation();
+          // Modifier and non-primary clicks belong to the browser (new tab, new
+          // window) — that is the entire point of rendering a real href.
+          if (e.metaKey || e.ctrlKey || e.shiftKey || e.altKey || e.button !== 0) return;
+          e.preventDefault();
+          onActivate();
+        }}
+        onKeyDown={(e) => {
+          // Enter is the anchor's OWN activation: the browser fires a click for
+          // it, which the handler above turns into the SPA path. Handling it
+          // here too would activate twice. Space is the one the span had that a
+          // link does not do natively, so it is carried over explicitly.
+          if (e.key === ' ') {
+            e.preventDefault();
+            e.stopPropagation();
+            onActivate();
+          }
+        }}
+      >
+        <RelatedRecordActionsProvider value={unlinkedHost}>{children}</RelatedRecordActionsProvider>
+      </a>
+    );
+  }
+
+  return (
+    <span
+      role="link"
+      tabIndex={0}
+      data-testid={testId}
+      className={cellClass}
+      onClick={(e) => {
+        e.stopPropagation();
+        onActivate();
+      }}
+      onKeyDown={(e) => {
+        if (e.key === 'Enter' || e.key === ' ') {
+          e.preventDefault();
+          e.stopPropagation();
+          onActivate();
+        }
+      }}
+    >
+      {children}
+    </span>
+  );
+};
+
+/**
+ * objectui#12608 — the face a `referenceVia` pointer column draws its rows
+ * with, or `null` when the field declares no pointer pair.
+ *
+ * The pair is resolved per row by `resolveRecordPointer` (`@object-ui/fields`),
+ * the one rule the record details grid asks too; `referenceVia` is read off the
+ * OBJECT field, where the spec declares it, and the type is the column's
+ * declared one, so a view that re-types the column keeps its own face. A row
+ * the rule answers `null` for (a half-addressed pair) is drawn by the column's
+ * ordinary face: the returned function answers `null` and the caller falls
+ * through to it. Inside a link cell the face is drawn under `LinkCell`'s
+ * unlinked host, so it draws the name without a second anchor.
+ */
+export function recordPointerFace(
+  fieldName: string,
+  declaredType: string | null,
+  fieldDef: { referenceVia?: unknown } | null | undefined,
+  dataSource: RecordPointerSource | null | undefined,
+): ((row: any) => React.ReactElement | null) | null {
+  const referenceVia = fieldDef?.referenceVia;
+  if (typeof referenceVia !== 'string' || referenceVia === '') return null;
+  return (row: any) => {
+    const pointer = resolveRecordPointer({ name: fieldName, type: declaredType, referenceVia }, row);
+    return pointer ? <RecordPointerCell pointer={pointer} dataSource={dataSource} /> : null;
+  };
+}
diff --git a/ui/packages/plugin-grid/src/objectGridQuery.ts b/ui/packages/plugin-grid/src/objectGridQuery.ts
new file mode 100644
index 00000000000..d252fddf167
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridQuery.ts
@@ -0,0 +1,150 @@
+/**
+ * The query helpers of `ObjectGrid` (`./ObjectGrid.tsx`): the held resolution
+ * of the node's own filter, the record-source ladder and the find-params
+ * signature, moved out of that file verbatim (objectstack#25994, slice 1).
+ */
+
+import { useState } from 'react';
+import type { ObjectGridSchema, ViewData } from '@object-ui/types';
+import { isSameAuthoredFilter } from '@object-ui/react';
+import { resolveRecordSourceConfig, resolveFilterPlaceholders, type FilterTokenScope } from '@object-ui/core';
+
+/**
+ * The node's own authored filter: the canonical `filter`. Its deprecated alias
+ * `defaultFilters` is not read: `@objectstack/spec` 18 retired it as a
+ * tombstone that refuses by name (objectstack#11509), and the alias read went
+ * with it (objectui#12030).
+ */
+interface AuthoredGridFilters {
+  filter: ObjectGridSchema['filter'];
+}
+
+/** One resolution, remembered with the inputs it was computed from. */
+interface HeldGridFilters {
+  authored: AuthoredGridFilters;
+  currentUserId: FilterTokenScope['currentUserId'];
+  currentOrgId: FilterTokenScope['currentOrgId'];
+  recordId: FilterTokenScope['recordId'];
+  onUnresolved: FilterTokenScope['onUnresolved'];
+  resolved: AuthoredGridFilters;
+}
+
+function resolveGridFilters(authored: AuthoredGridFilters, scope: FilterTokenScope): HeldGridFilters {
+  return {
+    authored,
+    currentUserId: scope.currentUserId,
+    currentOrgId: scope.currentOrgId,
+    recordId: scope.recordId,
+    onUnresolved: scope.onUnresolved,
+    resolved: resolveFilterPlaceholders(authored, scope),
+  };
+}
+
+/**
+ * objectui#10607 — resolve the node's own filter ONCE, through
+ * `@object-ui/core`'s shared `resolveFilterPlaceholders`, against the session
+ * scope the host provides (`useFilterScope`). Before this, a directly authored
+ * `object-grid` with `filter: [['owner', '=', '{current_user_id}']]` sent the
+ * literal token on `$filter`. `object-view` already resolves the filters it
+ * hands this grid (objectui#10506); resolving that value again changes
+ * nothing, because a resolved id no longer matches the whole-token pattern.
+ *
+ * ⛔ Not a second resolver, and no fallback: a token the scope cannot resolve
+ * is whatever `resolveFilterPlaceholders` makes of it (left intact, with one
+ * warning naming it).
+ *
+ * The result is HELD against its inputs, the shape `plugin-view`'s
+ * `useResolvedFilterSegments` uses. The load effect keys on the filter this
+ * grid lowers, so a resolved copy minted on every render would refetch on
+ * every render; and a date macro such as `{now}` resolves to a new value at
+ * every call, so comparing OUTPUTS cannot stop that. The key is the authored
+ * filters, compared by structure (a host that rebuilds an equal filter inline
+ * must not re-query), plus each scope member read one by one (`recordId`
+ * among them, objectui#7297), never the scope object's identity (AGENTS.md
+ * #10). The held pair lives in state,
+ * so the value handed out is always the one React committed.
+ */
+export function useResolvedGridFilters(authored: AuthoredGridFilters, scope: FilterTokenScope): AuthoredGridFilters {
+  const [held, setHeld] = useState(() => resolveGridFilters(authored, scope));
+  if (
+    held.currentUserId !== scope.currentUserId
+    || held.currentOrgId !== scope.currentOrgId
+    || held.recordId !== scope.recordId
+    || held.onUnresolved !== scope.onUnresolved
+    || !isSameAuthoredFilter(held.authored, authored)
+  ) {
+    // React's documented "information from previous renders" shape: a set
+    // during render re-renders this component at once, before any child sees
+    // the discarded pass, and the re-render finds the inputs equal.
+    const next = resolveGridFilters(authored, scope);
+    setHeld(next);
+    return next.resolved;
+  }
+  return held.resolved;
+}
+
+/**
+ * Helper to get data configuration from schema.
+ *
+ * The ruled three-rung ladder itself (`data`, then `staticData`, then
+ * `objectName`) is `resolveRecordSourceConfig` in `@object-ui/core` — ONE
+ * implementation of a contract published on both faces (`77cb489b4`), which
+ * this file used to hand-copy (`ce2aaefe1`).
+ *
+ * What used to stay here was the head above it: the bare-array `data`
+ * shorthand, which lifted `data: [...]` to `{ provider: 'value', items }`.
+ * ⛔ IT IS GONE (objectui#8348, decision batch #83, maintainer verbatim
+ * 「8348 以协议为准」 — the contract decides).
+ *
+ * MEASURED on `@objectstack/spec` 17.4.0:
+ * `ComponentPropsMap['object-grid'].data` is the `ViewData` union, and its own
+ * description names the refusal — *"Static inline rows live at
+ * `{ provider: 'value', items: [...] }`; the bare-array shortcut is refused —
+ * see migration `object-grid-data-view-data-converged`"*. This block's own
+ * registration publishes the same arm (`{ name: 'data', type: 'object' }` in
+ * `index.tsx`), and `gridDataInputContract.test.ts` has pinned that declaration
+ * since objectui#5090. The head was the last carrier of a spelling every one of
+ * those faces refuses, so `data` is honoured here on the OBJECT arm only and
+ * the shared rung is passed `'view-data'`.
+ *
+ * ⛔ WHAT THIS REACHES, measured per CARRIER — do NOT read it as "the array is
+ * gone". An authored `data` array reaches this component TWICE: as
+ * `schema.data`, which this function used to lift, and as the `data` PROP,
+ * because `SchemaRenderer` spreads every non-metadata node key and
+ * `index.tsx` forwards `{...rest}`. That prop is `passedData` below, and it
+ * lifts an array to `{ provider: 'value', items }` at HIGHER priority than this
+ * ladder — it is the channel a host such as `ListView` uses to hand down rows it
+ * already fetched, and it is indistinguishable here from an authored key.
+ *
+ * ⇒ at the ladder the array is no longer a record source; through
+ * `SchemaRenderer` an authored `data: [ …rows… ]` still draws, from the props
+ * channel. Both halves are pinned in
+ * `__tests__/gridBareArrayDataRefused-8348.test.tsx`, which had to correct its
+ * own first draft on exactly this point. Collapsing the two carriers would take
+ * the host path with it and is outside objectui#8348's scope — reported on the
+ * card, not changed in passing.
+ *
+ * The declared spelling for inline rows is
+ * `data: { provider: 'value', items: [...] }`, and the deprecated `staticData`
+ * array still works as before.
+ */
+export function getDataConfig(schema: ObjectGridSchema): ViewData | null {
+  return resolveRecordSourceConfig(schema, 'view-data');
+}
+
+/**
+ * Content signature of a host's find-params, used as the query-change signal for
+ * the cross-page escalation (objectui#4501 clause 2).
+ *
+ * CONTENT and not identity: a host re-render that rebuilds an equal params
+ * object must not drop an escalation the user just made, and identity is the
+ * one thing a host cannot be relied on to keep stable. Top-level keys are
+ * sorted so key ORDER — which differs between the host's literal and this
+ * grid's own loader — never reads as a query change.
+ */
+export function findParamsSignature(params: Record<string, unknown> | null | undefined): string | null {
+  if (!params) return null;
+  return JSON.stringify(
+    Object.keys(params).sort().map((k) => [k, params[k] ?? null]),
+  );
+}
diff --git a/ui/packages/plugin-grid/src/objectGridRowVersion.ts b/ui/packages/plugin-grid/src/objectGridRowVersion.ts
new file mode 100644
index 00000000000..371f78527d1
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridRowVersion.ts
@@ -0,0 +1,65 @@
+/**
+ * The optimistic-concurrency helpers of `ObjectGrid` (`./ObjectGrid.tsx`): the
+ * row's version token, the version a row save sends, and the conflict and
+ * batch-save outcome types, moved out of that file verbatim
+ * (objectstack#25994, slice 1).
+ */
+
+import type { DataTableSchema } from '@object-ui/types';
+
+/**
+ * The row key that carries a record's optimistic-concurrency token
+ * (objectui#12292): `updated_at`, the key the record surfaces send as
+ * `If-Match`.
+ */
+export const OCC_TOKEN_FIELD = 'updated_at';
+
+/**
+ * The concurrency token a row carries, read exactly as the record surfaces read
+ * it (`occVersionOf` in `plugin-form`, the save in `plugin-detail`'s
+ * `InlineEditSaveBar`): a non-empty string `updated_at`. Anything else (a
+ * backend without timestamps, a row read without the column) answers
+ * `undefined`, and the write goes out unguarded, as it did before.
+ */
+export function rowVersionOf(row: unknown): string | undefined {
+  const v = (row as Record<string, unknown> | null | undefined)?.[OCC_TOKEN_FIELD];
+  return typeof v === 'string' && v.length > 0 ? v : undefined;
+}
+
+/** What this grid remembers about its last landed write to one record. */
+export interface WrittenRowVersion {
+  /** The token the row carried when that write was made: the read it superseded. */
+  readVersion: string;
+  /** The token of the record the server answered that write with. */
+  version: string;
+}
+
+/**
+ * The `ifMatch` a row save sends: the rule `plugin-form`'s `versionToSend`
+ * applies to a form that stays open (objectui#10565), applied to a row.
+ *
+ * A saved row keeps the token it was READ with until the grid re-reads it, and
+ * that token stopped being current the moment this grid's own write landed. So
+ * while the row still carries the read a landed write superseded, the version
+ * that write answered with is sent. A row carrying any other token is a newer
+ * read, and its token wins. A row with no token stays unguarded.
+ */
+export function rowVersionToSend(
+  written: WrittenRowVersion | undefined,
+  readVersion: string | undefined,
+): string | undefined {
+  if (!readVersion) return undefined;
+  return written && written.readVersion === readVersion ? written.version : readVersion;
+}
+
+/** The three ways out of `ConcurrentUpdateDialog`, by its own button names. */
+export type RowConflictChoice = 'reload' | 'overwrite' | 'cancel';
+
+/**
+ * The per-row outcome the table's `onBatchSave` slot reads, derived from the
+ * slot's declared return rather than restated here.
+ */
+export type BatchSaveOutcome = Exclude<
+  Awaited<ReturnType<NonNullable<DataTableSchema['onBatchSave']>>>,
+  void
+>;
diff --git a/ui/packages/plugin-grid/src/objectGridTranslations.ts b/ui/packages/plugin-grid/src/objectGridTranslations.ts
new file mode 100644
index 00000000000..c2b2b0fb625
--- /dev/null
+++ b/ui/packages/plugin-grid/src/objectGridTranslations.ts
@@ -0,0 +1,93 @@
+/**
+ * The English fallback translations of `ObjectGrid` (`./ObjectGrid.tsx`) and
+ * the safe translation hook built on them, moved out of that file verbatim
+ * (objectstack#25994, slice 1).
+ */
+
+import { createSafeTranslation } from '@object-ui/i18n';
+
+// Default English fallback translations for the grid
+const GRID_DEFAULT_TRANSLATIONS: Record<string, string> = {
+  'grid.actions': 'Actions',
+  'grid.edit': 'Edit',
+  'grid.delete': 'Delete',
+  'grid.export': 'Export',
+  'grid.exportAs': 'Export as {{format}}',
+  'grid.loading': 'Loading grid…',
+  'grid.errorLoading': 'Error loading grid',
+  // objectui#9050 — the malformed-filter state, shared with `RelatedList`
+  // and `LineItemsPanel` because it is one sentence about one authored
+  // value, not three. Byte-identical to the `en` pack, which
+  // `defaults-maps-mirror-en-pack` enforces.
+  'view.malformedFilter': 'This view’s filter is malformed, so no records are shown: the {{subject}} condition cannot be applied.',
+  'grid.pullToRefresh': 'Pull to refresh',
+  'grid.refreshing': 'Refreshing…',
+  'grid.openRecord': 'Open record',
+  'grid.empty': 'Empty',
+  'grid.yes': 'Yes',
+  'grid.no': 'No',
+  'grid.systemFields': 'System',
+  // The grouped grid's refusal over a data source that cannot answer the
+  // group header query (objectui#10881, ruling F). It must exist HERE as well
+  // as in the locale packs: a provider-less host (a standalone grid, this
+  // package's own tests) never reaches them, and it is the only thing such a
+  // grid draws.
+  'grid.grouping.needsHeaderQuery':
+    'This view is grouped, but its data source does not implement queryGroupHeaders, so the groups cannot be counted. Remove the grouping to show the records.',
+  // …and over rows a host handed in while declaring them one page of more.
+  'grid.grouping.needsWholeRows':
+    'Grouping needs every record, but this grid was handed one page of them, so the groups cannot be counted. Hand in every record, or let the grid fetch them from a data source that implements queryGroupHeaders.',
+  // Reused by the grouped-view pager (falls back here when no I18nProvider).
+  'table.rowsPerPage': 'Rows per page',
+  'table.pageInfo': 'Page {{current}} of {{total}}',
+  // The grouped-view pager's four icon buttons are named by these
+  // (objectui#12143): the `data-table` pager's own keys, objectui#12124.
+  'table.firstPage': 'First page',
+  'table.previousPage': 'Previous page',
+  'table.nextPage': 'Next page',
+  'table.lastPage': 'Last page',
+  // The default inline-edit saves' success toast (objectui#12303), counted in
+  // the rows the server accepted — the `table.modified` unit the table's
+  // "Save All" bar counts in.
+  'table.saved': '{{count}} row saved',
+  'table.saved_one': '{{count}} row saved',
+  'table.saved_other': '{{count}} rows saved',
+  // The heading of an authored `emptyState` that declares no `title`
+  // (objectui#11068): the words the table's own empty row shows, so leaving the
+  // member out changes nothing a user reads.
+  'table.noResults': 'No results found',
+  // The empty state an empty grid draws when no authored `emptyState` and no
+  // search term are in force (objectui#13142). Borrowed from the `list.*`
+  // namespace `ListEmptyState` reads, so a grid and a list say the same thing
+  // about the same empty object; the rows exist HERE too for a provider-less
+  // host.
+  'list.firstRunTitle': 'Nothing here yet',
+  'list.firstRunMessage': 'Create your first record to get started.',
+  'list.noMatches': 'No matching records',
+  'list.viewFilterNoMatchesMessage': 'No records match this view’s filter.',
+  // objectstack#25898 — a grid filtered to the signed-in user, and an
+  // unfiltered grid for a caller who may not create (`ListEmptyState` says
+  // both in the same words).
+  'list.ownedNoneTitle': 'Nothing of yours yet',
+  'list.ownedNoneMessage': 'This view lists only records that are yours, and you don’t have any yet.',
+  'list.noneVisibleTitle': 'No records you can see',
+  'list.noneVisibleMessage': 'There are no records here that you have access to. If you expected to see some, ask your administrator for access.',
+  // Heading of the record-detail overlay this grid opens on row click
+  // (objectui#3426). Borrowed from the `detail.*` namespace rather than minted
+  // as `grid.recordDetail`: `NavigationOverlay` already resolves
+  // `detail.recordDetail` for hosts that pass no title, and one heading on one
+  // control should not get two translations that can drift apart. Both entries
+  // must exist HERE too — a provider-less host (a standalone grid, this
+  // package's own tests) never reaches the locale packs.
+  'detail.recordDetail': 'Record Detail',
+  'detail.recordDetailWithLabel': '{{label}} Detail',
+};
+
+/**
+ * Safe wrapper for useObjectTranslation that falls back to English defaults
+ * when I18nProvider is not available (e.g., standalone usage).
+ *
+ * Delegates to `@object-ui/i18n`'s `createSafeTranslation`; the local copy this
+ * replaced wrapped the hook in try/catch (rules-of-hooks, objectui#2879).
+ */
+export const useGridTranslation = createSafeTranslation(GRID_DEFAULT_TRANSLATIONS, 'grid.actions');

From fe3087e523932a0ebc1f6de9be237e0ca43dd735 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 26 Oct 2026 20:39:29 +0000
Subject: [PATCH 2/4] chore(plugin-grid): changeset and re-recorded sdui source
 record for the ObjectGrid helpers split
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The registry artefact is byte-identical (sha256 1f6e1ccb…); only plugin-grid's
source digest moves, because six new source files joined the package.

Claude-Session: https://claude.ai/code/session_01Bdrd2yH4eqnz2QobtN3haE
Co-authored-by: Claude <noreply@anthropic.com>
---
 .changeset/25994-objectgrid-helpers-split.md   | 12 ++++++++++++
 scripts/sdui-manifest.sources/plugin-grid.json |  2 +-
 2 files changed, 13 insertions(+), 1 deletion(-)
 create mode 100644 .changeset/25994-objectgrid-helpers-split.md

diff --git a/.changeset/25994-objectgrid-helpers-split.md b/.changeset/25994-objectgrid-helpers-split.md
new file mode 100644
index 00000000000..ac43043e80e
--- /dev/null
+++ b/.changeset/25994-objectgrid-helpers-split.md
@@ -0,0 +1,12 @@
+---
+'@object-ui/plugin-grid': patch
+---
+
+refactor(plugin-grid): `ObjectGrid`'s module-level helpers move into sibling modules
+
+Clause-②: no
+Metadata-protocol: none
+
+The query helpers (the held filter resolution, the record-source ladder, the find-params signature), the column helpers and column emit types, the record-link cell, the English fallback translations, the display defaults (row height, page sizes, selection default) and the row-version helpers move verbatim out of `ObjectGrid.tsx` into six modules beside it. No logic, name or rendered output changes. `ObjectGrid.tsx` re-exports every name it exported before, and the package entry is unchanged.
+
+What to do: nothing.
diff --git a/scripts/sdui-manifest.sources/plugin-grid.json b/scripts/sdui-manifest.sources/plugin-grid.json
index 8e53b237242..e1a14d9eeef 100644
--- a/scripts/sdui-manifest.sources/plugin-grid.json
+++ b/scripts/sdui-manifest.sources/plugin-grid.json
@@ -1 +1 @@
-{"package":"ui/packages/plugin-grid","sources":38,"sha256":"f6f7b1cbd89a1536a6e33febf4db131b8d526bd7281be460c401dccb8e97876a","manifestSha256":"1f6e1ccb925a678eaa393f9091dfc7d0285e4e3626e0a5c61a5474687debabb7"}
+{"package":"ui/packages/plugin-grid","sources":44,"sha256":"741fd0858975aa0a51960b9a7c18a79d6e0ddced65f6b1310eea491eeb3c807b","manifestSha256":"1f6e1ccb925a678eaa393f9091dfc7d0285e4e3626e0a5c61a5474687debabb7"}

From 2978029b0a9a45eab3ce2673a0cef9a300abe5d6 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 26 Oct 2026 21:15:27 +0000
Subject: [PATCH 3/4] refactor(plugin-grid): keep getDataConfig file-local in
 ObjectGrid.tsx

Exported from objectGridQuery.ts, it became a shared reader for
check:doc-example-readers, which then flagged the @example in
core's record-source.ts. Left where it was, unexported, the gate reads
the tree exactly as on main. Still move-only.

Claude-Session: https://claude.ai/code/session_01Bdrd2yH4eqnz2QobtN3haE
Co-authored-by: Claude <noreply@anthropic.com>
---
 ui/packages/plugin-grid/src/ObjectGrid.tsx    | 55 +++++++++++++++++-
 .../plugin-grid/src/objectGridQuery.ts        | 57 ++-----------------
 2 files changed, 56 insertions(+), 56 deletions(-)

diff --git a/ui/packages/plugin-grid/src/ObjectGrid.tsx b/ui/packages/plugin-grid/src/ObjectGrid.tsx
index 3a2a15c7e08..af84f5662ee 100644
--- a/ui/packages/plugin-grid/src/ObjectGrid.tsx
+++ b/ui/packages/plugin-grid/src/ObjectGrid.tsx
@@ -22,7 +22,7 @@
  */
 
 import React, { useEffect, useState, useCallback, useMemo } from 'react';
-import type { ObjectGridSchema, DataSource, DependsOnInput, ListColumn, TableSortItem, DataTableSchema, ListViewExportFormat, RecordNavigateAction } from '@object-ui/types';
+import type { ObjectGridSchema, DataSource, DependsOnInput, ListColumn, ViewData, TableSortItem, DataTableSchema, ListViewExportFormat, RecordNavigateAction } from '@object-ui/types';
 import { isSystemManagedField, normalizeTableColumnType } from '@object-ui/types';
 import { parseFilterAST, resolveFieldScale, type FilterCondition } from '@objectstack/spec/data';
 import { SchemaRenderer, useDataScope, useNavigationOverlay, useAction, useSafeFieldLabel, usePredicateScope, useCapabilityGate, useDataInvalidation, notifyDataChanged, useFilterScope, useMetadata } from '@object-ui/react';
@@ -58,7 +58,7 @@ import {
   toast,
 } from '@object-ui/components';
 import { usePullToRefresh } from '@object-ui/mobile';
-import { resolveConditionalFormatting, resolveDependsOnFields, isDeadlineSettled, leadWithNameField, declaredNameField, buildExpandFields, buildExportFileName, columnIdentity, collectPredicateFieldRefs, collectGroupingFieldRefs, listViewPredicates, resolveAffordance, resolveFieldAffordance, type SchemaLike, isProjectableField, isExpandableFieldType, isUnmaterializedFieldType, readObjectSortability, isPlatformSortableField, filterPlatformSortableSort, toFilterNodeSafely, filterRefusalSubject, FilterOperatorError, convertSortToQueryParams, normalizeSortEntries, type QuerySortEntry, resolveRecordSourceObjectName, partitionRowsByPredicate, buildCategoryOrder, buildCategoryRank, toDisplayDate } from '@object-ui/core';
+import { resolveConditionalFormatting, resolveDependsOnFields, isDeadlineSettled, leadWithNameField, declaredNameField, buildExpandFields, buildExportFileName, columnIdentity, collectPredicateFieldRefs, collectGroupingFieldRefs, listViewPredicates, resolveAffordance, resolveFieldAffordance, type SchemaLike, isProjectableField, isExpandableFieldType, isUnmaterializedFieldType, readObjectSortability, isPlatformSortableField, filterPlatformSortableSort, toFilterNodeSafely, filterRefusalSubject, FilterOperatorError, convertSortToQueryParams, normalizeSortEntries, type QuerySortEntry, resolveRecordSourceConfig, resolveRecordSourceObjectName, partitionRowsByPredicate, buildCategoryOrder, buildCategoryRank, toDisplayDate } from '@object-ui/core';
 import { usePermissions } from '@object-ui/permissions';
 import {
   RECORD_OVERLAY_DEFAULT_WIDTH,
@@ -87,7 +87,7 @@ import { BulkActionBar } from './components/BulkActionBar';
 import { BulkActionDialog } from './components/BulkActionDialog';
 import type { BulkResult } from './hooks/useBulkExecutor';
 import type { BulkActionDef } from '@object-ui/types';
-import { findParamsSignature, getDataConfig, useResolvedGridFilters } from './objectGridQuery';
+import { findParamsSignature, useResolvedGridFilters } from './objectGridQuery';
 import { type ObjectGridColumn, type ObjectGridColumnDraft, isChipFieldType, normalizeColumns, resolveColumnLabel } from './objectGridColumns';
 import { LinkCell, recordPointerFace, rowRecordId } from './objectGridLinkCell';
 import { useGridTranslation } from './objectGridTranslations';
@@ -463,6 +463,55 @@ export interface ObjectGridComponentProps extends ObjectGridExternalPaginationPr
   onAddRecord?: () => void;
 }
 
+/**
+ * Helper to get data configuration from schema.
+ *
+ * The ruled three-rung ladder itself (`data`, then `staticData`, then
+ * `objectName`) is `resolveRecordSourceConfig` in `@object-ui/core` — ONE
+ * implementation of a contract published on both faces (`77cb489b4`), which
+ * this file used to hand-copy (`ce2aaefe1`).
+ *
+ * What used to stay here was the head above it: the bare-array `data`
+ * shorthand, which lifted `data: [...]` to `{ provider: 'value', items }`.
+ * ⛔ IT IS GONE (objectui#8348, decision batch #83, maintainer verbatim
+ * 「8348 以协议为准」 — the contract decides).
+ *
+ * MEASURED on `@objectstack/spec` 17.4.0:
+ * `ComponentPropsMap['object-grid'].data` is the `ViewData` union, and its own
+ * description names the refusal — *"Static inline rows live at
+ * `{ provider: 'value', items: [...] }`; the bare-array shortcut is refused —
+ * see migration `object-grid-data-view-data-converged`"*. This block's own
+ * registration publishes the same arm (`{ name: 'data', type: 'object' }` in
+ * `index.tsx`), and `gridDataInputContract.test.ts` has pinned that declaration
+ * since objectui#5090. The head was the last carrier of a spelling every one of
+ * those faces refuses, so `data` is honoured here on the OBJECT arm only and
+ * the shared rung is passed `'view-data'`.
+ *
+ * ⛔ WHAT THIS REACHES, measured per CARRIER — do NOT read it as "the array is
+ * gone". An authored `data` array reaches this component TWICE: as
+ * `schema.data`, which this function used to lift, and as the `data` PROP,
+ * because `SchemaRenderer` spreads every non-metadata node key and
+ * `index.tsx` forwards `{...rest}`. That prop is `passedData` below, and it
+ * lifts an array to `{ provider: 'value', items }` at HIGHER priority than this
+ * ladder — it is the channel a host such as `ListView` uses to hand down rows it
+ * already fetched, and it is indistinguishable here from an authored key.
+ *
+ * ⇒ at the ladder the array is no longer a record source; through
+ * `SchemaRenderer` an authored `data: [ …rows… ]` still draws, from the props
+ * channel. Both halves are pinned in
+ * `__tests__/gridBareArrayDataRefused-8348.test.tsx`, which had to correct its
+ * own first draft on exactly this point. Collapsing the two carriers would take
+ * the host path with it and is outside objectui#8348's scope — reported on the
+ * card, not changed in passing.
+ *
+ * The declared spelling for inline rows is
+ * `data: { provider: 'value', items: [...] }`, and the deprecated `staticData`
+ * array still works as before.
+ */
+function getDataConfig(schema: ObjectGridSchema): ViewData | null {
+  return resolveRecordSourceConfig(schema, 'view-data');
+}
+
 /**
  * The relational copy set and `applyRelationalMeta` moved to
  * `./relationalMetaKeys` for objectui#6875. The list there is DERIVED from a
diff --git a/ui/packages/plugin-grid/src/objectGridQuery.ts b/ui/packages/plugin-grid/src/objectGridQuery.ts
index d252fddf167..50f6bf8a1ad 100644
--- a/ui/packages/plugin-grid/src/objectGridQuery.ts
+++ b/ui/packages/plugin-grid/src/objectGridQuery.ts
@@ -1,13 +1,13 @@
 /**
  * The query helpers of `ObjectGrid` (`./ObjectGrid.tsx`): the held resolution
- * of the node's own filter, the record-source ladder and the find-params
- * signature, moved out of that file verbatim (objectstack#25994, slice 1).
+ * of the node's own filter and the find-params signature, moved out of that
+ * file verbatim (objectstack#25994, slice 1).
  */
 
 import { useState } from 'react';
-import type { ObjectGridSchema, ViewData } from '@object-ui/types';
+import type { ObjectGridSchema } from '@object-ui/types';
 import { isSameAuthoredFilter } from '@object-ui/react';
-import { resolveRecordSourceConfig, resolveFilterPlaceholders, type FilterTokenScope } from '@object-ui/core';
+import { resolveFilterPlaceholders, type FilterTokenScope } from '@object-ui/core';
 
 /**
  * The node's own authored filter: the canonical `filter`. Its deprecated alias
@@ -83,55 +83,6 @@ export function useResolvedGridFilters(authored: AuthoredGridFilters, scope: Fil
   return held.resolved;
 }
 
-/**
- * Helper to get data configuration from schema.
- *
- * The ruled three-rung ladder itself (`data`, then `staticData`, then
- * `objectName`) is `resolveRecordSourceConfig` in `@object-ui/core` — ONE
- * implementation of a contract published on both faces (`77cb489b4`), which
- * this file used to hand-copy (`ce2aaefe1`).
- *
- * What used to stay here was the head above it: the bare-array `data`
- * shorthand, which lifted `data: [...]` to `{ provider: 'value', items }`.
- * ⛔ IT IS GONE (objectui#8348, decision batch #83, maintainer verbatim
- * 「8348 以协议为准」 — the contract decides).
- *
- * MEASURED on `@objectstack/spec` 17.4.0:
- * `ComponentPropsMap['object-grid'].data` is the `ViewData` union, and its own
- * description names the refusal — *"Static inline rows live at
- * `{ provider: 'value', items: [...] }`; the bare-array shortcut is refused —
- * see migration `object-grid-data-view-data-converged`"*. This block's own
- * registration publishes the same arm (`{ name: 'data', type: 'object' }` in
- * `index.tsx`), and `gridDataInputContract.test.ts` has pinned that declaration
- * since objectui#5090. The head was the last carrier of a spelling every one of
- * those faces refuses, so `data` is honoured here on the OBJECT arm only and
- * the shared rung is passed `'view-data'`.
- *
- * ⛔ WHAT THIS REACHES, measured per CARRIER — do NOT read it as "the array is
- * gone". An authored `data` array reaches this component TWICE: as
- * `schema.data`, which this function used to lift, and as the `data` PROP,
- * because `SchemaRenderer` spreads every non-metadata node key and
- * `index.tsx` forwards `{...rest}`. That prop is `passedData` below, and it
- * lifts an array to `{ provider: 'value', items }` at HIGHER priority than this
- * ladder — it is the channel a host such as `ListView` uses to hand down rows it
- * already fetched, and it is indistinguishable here from an authored key.
- *
- * ⇒ at the ladder the array is no longer a record source; through
- * `SchemaRenderer` an authored `data: [ …rows… ]` still draws, from the props
- * channel. Both halves are pinned in
- * `__tests__/gridBareArrayDataRefused-8348.test.tsx`, which had to correct its
- * own first draft on exactly this point. Collapsing the two carriers would take
- * the host path with it and is outside objectui#8348's scope — reported on the
- * card, not changed in passing.
- *
- * The declared spelling for inline rows is
- * `data: { provider: 'value', items: [...] }`, and the deprecated `staticData`
- * array still works as before.
- */
-export function getDataConfig(schema: ObjectGridSchema): ViewData | null {
-  return resolveRecordSourceConfig(schema, 'view-data');
-}
-
 /**
  * Content signature of a host's find-params, used as the query-change signal for
  * the cross-page escalation (objectui#4501 clause 2).

From 8fe81ee965af51bf0a63fff3f03c227eb8872cbe Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Mon, 26 Oct 2026 21:27:55 +0000
Subject: [PATCH 4/4] chore(plugin-grid): re-record plugin-grid's sdui source
 digest after keeping getDataConfig in place

Claude-Session: https://claude.ai/code/session_01Bdrd2yH4eqnz2QobtN3haE
Co-authored-by: Claude <noreply@anthropic.com>
---
 scripts/sdui-manifest.sources/plugin-grid.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/sdui-manifest.sources/plugin-grid.json b/scripts/sdui-manifest.sources/plugin-grid.json
index e1a14d9eeef..be3fa2493dc 100644
--- a/scripts/sdui-manifest.sources/plugin-grid.json
+++ b/scripts/sdui-manifest.sources/plugin-grid.json
@@ -1 +1 @@
-{"package":"ui/packages/plugin-grid","sources":44,"sha256":"741fd0858975aa0a51960b9a7c18a79d6e0ddced65f6b1310eea491eeb3c807b","manifestSha256":"1f6e1ccb925a678eaa393f9091dfc7d0285e4e3626e0a5c61a5474687debabb7"}
+{"package":"ui/packages/plugin-grid","sources":44,"sha256":"afbc05964d76c725b0d533f1bd28b1515591d0748eca468158f64fc3bb7f7a80","manifestSha256":"1f6e1ccb925a678eaa393f9091dfc7d0285e4e3626e0a5c61a5474687debabb7"}