@object-ui/fields 17.5.0 → 17.6.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,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

@@ -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,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,7 +47,7 @@ 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? }
+ *   { name, label?, type?, options?, width?, required?, prefix?, step? }
  *   type ∈ 'text' | 'number' | 'currency' | 'date' | 'datetime' | 'time'
  *        | 'select' | 'lookup' | 'file'
  *
@@ -18,7 +55,22 @@ import { FieldWidgetComponentProps } from './types';
  *   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;
     /**
      * Cell control + read/write adapter for the column.
@@ -114,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,5 +1,5 @@
 import { default as React } from 'react';
-import { HostGroupProps } from './toHostGroupProps';
+import { HostGroupProps } from './toHostGroupProps.js';
 /**
  * The "this option list cannot be filled" state shared by every fixed-option
  * widget (`SelectField` single, `MultiSelectField`, `RadioField`,
@@ -46,13 +46,19 @@ export interface OptionsEmptyStateProps {
      * 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.
+     * 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 three-key type rather than an open props tail: only `id`,
-     * `aria-labelledby` and the `role` that makes them meaningful may reach this
-     * element, and reopening a spread is what objectui#3291 exists to prevent.
-     * 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.
+     * 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;
 }

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

package/dist/widgets/PercentField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * PercentField - Percentage input with configurable decimal precision
  * Stores values as decimals (0-1) and displays as percentages (0-100%)

package/dist/widgets/PhoneField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * PhoneField - Telephone number input with tel link in readonly mode
  * Renders as a clickable tel link when readonly, standard phone input otherwise

package/dist/widgets/QRCodeField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * QR Code field widget - generates QR codes from text
  * Uses a simple SVG-based QR code generator

package/dist/widgets/RadioField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * RadioField - choose exactly one value from a fixed option set, rendered as a
  * radio group. The stored value is the selected option value (string). Used for

package/dist/widgets/RatingField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Rating field widget - provides a star rating input
  * Supports numeric values from 0 to max (default 5)

package/dist/widgets/RecipientPickerField.d.ts

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

package/dist/widgets/RecordPickerDialog.d.ts

@@ -1,13 +1,11 @@
 import { default as React } from 'react';
 import { DataSource, LookupColumnDef, LookupFilterDef } from '@object-ui/types';
+import { LookupCellRendererResolver } from './lookupColumnDisplay.js';
 /**
  * Cell renderer function signature — matches getCellRenderer from @object-ui/fields.
  * Accepts a field type and returns a React component that renders a formatted cell.
  */
-export type CellRendererResolver = (fieldType: string) => React.FC<{
-    value: any;
-    field: any;
-}>;
+export type CellRendererResolver = LookupCellRendererResolver;
 /**
  * Filter column definition used by the inline filter bar.
  * A subset of LookupColumnDef enriched with filter-specific metadata.

package/dist/widgets/RichTextField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Rich text field with markdown/HTML support
  * For now, this is a simple textarea. A full implementation would use
@@ -22,5 +22,41 @@ import { FieldWidgetComponentProps } from './types';
  * tolerant fallback in one of them. The affordance and dialog themselves come
  * from the shared `FullscreenFieldEditor`, so one form-level setting keeps
  * producing one behaviour across both widgets.
+ *
+ * ## Readonly display (objectui#5498)
+ *
+ * The readonly early return used to render `{value}` as a React TEXT CHILD,
+ * so a readonly field of any of the three types showed the user the markup
+ * SOURCE of their own content — a `markdown` field's asterisks and hashes, a
+ * `richtext` field's tags. The `prose` classes on that wrapper were the tell:
+ * they exist to style RENDERED rich content and there was none to style. Every
+ * other read surface — grid, kanban card, gallery, related list, dashboard
+ * record panel, record detail read mode — dispatches through `getCellRenderer`
+ * and renders the same stored bytes FORMATTED, so one field disagreed with
+ * itself depending on which surface it was read on, and this branch was the
+ * one disagreeing with the platform.
+ *
+ * It now renders through {@link richTextCellRenderer} — literally the same
+ * components `getCellRenderer` resolves, one table shared by both (see
+ * `./richTextDisplay.tsx`), so the html/richtext path carries that renderer's
+ * `sanitizeHtml` trust boundary rather than a second hand-rolled escape, and a
+ * future change to either pipeline moves both surfaces at once.
+ *
+ * ## Host plumbing (objectui#4810)
+ *
+ * The editable branch had no `toDomProps` at all, so everything
+ * `<FormControl>`'s Radix `Slot` hands down — the field's `id`, the
+ * `aria-describedby` naming its `<FormDescription>` and `<FormMessage>` —
+ * arrived as props and landed on no element. Measured on a real form: the
+ * visible label's `for` pointed at an id nothing carried (`for=DANGLING`) and
+ * the rendered description had zero consumers, for all three registry keys
+ * (`markdown` / `html` / `richtext`) since they are this one widget.
+ *
+ * The fix is objectui#3318's standing recipe — `toDomProps(props)` spread onto
+ * the REAL focusable control, which here is the `<Textarea>` inside
+ * `RichTextEditorSurface`, never the wrapper `<div>`s (a non-focusable wrapper
+ * carrying the id would satisfy `document.getElementById` and still leave the
+ * label inert). Only the inline surface receives it; see `domProps` there for
+ * why the dialog's copy must not.
  */
 export declare function RichTextField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/SelectField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * SelectField - dropdown selection widget.
  *

