@object-ui/fields 17.5.0 → 17.7.0

package/dist/widgets/AddressField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
-import { AddressValue } from './address-format';
-export type { AddressValue } from './address-format';
+import { FieldWidgetComponentProps } from './types.js';
+import { AddressValue } from './address-format.js';
+export type { AddressValue } from './address-format.js';
 /**
  * Address field widget - provides a structured address input
  * Supports street, city, state, postal code, and country

package/dist/widgets/AutoNumberField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * AutoNumberField - Read-only auto-generated field
  * Values are automatically generated by the system and cannot be edited

package/dist/widgets/AvatarField.d.ts

@@ -1,7 +1,23 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
- * Avatar field widget - provides an avatar/profile picture uploader
- * Supports image URLs or file uploads
+ * Avatar field widget - provides an avatar/profile picture uploader.
+ *
+ * `avatar` is a member of the file-reference family, so its stored value is
+ * the bare `sys_file` id, exactly as for `file` and `image` (see
+ * `file-value`'s "Submitting"). A pick uploads through the ambient
+ * `UploadProvider` (`useUpload()`), and the id the adapter surfaced in
+ * `meta.fileId` is what `onChange` receives, through `fileValueForSubmit` —
+ * the one submit rule the file and image widgets use. A pick whose adapter
+ * surfaced no id (the object-URL default `useUpload()` falls back to when no
+ * provider is mounted, an S3/Azure-style adapter that mints no `sys_file`
+ * row) is refused with the same translated "did not complete" row, and the
+ * field is not changed. ⛔ The widget used to read the pick into a `data:` URL
+ * and store that string, inlining the whole image into the record row as a
+ * value the stored contract refuses (objectui#10785).
+ *
+ * Reading is `readFileValue`'s: a bare id renders from the storage endpoint,
+ * and a legacy `data:` or http(s) URL already on a record still renders as
+ * itself — ADR-0104's dual-read window is a read rule.
  */
-export declare function AvatarField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function AvatarField({ value, onChange, field, readonly, onUploadingChange, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/BooleanField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * BooleanField - Toggle input supporting switch and checkbox variants
  * Renders as Switch or Checkbox based on field widget configuration
  */
-export declare function BooleanField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<boolean>): React.JSX.Element;
+export declare function BooleanField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<boolean>): React.JSX.Element;

