@object-ui/core 17.7.0 → 18.0.0

package/dist/utils/chart-series.js

@@ -53,6 +53,22 @@ import { pivotBucketId, pivotDimensionValue } from './dataset-pivot.js';
  * and {@link resolveMeasureLabel} treats it as absent.
  */
 export const BUILTIN_AGGREGATES = ['count', 'sum', 'avg', 'min', 'max', 'count_distinct'];
+/**
+ * The aggregates whose every value is a whole number: a count of rows, or of
+ * distinct values (objectui#11681, triage ruling Q3 A on that card). `sum` /
+ * `min` / `max` over an integer field would qualify too, but the answer does
+ * not state the source field's scale, so they are not judged integer here.
+ */
+export const INTEGER_AGGREGATES = ['count', 'count_distinct'];
+/**
+ * Whether a measure column's `aggregate` makes every value a whole number — a
+ * value axis that plots only such measures takes integer ticks
+ * (objectui#11681). Judged over an untrusted wire value; anything else,
+ * absence included, answers `false`, so the axis keeps its default.
+ */
+export function isIntegerAggregate(value) {
+    return typeof value === 'string' && INTEGER_AGGREGATES.includes(value);
+}
 /** Runtime membership test for {@link BUILTIN_AGGREGATES}, over an untrusted wire value. */
 export function isBuiltinAggregate(value) {
     return typeof value === 'string' && BUILTIN_AGGREGATES.includes(value);
@@ -344,6 +360,12 @@ export function buildChartSeries(rows, dimensions, values, fields, options) {
         const field = (fields ?? []).find((f) => f.name === name);
         return field ? resolveMeasureLabel(field, options?.builtinAggregateLabels) : name;
     };
+    // The measure column's own `aggregate`, spread onto each series that plots
+    // it (objectui#11681) — present only when the column states a string one.
+    const aggregateOf = (name) => {
+        const aggregate = (fields ?? []).find((f) => f.name === name)?.aggregate;
+        return typeof aggregate === 'string' ? { aggregate } : {};
+    };
     // Multi-dimension, single-measure → pivot the second dimension into series.
     if (dims.length >= 2 && vals.length === 1) {
         const xKey = dims[0];
@@ -449,7 +471,8 @@ export function buildChartSeries(rows, dimensions, values, fields, options) {
             // server-resolved to display labels by queryDataset), except the null
             // group, which says so with the bucket label the renderer supplied. The
             // key is a separate question from the text — see `pivotSeriesBuckets`.
-            series: groups.map(({ dataKey, label }) => ({ dataKey, label })),
+            // Every group plots the one measure, so each carries its aggregate.
+            series: groups.map(({ dataKey, label }) => ({ dataKey, label, ...aggregateOf(measure) })),
         };
     }
     // Default: first dimension on the x-axis, one series per measure.
@@ -472,7 +495,7 @@ export function buildChartSeries(rows, dimensions, values, fields, options) {
             ? bucketNullCategories(safeRows, xKey, options?.nullCategoryLabel ?? NULL_CATEGORY_LABEL)
             : safeRows,
         xAxisKey: xKey,
-        series: vals.map((v) => ({ dataKey: v, label: labelOf(v) })),
+        series: vals.map((v) => ({ dataKey: v, label: labelOf(v), ...aggregateOf(v) })),
     };
 }
 /**

package/dist/utils/date-display.d.ts

@@ -6,56 +6,37 @@
  * LICENSE file in the root directory of this source tree.
  */
 /**
- * date-display - the ONE date/datetime display path behind every field cell,
- * grid card, gantt tooltip and dataset measure in the console.
- *
- * These functions are unchanged; what changed is where they live. They were
- * written in `@object-ui/fields`' barrel (`packages/fields/src/index.tsx`),
- * which is a React package, so `@object-ui/core` could not reach them - and
- * `core`'s `utils/dataset-format.ts` is exactly the caller that needed them:
- * `formatMeasure` returned `String(v)` for any non-numeric value, so a `min` /
- * `max` measure over a date field rendered its raw 24-character ISO string on
- * the metric tile, in chart values, in dataset table cells and in the
- * metadata-admin dataset preview (objectui#7178).
- *
- * The fix is the move, NOT a second formatter here. That choice is the whole
- * point, and it is the lesson of objectui#4576: when the percent convention
- * was duplicated across this same package boundary, a list cell and a
- * dashboard measure drifted apart (`1.234,5 %` beside `1.234,5%` in a German
- * session) while both were "correct". `dataset-format.ts`'s own header records
- * that history, and `number-display.ts` next door is the same remedy applied
- * to numbers: the pure function moves DOWN into the React-free engine and the
- * upper package re-exports it, so there is one home and nothing to drift.
- *
- * `@object-ui/fields` re-exports the formatting symbols below under their
- * original names, so `formatDate` / `formatDateTime` /
- * `formatDateTimeCompactParts` / `formatRelativeDate` / `DateDisplayOptions`
- * keep working unchanged for `ObjectGrid`, `ObjectGantt`,
- * `plugin-dashboard`'s `recordFields` and the `date` cell renderer.
- * `toDisplayDate` is exported from `@object-ui/core` alone (objectui#10183),
- * and so are `toDisplayEndDate` / `toInclusiveEndDay`, the end read and its
- * inverse both gantt surfaces share (objectui#11141).
- *
- * The `datetime` CELL face joined this file in objectui#7443. It used to be a
- * second convention inlined in `DateTimeCellRenderer`: two `Intl` option bags
- * for one field type, kept in step by nothing, while `date` had exactly one.
- * It is `formatDateTime`'s `'compact'` style now, byte-identical to what the
- * cell rendered before.
- *
- * Pure by construction (no React, no i18n): the only ambient inputs are `Intl`
- * and the clock, and the one phrase `Intl` cannot produce ("Overdue Nd") comes
- * in through the INJECTED `options.t`, the same way `buildDatasetFieldHelpers`
- * in `dataset-format.ts` takes `fieldLabel`.
- *
- * ⚠️ There is a third ambient input, and it is the one this module has to
- * decide about rather than pass on: the VIEWER's timezone. A value carrying a
- * time is an instant and renders in that zone; a DATE-ONLY value names a
- * calendar day, carries no instant, and must render as that day everywhere.
- * `toDisplayDate` below is the single parse step that tells the two apart —
- * every function here goes through it (objectui#10110), and so does every
- * caller elsewhere that needs a face or a day comparison none of these
- * functions produce (objectui#10183).
+ * Declare the zone instants render in — the host's half of objectui#11693.
+ *
+ * ## Why the zone enters HERE and nowhere else
+ *
+ * Every date and datetime face in the console is a function of this module
+ * (see the header), and each caller threads only its `locale`. The zone the
+ * signed-in workspace configures (`localization.timezone`, served by
+ * `GET /api/v1/auth/me/localization`) is the same for every face on the
+ * page, so it is set once, here, and every face reads it — rather than
+ * threaded through each call site, where one forgotten caller renders the
+ * same instant in a second zone beside the first (objectui#4272 is that
+ * defect for the locale). `LocalizationProvider` (`@object-ui/i18n`) is the
+ * host that calls this; a renderer never does.
+ *
+ * `undefined` (or an empty string) clears it: instants render in the
+ * viewer's zone again. A name this runtime's `Intl` does not know — a zone
+ * newer than the browser's time-zone data, say — clears it too, with a
+ * warning, rather than make every face throw the `RangeError` `Intl` raises
+ * for it.
+ *
+ * ⛔ A date-only value never takes the zone; see {@link toDisplayDate}.
  */
