@object-ui/fields 17.3.0 → 17.6.0

package/dist/widgets/AddressField.d.ts

@@ -1,17 +1,9 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
-/**
- * Address data structure
- */
-export interface AddressValue {
-    street?: string;
-    city?: string;
-    state?: string;
-    zipCode?: string;
-    country?: string;
-}
+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, zip code, and country
+ * Supports street, city, state, postal code, and country
  */
 export declare function AddressField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<AddressValue>): React.JSX.Element;

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,5 +1,5 @@
 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

package/dist/widgets/BooleanField.d.ts

@@ -1,5 +1,5 @@
 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

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,5 +1,5 @@
 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

package/dist/widgets/DateTimeField.d.ts

@@ -1,5 +1,5 @@
 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

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,11 +1,38 @@
 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#4023,
+ * 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.
+ *
+ *   - `containsCaseInsensitive` authors `$icontains`, executable on every
+ *     driver and evaluation face the platform ships (objectstack#5702 +
+ *     objectstack#6520).
+ *   - `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).
+ *
+ * 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,

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

@@ -1,155 +1,52 @@
 import { default as React } from 'react';
+import { FullscreenEditorProps } from '@object-ui/components';
 /**
- * The fullscreen-edit affordance shared by every long-text widget: the "expand"
- * button plus the full-height dialog it opens.
- *
- * ## Why this is shared rather than copied
- *
- * `ObjectFormSchema.mobile.fullscreenLongText` is ONE form-level promise, and
- * `ObjectForm` projects it onto EVERY long-text field as `mobile_fullscreen`
- * (`field:textarea` → `TextAreaField`, `field:markdown` / `field:html` →
- * `RichTextField`). A user who turns the setting on gets one behaviour, so the
- * behaviour has one implementation. objectui#3301 is what the other
- * arrangement costs: the flag reached `RichTextField` for as long as the
- * feature has existed and that widget simply never read it, so half the
- * documented promise ("textarea/rich-text get an expand button") silently did
- * nothing. A second hand-written copy of the state machine is the same failure
- * with an extra step — it drifts, and nothing reports the drift.
- *
- * What is genuinely per-widget is the EDITOR, so that is the only thing
- * injected: `children` renders it against the draft. Everything a user can
- * observe about the *interaction* — when the affordance appears, that the
- * dialog seeds from the committed value, that typing stays local until "Done",
- * that "Cancel" discards — lives here, once.
- *
- * ## Draft semantics (unchanged from the original `TextAreaField` behaviour)
- *
- * The dialog edits a LOCAL draft seeded from `value` at open time and commits
- * once, on "Done". It deliberately does not stream every keystroke to the host:
- * these widgets sit in a react-hook-form field, and per-keystroke `onChange`
- * during a modal edit would mark the form dirty (and fire validation) for an
- * edit the user may still cancel. "Cancel" therefore needs no undo — nothing
- * was written.
- *
- * ## `disabled` (objectui#3402)
- *
- * The dialog is a SECOND editing surface for the same value, so a field that is
- * not interactive has to be not interactive here too. It was not: hosts landed
- * `disabled` on their inline control only, this component never declared the
- * prop at all, and a disabled long-text field therefore sat correctly greyed out
- * next to a live expand button — click it, type anything, press "Done", and the
- * edit went into form state through `onCommit`. Measured on `origin/main`
- * before the fix: inline `disabled=true`, toggle `disabled=false`, dialog input
- * `disabled=false`, `onChange` called with "EDITED WHILE DISABLED".
- *
- * The gate is shaped like the built-in path's (`FullscreenTextarea` in
- * `components/src/renderers/form/form.tsx`, objectui#3400/PR #3401), because
- * one form-level setting must keep producing one behaviour on both paths:
- *
- *  - the toggle STAYS but is `disabled` — `disabled` means "not interactive,
- *    muted", not "shown plainly", which is `readonly`'s job (and `readonly`
- *    never reaches this component at all — see below);
- *  - `openFullscreen` refuses independently of the attribute, since a
- *    programmatic dispatch and a lost `pointer-events` rule both get past it;
- *  - the dialog locks on its OWN — `disabled` is not merely a static flag, it is
- *    also the form's `isSubmitting`, which flips to true while the dialog may
- *    already be open. At that moment the toggle is no longer the gate. So the
- *    editor is told (third `children` argument) and "Done" is disabled;
- *  - and `onCommit` is gated, because that is the single point where a value can
- *    leave this component for host state. Nothing native guards it: it is a
- *    click handler on a different control reading React state.
- *
- * "Cancel" and `Esc` stay live in every state — a dialog that goes disabled
- * mid-edit must still be closable, or a submit in flight traps the user in it.
- *
- * ## Why there is no `readonly` prop
- *
- * Both hosts early-return a read-only DISPLAY before they compute the affordance
- * (`TextAreaField.tsx`, `RichTextField.tsx`), so this component is never
- * rendered for a read-only field and a `readonly` prop here would be declared
- * with no producer — the shape this package keeps deleting (objectui#3232/#3233).
- * A future host that renders an editor for read-only fields must add the prop
- * AND the producer together; do not add it "for symmetry" beforehand.
- *
- * ## `testIdPrefix`
- *
- * Each host passes its own (`textarea`, `richtext`), yielding the same
- * convention with a per-widget namespace: `<prefix>-fullscreen-toggle` /
- * `-dialog` / `-save`. One form can contain both a textarea and a markdown
- * field, so a single shared id would make a test unable to say which widget it
- * had found. The editor's own test id belongs to `children` for the same
- * reason.
- *
- * ## Copy (objectui#3404)
- *
- * Every string here goes through `useFieldTranslation()` and consumes the
- * EXISTING `form.fullscreen.*` / `common.cancel` keys — the same ones the
- * built-in branch consumes since objectui#3272. Nothing was missing from the
- * ten locale packs; this path simply never read them, so a zh session opened a
- * dialog reading `Cancel` / `Done` while a long-text field rendered by the
- * built-in branch **in the same form** read 「取消 / 完成」.
- *
- * Sharing the keys rather than minting `fields.fullscreen.*` twins is the
- * point: one form-level setting (`mobile.fullscreenLongText`) projects onto
- * both render paths, so two copies of this copy could only drift.
- *
- * `useFieldTranslation` (not bare `useObjectTranslation`) because this widget
- * is rendered without an `I18nProvider` by standalone/embedded hosts and by
- * every bare-render test in this package. Measured before the change: with no
- * provider mounted `useObjectTranslation().t('common.cancel')` returns
- * `"common.cancel"` — the raw key — and the `{{label}}` interpolation collapses
- * entirely. The safe hook's English defaults are byte-identical to the literals
- * they replaced, so the provider-less rendering is unchanged.
- *
- * Focus management, `Esc`, the overlay and the close button are Radix's, via
- * the repo's `Dialog` (`@object-ui/components`) — deliberately not re-answered
- * here.
+ * The fullscreen-edit affordance shared by every long-text widget in this
+ * package (`field:textarea` → `TextAreaField`, `field:markdown` / `field:html`
+ * → `RichTextField`).
+ *
+ * ## This is now a thin wrapper (objectui#3398)
+ *
+ * The affordance, the dialog, the draft/commit state machine and the
+ * `readOnly` / `disabled` semantics all live in `FullscreenEditor`
+ * (`@object-ui/components`). They used to live here AND, separately, in the
+ * form renderer's built-in `textarea` branch — one form-level promise
+ * (`ObjectFormSchema.mobile.fullscreenLongText`, projected onto every long-text
+ * field as `mobile_fullscreen`) answered twice, on the two render paths.
+ *
+ * Two copies of a state machine drift, and these did: objectui#3400 measured a
+ * read-only field editable through the built-in branch's dialog, objectui#3402
+ * measured the same hole for `disabled` here, and #3393 (label in the dialog
+ * title) and #3272 (i18n) each landed on one side before the other. The
+ * maintainer's ruling of 2026-08-10 was one implementation hoisted to the
+ * dependency-legal side — and the measured import graph allows exactly that
+ * direction: this package depends on `@object-ui/components`, which declares no
+ * dependency on `@object-ui/fields` in `dependencies` or `peerDependencies`.
+ *
+ * ## Why the wrapper survives the merge rather than being deleted
+ *
+ * It carries the one thing that is genuinely about THIS package: `readOnly` is
+ * not part of the contract here. Both hosts early-return a read-only DISPLAY
+ * before they compute the affordance (`TextAreaField.tsx`, `RichTextField.tsx`),
+ * so a `readOnly` reaching this component would be a prop with no producer on
+ * this path — the shape this package keeps deleting (objectui#3232/#3233). The
+ * `Omit` below is that statement in the type system, and it is why the hoist did
+ * not simply re-export the primitive. A future host that renders an editor for
+ * read-only fields must widen this type AND pass the prop together; the
+ * primitive already answers it (no affordance at all).
+ *
+ * Everything else — `value` / `onCommit` / `label` / `testIdPrefix` /
+ * `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.
  */
-export interface FullscreenFieldEditorProps {
-    /**
-     * The committed value. Seeds the draft each time the dialog opens — read at
-     * open time, not held, so a value that changes underneath while the dialog is
-     * closed is picked up on the next open.
-     */
-    value: string;
-    /** Called once with the draft when the user confirms. */
-    onCommit: (next: string) => void;
-    /** Field label — the dialog title and part of the toggle's accessible name. */
-    label?: string;
-    /** Namespace for this widget's fullscreen test ids. See above. */
-    testIdPrefix: string;
-    /**
-     * The host field is not interactive (objectui#3402). Disables the toggle, the
-     * "Done" button and the write-back, and is handed to `children` so the host's
-     * own editor renders disabled too. See the `disabled` section above for why
-     * each of those is a separate line rather than belt-and-braces.
-     *
-     * **Producer**: the widget's `disabled` prop, which the form renderer computes
-     * as `disabled || fieldDisabled || isSubmitting || optionGroupGated` and
-     * forwards to registered widgets (`stripRegisteredFieldProps` does not strip
-     * it).
-     */
-    disabled?: boolean;
-    /**
-     * The editor itself, rendered inside the dialog body against the draft. The
-     * host passes the SAME editor it renders inline, so "fullscreen" is a size
-     * change rather than a second, poorer editing surface.
-     *
-     * The third argument is this component's `disabled`, and the host is expected
-     * to put it on the control it renders: only the host knows which element its
-     * editor's disabled state belongs on. Ignoring it is not a write-back hole —
-     * `onCommit` is gated here regardless — but it does leave a control that looks
-     * editable while the field is not, so both in-repo hosts apply it and their
-     * tests pin it.
-     */
-    children: (draft: string, setDraft: (next: string) => void, disabled: boolean) => React.ReactNode;
-    /** Optional footer status for the draft (e.g. a character counter). */
-    footer?: (draft: string) => React.ReactNode;
-    /**
-     * Extra classes for the toggle button. It is absolutely positioned by
-     * default and expects a `relative` ancestor; a host whose layout has a
-     * better home for it can re-place it here.
-     */
-    toggleClassName?: string;
-}
-export declare function FullscreenFieldEditor({ value, onCommit, label, testIdPrefix, disabled, children, footer, toggleClassName, }: FullscreenFieldEditorProps): React.JSX.Element;
+export type FullscreenFieldEditorProps = Omit<FullscreenEditorProps, 'readOnly'>;
+export declare function FullscreenFieldEditor(props: FullscreenFieldEditorProps): React.JSX.Element;

package/dist/widgets/GeolocationField.d.ts

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

package/dist/widgets/GridField.d.ts

@@ -1,8 +1,45 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * 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
@@ -10,16 +47,41 @@ import { FieldWidgetComponentProps } from './types';
  * 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' | 'select' | 'lookup' | 'file'
+ *   { name, label?, type?, options?, width?, required?, prefix?, step? }
+ *   type ∈ 'text' | 'number' | 'currency' | 'date' | 'datetime' | 'time'
+ *        | 'select' | 'lookup' | 'file'
  *
  * Field-level config (from `GridFieldMetadata`):
  *   columns, min_rows, max_rows, allow_add, allow_delete, total_field
  */
 export interface GridColumn {
-    field: string;
+    /**
+     * The column's field name — the key it reads and writes on each row object.
+     *
+     * Spelled `name`, exactly as the declared `GridColumnDefinition`
+     * (`@object-ui/types`) and the grid docs page say (objectui#3951). This
+     * widget used to read a divergent `field` key, so metadata authored against
+     * the published type rendered every cell empty plus a React key warning.
+     * There is deliberately no tolerant alias bridging the retired spelling to
+     * this one: a single spelling, enforced at the producer — AGENTS.md #0.1.
+     *
+     * (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.)
+     */
+    name: string;
     label?: string;
-    type?: 'text' | 'number' | 'currency' | 'date' | 'select' | 'lookup' | 'file';
+    /**
+     * 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;
@@ -104,7 +166,7 @@ export declare function lookupAutofillPatch(columns: GridColumn[], col: GridColu
 export declare function computeRow(columns: GridColumn[], row: Row): 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,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+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

package/dist/widgets/LookupField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 export interface LookupOption {
     value: string | number;
     label: string;

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,5 +1,5 @@
 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

package/dist/widgets/ObjectField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * ObjectField - JSON object editor
  * Allows editing structured JSON data

package/dist/widgets/ObjectRefField.d.ts

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

package/dist/widgets/OptionsEmptyState.d.ts

@@ -1,4 +1,5 @@
 import { default as React } from 'react';
+import { HostGroupProps } from './toHostGroupProps.js';
 /**
  * The "this option list cannot be filled" state shared by every fixed-option
  * widget (`SelectField` single, `MultiSelectField`, `RadioField`,
@@ -41,5 +42,24 @@ export interface OptionsEmptyStateProps {
     testId?: string;
     /** Widget-specific sizing (the dropdown is a fixed `h-9`, lists grow). */
     className?: string;
+    /**
+     * The host label's IDREF plumbing, when this box is the whole rendered surface
+     * of a group-labelled field (objectui#3990) — a `checkboxes` / `radio` /
+     * `multiselect` whose option list came back empty renders NOTHING but this
+     * box, so the visible label named zero elements until it landed here. Its
+     * help text described zero elements for the same reason, which is why the
+     * callers ask `toHostGroupProps` for the `'instead-of-the-inputs'` surface:
+     * there is no option control in this state to announce the description on
+     * (objectui#4005).
+     *
+     * A closed type rather than an open props tail: only `id`, `aria-labelledby`,
+     * `aria-describedby` and the `role` that makes them meaningful may reach this
+     * element, and reopening a spread is what objectui#3291 exists to prevent —
+     * `aria-invalid` / `aria-required` are control-channel state and stay off this
+     * surface. Absent for the single `SelectField` — it is not group-labelled, its
+     * label still uses a plain `for`, and it must keep emitting no such
+     * attributes.
+     */
+    hostGroupProps?: HostGroupProps;
 }
-export declare function OptionsEmptyState({ emptyHint, gated, dependsOnFields, testId, className, }: OptionsEmptyStateProps): React.JSX.Element;
+export declare function OptionsEmptyState({ emptyHint, gated, dependsOnFields, testId, className, hostGroupProps, }: OptionsEmptyStateProps): React.JSX.Element;

package/dist/widgets/PasswordField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * PasswordField - Secure password input with visibility toggle
  * Includes show/hide toggle button and masks value in readonly mode