package/dist/widgets/SignatureField.d.ts

@@ -1,7 +1,37 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Signature field widget - provides a signature pad for capturing signatures
  * Outputs signature as a base64 PNG image
+ *
+ * ## Naming, and the half that is deliberately absent (objectui#3318)
+ *
+ * This widget forwarded nothing a host handed it — every branch below wrote its
+ * attributes by hand — so its visible label pointed `for` at an id no element
+ * in the row carried, and the rendered help text had zero consumers. Measured
+ * on `origin/main`, a real form, this field required and freshly failed:
+ *
+ * ```
+ * signature  labelFor=…-form-item -> DANGLING  descConsumers=0  ids=[]
+ * ```
+ *
+ * The name and the description arrive here, on the container, through
+ * {@link toHostGroupProps} — the objectui#3961 route for a widget whose surface
+ * no `<label for>` can reach (`<canvas>` is not a labelable element), and which
+ * therefore declares `labelling: 'group'` in `FIELD_WIDGET_LABELLING`.
+ * `'instead-of-the-inputs'` because this field renders no input of its own for
+ * the description to land on: the Clear button is auxiliary — it acts on the
+ * value, it is not the value's control — the same reading that put
+ * `geolocation`'s focusable "View on map" link on that side of the split.
+ *
+ * `aria-invalid` and `aria-required` are NOT here, and their absence is a
+ * verdict rather than an omission. The drawing surface has no keyboard path at
+ * all (measured: this row offers zero focusable elements while empty — the only
+ * candidate, Clear, is `disabled` until something has been drawn), so there is
+ * no element assistive technology would read a control state from. Marking the
+ * container instead would announce a state with no control behind it — the
+ * non-focusable-wrapper move objectui#3291 and #3318 both draw the line
+ * against. The type is recorded in that sweep's NOT_APPLICABLE ledger with a
+ * guard that turns red the day a real control appears here.
  */
-export declare function SignatureField({ value, onChange, readonly }: FieldWidgetComponentProps<string>): React.JSX.Element;
+export declare function SignatureField({ value, onChange, readonly, ...props }: FieldWidgetComponentProps<string>): React.JSX.Element;

package/dist/widgets/SliderField.d.ts

@@ -1,7 +1,42 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * Slider field widget - provides a range slider input
  * Supports numeric values with configurable min, max, and step
+ *
+ * ## Where the host's facts go, and why (objectui#3318)
+ *
+ * This widget used to read exactly two keys off its props (`disabled`,
+ * `className`) and forward nothing else, so everything `<FormControl>`'s Slot
+ * delivered was dropped on the floor. Measured on `origin/main`, a real form
+ * with a required slider that had just failed validation:
+ *
+ * ```
+ * ariaInvalidTrue=[]   labelFor=…-form-item -> DANGLING
+ * descConsumers=0      ids=[]   <- no element of the row carried an id at all
+ * ```
+ *
+ * Three channels, one cause. The DOM pass-through now goes to the THUMB — the
+ * `span[role="slider"]` a keyboard user lands on, which is where ARIA state
+ * belongs — through the `thumbProps` the primitive grew for this
+ * (`lib/slider-thumb.ts`; the shadcn `ui/slider.tsx` renders its thumb
+ * internally and exports only `Slider`, so it cannot be addressed from here
+ * the way objectui#3306 addressed `SelectTrigger`).
+ *
+ * The split of which keys stay on Root is `SelectField`'s, key for key:
+ *
+ * - `name`: Root owns the hidden input that takes part in form submission; on
+ *   a `span` it is not even DOM-legal, and is exactly the leak objectui#3291
+ *   sweeps for.
+ * - `disabled`: Root is the single authority (it disables the thumb and the
+ *   hidden input together); forwarding the raw prop to the thumb as well would
+ *   give the state a second, OR-merged author.
+ *
+ * The visible label reaches the thumb by IDREF, not by `for`: a
+ * `span[role="slider"]` is not one of HTML's labelable elements, so this widget
+ * is declared `labelling: 'group'` for the same reason `file` is — see
+ * `FIELD_WIDGET_LABELLING` in `../index` and objectui#3961. No extra
+ * `role="group"` wrapper: there is one control here, and `slider` is a role
+ * that carries a name perfectly well on its own.
  */
-export declare function SliderField({ value, onChange, field, readonly, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;
+export declare function SliderField({ value, onChange, field, readonly, error, ...props }: FieldWidgetComponentProps<number>): React.JSX.Element;

package/dist/widgets/SummaryField.d.ts

@@ -1,5 +1,5 @@
 import { default as React } from 'react';
-import { FieldWidgetComponentProps } from './types';
+import { FieldWidgetComponentProps } from './types.js';
 /**
  * SummaryField - Read-only aggregation field
  * Values are aggregated from related records and cannot be edited