+export declare function setDisplayTimeZone(timeZone: string | undefined): void;
+/** The zone {@link setDisplayTimeZone} declared, or `undefined` for the viewer's own. */
+export declare function getDisplayTimeZone(): string | undefined;
+/**
+ * Be told when the display zone changes; returns the unsubscribe. The shape is
+ * React's `useSyncExternalStore` contract, which is how `LocalizationProvider`
+ * re-renders its consumers once the zone they format in has moved.
+ */
+export declare function subscribeDisplayTimeZone(listener: () => void): () => void;
 /**
  * Options shared by {@link formatDate} / {@link formatRelativeDate} /
  * {@link formatDateTime}. One bag, and each function reads the keys it needs:
@@ -207,7 +188,9 @@ export declare function isRealCalendarDate(dateOnly: string): boolean;
  * ⛔ Read the result with LOCAL getters or local-zone `Intl` formatting only.
  * For a date-only value it is local midnight of the named day, so its
  * `toISOString()` / UTC getters name the previous day east of UTC — hand
- * those the stored value, never this.
+ * those the stored value, never this. The faces in this module know such a
+ * `Date` when they are handed one and keep it out of the display zone
+ * (objectui#11693, see `calendarDays`).
  */
 export declare function toDisplayDate(value: string | Date | number): Date;
 /**
@@ -269,6 +252,11 @@ export declare function toInclusiveEndDay(end: Date): Date;
  * past dates render as plain "N days ago" instead. The overdue phrase has no
  * `Intl` equivalent, so it resolves through `options.t` (key
  * `fields.relativeDate.overdue`) with an English fallback.
+ *
+ * Days are counted in the display zone (objectui#11693): "today" is the
+ * display zone's today, and an instant falls on its day there. A date-only
+ * value keeps the day it names and is counted from that same today, so an
+ * instant and a date-only value on one day read one phrase.
  */
 export declare function formatRelativeDate(value: string | Date | number, options?: DateDisplayOptions): string;
 /**
@@ -350,5 +338,9 @@ export declare function formatDateTimeCompactParts(value: string | Date | number
  * hard it tried — it always handed `Intl` an `undefined` tag, i.e. the
  * MACHINE's locale, which is neither of the repo's two locale channels.
  * Callers should pass the tag from `useDisplayLocale()`.
+ *
+ * The zone is NOT an option: an instant renders in the display zone the host
+ * declared with {@link setDisplayTimeZone}, else the viewer's, on every face
+ * this module produces (objectui#11693).
  */
 export declare function formatDateTime(value: string | Date | number, options?: DateDisplayOptions): string;