package/dist/widgets/CapabilityMultiSelectField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Parse the stored value into the selected capability-name list. The canonical
  * storage is a JSON-string array; we also tolerate an already-parsed array (in

package/dist/widgets/CheckboxesField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * CheckboxesField - select zero or more values from a fixed option set, rendered
  * as a list of checkboxes. The stored value is a string[]. Used for the

package/dist/widgets/CodeField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Code field widget - provides a code editor with syntax highlighting
  * Uses a simple textarea with monospace font

package/dist/widgets/ColorField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Color field widget - provides a color picker input
  * Supports hex color values (e.g., #ff0000)

package/dist/widgets/CurrencyField.d.ts

@@ -1,3 +1,3 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 export declare function CurrencyField({ value, onChange, field, readonly, error, className, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;

package/dist/widgets/DateField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * DateField - Date picker input widget
  * Uses native date input and displays locale-formatted date in readonly mode
  */
-export declare function DateField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function DateField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/DateTimeField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * DateTimeField - Combined date and time picker widget
  * Displays both date and time in locale format when readonly
  */
-export declare function DateTimeField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function DateTimeField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/EmailField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * EmailField - Email address input with mailto link in readonly mode
  * Renders as a clickable mailto link when readonly, standard email input otherwise

package/dist/widgets/FileField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * FileField - File upload widget with drag-and-drop support
  * Supports single and multiple file uploads with configurable accepted file types.
@@ -15,7 +15,7 @@ export declare function FileField({ value, onChange, field, readonly, onUploadin
  * drag-and-drop zone — a grid cell has no room for one; the per-row expand
  * form still offers the full-size FileField.
  */
-export declare function FileCell({ value, onChange, disabled, multiple, accept, maxSize, 'aria-label': ariaLabel, 'data-cell': dataCell, }: {
+export declare function FileCell({ value, onChange, disabled, multiple, accept, maxSize, error, 'aria-label': ariaLabel, 'data-cell': dataCell, }: {
     value: any;
     onChange: (value: any) => void;
     disabled?: boolean;
@@ -24,6 +24,22 @@ export declare function FileCell({ value, onChange, disabled, multiple, accept,
     accept?: string;
     /** Max file size in bytes (oversize picks are rejected with an inline error). */
     maxSize?: number;
+    /**
+     * The active validation message for this cell, named as
+     * `@objectstack/spec/ui`'s `FieldWidgetPropsSchema` names it — the same
+     * published slot `FieldWidgetComponentProps` declares and `LookupField` /
+     * `FileField` above already consume (objectui#5431, completing #3318's
+     * per-cell delivery). NOT the per-pick upload `errors` this component
+     * computes itself — this is the HOST's verdict on the cell's value.
+     *
+     * **Producer**: `GridField`, for a required-but-empty `file` cell.
+     * **Consumer**: drives `aria-invalid` on the picker button — the focusable
+     * control assistive tech reads a control state from (objectui#5223; a mark
+     * on the non-focusable wrapper is exactly what the registry sweep forbids).
+     * The message TEXT stays with the cell's `title` in `GridField`; rendering
+     * it here would double-display it.
+     */
+    error?: string;
     'aria-label'?: string;
     /** Focus-grid coordinate (see GridField keyboard navigation). */
     'data-cell'?: string;

package/dist/widgets/FilterConditionField.d.ts

@@ -1,22 +1,63 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 interface BuilderCondition {
     id: string;
     field: string;
     operator: string;
     value: any;
 }
+/**
+ * Opt-in FilterBuilder operators this widget offers (objectui#4736).
+ *
+ * The shared dropdown withholds these because two of its three consumers
+ * persist into dialects that cannot carry them (see `OPT_IN_OPERATORS` in
+ * `@object-ui/components`'s `filter-builder.tsx`). THIS widget can: its value
+ * is a MongoDB-style `FieldOperatorsSchema` criteria that the server's engine
+ * evaluates directly — never lowered through the array/triplet AST and never
+ * folded into a `ViewFilterRule` — so the spec's `FILTER_OPERATORS` is the only
+ * vocabulary it has to satisfy.
+ *
+ *   - `exists` / `notExists` author `$exists`, which `condToMongo` has emitted
+ *     and `kvToCondition` has read back since objectui#2942. Naming them here
+ *     is what KEEPS them reachable now that the shared dropdown no longer
+ *     offers them to the list and view surfaces, whose dialects have no
+ *     existence operator at all (objectui#4736). They are NOT folded onto
+ *     `is_not_null` / `is_null` (objectui#9559 ruling B, objectui#9306): on the
+ *     key-presence drivers that would change which records a stored sharing
+ *     rule matches.
+ *
+ * The case-insensitive contains used to be named here too, as
+ * `containsCaseInsensitive`. Since objectui#9306 it is the protocol's own
+ * `icontains` and an ordinary operator every consumer is offered, so there is
+ * nothing to opt into; it still authors `$icontains`, exactly as before.
+ *
+ * Module scope, not an inline literal: a fresh array each render would reset
+ * `FilterBuilder`'s memo inputs on every keystroke.
+ *
+ * @internal exported for tests
+ */
+export declare const FILTER_CONDITION_EXTRA_OPERATORS: readonly string[];
 /**
  * Builder condition → `$`-operator criteria. Exported for tests: this is the
  * chokepoint where a builder token becomes a spec `FieldOperatorsSchema` key,
  * and a wrong spelling here is rejected downstream by `convertFiltersToAST`
  * rather than at authoring time. @internal
+ *
+ * ⚠️ The arms are keyed on the builder's PROTOCOL ids (objectui#9306), and the
+ * `default` arm stores an EQUALITY. So an operator id with no arm here is not
+ * refused — it silently becomes `{ [field]: value }`, which for a
+ * `greater_than_or_equal` row would share a different set of records than the
+ * one on screen. Every id the dropdown can draw has its own arm, and
+ * `filter-builder-protocol-ids-census-9306.test.ts` (app-shell) pins each one's
+ * stored predicate, so a missing arm is a red test rather than a quiet `$eq`.
  */
 export declare function condToMongo(c: BuilderCondition, typeOf: (f: string) => string | undefined): Record<string, any> | null;
 /**
  * Criteria → builder condition (the reverse of {@link condToMongo}). Returning
  * `null` makes the builder refuse to load the rule ("criteria can't be
  * represented"), so this must keep accepting spellings previously written.
+ * The rows it produces carry the builder's protocol ids (objectui#9306); the
+ * stored criteria are `$`-tokens, which that change did not touch.
  * @internal
  */
 export declare function kvToCondition(field: string, v: any, idx: number): BuilderCondition | null;
@@ -24,7 +65,7 @@ export declare function kvToCondition(field: string, v: any, idx: number): Build
  * Would this criteria select EVERY record of the object?
  *
  * Mirrors the server's `isMatchAllCriteria` (objectstack `plugin-sharing`,
- * #3896) closely enough to warn before the round-trip: blank, `{}`, `[]`, and
+ * objectstack-ai/objectstack#3896) closely enough to warn before the round-trip: blank, `{}`, `[]`, and
  * the vacuous combinators. Deliberately conservative in the same direction —
  * the cost of a false positive is one extra hint, the cost of a false negative
  * is a save that fails with a toast. The server stays authoritative.

package/dist/widgets/FormulaField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * FormulaField - Read-only computed field
  * Values are computed on the backend and cannot be edited

package/dist/widgets/FullscreenFieldEditor.d.ts

@@ -36,8 +36,15 @@ import { FullscreenEditorProps } from '@object-ui/components';
  * primitive already answers it (no affordance at all).
  *
  * Everything else — `value` / `onCommit` / `label` / `testIdPrefix` /
- * `disabled` / `children` / `footer` — passes straight through, so the hosts and
- * their pins are unchanged. `testIdPrefix` still namespaces this package's ids
+ * `disabled` / `error` / `children` / `footer` — passes straight through, so the
+ * hosts and their pins are unchanged. `error` is REQUIRED by the primitive
+ * (objectui#4824) and stays required here: both hosts already destructure it off
+ * the widget props contract (objectui#3222), and it is what the primitive turns
+ * into the dialog control's `aria-invalid` / `aria-errormessage` and into the
+ * dialog-local message node. A host that omits it gets a dialog announcing
+ * `aria-invalid="false"` for an invalid field, which is the defect #4824
+ * measured — so the type system asks for it rather than trusting the next
+ * author to remember. `testIdPrefix` still namespaces this package's ids
  * (`textarea-`, `richtext-`), distinct from the built-in branch's
  * `form-textarea-`, so a test can still say which render path it found.
  */

package/dist/widgets/GeolocationField.d.ts

@@ -1,12 +1,18 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Geolocation data structure
  */
 export interface GeolocationValue {
-    latitude?: number;
-    longitude?: number;
-    accuracy?: number;
+    /**
+     * `number | null` since objectui#6848. `null` is what an emptied box emits —
+     * the spelling `CurrencyField` / `PercentField` / `NumberField` already used
+     * for the same user action — so the type has to admit it. `undefined` stays
+     * admissible because an untouched coordinate is genuinely absent.
+     */
+    latitude?: number | null;
+    longitude?: number | null;
+    accuracy?: number | null;
 }
 /**
  * Geolocation field widget - provides a location picker with coordinates

package/dist/widgets/GridField.d.ts

@@ -1,99 +1,110 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
+import { InlineGridColumn } from '@objectstack/spec/data';
 /**
  * GridField / LineItemsField — editable child-grid ("line items") widget.
  *
+ * ## Where the host's label and help text land, and why (objectui#4857)
+ *
+ * This widget forwarded nothing a host handed it, so the field's visible label
+ * pointed `for` at an id no element carried and the help text had zero
+ * consumers. Measured on `origin/main` at `e71c854ce`, a real form, editable
+ * state, `description` set:
+ *
+ * ```
+ * bare (no columns)   for=DANGLING hostIdEl=NONE consumers=0  focusables=[button]
+ * columns + one row   for=DANGLING hostIdEl=NONE consumers=0  focusables=[drag,
+ *                       input(Item), input(Qty), button(Duplicate row),
+ *                       button(Remove row), input(Item), input(Qty), button(Add)]
+ * ```
+ *
+ * The bare row's single focusable is the auxiliary "Add line" BUTTON — labelable,
+ * but routing the host id (and so the label's `for`) onto it would make the
+ * field's label NAME the add-row action and make a click on the label insert a
+ * row. Every realistic config is a composite: many cell inputs, each with its
+ * own `aria-label`, under one container. So this widget declares
+ * `labelling: 'group'` (see `FIELD_WIDGET_LABELLING` in `../index`) — the
+ * objectui#3961 composite shape, like `address` — and the CONTAINER consumes the
+ * host's keys:
+ *
+ *  - editable / list mode: the root div takes the DOM pass-through minus `name`
+ *    (DOM-legal on form controls only — the objectui#3291 leak) and minus
+ *    `aria-invalid` (control-channel state; this grid reports validity per CELL,
+ *    with its own inline marks), answering `role="group"` only when a host
+ *    actually named it — `CheckboxesField`'s split, key for key.
+ *
+ *    That strip STANDS (objectui#3318 upheld it rather than overturning it):
+ *    the container is not a control, so the host's state is not re-routed onto
+ *    it. What #3318 added is the other half the strip implied but nobody had
+ *    built — the host's failure now DRIVES the per-cell channel this comment
+ *    already claimed as the reporting path. See `hostFailedEmpty`.
+ *  - readonly: the table replaces the inputs entirely, so that surface takes the
+ *    name AND the description via `toHostGroupProps` — `'instead-of-the-inputs'`.
+ *
  * A controlled component: `value` is an array of row objects, `onChange`
  * receives the next array. It renders one editable cell per configured
  * column, supports add / delete row, and shows a running total of a numeric
  * column. This is the renderer for the `field:grid` widget and the cell
  * engine behind the master-detail subform (see ADR-0001).
  *
- * Column config (a subset of `GridColumnDefinition`):
- *   { field, label?, type?, options?, width?, required?, prefix?, step? }
- *   type ∈ 'text' | 'number' | 'currency' | 'date' | 'datetime' | 'time'
- *        | 'select' | 'lookup' | 'file'
+ * Column config: `@objectstack/spec`'s inline grid column, by reference —
+ * see {@link GridColumn}.
  *
- * Field-level config (from `GridFieldMetadata`):
- *   columns, min_rows, max_rows, allow_add, allow_delete, total_field
+ * Field-level config: the keys `GridFieldMetadata` (`@object-ui/types`)
+ * declares, each read under that one spelling (objectui#11070 round 8), and
+ * no other key: `sort_field`, the last key read before any face declared it,
+ * is declared there too (objectui#11070 round 9).
  */
-export interface GridColumn {
-    field: string;
-    label?: string;
-    /**
-     * Cell control + read/write adapter for the column.
-     *
-     * `date` / `datetime` / `time` are three DISTINCT controls, not one
-     * (objectui#3569). Collapsing `datetime` onto the `date` control did not
-     * merely under-render it — `<input type="date">` hands back a bare
-     * `YYYY-MM-DD` on change, so touching the day of a `datetime` cell silently
-     * DELETED its time component from the record.
-     */
-    type?: 'text' | 'number' | 'currency' | 'date' | 'datetime' | 'time' | 'select' | 'lookup' | 'file';
-    options?: Array<{
-        label: string;
-        value: string;
-    }>;
-    width?: number;
-    required?: boolean;
-    prefix?: string;
-    step?: number;
-    /** For `type: 'lookup'` — the referenced object and label/id fields. */
-    reference?: string;
-    displayField?: string;
-    idField?: string;
-    /** Multi-value column: multi-record lookup, or multi-file upload cell. */
-    multiple?: boolean;
-    /** For `type: 'file'` — accepted MIME types / extensions for the picker
-     *  (e.g. `['image/*', '.pdf']`). Omit to accept anything. */
-    accept?: string[];
-    /**
-     * Hidden from the grid by default but revealable via the column chooser.
-     * Set by `deriveColumns` for fields beyond the default-visible budget — the
-     * data is NOT dropped (it's just collapsed, like Odoo's `optional` columns /
-     * Salesforce column personalization), so business-critical fields stay
-     * reachable. Required columns are never default-hidden.
-     */
-    defaultHidden?: boolean;
-    /**
-     * A computed (read-only) column whose value is derived live from sibling
-     * cells via {@link expr} — e.g. an invoice line's `amount = quantity *
-     * unit_price`. The grid renders it read-only, recomputes it as the row's
-     * inputs change, and writes the result back into the row so it persists
-     * (and any running total reflects it). The classic spreadsheet pattern used
-     * by QuickBooks / Stripe / NetSuite line grids — nobody types the amount.
-     */
-    computed?: boolean;
-    /** Arithmetic expression for a {@link computed} column. Supports `+ - * / %`,
-     *  parentheses, numeric literals and field refs (`record.qty` or bare `qty`). */
-    expr?: string;
-    /** Decimal places to round a computed numeric/currency result to. */
-    scale?: number;
-    /** For `type: 'lookup'` — when a record is picked, copy its fields into any
-     *  sibling columns of the same name (e.g. a product's unit_price/description).
-     *  On by default for lookup columns; set `false` to disable the auto-fill. */
-    autofill?: boolean;
-    /**
-     * CEL predicate: when TRUE for this row, the cell is **read-only** (B2 field
-     * rules, generalized to grid cells). Evaluated per row against the row as
-     * `record` plus the header as `parent` (so a line locks when
-     * `parent.status == 'paid'` *or* on an intra-row condition like
-     * `record.kind == 'auto'`). Client-side UX; fails open (stays editable).
-     */
-    readonlyWhen?: string | {
-        dialect?: string;
-        source: string;
-    };
-    /**
-     * CEL predicate: when TRUE for this row, the cell is **required** (flagged
-     * inline-invalid while empty). Same `record` + `parent` scope as
-     * {@link readonlyWhen}.
-     */
-    requiredWhen?: string | {
-        dialect?: string;
-        source: string;
-    };
-}
+/**
+ * One grid column — `@objectstack/spec`'s inline grid column
+ * (`InlineGridColumn`, the element of `FieldSchema.inlineColumns`), BY
+ * REFERENCE (objectui#11070). The spec declares that shape as the strict
+ * mirror of this widget's column, so the widget's type IS the spec's: one
+ * declaration, the same one `GridFieldMetadata.columns` and
+ * `FormField.columns` (`@object-ui/types`) carry. This widget reads each
+ * column by exactly the spec's keys — every key below is one the spec
+ * declares, and there is no second spelling of any of them.
+ *
+ * How the widget reads the keys (the spec's own descriptions say what each
+ * MEANS; these are the renderer's notes):
+ *
+ *  - `name` — the key a column reads and writes on each row object. There is
+ *    deliberately no tolerant alias bridging the spelling objectui#3951
+ *    retired to this one: a single spelling, enforced at the producer —
+ *    AGENTS.md #0.1 (the spec refuses the retired spelling by name).
+ *    (Wording note: do not restate that rule as an alternation expression over
+ *    the two key names. `column-identity.ratchet.test.ts` (objectui#3104) scans
+ *    these files line by line and cannot tell prose from code, so spelling the
+ *    shape out here registers as a new dual read and fails the gate.)
+ *  - `type` — the cell control and its read/write adapter. `date` /
+ *    `datetime` / `time` are three DISTINCT controls, not one
+ *    (objectui#3569): `<input type="date">` hands back a bare `YYYY-MM-DD` on
+ *    change, so collapsing `datetime` onto it silently DELETED the time
+ *    component from the record.
+ *  - `prefix` — a symbol shown in a `currency` cell IN PLACE OF the resolved
+ *    currency's own symbol. When absent, the cell shows the symbol of the
+ *    currency it resolves (objectui#10355); there is no default symbol.
+ *  - `defaultHidden` — collapsed into the column chooser, not dropped
+ *    (`deriveColumns` sets it beyond the default-visible budget). Required
+ *    columns are never default-hidden.
+ *  - `computed` + `expr` — a read-only column recomputed live from sibling
+ *    cells by this file's own safe arithmetic evaluator (`+ - * / %`,
+ *    parentheses, numeric literals, `record.qty` or bare `qty`), and written
+ *    back into the row so it persists and any running total reflects it.
+ *  - `scale` — decimal places for a computed `number` result. ⛔ Not read on
+ *    a `currency` column (objectui#10783): the resolved currency's ISO 4217
+ *    minor unit decides both the stored and the shown width
+ *    (`currencyWidth`), and the spec refuses `scale` on a column declaring
+ *    `type: 'currency'`. A column that takes `currency` from its child field
+ *    at render time is reported by `hydrateColumns` in
+ *    `@object-ui/plugin-form` instead of being read in silence.
+ *  - `autofill` — for a `lookup` column: picking a record copies its fields
+ *    into sibling columns of the same name. On unless set `false`.
+ *  - `readonlyWhen` / `requiredWhen` — CEL predicates evaluated per row
+ *    against the row as `record` plus the header as `parent`. Client-side UX;
+ *    a predicate that faults fails open.
+ */
+export type GridColumn = InlineGridColumn;
 type Row = Record<string, any>;
 /** Evaluate an arithmetic `expr` against `row`. null when blank/unparseable. */
 export declare function evalArith(expr: string, row: Row): number | null;
@@ -111,10 +122,15 @@ export declare function evalArith(expr: string, row: Row): number | null;
  * it is unit-testable independent of the picker UI.
  */
 export declare function lookupAutofillPatch(columns: GridColumn[], col: GridColumn, record: any): Row;
-export declare function computeRow(columns: GridColumn[], row: Row): Row;
+/**
+ * @param tenantCurrency the tenant's default currency (`useLocalization()`),
+ *   the resolver's last step for a `currency` column — see
+ *   {@link storedFractionScale}.
+ */
+export declare function computeRow(columns: GridColumn[], row: Row, tenantCurrency?: string): Row;
 /** Sum a numeric column across rows (ignoring blanks/NaN). */
 export declare function sumColumn(rows: Row[], field: string): number;
-export declare function GridField({ value, onChange, field, readonly, disabled, className, onRowExpand, displayMode, onAdd, ...props }: FieldWidgetComponentProps<Row[]> & {
+export declare function GridField({ value, onChange, field, readonly, disabled, className, error, onRowExpand, displayMode, onAdd, ...props }: FieldWidgetComponentProps<Row[]> & {
     /** When provided, each row shows an "expand" button that opens the row in a
      *  full form (the host — e.g. MasterDetailForm — renders the drawer/modal and
      *  writes the edited values back). Lets a "fat" child be edited in a real form

package/dist/widgets/ImageField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * ImageField - Image upload widget with preview thumbnails
  * Supports single and multiple image uploads with drag-and-drop and preview display

package/dist/widgets/LocationField.d.ts

@@ -1,7 +1,34 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { LocationValue } from '@objectstack/spec/data';
+import { FieldWidgetComponentProps } from './types.js';
 /**
- * LocationField - Geographic coordinate input for latitude and longitude
- * Stores location as { latitude, longitude } object and displays as comma-separated pair
+ * The stored shape of a `type: 'location'` value — RE-EXPORTED from
+ * `@objectstack/spec/data`, never re-declared here (objectui#6272).
+ *
+ * `LocationValue` is `z.input` of the spec's `LocationValueSchema`
+ * (`{ lat, lng, altitude?, accuracy? }`), which is what `valueSchemaFor({ type:
+ * 'location' })` validates a stored location against. A second local
+ * declaration under the spec's own name is objectstack#4115's failure class and
+ * is refused by `scripts/check-spec-symbol-derivation.mjs` — it was refused on
+ * the closed PR #6418, which is why this is a bare re-export.
  */
-export declare function LocationField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<any>): React.JSX.Element;
+export type { LocationValue } from '@objectstack/spec/data';
+/**
+ * LocationField - Geographic coordinate input for a `type: 'location'` value.
+ *
+ * Reads and writes `@objectstack/spec`'s `LocationValue` (`{ lat, lng }`) and
+ * displays it as the comma-separated pair a user types. The coordinates are
+ * still called latitude and longitude to a human — only the STORED key names
+ * are the spec's (objectui#6272), which is why the placeholder names the two
+ * coordinates rather than the `lat`/`lng` keys. That is a statement about KEY
+ * NAMES, not about language: the placeholder's words are the reader's, from
+ * the locale packs (objectui#8149, {@link placeholderPair}).
+ *
+ * ⚠️ BREAKING (objectui#6272): a record stored in the deprecated
+ * `{ latitude, longitude }` spelling — including one this widget itself wrote
+ * before the flip — now renders EMPTY here until it is re-saved or fixed at the
+ * data layer. It keeps rendering correctly in detail views and on the map,
+ * which read the spec spelling first. That cost was presented and accepted as
+ * part of the A1 ruling; it is not an oversight to route around with a shim.
+ */
+export declare function LocationField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<LocationValue | null>): React.JSX.Element;

package/dist/widgets/LookupField.d.ts

@@ -1,8 +1,16 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 export interface LookupOption {
     value: string | number;
     label: string;
+    /**
+     * Secondary text: searched by the popover typeahead alongside the label, and
+     * rendered as supporting text. For AUTHORED static options this is the
+     * declared `SelectOptionMetadata.description` (objectui#6153 — declared
+     * there, and on `@objectstack/spec`'s `SelectOptionSchema`, precisely
+     * because this widget consumes it); for fetched records `recordToOption`
+     * derives it from `descriptionField`.
+     */
     description?: string;
     [key: string]: any;
 }

package/dist/widgets/MasterDetailField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Master-Detail relationship data structure
  */

package/dist/widgets/MultiSelectField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * MultiSelectField - select zero or more values from a fixed option set.
  *

package/dist/widgets/NumberField.d.ts

@@ -1,7 +1,7 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * NumberField - Numeric input with optional decimal precision
  * Supports min/max/step constraints and configurable decimal precision
  */
-export declare function NumberField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;
+export declare function NumberField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;

package/dist/widgets/ObjectField.d.ts

@@ -1,7 +1,14 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
- * ObjectField - JSON object editor
- * Allows editing structured JSON data
+ * ObjectField - JSON editor for a structured value.
+ *
+ * The form face of the free-form JSON types: `object`, `composite`, `record`, and
+ * since objectui#11448 `json`, which used to alias the raw-text code editor and
+ * so showed a stored object as `[object Object]` and saved an edit as a string.
+ * A json value need not be an object — an array, a number, a string, a boolean
+ * and `null` are all JSON — and this editor shows and parses each of them as
+ * itself: the box holds `JSON.stringify(value, null, 2)` and an edit emits
+ * `JSON.parse(text)`.
  */
 export declare function ObjectField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<any>): React.JSX.Element;