package/dist/utils/date-display.js

@@ -5,6 +5,169 @@
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  */
+/**
+ * date-display - the ONE date/datetime display path behind every field cell,
+ * grid card, gantt tooltip and dataset measure in the console.
+ *
+ * These functions are unchanged; what changed is where they live. They were
+ * written in `@object-ui/fields`' barrel (`packages/fields/src/index.tsx`),
+ * which is a React package, so `@object-ui/core` could not reach them - and
+ * `core`'s `utils/dataset-format.ts` is exactly the caller that needed them:
+ * `formatMeasure` returned `String(v)` for any non-numeric value, so a `min` /
+ * `max` measure over a date field rendered its raw 24-character ISO string on
+ * the metric tile, in chart values, in dataset table cells and in the
+ * metadata-admin dataset preview (objectui#7178).
+ *
+ * The fix is the move, NOT a second formatter here. That choice is the whole
+ * point, and it is the lesson of objectui#4576: when the percent convention
+ * was duplicated across this same package boundary, a list cell and a
+ * dashboard measure drifted apart (`1.234,5 %` beside `1.234,5%` in a German
+ * session) while both were "correct". `dataset-format.ts`'s own header records
+ * that history, and `number-display.ts` next door is the same remedy applied
+ * to numbers: the pure function moves DOWN into the React-free engine and the
+ * upper package re-exports it, so there is one home and nothing to drift.
+ *
+ * `@object-ui/fields` re-exports the formatting symbols below under their
+ * original names, so `formatDate` / `formatDateTime` /
+ * `formatDateTimeCompactParts` / `formatRelativeDate` / `DateDisplayOptions`
+ * keep working unchanged for `ObjectGrid`, `ObjectGantt`,
+ * `plugin-dashboard`'s `recordFields` and the `date` cell renderer.
+ * `toDisplayDate` is exported from `@object-ui/core` alone (objectui#10183),
+ * and so are `toDisplayEndDate` / `toInclusiveEndDay`, the end read and its
+ * inverse both gantt surfaces share (objectui#11141).
+ *
+ * The `datetime` CELL face joined this file in objectui#7443. It used to be a
+ * second convention inlined in `DateTimeCellRenderer`: two `Intl` option bags
+ * for one field type, kept in step by nothing, while `date` had exactly one.
+ * It is `formatDateTime`'s `'compact'` style now, byte-identical to what the
+ * cell rendered before.
+ *
+ * No React, no i18n: the ambient inputs are `Intl`, the clock and the display
+ * zone below, and the one phrase `Intl` cannot produce ("Overdue Nd") comes
+ * in through the INJECTED `options.t`, the same way `buildDatasetFieldHelpers`
+ * in `dataset-format.ts` takes `fieldLabel`.
+ *
+ * ⚠️ There is a third ambient input, and it is the one this module has to
+ * decide about rather than pass on: the zone an instant renders in. A value
+ * carrying a time is an instant and renders in the DISPLAY ZONE — the zone the
+ * host declared through {@link setDisplayTimeZone} (objectui#11693), else the
+ * viewer's own; a DATE-ONLY value names a calendar day, carries no instant,
+ * and must render as that day everywhere, whatever the display zone.
+ * `toDisplayDate` below is the single parse step that tells the two apart —
+ * every function here goes through it (objectui#10110), and so does every
+ * caller elsewhere that needs a face or a day comparison none of these
+ * functions produce (objectui#10183).
+ */
+// ── The display zone (objectui#11693) ──────────────────────────────────────
+/**
+ * The zone every instant face below renders in, when the host has declared
+ * one; `undefined` means the viewer's own zone (the runtime default), which is
+ * what every face rendered in before objectui#11693.
+ */
+let displayTimeZone;
+const displayTimeZoneListeners = new Set();
+/** `true` when this runtime's `Intl` knows `timeZone`. */
+function isKnownTimeZone(timeZone) {
+    try {
+        new Intl.DateTimeFormat('en-US', { timeZone });
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+/**
+ * Declare the zone instants render in — the host's half of objectui#11693.
+ *
+ * ## Why the zone enters HERE and nowhere else
+ *
+ * Every date and datetime face in the console is a function of this module
+ * (see the header), and each caller threads only its `locale`. The zone the
+ * signed-in workspace configures (`localization.timezone`, served by
+ * `GET /api/v1/auth/me/localization`) is the same for every face on the
+ * page, so it is set once, here, and every face reads it — rather than
+ * threaded through each call site, where one forgotten caller renders the
+ * same instant in a second zone beside the first (objectui#4272 is that
+ * defect for the locale). `LocalizationProvider` (`@object-ui/i18n`) is the
+ * host that calls this; a renderer never does.
+ *
+ * `undefined` (or an empty string) clears it: instants render in the
+ * viewer's zone again. A name this runtime's `Intl` does not know — a zone
+ * newer than the browser's time-zone data, say — clears it too, with a
+ * warning, rather than make every face throw the `RangeError` `Intl` raises
+ * for it.
+ *
+ * ⛔ A date-only value never takes the zone; see {@link toDisplayDate}.
+ */
+export function setDisplayTimeZone(timeZone) {
+    let next;
+    if (timeZone) {
+        if (isKnownTimeZone(timeZone))
+            next = timeZone;
+        else
+            console.warn(`[date-display] unknown time zone "${timeZone}"; instants render in the viewer's zone`);
+    }
+    if (next === displayTimeZone)
+        return;
+    displayTimeZone = next;
+    for (const listener of [...displayTimeZoneListeners])
+        listener();
+}
+/** The zone {@link setDisplayTimeZone} declared, or `undefined` for the viewer's own. */
+export function getDisplayTimeZone() {
+    return displayTimeZone;
+}
+/**
+ * Be told when the display zone changes; returns the unsubscribe. The shape is
+ * React's `useSyncExternalStore` contract, which is how `LocalizationProvider`
+ * re-renders its consumers once the zone they format in has moved.
+ */
+export function subscribeDisplayTimeZone(listener) {
+    displayTimeZoneListeners.add(listener);
+    return () => {
+        displayTimeZoneListeners.delete(listener);
+    };
+}
+/**
+ * The `Date`s this module built to NAME A CALENDAR DAY — {@link toDisplayDate}'s
+ * local midnight for a date-only value, and {@link toInclusiveEndDay}'s day.
+ *
+ * The faces below must read such a `Date` in the local zone (its own docblock
+ * says so), never in the display zone: west of the viewer it would name the
+ * day before. A string still says what it is, but callers hand these `Date`s
+ * on — `GridField`'s date cell formats the one `toDisplayDate` returned, and
+ * the functions here hand theirs to each other — so the fact travels with the
+ * object rather than with the string it came from.
+ */
+const calendarDays = new WeakSet();
+/** The zone a parsed value renders in: the display zone for an instant, the viewer's for a calendar day. */
+function zoneFor(date) {
+    return calendarDays.has(date) ? undefined : displayTimeZone;
+}
+/** `Intl` options naming `timeZone`, or none, so a face with no zone keeps its exact options bag. */
+function inZone(timeZone) {
+    return timeZone ? { timeZone } : {};
+}
+const dayPartsFormats = new Map();
+/** The calendar day `date` falls on in `timeZone` (the viewer's when `undefined`); `month` is 0-based. */
+function dayIn(date, timeZone) {
+    if (!timeZone)
+        return { year: date.getFullYear(), month: date.getMonth(), day: date.getDate() };
+    let format = dayPartsFormats.get(timeZone);
+    if (!format) {
+        format = new Intl.DateTimeFormat('en-US', { timeZone, year: 'numeric', month: 'numeric', day: 'numeric' });
+        dayPartsFormats.set(timeZone, format);
+    }
+    const parts = format.formatToParts(date);
+    const part = (type) => Number(parts.find((p) => p.type === type)?.value);
+    return { year: part('year'), month: part('month') - 1, day: part('day') };
+}
+/** A day as a whole number of days, so two days subtract to their distance with no DST hour in it. */
+function dayNumber({ year, month, day }) {
+    const probe = new Date(0);
+    probe.setUTCFullYear(year, month, day);
+    return Math.round(probe.getTime() / 86400000);
+}
 /**
  * The date-only ISO spelling — `2026-08-01`, and nothing else.
  *
@@ -147,7 +310,9 @@ export function isRealCalendarDate(dateOnly) {
  * ⛔ Read the result with LOCAL getters or local-zone `Intl` formatting only.
  * For a date-only value it is local midnight of the named day, so its
  * `toISOString()` / UTC getters name the previous day east of UTC — hand
- * those the stored value, never this.
+ * those the stored value, never this. The faces in this module know such a
+ * `Date` when they are handed one and keep it out of the display zone
+ * (objectui#11693, see `calendarDays`).
  */
 export function toDisplayDate(value) {
     const parsed = value instanceof Date ? value : new Date(value);
@@ -169,6 +334,7 @@ export function toDisplayDate(value) {
     // Setting the year back is co-extensive with that legacy mapping and a
     // no-op on every other year.
     local.setFullYear(year);
+    calendarDays.add(local);
     return local;
 }
 /**
@@ -233,6 +399,7 @@ export function toDisplayEndDate(value) {
 export function toInclusiveEndDay(end) {
     const day = new Date(end.getTime() - 1);
     day.setHours(0, 0, 0, 0);
+    calendarDays.add(day);
     return day;
 }
 /**
@@ -289,6 +456,11 @@ function absoluteFallbackOptions(options) {
  * past dates render as plain "N days ago" instead. The overdue phrase has no
  * `Intl` equivalent, so it resolves through `options.t` (key
  * `fields.relativeDate.overdue`) with an English fallback.
+ *
+ * Days are counted in the display zone (objectui#11693): "today" is the
+ * display zone's today, and an instant falls on its day there. A date-only
+ * value keeps the day it names and is counted from that same today, so an
+ * instant and a date-only value on one day read one phrase.
  */
 export function formatRelativeDate(value, options) {
     if (value === null || value === undefined || value === '')
@@ -296,11 +468,7 @@ export function formatRelativeDate(value, options) {
     const date = toDisplayDate(value);
     if (!(date instanceof Date) || isNaN(date.getTime()))
         return '—';
-    const now = new Date();
-    const startOfToday = new Date(now.getFullYear(), now.getMonth(), now.getDate());
-    const startOfDate = new Date(date.getFullYear(), date.getMonth(), date.getDate());
-    const diffMs = startOfDate.getTime() - startOfToday.getTime();
-    const diffDays = Math.round(diffMs / (1000 * 60 * 60 * 24));
+    const diffDays = dayNumber(dayIn(date, zoneFor(date))) - dayNumber(dayIn(new Date(), displayTimeZone));
     // Beyond the ±7-day window, fall back to the absolute (already localized) form.
     if (diffDays < -7 || diffDays > 7)
         return formatDate(date, undefined, absoluteFallbackOptions(options));
@@ -354,6 +522,9 @@ export function formatDate(value, style, options) {
     if (!(date instanceof Date) || isNaN(date.getTime()))
         return '—';
     const effectiveStyle = style ?? options?.style;
+    // An instant names its day in the display zone; a calendar day is its own
+    // day in every zone (objectui#11693).
+    const zone = zoneFor(date);
     if (effectiveStyle === 'short') {
         // Compact format for mobile: "Jan 15, '24" / "1月 15, '24".
         // Only the MONTH token is localized: the surrounding compact shape (day,
@@ -361,10 +532,9 @@ export function formatDate(value, style, options) {
         // cards, not a locale-derived one. The tag comes from `options.locale`
         // like the default branch below — hardcoding `'en-US'` here made this the
         // one branch that ignored a locale its caller had threaded (objectui#4272).
-        const month = date.toLocaleDateString(options?.locale, { month: 'short' });
-        const day = date.getDate();
-        const year = String(date.getFullYear()).slice(-2);
-        return `${month} ${day}, '${year}`;
+        const month = date.toLocaleDateString(options?.locale, { month: 'short', ...inZone(zone) });
+        const { day, year } = dayIn(date, zone);
+        return `${month} ${day}, '${String(year).slice(-2)}`;
     }
     if (effectiveStyle === 'relative') {
         return formatRelativeDate(date, options);
@@ -374,11 +544,12 @@ export function formatDate(value, style, options) {
     // because the year is rarely useful for in-progress records and the
     // verbose "2026年7月21日" form crowds cards and table cells. Past- /
     // future-year dates keep the year so users can disambiguate.
-    const isCurrentYear = date.getFullYear() === new Date().getFullYear();
+    const isCurrentYear = dayIn(date, zone).year === dayIn(new Date(), displayTimeZone).year;
     return date.toLocaleDateString(options?.locale, {
         year: isCurrentYear ? undefined : 'numeric',
         month: 'short',
         day: 'numeric',
+        ...inZone(zone),
     });
 }
 /**
@@ -402,11 +573,15 @@ export function formatDateTimeCompactParts(value, options) {
     const date = toDisplayDate(value);
     if (!(date instanceof Date) || isNaN(date.getTime()))
         return null;
+    // Both halves in the display zone, so the day and the time of one instant
+    // never come from two zones (objectui#11693).
+    const zone = zoneFor(date);
     return {
         date: date.toLocaleDateString(options?.locale, {
             month: 'numeric',
             day: 'numeric',
             year: 'numeric',
+            ...inZone(zone),
         }),
         // `hour12` stays declared: this is the compact Airtable-style cell, and
         // the 12-hour face is its design, not a locale artefact. Locales that
@@ -415,6 +590,7 @@ export function formatDateTimeCompactParts(value, options) {
             hour: 'numeric',
             minute: '2-digit',
             hour12: true,
+            ...inZone(zone),
         }).toLowerCase(),
     };
 }
@@ -442,6 +618,10 @@ export function formatDateTimeCompactParts(value, options) {
  * hard it tried — it always handed `Intl` an `undefined` tag, i.e. the
  * MACHINE's locale, which is neither of the repo's two locale channels.
  * Callers should pass the tag from `useDisplayLocale()`.
+ *
+ * The zone is NOT an option: an instant renders in the display zone the host
+ * declared with {@link setDisplayTimeZone}, else the viewer's, on every face
+ * this module produces (objectui#11693).
  */
 export function formatDateTime(value, options) {
     if (value === null || value === undefined || value === '')
@@ -459,5 +639,6 @@ export function formatDateTime(value, options) {
         day: 'numeric',
         hour: '2-digit',
         minute: '2-digit',
+        ...inZone(zoneFor(date)),
     });
 }

package/dist/utils/expand-fields.d.ts

@@ -98,7 +98,8 @@
  *  - the dashboard's relation/link test — `isLookupType` in
  *    `packages/plugin-dashboard/src/recordFields.tsx` (objectui#5692);
  *  - the action-param RESOLVER (one step before `paramToField`) —
- *    `packages/app-shell/src/utils/resolveActionParams.ts` (objectui#5874);
+ *    `packages/fields/src/resolveActionParams.ts` (objectui#5874; moved out of
+ *    app-shell by objectui#12105 so the bulk dialog shares it);
  *  - the detail header's relation test — `HeaderHighlight.tsx` in
  *    `packages/plugin-detail` (objectui#5874);
  *  - the detail drawer's relation test — `RecordDetailDrawer.tsx` in
@@ -134,10 +135,11 @@
  * (objectui#4790). The form now DERIVES from this set instead of restating it:
  *
  *     form's data-source rule  ==  EXPANDABLE_FIELD_TYPES
- *                                  + three widget-hint-only picker names
+ *                                  + the widget-hint-only picker names
  *
  * The extension is one-directional and cannot fold back into this set:
- * `object-ref` / `filter-condition` / `recipient-picker` are widget HINTS, never
+ * `object-ref` / `filter-condition` / `recipient-picker` (and the registry-name
+ * pickers `position-ref` / `permission-ref`, objectui#7611) are widget HINTS, never
  * declarable field types (`widgetHintOnly: true` in
  * `app-shell/src/utils/paramValueShape.ts`), so no object schema can produce a
  * field whose `type` is one of them.
@@ -146,7 +148,7 @@
  * of the above (`lookup` / `master_detail` / `user` — no `tree`, no pickers, and
  * for a while a fifth spelling, `owner`, that objectui#4814 retired). It now
  * derives from this set with NO extension, because the bulk dialog's params
- * cannot produce the three widget-hint names (objectui#4815):
+ * cannot produce the widget-hint names (objectui#4815):
  *
  *     bulk dialog's data-source rule  ==  EXPANDABLE_FIELD_TYPES
  *

package/dist/utils/expand-fields.js

@@ -99,7 +99,8 @@ import { columnIdentity } from './column-identity.js';
  *  - the dashboard's relation/link test — `isLookupType` in
  *    `packages/plugin-dashboard/src/recordFields.tsx` (objectui#5692);
  *  - the action-param RESOLVER (one step before `paramToField`) —
- *    `packages/app-shell/src/utils/resolveActionParams.ts` (objectui#5874);
+ *    `packages/fields/src/resolveActionParams.ts` (objectui#5874; moved out of
+ *    app-shell by objectui#12105 so the bulk dialog shares it);
  *  - the detail header's relation test — `HeaderHighlight.tsx` in
  *    `packages/plugin-detail` (objectui#5874);
  *  - the detail drawer's relation test — `RecordDetailDrawer.tsx` in
@@ -135,10 +136,11 @@ import { columnIdentity } from './column-identity.js';
  * (objectui#4790). The form now DERIVES from this set instead of restating it:
  *
  *     form's data-source rule  ==  EXPANDABLE_FIELD_TYPES
- *                                  + three widget-hint-only picker names
+ *                                  + the widget-hint-only picker names
  *
  * The extension is one-directional and cannot fold back into this set:
- * `object-ref` / `filter-condition` / `recipient-picker` are widget HINTS, never
+ * `object-ref` / `filter-condition` / `recipient-picker` (and the registry-name
+ * pickers `position-ref` / `permission-ref`, objectui#7611) are widget HINTS, never
  * declarable field types (`widgetHintOnly: true` in
  * `app-shell/src/utils/paramValueShape.ts`), so no object schema can produce a
  * field whose `type` is one of them.
@@ -147,7 +149,7 @@ import { columnIdentity } from './column-identity.js';
  * of the above (`lookup` / `master_detail` / `user` — no `tree`, no pickers, and
  * for a while a fifth spelling, `owner`, that objectui#4814 retired). It now
  * derives from this set with NO extension, because the bulk dialog's params
- * cannot produce the three widget-hint names (objectui#4815):
+ * cannot produce the widget-hint names (objectui#4815):
  *
  *     bulk dialog's data-source rule  ==  EXPANDABLE_FIELD_TYPES
  *

package/dist/utils/filter-converter.d.ts

@@ -174,8 +174,12 @@ export declare function convertFiltersToAST(filter: Record<string, any>): Filter
  *
  * The third is the one that kept getting lost. Renderers tested `source.length
  * > 0` before using it, which is `undefined > 0` for an object — so a
- * `table.defaultFilters` (declared `Record<string, any>`) was DROPPED and the
- * view returned every record. Silently: no error, just a wider answer.
+ * `table.defaultFilters` (declared `Record<string, any>` until objectui#6152
+ * round 10; the protocol's `ViewFilterRule` array since, and the record no
+ * longer validates there) was DROPPED and the view returned every record.
+ * Silently: no error, just a wider answer. That narrowing moved what an author
+ * may write, not this sink: the object arm below still lowers a record whatever
+ * caller hands it one.
  *
  * The FIRST never worked at all (objectui#3431). The array branch returned
  * every array VERBATIM, so a saved view's `ViewFilterRule[]` travelled to

package/dist/utils/filter-converter.js

@@ -1256,8 +1256,12 @@ function viewFilterRuleToNode(rule) {
  *
  * The third is the one that kept getting lost. Renderers tested `source.length
  * > 0` before using it, which is `undefined > 0` for an object — so a
- * `table.defaultFilters` (declared `Record<string, any>`) was DROPPED and the
- * view returned every record. Silently: no error, just a wider answer.
+ * `table.defaultFilters` (declared `Record<string, any>` until objectui#6152
+ * round 10; the protocol's `ViewFilterRule` array since, and the record no
+ * longer validates there) was DROPPED and the view returned every record.
+ * Silently: no error, just a wider answer. That narrowing moved what an author
+ * may write, not this sink: the object arm below still lowers a record whatever
+ * caller hands it one.
  *
  * The FIRST never worked at all (objectui#3431). The array branch returned
  * every array VERBATIM, so a saved view's `ViewFilterRule[]` travelled to

package/dist/utils/normalize-list-view.d.ts

@@ -199,6 +199,12 @@ export declare function isListViewVisualization(value: unknown): value is ListVi
  *    stays absent, because the defaults are per-toggle (search/sort/filter/
  *    rowHeight/group default ON, hideFields/rowColor default OFF) and belong to
  *    the renderer, not to the vocabulary bridge.
+ *  - the view's `inlineEdit` → `userActions.editInline` (objectui#5144), with
+ *    the value carried over and an explicit `editInline` winning. `inlineEdit`
+ *    stays on the result, because `ListView` seeds the grid's edit mode from
+ *    it. See {@link foldsInlineEditIntoEditInline}. An absent pair stays
+ *    absent here as well; `ListView` reads that as on, the spec's default
+ *    (objectstack#22605).
  *  - `aria: { label, describedBy }` → the spec's `AriaProps`
  *    (`{ ariaLabel, ariaDescribedBy }`), and `sharing: { visibility, enabled }`
  *    → the spec's `ViewSharing` (`{ type }`) — #2890 scope A step 5. `aria.live`
@@ -221,8 +227,8 @@ export declare function isListViewVisualization(value: unknown): value is ListVi
  *      · an already-present `objectName` WINS — this fold only fills a gap, it
  *        never re-points a binding that already resolves;
  *      · `data` is NOT deleted. Every other fold deletes because the legacy key
- *        has one meaning and one home; `data` has four providers, `api`/`value`
- *        are read live in `ListView`, and the whole block is FORWARDED to child
+ *        has one meaning and one home; `data` has more providers than
+ *        `object`, `value` is read live in `ListView`, and the whole block is FORWARDED to child
  *        views (the gantt branch), whose own `getDataConfig` reads `data` before
  *        `objectName`. Deleting it for one provider would rewrite what a child
  *        resolves. Nothing in `ListView` reads `data.provider === 'object'`, so
@@ -245,15 +251,13 @@ export declare function isListViewVisualization(value: unknown): value is ListVi
  *    breaking change with no inventory. Runs AFTER the `fields` → `columns` fold
  *    above, so a view that spells its column list the legacy way still gets its
  *    entries canonicalized.
- *  - the four PER-VIEW-TYPE config aliases phase 3 carried over
- *    ({@link PER_VIEW_CONFIG_ALIASES}): `kanban.groupField` → `groupByField`,
- *    `kanban.cardFields` → `columns`, `gallery.imageField` → `coverField`,
- *    `timeline.dateField` → `startDateField`. One read-site changes behaviour
- *    as a result, and it is a CORRECTION of the same inverted precedence A2
- *    fixed for `densityMode`: `ListView`'s kanban adapter resolves
- *    `cardFields || columns`, i.e. legacy over canonical, so a config carrying
- *    BOTH used to render the legacy value. After the fold the canonical
- *    `columns` reaches it. Every other reader of these four was already
- *    canonical-first and is unaffected.
+ *
+ * No longer folded: the four PER-VIEW-TYPE config aliases phase 3 carried over
+ * (`kanban.groupField` → `groupByField`, `kanban.cardFields` → `columns`,
+ * `gallery.imageField` → `coverField`, `timeline.dateField` →
+ * `startDateField`). objectui#6152 round 14 retired that fold with every
+ * renderer-side reader of the four: each list-view door refuses them by name
+ * (rounds 11 and 12), and a stored block that still carries one passes through
+ * here untouched and binds nothing downstream.
  */
 export declare function normalizeListViewSchema<T>(schema: T): T;