diff --git a/.changeset/aria-required-reaches-the-control.md b/.changeset/aria-required-reaches-the-control.md
deleted file mode 100644
index 40a226d10d..0000000000
--- a/.changeset/aria-required-reaches-the-control.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-"@object-ui/components": patch
----
-
-The required state now reaches the input control as `aria-required`, instead of
-existing only as part of the control's accessible name (objectui#3290).
-
-The form renderer has always computed a correct `required` — the static
-`required` flag merged with the `requiredWhen` CEL verdict — and then spent it
-on exactly one thing: the red asterisk in `<FormLabel>`. That asterisk carried
-`aria-label="required"`, so the only path from the computed state to assistive
-tech was `<label for>` folding it into the control's **accessible name**: the
-field was announced as "Title required".
-
-A state smuggled through a name is broken three ways:
-
-- it is read in name order rather than announced as a state, and "list the
-  required fields" style navigation cannot see it at all;
-- a field rendered without a `label` (compact layouts, inline grid editing)
-  draws no asterisk, so the signal disappears entirely;
-- `requiredWhen` makes required **dynamic**, and a state channel can express
-  the flip where a name cannot.
-
-## What changed
-
-- Every field control — built-in (`input` / `textarea` / `checkbox` / `switch` /
-  `select`) and registered widget alike — now receives `aria-required="true"`
-  when the field resolves required, and **no attribute at all** when it does
-  not. Absence rather than `aria-required="false"` is deliberate: it is what
-  the `requiredWhen`-turns-false case has to produce.
-- The red asterisk is now `aria-hidden="true"` and no longer carries
-  `aria-label="required"`. It renders exactly as before for sighted users; it
-  simply stops being announced, so the state is reported once (as a state) and
-  not twice.
-
-**No field widget needed a change.** `aria-required` is already declared and
-typed on the widget props contract (`FieldWidgetComponentProps &
-AriaAttributes`) and every widget forwards its leftover props to the control it
-renders, so all 48 widgets pick it up unmodified.
-
-Two non-changes, both deliberate:
-
-- **No native `required` attribute.** That would arm the browser's own
-  constraint-validation bubble alongside react-hook-form's `<FormMessage/>` —
-  two validators, two UIs, one field. `aria-required` reports the state without
-  triggering native validation.
-- **No `required` boolean in the widget props contract.** A boolean would give
-  the required marker a second author, and the next widget draws its own
-  asterisk next to the renderer's — the double-display failure objectui#3222
-  already declined for the validation message.
-
-If you select the asterisk in a test, it is now
-`span[data-required-marker]` — an explicit locator, rather than an
-accessibility attribute doubling as a test hook.
diff --git a/.changeset/builtin-select-empty-state-translated.md b/.changeset/builtin-select-empty-state-translated.md
deleted file mode 100644
index aeff8e5ab7..0000000000
--- a/.changeset/builtin-select-empty-state-translated.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-"@object-ui/components": patch
----
-
-The form renderer's built-in `select` branch stops saying "No options available"
-in English to non-English sessions (objectui#3263).
-
-FROM: the inline branch that renders a `type: 'select'` field — the one taken
-whenever the field is a `BUILTIN_FIELD_TYPES` member, i.e. before the `field:`
-registry is consulted — rendered `{emptyHint || 'No options available'}`. TO:
-`{emptyHint || t('fields.options.empty')}`, the same i18n key the registered
-option widgets fall back to (objectui#3231, all ten locale packs).
-
-This was the last hardcoded copy of that sentence in `form.tsx`, and the file was
-half-translated in a way a user could see inside one widget: the dependency-gate
-sentence next to it already went through `t()`
-(`fields.options.selectFirst`), so under a `zh` session a gated select read
-"请先选择Country" and the same select — one keystroke later, when the parent
-value matched no option — flipped to English.
-
-`fields.options.empty` is added to `useSafeFormTranslation`'s defaults map, the
-pattern `fields.options.selectFirst` already follows there, so a form rendered
-with no `I18nProvider` (standalone widget, test, embedded form) produces the
-byte-identical English string it produced before. Both halves are pinned by
-tests: the Chinese rendering in one file, the no-provider English fallback in
-another (mounting a provider installs it as react-i18next's global default,
-which would erase the state the second one observes).
-
-The box moved from an inline `<div>` into a small `BuiltinSelectEmptyState`
-component in the same file, because `renderFieldComponent` is a plain helper that
-early-returns on the registered-widget path — a hook called there would run
-conditionally. It forwards its rest props, since `<FormControl>` is a Radix
-`Slot` that supplies the control's `id` / `aria-describedby`; a test pins that
-the field's `<label for>` still resolves to this box.
-
-Deliberately NOT unified with `@object-ui/fields`' `OptionsEmptyState`: different
-package, different render path (inline branch vs. registry). What the two share
-is the i18n key, not a component — merging them would impose one path's markup
-and props on the other.
diff --git a/.changeset/field-widget-error-slot-follows-spec.md b/.changeset/field-widget-error-slot-follows-spec.md
deleted file mode 100644
index 0dc5c00553..0000000000
--- a/.changeset/field-widget-error-slot-follows-spec.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-"@object-ui/fields": minor
-"@object-ui/components": minor
----
-
-Field widgets are finally told when their field fails validation, and the props
-slot that carries it takes the name the published contract gives it
-(objectui#3222).
-
-**Breaking** for anyone implementing a field widget (see migration below). The
-repo version policy keeps this a `minor` — objectui's major tracks
-`@objectstack`'s — so read the bump as "breaking within objectui".
-
-## The a11y defect this fixes
-
-`@objectstack/spec/ui`'s `FieldWidgetPropsSchema` — the published contract that
-third-party and AI-authored field widgets are written against — has always
-declared `error?: string`. `@object-ui/fields` declared its own slot as
-`errorMessage`. That looked like a naming split; it was worse:
-
-```
-producers of `errorMessage` anywhere in packages/ + apps/ :  0
-reads of `errorMessage` in packages/fields/src            : 15  (7 widgets)
-reads of `props.error`                                    :  0
-```
-
-The slot was dead under BOTH spellings. No host ever passed it: the form
-renderer showed validation text through its own `<FormMessage/>` and never
-forwarded the prop. So `EmailField`, `CurrencyField`, `UrlField`,
-`RichTextField`, `PercentField`, `TextAreaField` and `PhoneField` each computed
-`aria-invalid={!!errorMessage}` from a value that was `undefined` forever —
-**`aria-invalid` had never once been set, and a screen reader was never told
-the field had failed validation.**
-
-Worse than "never set": `<FormControl>` is a Radix `Slot` that hands its child a
-CORRECT `aria-invalid`, but a widget's own attribute is written after the props
-spread, so it wins. Those seven widgets were actively overwriting the right
-answer with `false`.
-
-FROM: `renderFieldComponent` received no validation state, and the widget props
-type declared `errorMessage?: string`, which nothing produced.
-TO: the form renderer passes react-hook-form's `fieldState.error?.message` down
-as `error` when it renders a registered widget, and the props type declares
-`error?: string`. Both ends of the contract are live for the first time; a
-rename alone would only have swapped one dead key for another.
-
-## Migration for widget authors
-
-```diff
--export function MyField({ value, onChange, field, readonly, errorMessage }: FieldWidgetComponentProps< string >) {
--  return <Input value={value} aria-invalid={!!errorMessage} />;
-+export function MyField({ value, onChange, field, readonly, error }: FieldWidgetComponentProps< string >) {
-+  return <Input value={value} aria-invalid={!!error} />;
-```
-
-No alias is kept. `errorMessage` was retained nowhere on purpose — a tolerant
-second spelling is exactly the de-facto second contract AGENTS.md #0.1 forbids,
-and it is what would let a missed call site go quiet again. Because
-objectui#3221 had already removed the type's `[key: string]: any`, every missed
-site is a compile error rather than a silent `any`, so the compiler — not grep
-— validated this rename.
-
-## Responsibilities are split, not duplicated
-
-The widget consumes `error` **only** to drive `aria-invalid` on the control it
-renders (which only it can do — `aria-invalid` has to sit on the input element).
-The message TEXT stays with `<FormMessage/>` in the form renderer. A widget that
-also renders the text double-displays it, and the docs, the agent prompt and the
-tests all now say so.
-
-For the same reason `required` — also declared by the spec, also never delivered
-— is deliberately NOT lowered into widget props: the required marker has exactly
-one author, the renderer's `<FormLabel>`, and giving widgets the flag invites a
-second asterisk. The a11y state a widget could legitimately carry is
-`aria-required`, which needs no contract change at all (`AriaAttributes` is
-already part of the type and widgets already forward it).
-
-Builtin field types are unaffected: they render inside `<FormControl>`, whose
-Slot already supplies `aria-invalid`, so `error` is stripped there rather than
-leaking into the DOM as a stray attribute.
-
-Docs updated to match: `content/docs/guide/plugin-development.md`,
-`skills/objectui/guides/plugin-development.md` and
-`.github/prompts/component.prompt.md` — the last of which additionally used the
-spec's non-generic type alias as a generic (`FieldWidgetProps< number >`) and
-destructured a `mode` prop that exists on neither type.
diff --git a/.changeset/field-widget-single-metadata-carrier.md b/.changeset/field-widget-single-metadata-carrier.md
deleted file mode 100644
index 6bb7cebefd..0000000000
--- a/.changeset/field-widget-single-metadata-carrier.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-"@object-ui/fields": minor
-"@object-ui/components": minor
----
-
-**BREAKING (v17)** — field widgets receive their metadata on ONE key, `field`.
-`schema` is removed from the widget contract (objectui#3233).
-
-## What changed
-
-`schema` was a second carrier for what `field` already means. Two producers fed
-it: `SchemaRenderer` passed the authored node as `schema`, and the form
-renderer's `renderFieldComponent` passed `schema={props.field || props.schema ||
-props}` *alongside* `field`. The predictable result was ~30 widgets resolving
-their config as `field || schema` — one concept, two spellings, a de-facto
-second contract (AGENTS.md #0.1).
-
-- `FieldWidgetComponentProps` no longer declares `schema`. Reading
-  `props.schema` is now a compile error, not a silent `any`.
-- Both producers converged. The form renderer passes `field` only. The SDUI node
-  → `field` translation happens exactly once, in a new registration adapter
-  (`withFieldCarrier`), which every built-in field widget is registered through.
-- All `field || schema` reads in `@object-ui/fields` are now plain `field` reads.
-
-## Migrating a widget you wrote
-
-**Reading the metadata** — replace the fallback with the single key:
-
-```diff
--const config = field || (props as any).schema;
-+const config = field;
-```
-
-**Registering a widget** — if your widget can be rendered from a schema node
-(anything `SchemaRenderer` dispatches, not just forms), wrap it once so it still
-gets `field`:
-
-```diff
-+import { withFieldCarrier } from '@object-ui/fields';
-+
--ComponentRegistry.register('color', ColorField, { namespace: 'field' });
-+ComponentRegistry.register('color', withFieldCarrier(ColorField), { namespace: 'field' });
-```
-
-`withFieldCarrier` forwards the node **by reference** — nothing is copied,
-narrowed or renamed — and consumes `schema` so it cannot reach the DOM through a
-widget's `...props` spread.
-
-A third-party widget that still reads `props.schema` and is **not** re-registered
-through the adapter will read `undefined` in v17 and silently render an empty /
-default state. That is the deliberate cost of a major boundary: one contract
-beats N dialects, and a widget that picks the wrong spelling should fail at
-compile time rather than work under one host and not another.
-
-## What did NOT change
-
-- **Host metadata (SDUI JSON) is untouched.** No authored schema changes; this is
-  a change to how widgets are *written*, not to what apps declare.
-- **`schema` is still the universal SDUI prop** every registered component
-  receives from `SchemaRenderer` (`element:*`, `page:*`, grids, reports). Only
-  the *field-widget* contract retired it. In particular `renderFieldComponent`
-  still passes `schema` when a form field type resolves to a plain component
-  through the bare-name fallback (e.g. `type: 'text'` reaching the display text
-  widget) — that component's contract is the node, and dropping it there would
-  render `undefined.className`.
-
-## Payload equivalence
-
-Every path that used to deliver a payload through `schema` now delivers the
-identical object through `field`, and both halves are pinned by tests asserting
-**object identity**, not shape:
-
-- form path — `packages/components/src/renderers/form/__tests__/form-field-carrier.test.tsx`
-- SDUI path — `packages/fields/src/__tests__/field-carrier-sdui.test.tsx`
diff --git a/.changeset/flow-node-geometry-is-spec-position.md b/.changeset/flow-node-geometry-is-spec-position.md
deleted file mode 100644
index b61ea0f19b..0000000000
--- a/.changeset/flow-node-geometry-is-spec-position.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-"@object-ui/app-shell": minor
----
-
-The flow designer writes node geometry as the spec's `FlowNode.position`, not its
-own `ui: { x, y }` (objectui#3172).
-
-FROM: dragging, adding-at-a-point and insert-on-edge each wrote `node.ui = {x, y}`
-— a fourth-generation local spelling of a concept `@objectstack/spec` has modelled
-as `FlowNode.position` all along. TO: all three write `position: { x, y }`, and the
-canvas migrates on write: a stored flow's legacy `ui` is lifted onto `position` and
-the key removed in the first patch the canvas emits, geometry-related or not.
-
-**This is a behaviour fix, not a rename.** `FlowNodeSchema` has been `.strict()`
-since objectstack#4001, so `ui` is an `unrecognized_keys` error: the live client
-validation flagged the draft on every keystroke and the server rejected the save
-with a 422. In other words, dragging a node made the flow unsavable — the
-convergence is what makes the designer's most basic gesture round-trip again. A
-test now parses `{ …node, ui: {x, y} }` through the spec's own schema and asserts
-the rejection, so the claim is executed rather than argued.
-
-Reading is backwards-compatible: `manualPosition()` prefers `position` and falls
-back to a legacy `ui`, so a flow stored before this change still opens with its
-nodes exactly where the author left them (pinned by a test that lays out both
-spellings and compares the maps). The fallback is a migration path, not a second
-contract — nothing writes `ui`, and the canvas strips it at its input boundary, so
-no patch can re-emit it.
-
-The geometry type is now derived from the spec by reference
-(`FlowNodePosition = NonNullable< SpecFlowNode['position'] >`), and
-`spec-symbol-parity.test.ts` pins the equality in both directions — including that
-both coordinates are required, so a half-position stays unrepresentable. The
-shape-copy in `FlowPreview.tsx` is gone; it reads the canvas's own node type, the
-way it already read the canvas's edge type.
-
-Breaking for anyone reading `node.ui` off a flow draft: after the author's first
-edit the key is gone and the coordinates live under `node.position`. Nothing in
-this repo or the engine read it — it was a designer-local key the schema rejected.
diff --git a/.changeset/option-widgets-empty-hint-single-source.md b/.changeset/option-widgets-empty-hint-single-source.md
deleted file mode 100644
index 52e98ffcee..0000000000
--- a/.changeset/option-widgets-empty-hint-single-source.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-"@object-ui/components": patch
-"@object-ui/fields": patch
-"@object-ui/i18n": patch
----
-
-The option widgets' "this list cannot be filled" message now has one source, and
-it is translated (objectui#3231).
-
-FROM: `SelectField`, `MultiSelectField`, `RadioField` and `CheckboxesField` each
-carried their own copy of the empty/gated state, each destructured the declared
-`emptyHint` prop into `_emptyHint` and dropped it, and each rendered a hardcoded
-English literal (`'No options available'`, `` `Select ${…} first` ``) even in a
-Chinese or Japanese session. TO: one shared `OptionsEmptyState` — the host's
-`emptyHint` when it supplied one, otherwise a translated fallback
-(`fields.options.empty` / `fields.options.selectFirst`, added to all ten locale
-packs).
-
-`emptyHint` was declared, produced by the form renderer and transported, then
-lost three times over — so no registered widget could ever render it. All three
-breaks are fixed, because closing only the last one delivers nothing:
-
-- `isOptionField` compared the raw resolved type against `'select'` /`'radio'` /
-  `'multiselect'` / `'checkboxes'`. Object-derived forms emit
-  `mapFieldTypeToFormType`'s prefixed ids (`field:select`), which matched none of
-  them, so for every option field coming from an object schema — the normal case
-  in the console — the whole cascade block was skipped and no hint was computed
-  at all. It now normalizes the `field:` prefix, the same normalization
-  `stripRegisteredFieldProps` already applied a few lines below.
-- `stripRegisteredFieldProps` then removed the `emptyHint` key from what was
-  left. It is now forwarded to the four cascade option types, alongside
-  `dependentValues`. This stays an allow-list rather than a blanket
-  pass-through: every other registered widget spreads its leftover props onto a
-  DOM node, where an unknown `emptyHint` attribute is a React warning.
-- the widgets themselves discarded it. Keeping it out of the `...props` spread
-  was correct; not using it afterwards was not.
-
-User-visible effect: a dependency-gated option list now prompts with the
-controlling field's **label** ("Select Country first") instead of its raw
-metadata name, in the session's language; an unconfigured list says so in the
-session's language too. The gate sentence is one i18n key shared by the renderer
-and the widget fallback, so the two sides cannot word it differently.
-
-Untouched: the built-in (unregistered) `select` branch of the form renderer,
-which already consumed `emptyHint`. That is a separate live path.
diff --git a/.changeset/page-block-inspector-visible-when.md b/.changeset/page-block-inspector-visible-when.md
deleted file mode 100644
index d6c1a1697c..0000000000
--- a/.changeset/page-block-inspector-visible-when.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-"@object-ui/app-shell": patch
----
-
-The Page block inspector's conditional-visibility control now authors
-`visibleWhen`, and says "Visible when" while doing it (objectui#3229).
-
-FROM: the `ConditionBuilder` rendered for the selected page block read and wrote
-`block.hidden`. TO: it reads and writes `block.visibleWhen`, the canonical
-conditional-visibility key (ADR-0089), through the same envelope read/write pair
-the hook and action guards use (objectui#3218).
-
-`PageComponentSchema` (`ui/page.zod.ts`) is `.strict()` and has no `hidden` key
-at all. So this was not a tolerant consumer accepting something sloppy — it was
-the **producer emitting a key the contract rejects**: every author who filled
-that box got a save-time parse failure naming a key they never typed, because the
-inspector typed it for them. The spec's own error message already names the fix
-(`` the canonical key is `visibleWhen` ``). A designer that mass-produces drafts
-guaranteed to be rejected is a worse failure than a lenient reader — a lenient
-reader lets wrong metadata run, this made the *correct tool* emit the wrong thing.
-
-The fix also closes the gap in the other direction: a **valid** block carrying
-`visibleWhen` previously had no control in the inspector that could edit its
-visibility, because the only visibility control on screen wrote a different key.
-Removing the control instead would have stopped teaching the wrong key but left
-that gap open, which is a capability regression.
-
-**The semantic flip lands in the UI copy, not just the key.** `hidden` and
-`visibleWhen` are inverses (`hidden` true ⇒ gone; `visibleWhen` true ⇒ shown), so
-the label, the i18n key (`engine.inspector.pageBlock.hidden` →
-`engine.inspector.pageBlock.visibleWhen`) and both language packs move together:
-"Hidden (CEL)" → "Visible when (CEL)", 「隐藏条件（CEL）」→「显示条件（CEL）」.
-Renaming the key while leaving hide-flavoured copy would have been worse than
-leaving the bug: authors would write the predicate backwards, producing metadata
-that PARSES and means the opposite — the objectui#3276 class, which objectui#3257's
-guard is structurally blind to because it only asks whether a draft parses.
-
-**No value is migrated.** An existing `hidden` expression is NOT negated into
-`visibleWhen`: textually negating an arbitrary CEL predicate is unsound
-(`!(a && b)` is not `!a && !b`), and there is no stored valid draft to migrate
-anyway — since ADR-0089 D3a `hidden` is a loud parse failure on save, and before
-D3a the key was silently dropped, so it never reached published metadata either.
-A loud error on a rare stale draft, with the spec's message pointing at
-`visibleWhen`, beats silently rewriting an author's predicate.
-
-Because `visibleWhen` is `ExpressionInputSchema`, a persisted block carries the
-`{ dialect, source }` envelope rather than the authored string, so the control
-goes through `expressionSource` / `writeExpressionSource` — an edit preserves
-`dialect` and `meta` and drops the stale `ast`, instead of flattening the
-envelope to a bare string and silently swapping the evaluation engine.
-
-Tests pin DIRECTION, not just the key name (the objectui#3276 precedent makes
-that a hard requirement): the block the inspector actually commits is rendered
-through `SchemaRenderer` and must appear when its predicate is true and be absent
-when it is false, alongside assertions that the committed key is `visibleWhen`,
-never `hidden`, and that the resulting draft parses.
diff --git a/.changeset/page-header-inputs-declare-subtitle.md b/.changeset/page-header-inputs-declare-subtitle.md
deleted file mode 100644
index 82c5321d13..0000000000
--- a/.changeset/page-header-inputs-declare-subtitle.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-"@object-ui/layout": patch
----
-
-The legacy `page-header` alias stops advertising `description` as an authorable
-key (objectui#3226).
-
-FROM: `registerLayout()` declared `inputs: [title, description]`. TO:
-`inputs: [title, subtitle]` — the key `@objectstack/spec/ui`'s `PageHeaderProps`
-declares, and the one the canonical `page:header` renderer in
-`@object-ui/components` already declares.
-
-`inputs` is a DECLARATION surface, not documentation: the designer builds its
-property palette from it, and the framework's `check:react-declaration-parity`
-diffs it against the spec schemas. Declaring `description` therefore did not
-merely tolerate a legacy spelling — it published a second dialect for the one
-concept the protocol calls `subtitle`, and told authors (an AI author most
-readily, since the registry is what it reads to learn the shape) that the
-non-spec key was legal. Metadata that took the offer renders a subtitle under
-`page-header` and silently loses it under `page:header`: same JSON, two results,
-which is the outcome a single contract exists to prevent.
-
-No runtime behaviour changes. `PageHeader` still reads `subtitle ?? description`,
-deliberately: this alias exists for out-of-repo consumer schemas, so "no in-repo
-author writes `description`" (verified — zero hits) is not evidence that nobody
-does, and dropping the read today would delete an external page's second line
-while its title kept rendering, the least reportable failure mode there is. That
-read is retired together with an ADR-0087 D2 conversion entry
-(`page-header-subtitle-alias`, `description` → `subtitle` rewritten at load
-time), which lives in the framework repo and is tracked separately. Narrowing the
-declaration did not need to wait on it and breaks no consumer; leaving the
-declaration wrong in the meantime keeps minting the metadata the conversion would
-then have to absorb.
-
-New tests pin both halves so neither can drift back: the registration may not
-declare `description`, must declare `subtitle`, and — checked against the spec's
-own shape rather than a hand-written allowlist — may declare nothing
-`@objectstack/spec` does not; while the runtime fallback is pinned as a sequencing
-guard, to be deleted in the same change that lands the conversion entry.
diff --git a/.changeset/previews-read-only-spec-declared-keys.md b/.changeset/previews-read-only-spec-declared-keys.md
deleted file mode 100644
index 4956619356..0000000000
--- a/.changeset/previews-read-only-spec-declared-keys.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-"@object-ui/app-shell": patch
----
-
-Five metadata designers stop rendering keys `@objectstack/spec` rejects, and start
-rendering the keys it declares (objectui#3275, objectui#3281).
-
-The previews and the console's sample drafts had been wrong TOGETHER, which is
-why the gallery looked healthy. objectui#3266 corrected the samples and the
-gallery immediately rendered LESS — agent's TOOLS and KNOWLEDGE blocks, skill's
-TRIGGER PHRASES, app's per-item row and `Dashboard` badge, and datasource's
-CAPABILITIES all vanished or degraded. Nothing had broken: those blocks were only
-ever lit up by metadata that cannot be saved. This is the renderer half of that
-finding, and the same fix objectui#3236 / PR #3258 made to `ToolPreview`.
-
-A preview that renders a rejected key does not just show something useless — it
-tells the author "this is correct" until publish refuses it. For AI-generated
-metadata that is where a stale key hides and multiplies, so every read below was
-deleted rather than kept behind a fallback (AGENTS.md #0.1).
-
-**Retired keys, deleted** — each is a `retiredKey()` tombstone rejected by name:
-`agent.tools` (objectstack#3894 — an agent reaches exactly the tools its skills
-declare, ADR-0064), `agent.knowledge` (objectstack#3896 — it never scoped
-retrieval), `skill.triggerPhrases` (objectstack#3896 — phrases were never matched
-against a user's message).
-
-**`AppPreview` / `AppNavCanvas`** — `AppSchema.navigation` is a discriminated
-union on `type` whose every branch is `.strict()`. Both surfaces ignored the
-discriminator: kind came from `it.object` / `it.dashboard`, the route from
-`it.path ?? it.href ?? it.route ?? it.url`, and the landing from
-`landingRoute ?? landing ?? defaultRoute ?? '/'`. Not one of those is a key
-(`landing` was removed in objectstack#4001), so the reading was exactly inverted —
-a valid app showed generic badges, no targets and an invented `Landing: /`. Now
-`type` is the badge, each branch's own key is the target
-(`objectName`/`pageName`/`dashboardName`/`url`/`reportName`/`componentRef`/
-`actionDef.actionName`), and the route comes from `resolveHref`, the shell's own
-nav → URL mapping that `useNavPins` and `SearchResultsPage` already share — so a
-link in the preview is the link the runtime follows. `homePageId` is rendered as
-the nav item **id** it is, resolved to the entry it selects; it is never printed
-as a path.
-
-**`DatasourcePreview`** — `capabilities` is a `DatasourceCapabilities` object of
-boolean flags, and the preview tested `Array.isArray`, lighting the block up only
-for the pre-17 token array the schema refuses. It now lists the flags set to
-`true`. The `driver ?? d.type` fallback is gone (the schema's own hint is
-`type` → `driver`), as is the `default` pill behind `isDefault ?? default` —
-routing is declared at stack level via `datasourceMapping`, never on the
-datasource.
-
-**`SkillPreview`** — the trigger-conditions table read `cond.expression ??
-cond.value` under a `cond.type` gutter, so a spec-valid condition rendered as
-`COND | sales_order` with the field it tests and the operator it applies both
-invisible. It is now three columns — `field` / `operator` / `value` — straight off
-`SkillTriggerConditionSchema`, and a row missing one of those required cells says
-so instead of rendering a blank that reads as fine.
-
-**`ValidationPreview`** (objectui#3281) — drew nine rule types where the union has
-six. `unique`, `async` and `custom` were removed by one paragraph of
-`validation.zod.ts`, because a rule must be a deterministic, synchronous,
-side-effect-free predicate over one record; each now redirects to the layer that
-does the job (a unique **index** — a SELECT-then-INSERT rule is racy, TOCTOU — a
-form-layer check, a lifecycle hook). Two alias fallbacks went with them:
-`condition ?? expression` and `pattern ?? regex`, where neither `expression` nor
-`pattern` has ever been a key on any branch — which is precisely why a bogus
-`expression` sat unnoticed in the console sample. Two branches were also simply
-wrong: `conditional` read `condition` instead of its `when` (a valid rule showed
-"No expression set", and its nested `then`/`otherwise` now render), and
-`json_schema` had no branch at all, so a valid rule displayed "Unknown rule type".
-
-`validation.object` is deliberately still read: `anchors.ts` registers a
-standalone `validation` resource matched by `anchorByField('object')`, so a
-standalone rule genuinely carries it. Not every key a union omits is residue.
-
-Verified in the preview gallery before and after, per designer; each preview also
-gains tests that feed a spec-valid draft and assert the block renders, then feed a
-stale draft carrying the retired key and assert nothing renders from it.
diff --git a/.changeset/record-chatter-loading-signal.md b/.changeset/record-chatter-loading-signal.md
deleted file mode 100644
index 6a3d559936..0000000000
--- a/.changeset/record-chatter-loading-signal.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-"@object-ui/app-shell": patch
-"@object-ui/plugin-detail": patch
----
-
-The record discussion panel now says "loading" while it is loading, instead of
-"No comments yet" (objectui#3209).
-
-FROM: opening any record page showed the discussion/chatter panel asserting
-`No comments yet` for the whole first leg of the page, then contradicting
-itself when the comments appeared. TO: the panel shows the loading row until
-the feed has actually answered, and only then commits to "this record has no
-comments".
-
-objectui#3205 gave `RecordActivityTimeline` the render branch that prefers a
-loading row over the empty copy, and `RecordChatterPanel` already forwarded
-`loading` to it in both positions — but on the chatter chain **nothing
-produced the signal**, so that branch could never fire. `record:activity`
-computes its own flag and was visibly fixed by #3205; chatter was not. The
-four wiring points are one chain and are all closed here, because any one of
-them left open still ships the empty copy to some user:
-
-- `RecordDetailView` — the host that OWNS the feed fetch — now derives a
-  `feedLoading` flag from its two reads (`sys_comment` + `sys_activity`);
-- `<DiscussionContextProvider loading={feedLoading}>` publishes it (the field
-  was already declared on `DiscussionContextValue`, and already read by
-  `record:activity`);
-- the auto-appended `<RecordChatterPanel loading={feedLoading}>` — the panel
-  authored pages get when they place no discussion slot — receives it
-  directly;
-- the `record:chatter` / `record:discussion` renderer forwards
-  `loading={discussion?.loading}`, so a hand-placed block is on the same
-  chain as the synthesized one.
-
-The two reads run in parallel, so the flag closes over **both**: it clears on
-`Promise.allSettled`, and a REJECTED read counts as an answer. A deployment
-without the audit plugin 404s `sys_activity` and an object with
-`enable.feeds: false` 403s `sys_comment`; neither may pin the panel in a
-permanent spinner, which would be a worse bug than the one being fixed. The
-flag is keyed by `object:recordId` rather than being a plain boolean, so the
-first render of a record already reads as loading (no one-frame flash of the
-empty state) and navigating between records cannot show the previous record's
-settled answer.
-
-No tolerance was added at the consumer. The timeline still does not guess that
-"no items yet and just mounted" means loading — that guess is wrong the moment
-a record genuinely has no comments, and the signal belongs to whoever owns the
-fetch. Same shape as objectui#3165 / #3205: divergence converges at the
-producer.
diff --git a/.changeset/record-feed-keyed-by-record.md b/.changeset/record-feed-keyed-by-record.md
deleted file mode 100644
index bd40473d6a..0000000000
--- a/.changeset/record-feed-keyed-by-record.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-"@object-ui/app-shell": patch
----
-
-The record discussion panel no longer shows the PREVIOUS record's comments and
-activity (objectui#3268).
-
-FROM: clicking from record A to record B in a list left A's comments and
-activity rows on B's discussion panel, with B's own rows merged in alongside
-them. TO: each record's panel shows that record's feed and nothing else, and a
-record that is still being fetched shows the loading row rather than the
-record the user just came from.
-
-This was cross-record data display, not a cosmetic glitch. `RecordDetailView`
-is deliberately NOT remounted between records — no mount site passes a `key=`
-(`console/AppContent.tsx`, and the `ObjectView` / `ObjectDataPage` /
-`InterfaceListPage` drawers just swap `recordIdOverride`), per objectui#2269
-"refresh data, don't rebuild UI" — so its feed state survived the navigation,
-and both reads (`sys_comment`, `sys_activity`) merged into it BY ROW ID. A's
-rows and B's rows have different ids, so the merge could not dedupe them away
-and nothing anywhere reset the list.
-
-It also suppressed the fix objectui#3209 had just shipped. On record→record
-navigation `feedLoading` did flip true, but `RecordActivityTimeline`'s branch
-is `loading && filtered.length === 0` (objectui#3205, deliberate: a refresh
-must not turn an on-screen feed into a spinner) and the leftover rows kept
-`filtered` non-empty — so the panel rendered the previous record's content
-where a loading state belonged. The two issues only add up to a working
-feature together.
-
-The feed state is now keyed by `objectName:recordId` — the same key
-objectui#3209 introduced in this file for the loading flag, and the very
-`thread_id` the rows carry server-side. The render reads only the current
-key's slice, so "empty for a new record" FALLS OUT of reading a key that has
-no slice; there is no `setFeedItems([])` racing the fetch that fills it. A
-response that lands after the user has navigated away is written under the key
-its effect closed over, so it updates the record it was fetched for and can
-never bleed into the record now on screen — the same guarantee `settledFeedKey`
-already gave the loading flag. One idiom in this file, not two.
-
-Keying rather than clearing is what keeps OPTIMISTIC rows safe. A comment the
-user has just posted but that has not come back from the server lives only in
-this state, and it now rides in its own record's slice: navigating away and
-back finds it again, and it never appears on another record's panel. Nothing
-deletes a slice, so returning to a record shows its rows immediately while the
-re-read confirms them (objectui#3205 again), and the re-read folds the
-persisted copy onto the optimistic row by id — same id, because that is the id
-it was created under — so there is no duplicate when it lands. The same
-scoping applies to threaded replies and reaction toggles.
-
-No tolerance was added at the consumer. `RecordActivityTimeline` still keeps
-`loading && filtered.length === 0` exactly as objectui#3205 wrote it; once the
-feed's lifecycle is correct that condition is right on its own. Weakening it
-would have been treating the symptom at the consumer, which is what
-objectui#3165 / #3205 / #3209 all deliberately avoided.
diff --git a/.changeset/retire-action-param-validation.md b/.changeset/retire-action-param-validation.md
deleted file mode 100644
index 5e5adce3be..0000000000
--- a/.changeset/retire-action-param-validation.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-"@object-ui/types": minor
-"@object-ui/core": minor
----
-
-Retire `validation` from the action-param contract — it was declared on both
-halves, read by neither, and rejected outright by the server (objectui#3201).
-
-FROM: `validation?: string` was declared on the AUTHORING type
-(`@object-ui/types`' `ActionParam`) and on the RESOLVED type (`@object-ui/core`'s
-`ActionParamDef`). TO: it is declared on neither.
-
-**Breaking for anyone who declared it — but it never did anything.** This is
-marked `minor`, not `major`, per the repo's version-alignment policy (objectui's
-major tracks `@objectstack`'s, so objectui's own breaking changes ship as `minor`
-with the breaking semantics spelled out here).
-
-**Migration: delete it.** If you authored `validation: '...'` on an action param,
-it never took effect, and publishing that metadata to the server is a hard parse
-failure — so any metadata that reached production either never carried the key or
-never parsed. Removing it changes no runtime behaviour; it only moves the error
-from "silent no-op, then rejected at publish" to a `tsc` error at the keystroke.
-
-Why it could not work as authored:
-
-- `ActionParamSchema` in `@objectstack/spec/ui` is `.strict()` and does not list
-  `validation`, so an authored key is a PARSE REJECTION on the server:
-  `Unrecognized key(s) on this action param: \`validation\``. Meanwhile `tsc`
-  against the public type accepted it — the type vouched for a key the platform
-  itself refuses.
-- Nothing read it on the resolved side either: it was never a key of
-  `resolveActionParams()`'s `RawActionParam`, the runtime field metadata a
-  field-backed param inherits from carries no `validation` to source one from,
-  and `paramToField()` never mapped it — so it could not reach the field widgets,
-  whose rules `buildValidationRules()` builds from `required` / `minLength` /
-  `maxLength` / `pattern`.
-
-Removed rather than implemented, on ADR-0049 enforce-or-remove. Giving it meaning
-would mean first deciding what an "expression" is here (CEL? a formula? a regex?)
-and adding it to `@objectstack/spec`, which is where such a capability has to
-start — not accreted renderer-side around a key the contract does not have.
-
-This also retires the last named exception in objectui#3174's drift guard
-(`packages/types/src/__tests__/page-nav-misc-spec-parity.test.ts`), which carried
-`validation` as the one key `ActionParam` added on top of the spec's set. The
-rule it pins — **the authoring type declares exactly the spec's authorable
-keys** — is now literal: the guard asserts the local-only key set is empty, so
-any future addition fails the build instead of being waved through.
diff --git a/.changeset/textarea-mobile-fullscreen-single-source.md b/.changeset/textarea-mobile-fullscreen-single-source.md
deleted file mode 100644
index 2a68da3c30..0000000000
--- a/.changeset/textarea-mobile-fullscreen-single-source.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-"@object-ui/fields": patch
----
-
-`TextAreaField`'s mobile fullscreen flag converges on its one real producer
-(objectui#3232).
-
-FROM: the widget resolved the "show the expand affordance" decision through a
-four-way `??` chain — a `mobileFullscreen` (camelCase) prop, the field
-metadata's `mobile_fullscreen`, a `mobile_fullscreen` prop, and
-`schema.mobile_fullscreen`. TO: a single read of the field metadata's
-`mobile_fullscreen`, resolved through the `field || schema` carrier pair every
-widget in this package already uses.
-
-No runtime behaviour changes, because three of those four reads were
-permanently `undefined`:
-
-- `mobileFullscreen` (camelCase) had **no producer anywhere in the repo** — the
-  only occurrences of that spelling were the widget's own read and the
-  destructure that kept it off the DOM spread. The doc comment nonetheless
-  claimed "the host form passes `mobileFullscreen`", so the contract it
-  described had never held.
-- `mobile_fullscreen` as a **prop** cannot arrive: the form renderer's
-  `stripRegisteredFieldProps` explicitly removes `mobile_fullscreen` and
-  `fullscreen` from the props forwarded to registered field widgets.
-- `schema.mobile_fullscreen` was the same object `field || schema` already
-  resolves, so it could only ever restate the metadata read.
-
-What actually drives the affordance — and is now the only thing that does — is
-the field metadata flag `ObjectForm` stamps onto long-text fields from
-`ObjectFormSchema.mobile.fullscreenLongText`. That path is unchanged and is now
-pinned by tests (button, dialog, and the committed edit), so the cleanup cannot
-have silently removed the working behaviour.
-
-Also untouched: the built-in (unregistered) `textarea` branch of the form
-renderer, which reads `mobile_fullscreen || fullscreen` off the form-field
-props and renders its own `FullscreenTextarea`. That is a separate live path.
-
-Why this is worth a changeset rather than a silent tidy-up: reads that nobody
-writes are not free. They document a contract that does not exist — the next
-author follows the comment, passes the prop, and is ignored without a word —
-and a `??` chain that accepts four spellings and rejects none is exactly where
-a misspelled key hides. With one source, a wrong spelling has no read path left
-to absorb it. Per AGENTS.md #0.1 and Prime Directive #12, divergence like this
-converges at the producer, not by accumulating tolerance at the consumer. No
-host-override prop was invented in its place: inventing a key with no producer
-is the same mistake in the other direction.
diff --git a/.changeset/toolpreview-drop-retired-flag-pills.md b/.changeset/toolpreview-drop-retired-flag-pills.md
deleted file mode 100644
index 4ea900710c..0000000000
--- a/.changeset/toolpreview-drop-retired-flag-pills.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-"@object-ui/app-shell": patch
----
-
-`ToolPreview` stops advertising retired `ToolSchema` flags (objectui#3236).
-
-The metadata-admin tool preview painted a header strip of flag pills read
-straight off the raw draft: `Requires confirmation`, `Active` / `Disabled`,
-`built-in`, and the `category` tag. All four keys have been removed from
-`@objectstack/spec`'s `ToolSchema` — `requiresConfirmation` in the 16.x line
-(objectstack#3715, ADR-0033 §2) and `category` / `active` / `builtIn` in
-17.0.0 (objectstack#3896 audit close-out). The schema is `.strict()` and now
-rejects each by name with an upgrade prescription, so no newly authored tool
-can carry them; verified against the `@objectstack/spec@17.0.0-rc.1` this repo
-depends on.
-
-New metadata could not reach these pills — but rows stored before the removals
-still carry the keys, and for those the preview kept rendering. That is the
-harmful direction, not a cosmetic one:
-
-- `Requires confirmation` advertised a safety pause that no execution path has
-  ever performed. Nothing read the key — not the LLM tool set (a tool reaches
-  the model as name/description/parameters only), not `ToolRegistry.execute`,
-  not `POST /ai/tools/:name/execute`. A reviewer reading the preview saw a
-  destructive tool marked as gated when it was not. The real gate is
-  `action.ai.requiresConfirmation`, which the HITL approval queue reads.
-- `Disabled` claimed a tool had been withdrawn while `ToolRegistry.getAll()`
-  kept handing it to the LLM and the execute route kept running it.
-
-Same shape as objectui#2962: a UI badge advertising a capability the runtime
-does not have. The pills are gone; the surviving header strip shows label,
-machine name and the `objectName` pill (`objectName` is still a live spec key),
-and nothing else in the preview changed — parameters table, example LLM call
-and output schema are untouched.
-
-New tests feed the preview a stale draft that still carries all four retired
-keys and assert none of them renders, so the pills cannot grow back: the names
-survive in the spec's tombstone guidance, which gives the next reader a
-plausible-looking reason to "restore" them.
diff --git a/apps/console/CHANGELOG.md b/apps/console/CHANGELOG.md
index 90f79d1326..b12924b303 100644
--- a/apps/console/CHANGELOG.md
+++ b/apps/console/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/console
 
+## 17.3.0
+
+### Patch Changes
+
+- @object-ui/sdui-parser@17.3.0
+- @object-ui/react-runtime@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/apps/console/package.json b/apps/console/package.json
index d644cbe689..a6b7190bc1 100644
--- a/apps/console/package.json
+++ b/apps/console/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/console",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "ObjectStack Console — opinionated, fork-ready runtime console built on @object-ui/app-shell with the full plugin set wired up. Ships as a Hono UI plugin serving a pre-built SPA.",
   "license": "MIT",
   "type": "module",
diff --git a/packages/app-shell/CHANGELOG.md b/packages/app-shell/CHANGELOG.md
index 994643bf3e..2197c388d2 100644
--- a/packages/app-shell/CHANGELOG.md
+++ b/packages/app-shell/CHANGELOG.md
@@ -1,5 +1,327 @@
 # @object-ui/app-shell — Changelog
 
+## 17.3.0
+
+### Minor Changes
+
+- 6e794a1: The flow designer writes node geometry as the spec's `FlowNode.position`, not its
+  own `ui: { x, y }` (objectui#3172).
+
+  FROM: dragging, adding-at-a-point and insert-on-edge each wrote `node.ui = {x, y}`
+  — a fourth-generation local spelling of a concept `@objectstack/spec` has modelled
+  as `FlowNode.position` all along. TO: all three write `position: { x, y }`, and the
+  canvas migrates on write: a stored flow's legacy `ui` is lifted onto `position` and
+  the key removed in the first patch the canvas emits, geometry-related or not.
+
+  **This is a behaviour fix, not a rename.** `FlowNodeSchema` has been `.strict()`
+  since objectstack#4001, so `ui` is an `unrecognized_keys` error: the live client
+  validation flagged the draft on every keystroke and the server rejected the save
+  with a 422. In other words, dragging a node made the flow unsavable — the
+  convergence is what makes the designer's most basic gesture round-trip again. A
+  test now parses `{ …node, ui: {x, y} }` through the spec's own schema and asserts
+  the rejection, so the claim is executed rather than argued.
+
+  Reading is backwards-compatible: `manualPosition()` prefers `position` and falls
+  back to a legacy `ui`, so a flow stored before this change still opens with its
+  nodes exactly where the author left them (pinned by a test that lays out both
+  spellings and compares the maps). The fallback is a migration path, not a second
+  contract — nothing writes `ui`, and the canvas strips it at its input boundary, so
+  no patch can re-emit it.
+
+  The geometry type is now derived from the spec by reference
+  (`FlowNodePosition = NonNullable< SpecFlowNode['position'] >`), and
+  `spec-symbol-parity.test.ts` pins the equality in both directions — including that
+  both coordinates are required, so a half-position stays unrepresentable. The
+  shape-copy in `FlowPreview.tsx` is gone; it reads the canvas's own node type, the
+  way it already read the canvas's edge type.
+
+  Breaking for anyone reading `node.ui` off a flow draft: after the author's first
+  edit the key is gone and the coordinates live under `node.position`. Nothing in
+  this repo or the engine read it — it was a designer-local key the schema rejected.
+
+### Patch Changes
+
+- 8e02ad7: The Page block inspector's conditional-visibility control now authors
+  `visibleWhen`, and says "Visible when" while doing it (objectui#3229).
+
+  FROM: the `ConditionBuilder` rendered for the selected page block read and wrote
+  `block.hidden`. TO: it reads and writes `block.visibleWhen`, the canonical
+  conditional-visibility key (ADR-0089), through the same envelope read/write pair
+  the hook and action guards use (objectui#3218).
+
+  `PageComponentSchema` (`ui/page.zod.ts`) is `.strict()` and has no `hidden` key
+  at all. So this was not a tolerant consumer accepting something sloppy — it was
+  the **producer emitting a key the contract rejects**: every author who filled
+  that box got a save-time parse failure naming a key they never typed, because the
+  inspector typed it for them. The spec's own error message already names the fix
+  (`` the canonical key is `visibleWhen` ``). A designer that mass-produces drafts
+  guaranteed to be rejected is a worse failure than a lenient reader — a lenient
+  reader lets wrong metadata run, this made the _correct tool_ emit the wrong thing.
+
+  The fix also closes the gap in the other direction: a **valid** block carrying
+  `visibleWhen` previously had no control in the inspector that could edit its
+  visibility, because the only visibility control on screen wrote a different key.
+  Removing the control instead would have stopped teaching the wrong key but left
+  that gap open, which is a capability regression.
+
+  **The semantic flip lands in the UI copy, not just the key.** `hidden` and
+  `visibleWhen` are inverses (`hidden` true ⇒ gone; `visibleWhen` true ⇒ shown), so
+  the label, the i18n key (`engine.inspector.pageBlock.hidden` →
+  `engine.inspector.pageBlock.visibleWhen`) and both language packs move together:
+  "Hidden (CEL)" → "Visible when (CEL)", 「隐藏条件（CEL）」→「显示条件（CEL）」.
+  Renaming the key while leaving hide-flavoured copy would have been worse than
+  leaving the bug: authors would write the predicate backwards, producing metadata
+  that PARSES and means the opposite — the objectui#3276 class, which objectui#3257's
+  guard is structurally blind to because it only asks whether a draft parses.
+
+  **No value is migrated.** An existing `hidden` expression is NOT negated into
+  `visibleWhen`: textually negating an arbitrary CEL predicate is unsound
+  (`!(a && b)` is not `!a && !b`), and there is no stored valid draft to migrate
+  anyway — since ADR-0089 D3a `hidden` is a loud parse failure on save, and before
+  D3a the key was silently dropped, so it never reached published metadata either.
+  A loud error on a rare stale draft, with the spec's message pointing at
+  `visibleWhen`, beats silently rewriting an author's predicate.
+
+  Because `visibleWhen` is `ExpressionInputSchema`, a persisted block carries the
+  `{ dialect, source }` envelope rather than the authored string, so the control
+  goes through `expressionSource` / `writeExpressionSource` — an edit preserves
+  `dialect` and `meta` and drops the stale `ast`, instead of flattening the
+  envelope to a bare string and silently swapping the evaluation engine.
+
+  Tests pin DIRECTION, not just the key name (the objectui#3276 precedent makes
+  that a hard requirement): the block the inspector actually commits is rendered
+  through `SchemaRenderer` and must appear when its predicate is true and be absent
+  when it is false, alongside assertions that the committed key is `visibleWhen`,
+  never `hidden`, and that the resulting draft parses.
+
+- 8ff3ad7: Five metadata designers stop rendering keys `@objectstack/spec` rejects, and start
+  rendering the keys it declares (objectui#3275, objectui#3281).
+
+  The previews and the console's sample drafts had been wrong TOGETHER, which is
+  why the gallery looked healthy. objectui#3266 corrected the samples and the
+  gallery immediately rendered LESS — agent's TOOLS and KNOWLEDGE blocks, skill's
+  TRIGGER PHRASES, app's per-item row and `Dashboard` badge, and datasource's
+  CAPABILITIES all vanished or degraded. Nothing had broken: those blocks were only
+  ever lit up by metadata that cannot be saved. This is the renderer half of that
+  finding, and the same fix objectui#3236 / PR #3258 made to `ToolPreview`.
+
+  A preview that renders a rejected key does not just show something useless — it
+  tells the author "this is correct" until publish refuses it. For AI-generated
+  metadata that is where a stale key hides and multiplies, so every read below was
+  deleted rather than kept behind a fallback (AGENTS.md #0.1).
+
+  **Retired keys, deleted** — each is a `retiredKey()` tombstone rejected by name:
+  `agent.tools` (objectstack#3894 — an agent reaches exactly the tools its skills
+  declare, ADR-0064), `agent.knowledge` (objectstack#3896 — it never scoped
+  retrieval), `skill.triggerPhrases` (objectstack#3896 — phrases were never matched
+  against a user's message).
+
+  **`AppPreview` / `AppNavCanvas`** — `AppSchema.navigation` is a discriminated
+  union on `type` whose every branch is `.strict()`. Both surfaces ignored the
+  discriminator: kind came from `it.object` / `it.dashboard`, the route from
+  `it.path ?? it.href ?? it.route ?? it.url`, and the landing from
+  `landingRoute ?? landing ?? defaultRoute ?? '/'`. Not one of those is a key
+  (`landing` was removed in objectstack#4001), so the reading was exactly inverted —
+  a valid app showed generic badges, no targets and an invented `Landing: /`. Now
+  `type` is the badge, each branch's own key is the target
+  (`objectName`/`pageName`/`dashboardName`/`url`/`reportName`/`componentRef`/
+  `actionDef.actionName`), and the route comes from `resolveHref`, the shell's own
+  nav → URL mapping that `useNavPins` and `SearchResultsPage` already share — so a
+  link in the preview is the link the runtime follows. `homePageId` is rendered as
+  the nav item **id** it is, resolved to the entry it selects; it is never printed
+  as a path.
+
+  **`DatasourcePreview`** — `capabilities` is a `DatasourceCapabilities` object of
+  boolean flags, and the preview tested `Array.isArray`, lighting the block up only
+  for the pre-17 token array the schema refuses. It now lists the flags set to
+  `true`. The `driver ?? d.type` fallback is gone (the schema's own hint is
+  `type` → `driver`), as is the `default` pill behind `isDefault ?? default` —
+  routing is declared at stack level via `datasourceMapping`, never on the
+  datasource.
+
+  **`SkillPreview`** — the trigger-conditions table read `cond.expression ??
+cond.value` under a `cond.type` gutter, so a spec-valid condition rendered as
+  `COND | sales_order` with the field it tests and the operator it applies both
+  invisible. It is now three columns — `field` / `operator` / `value` — straight off
+  `SkillTriggerConditionSchema`, and a row missing one of those required cells says
+  so instead of rendering a blank that reads as fine.
+
+  **`ValidationPreview`** (objectui#3281) — drew nine rule types where the union has
+  six. `unique`, `async` and `custom` were removed by one paragraph of
+  `validation.zod.ts`, because a rule must be a deterministic, synchronous,
+  side-effect-free predicate over one record; each now redirects to the layer that
+  does the job (a unique **index** — a SELECT-then-INSERT rule is racy, TOCTOU — a
+  form-layer check, a lifecycle hook). Two alias fallbacks went with them:
+  `condition ?? expression` and `pattern ?? regex`, where neither `expression` nor
+  `pattern` has ever been a key on any branch — which is precisely why a bogus
+  `expression` sat unnoticed in the console sample. Two branches were also simply
+  wrong: `conditional` read `condition` instead of its `when` (a valid rule showed
+  "No expression set", and its nested `then`/`otherwise` now render), and
+  `json_schema` had no branch at all, so a valid rule displayed "Unknown rule type".
+
+  `validation.object` is deliberately still read: `anchors.ts` registers a
+  standalone `validation` resource matched by `anchorByField('object')`, so a
+  standalone rule genuinely carries it. Not every key a union omits is residue.
+
+  Verified in the preview gallery before and after, per designer; each preview also
+  gains tests that feed a spec-valid draft and assert the block renders, then feed a
+  stale draft carrying the retired key and assert nothing renders from it.
+
+- 12bf669: The record discussion panel now says "loading" while it is loading, instead of
+  "No comments yet" (objectui#3209).
+
+  FROM: opening any record page showed the discussion/chatter panel asserting
+  `No comments yet` for the whole first leg of the page, then contradicting
+  itself when the comments appeared. TO: the panel shows the loading row until
+  the feed has actually answered, and only then commits to "this record has no
+  comments".
+
+  objectui#3205 gave `RecordActivityTimeline` the render branch that prefers a
+  loading row over the empty copy, and `RecordChatterPanel` already forwarded
+  `loading` to it in both positions — but on the chatter chain **nothing
+  produced the signal**, so that branch could never fire. `record:activity`
+  computes its own flag and was visibly fixed by #3205; chatter was not. The
+  four wiring points are one chain and are all closed here, because any one of
+  them left open still ships the empty copy to some user:
+
+  - `RecordDetailView` — the host that OWNS the feed fetch — now derives a
+    `feedLoading` flag from its two reads (`sys_comment` + `sys_activity`);
+  - `<DiscussionContextProvider loading={feedLoading}>` publishes it (the field
+    was already declared on `DiscussionContextValue`, and already read by
+    `record:activity`);
+  - the auto-appended `<RecordChatterPanel loading={feedLoading}>` — the panel
+    authored pages get when they place no discussion slot — receives it
+    directly;
+  - the `record:chatter` / `record:discussion` renderer forwards
+    `loading={discussion?.loading}`, so a hand-placed block is on the same
+    chain as the synthesized one.
+
+  The two reads run in parallel, so the flag closes over **both**: it clears on
+  `Promise.allSettled`, and a REJECTED read counts as an answer. A deployment
+  without the audit plugin 404s `sys_activity` and an object with
+  `enable.feeds: false` 403s `sys_comment`; neither may pin the panel in a
+  permanent spinner, which would be a worse bug than the one being fixed. The
+  flag is keyed by `object:recordId` rather than being a plain boolean, so the
+  first render of a record already reads as loading (no one-frame flash of the
+  empty state) and navigating between records cannot show the previous record's
+  settled answer.
+
+  No tolerance was added at the consumer. The timeline still does not guess that
+  "no items yet and just mounted" means loading — that guess is wrong the moment
+  a record genuinely has no comments, and the signal belongs to whoever owns the
+  fetch. Same shape as objectui#3165 / #3205: divergence converges at the
+  producer.
+
+- a8aa576: The record discussion panel no longer shows the PREVIOUS record's comments and
+  activity (objectui#3268).
+
+  FROM: clicking from record A to record B in a list left A's comments and
+  activity rows on B's discussion panel, with B's own rows merged in alongside
+  them. TO: each record's panel shows that record's feed and nothing else, and a
+  record that is still being fetched shows the loading row rather than the
+  record the user just came from.
+
+  This was cross-record data display, not a cosmetic glitch. `RecordDetailView`
+  is deliberately NOT remounted between records — no mount site passes a `key=`
+  (`console/AppContent.tsx`, and the `ObjectView` / `ObjectDataPage` /
+  `InterfaceListPage` drawers just swap `recordIdOverride`), per objectui#2269
+  "refresh data, don't rebuild UI" — so its feed state survived the navigation,
+  and both reads (`sys_comment`, `sys_activity`) merged into it BY ROW ID. A's
+  rows and B's rows have different ids, so the merge could not dedupe them away
+  and nothing anywhere reset the list.
+
+  It also suppressed the fix objectui#3209 had just shipped. On record→record
+  navigation `feedLoading` did flip true, but `RecordActivityTimeline`'s branch
+  is `loading && filtered.length === 0` (objectui#3205, deliberate: a refresh
+  must not turn an on-screen feed into a spinner) and the leftover rows kept
+  `filtered` non-empty — so the panel rendered the previous record's content
+  where a loading state belonged. The two issues only add up to a working
+  feature together.
+
+  The feed state is now keyed by `objectName:recordId` — the same key
+  objectui#3209 introduced in this file for the loading flag, and the very
+  `thread_id` the rows carry server-side. The render reads only the current
+  key's slice, so "empty for a new record" FALLS OUT of reading a key that has
+  no slice; there is no `setFeedItems([])` racing the fetch that fills it. A
+  response that lands after the user has navigated away is written under the key
+  its effect closed over, so it updates the record it was fetched for and can
+  never bleed into the record now on screen — the same guarantee `settledFeedKey`
+  already gave the loading flag. One idiom in this file, not two.
+
+  Keying rather than clearing is what keeps OPTIMISTIC rows safe. A comment the
+  user has just posted but that has not come back from the server lives only in
+  this state, and it now rides in its own record's slice: navigating away and
+  back finds it again, and it never appears on another record's panel. Nothing
+  deletes a slice, so returning to a record shows its rows immediately while the
+  re-read confirms them (objectui#3205 again), and the re-read folds the
+  persisted copy onto the optimistic row by id — same id, because that is the id
+  it was created under — so there is no duplicate when it lands. The same
+  scoping applies to threaded replies and reaction toggles.
+
+  No tolerance was added at the consumer. `RecordActivityTimeline` still keeps
+  `loading && filtered.length === 0` exactly as objectui#3205 wrote it; once the
+  feed's lifecycle is correct that condition is right on its own. Weakening it
+  would have been treating the symptom at the consumer, which is what
+  objectui#3165 / #3205 / #3209 all deliberately avoided.
+
+- 30ac2e1: `ToolPreview` stops advertising retired `ToolSchema` flags (objectui#3236).
+
+  The metadata-admin tool preview painted a header strip of flag pills read
+  straight off the raw draft: `Requires confirmation`, `Active` / `Disabled`,
+  `built-in`, and the `category` tag. All four keys have been removed from
+  `@objectstack/spec`'s `ToolSchema` — `requiresConfirmation` in the 16.x line
+  (objectstack#3715, ADR-0033 §2) and `category` / `active` / `builtIn` in
+  17.0.0 (objectstack#3896 audit close-out). The schema is `.strict()` and now
+  rejects each by name with an upgrade prescription, so no newly authored tool
+  can carry them; verified against the `@objectstack/spec@17.0.0-rc.1` this repo
+  depends on.
+
+  New metadata could not reach these pills — but rows stored before the removals
+  still carry the keys, and for those the preview kept rendering. That is the
+  harmful direction, not a cosmetic one:
+
+  - `Requires confirmation` advertised a safety pause that no execution path has
+    ever performed. Nothing read the key — not the LLM tool set (a tool reaches
+    the model as name/description/parameters only), not `ToolRegistry.execute`,
+    not `POST /ai/tools/:name/execute`. A reviewer reading the preview saw a
+    destructive tool marked as gated when it was not. The real gate is
+    `action.ai.requiresConfirmation`, which the HITL approval queue reads.
+  - `Disabled` claimed a tool had been withdrawn while `ToolRegistry.getAll()`
+    kept handing it to the LLM and the execute route kept running it.
+
+  Same shape as objectui#2962: a UI badge advertising a capability the runtime
+  does not have. The pills are gone; the surviving header strip shows label,
+  machine name and the `objectName` pill (`objectName` is still a live spec key),
+  and nothing else in the preview changed — parameters table, example LLM call
+  and output schema are untouched.
+
+  New tests feed the preview a stale draft that still carries all four retired
+  keys and assert none of them renders, so the pills cannot grow back: the names
+  survive in the spec's tombstone guidance, which gives the next reader a
+  plausible-looking reason to "restore" them.
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [d2363e7]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/layout@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/plugin-editor@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/auth@17.3.0
+  - @object-ui/collaboration@17.3.0
+  - @object-ui/data-objectstack@17.3.0
+  - @object-ui/permissions@17.3.0
+  - @object-ui/providers@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/app-shell/package.json b/packages/app-shell/package.json
index 0457e8b1c7..57b4a4aa35 100644
--- a/packages/app-shell/package.json
+++ b/packages/app-shell/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/app-shell",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Minimal application shell for ObjectUI - framework-agnostic rendering engine",
diff --git a/packages/auth/CHANGELOG.md b/packages/auth/CHANGELOG.md
index 61337673c9..6db9945c98 100644
--- a/packages/auth/CHANGELOG.md
+++ b/packages/auth/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/auth
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/auth/package.json b/packages/auth/package.json
index 5d6cd37bd2..bb553e0df2 100644
--- a/packages/auth/package.json
+++ b/packages/auth/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/auth",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Authentication system for Object UI with AuthProvider, useAuth hook, AuthGuard, and form components.",
diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md
index 2f12436f9d..7d2c4a76e1 100644
--- a/packages/cli/CHANGELOG.md
+++ b/packages/cli/CHANGELOG.md
@@ -1,5 +1,19 @@
 # @object-ui/cli
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/cli/package.json b/packages/cli/package.json
index e4bfcccaf7..9db12381b7 100644
--- a/packages/cli/package.json
+++ b/packages/cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/cli",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "Standalone CLI for Object UI — scaffold, develop, build and validate JSON/YAML schema-driven applications.",
   "type": "module",
   "homepage": "https://www.objectui.org/docs/utilities/cli",
diff --git a/packages/collaboration/CHANGELOG.md b/packages/collaboration/CHANGELOG.md
index 30a9884e52..5f5199efbb 100644
--- a/packages/collaboration/CHANGELOG.md
+++ b/packages/collaboration/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/collaboration
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/collaboration/package.json b/packages/collaboration/package.json
index f02ceab262..22293b8bb9 100644
--- a/packages/collaboration/package.json
+++ b/packages/collaboration/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/collaboration",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Real-time collaboration for Object UI with presence tracking, live cursors, conflict resolution, and comment threads.",
diff --git a/packages/components/CHANGELOG.md b/packages/components/CHANGELOG.md
index edc3934da4..c298c783e2 100644
--- a/packages/components/CHANGELOG.md
+++ b/packages/components/CHANGELOG.md
@@ -1,5 +1,297 @@
 # @object-ui/components
 
+## 17.3.0
+
+### Minor Changes
+
+- 56409c2: Field widgets are finally told when their field fails validation, and the props
+  slot that carries it takes the name the published contract gives it
+  (objectui#3222).
+
+  **Breaking** for anyone implementing a field widget (see migration below). The
+  repo version policy keeps this a `minor` — objectui's major tracks
+  `@objectstack`'s — so read the bump as "breaking within objectui".
+
+  ## The a11y defect this fixes
+
+  `@objectstack/spec/ui`'s `FieldWidgetPropsSchema` — the published contract that
+  third-party and AI-authored field widgets are written against — has always
+  declared `error?: string`. `@object-ui/fields` declared its own slot as
+  `errorMessage`. That looked like a naming split; it was worse:
+
+  ```
+  producers of `errorMessage` anywhere in packages/ + apps/ :  0
+  reads of `errorMessage` in packages/fields/src            : 15  (7 widgets)
+  reads of `props.error`                                    :  0
+  ```
+
+  The slot was dead under BOTH spellings. No host ever passed it: the form
+  renderer showed validation text through its own `<FormMessage/>` and never
+  forwarded the prop. So `EmailField`, `CurrencyField`, `UrlField`,
+  `RichTextField`, `PercentField`, `TextAreaField` and `PhoneField` each computed
+  `aria-invalid={!!errorMessage}` from a value that was `undefined` forever —
+  **`aria-invalid` had never once been set, and a screen reader was never told
+  the field had failed validation.**
+
+  Worse than "never set": `<FormControl>` is a Radix `Slot` that hands its child a
+  CORRECT `aria-invalid`, but a widget's own attribute is written after the props
+  spread, so it wins. Those seven widgets were actively overwriting the right
+  answer with `false`.
+
+  FROM: `renderFieldComponent` received no validation state, and the widget props
+  type declared `errorMessage?: string`, which nothing produced.
+  TO: the form renderer passes react-hook-form's `fieldState.error?.message` down
+  as `error` when it renders a registered widget, and the props type declares
+  `error?: string`. Both ends of the contract are live for the first time; a
+  rename alone would only have swapped one dead key for another.
+
+  ## Migration for widget authors
+
+  ```diff
+  -export function MyField({ value, onChange, field, readonly, errorMessage }: FieldWidgetComponentProps< string >) {
+  -  return <Input value={value} aria-invalid={!!errorMessage} />;
+  +export function MyField({ value, onChange, field, readonly, error }: FieldWidgetComponentProps< string >) {
+  +  return <Input value={value} aria-invalid={!!error} />;
+  ```
+
+  No alias is kept. `errorMessage` was retained nowhere on purpose — a tolerant
+  second spelling is exactly the de-facto second contract AGENTS.md #0.1 forbids,
+  and it is what would let a missed call site go quiet again. Because
+  objectui#3221 had already removed the type's `[key: string]: any`, every missed
+  site is a compile error rather than a silent `any`, so the compiler — not grep
+  — validated this rename.
+
+  ## Responsibilities are split, not duplicated
+
+  The widget consumes `error` **only** to drive `aria-invalid` on the control it
+  renders (which only it can do — `aria-invalid` has to sit on the input element).
+  The message TEXT stays with `<FormMessage/>` in the form renderer. A widget that
+  also renders the text double-displays it, and the docs, the agent prompt and the
+  tests all now say so.
+
+  For the same reason `required` — also declared by the spec, also never delivered
+  — is deliberately NOT lowered into widget props: the required marker has exactly
+  one author, the renderer's `<FormLabel>`, and giving widgets the flag invites a
+  second asterisk. The a11y state a widget could legitimately carry is
+  `aria-required`, which needs no contract change at all (`AriaAttributes` is
+  already part of the type and widgets already forward it).
+
+  Builtin field types are unaffected: they render inside `<FormControl>`, whose
+  Slot already supplies `aria-invalid`, so `error` is stripped there rather than
+  leaking into the DOM as a stray attribute.
+
+  Docs updated to match: `content/docs/guide/plugin-development.md`,
+  `skills/objectui/guides/plugin-development.md` and
+  `.github/prompts/component.prompt.md` — the last of which additionally used the
+  spec's non-generic type alias as a generic (`FieldWidgetProps< number >`) and
+  destructured a `mode` prop that exists on neither type.
+
+- 042e09d: **BREAKING (v17)** — field widgets receive their metadata on ONE key, `field`.
+  `schema` is removed from the widget contract (objectui#3233).
+
+  ## What changed
+
+  `schema` was a second carrier for what `field` already means. Two producers fed
+  it: `SchemaRenderer` passed the authored node as `schema`, and the form
+  renderer's `renderFieldComponent` passed `schema={props.field || props.schema ||
+props}` _alongside_ `field`. The predictable result was ~30 widgets resolving
+  their config as `field || schema` — one concept, two spellings, a de-facto
+  second contract (AGENTS.md #0.1).
+
+  - `FieldWidgetComponentProps` no longer declares `schema`. Reading
+    `props.schema` is now a compile error, not a silent `any`.
+  - Both producers converged. The form renderer passes `field` only. The SDUI node
+    → `field` translation happens exactly once, in a new registration adapter
+    (`withFieldCarrier`), which every built-in field widget is registered through.
+  - All `field || schema` reads in `@object-ui/fields` are now plain `field` reads.
+
+  ## Migrating a widget you wrote
+
+  **Reading the metadata** — replace the fallback with the single key:
+
+  ```diff
+  -const config = field || (props as any).schema;
+  +const config = field;
+  ```
+
+  **Registering a widget** — if your widget can be rendered from a schema node
+  (anything `SchemaRenderer` dispatches, not just forms), wrap it once so it still
+  gets `field`:
+
+  ```diff
+  +import { withFieldCarrier } from '@object-ui/fields';
+  +
+  -ComponentRegistry.register('color', ColorField, { namespace: 'field' });
+  +ComponentRegistry.register('color', withFieldCarrier(ColorField), { namespace: 'field' });
+  ```
+
+  `withFieldCarrier` forwards the node **by reference** — nothing is copied,
+  narrowed or renamed — and consumes `schema` so it cannot reach the DOM through a
+  widget's `...props` spread.
+
+  A third-party widget that still reads `props.schema` and is **not** re-registered
+  through the adapter will read `undefined` in v17 and silently render an empty /
+  default state. That is the deliberate cost of a major boundary: one contract
+  beats N dialects, and a widget that picks the wrong spelling should fail at
+  compile time rather than work under one host and not another.
+
+  ## What did NOT change
+  - **Host metadata (SDUI JSON) is untouched.** No authored schema changes; this is
+    a change to how widgets are _written_, not to what apps declare.
+  - **`schema` is still the universal SDUI prop** every registered component
+    receives from `SchemaRenderer` (`element:*`, `page:*`, grids, reports). Only
+    the _field-widget_ contract retired it. In particular `renderFieldComponent`
+    still passes `schema` when a form field type resolves to a plain component
+    through the bare-name fallback (e.g. `type: 'text'` reaching the display text
+    widget) — that component's contract is the node, and dropping it there would
+    render `undefined.className`.
+
+  ## Payload equivalence
+
+  Every path that used to deliver a payload through `schema` now delivers the
+  identical object through `field`, and both halves are pinned by tests asserting
+  **object identity**, not shape:
+
+  - form path — `packages/components/src/renderers/form/__tests__/form-field-carrier.test.tsx`
+  - SDUI path — `packages/fields/src/__tests__/field-carrier-sdui.test.tsx`
+
+### Patch Changes
+
+- 680080a: The required state now reaches the input control as `aria-required`, instead of
+  existing only as part of the control's accessible name (objectui#3290).
+
+  The form renderer has always computed a correct `required` — the static
+  `required` flag merged with the `requiredWhen` CEL verdict — and then spent it
+  on exactly one thing: the red asterisk in `<FormLabel>`. That asterisk carried
+  `aria-label="required"`, so the only path from the computed state to assistive
+  tech was `<label for>` folding it into the control's **accessible name**: the
+  field was announced as "Title required".
+
+  A state smuggled through a name is broken three ways:
+
+  - it is read in name order rather than announced as a state, and "list the
+    required fields" style navigation cannot see it at all;
+  - a field rendered without a `label` (compact layouts, inline grid editing)
+    draws no asterisk, so the signal disappears entirely;
+  - `requiredWhen` makes required **dynamic**, and a state channel can express
+    the flip where a name cannot.
+
+  ## What changed
+  - Every field control — built-in (`input` / `textarea` / `checkbox` / `switch` /
+    `select`) and registered widget alike — now receives `aria-required="true"`
+    when the field resolves required, and **no attribute at all** when it does
+    not. Absence rather than `aria-required="false"` is deliberate: it is what
+    the `requiredWhen`-turns-false case has to produce.
+  - The red asterisk is now `aria-hidden="true"` and no longer carries
+    `aria-label="required"`. It renders exactly as before for sighted users; it
+    simply stops being announced, so the state is reported once (as a state) and
+    not twice.
+
+  **No field widget needed a change.** `aria-required` is already declared and
+  typed on the widget props contract (`FieldWidgetComponentProps &
+AriaAttributes`) and every widget forwards its leftover props to the control it
+  renders, so all 48 widgets pick it up unmodified.
+
+  Two non-changes, both deliberate:
+
+  - **No native `required` attribute.** That would arm the browser's own
+    constraint-validation bubble alongside react-hook-form's `<FormMessage/>` —
+    two validators, two UIs, one field. `aria-required` reports the state without
+    triggering native validation.
+  - **No `required` boolean in the widget props contract.** A boolean would give
+    the required marker a second author, and the next widget draws its own
+    asterisk next to the renderer's — the double-display failure objectui#3222
+    already declined for the validation message.
+
+  If you select the asterisk in a test, it is now
+  `span[data-required-marker]` — an explicit locator, rather than an
+  accessibility attribute doubling as a test hook.
+
+- a7651e6: The form renderer's built-in `select` branch stops saying "No options available"
+  in English to non-English sessions (objectui#3263).
+
+  FROM: the inline branch that renders a `type: 'select'` field — the one taken
+  whenever the field is a `BUILTIN_FIELD_TYPES` member, i.e. before the `field:`
+  registry is consulted — rendered `{emptyHint || 'No options available'}`. TO:
+  `{emptyHint || t('fields.options.empty')}`, the same i18n key the registered
+  option widgets fall back to (objectui#3231, all ten locale packs).
+
+  This was the last hardcoded copy of that sentence in `form.tsx`, and the file was
+  half-translated in a way a user could see inside one widget: the dependency-gate
+  sentence next to it already went through `t()`
+  (`fields.options.selectFirst`), so under a `zh` session a gated select read
+  "请先选择Country" and the same select — one keystroke later, when the parent
+  value matched no option — flipped to English.
+
+  `fields.options.empty` is added to `useSafeFormTranslation`'s defaults map, the
+  pattern `fields.options.selectFirst` already follows there, so a form rendered
+  with no `I18nProvider` (standalone widget, test, embedded form) produces the
+  byte-identical English string it produced before. Both halves are pinned by
+  tests: the Chinese rendering in one file, the no-provider English fallback in
+  another (mounting a provider installs it as react-i18next's global default,
+  which would erase the state the second one observes).
+
+  The box moved from an inline `<div>` into a small `BuiltinSelectEmptyState`
+  component in the same file, because `renderFieldComponent` is a plain helper that
+  early-returns on the registered-widget path — a hook called there would run
+  conditionally. It forwards its rest props, since `<FormControl>` is a Radix
+  `Slot` that supplies the control's `id` / `aria-describedby`; a test pins that
+  the field's `<label for>` still resolves to this box.
+
+  Deliberately NOT unified with `@object-ui/fields`' `OptionsEmptyState`: different
+  package, different render path (inline branch vs. registry). What the two share
+  is the i18n key, not a component — merging them would impose one path's markup
+  and props on the other.
+
+- 825bbe3: The option widgets' "this list cannot be filled" message now has one source, and
+  it is translated (objectui#3231).
+
+  FROM: `SelectField`, `MultiSelectField`, `RadioField` and `CheckboxesField` each
+  carried their own copy of the empty/gated state, each destructured the declared
+  `emptyHint` prop into `_emptyHint` and dropped it, and each rendered a hardcoded
+  English literal (`'No options available'`, `` `Select ${…} first` ``) even in a
+  Chinese or Japanese session. TO: one shared `OptionsEmptyState` — the host's
+  `emptyHint` when it supplied one, otherwise a translated fallback
+  (`fields.options.empty` / `fields.options.selectFirst`, added to all ten locale
+  packs).
+
+  `emptyHint` was declared, produced by the form renderer and transported, then
+  lost three times over — so no registered widget could ever render it. All three
+  breaks are fixed, because closing only the last one delivers nothing:
+
+  - `isOptionField` compared the raw resolved type against `'select'` /`'radio'` /
+    `'multiselect'` / `'checkboxes'`. Object-derived forms emit
+    `mapFieldTypeToFormType`'s prefixed ids (`field:select`), which matched none of
+    them, so for every option field coming from an object schema — the normal case
+    in the console — the whole cascade block was skipped and no hint was computed
+    at all. It now normalizes the `field:` prefix, the same normalization
+    `stripRegisteredFieldProps` already applied a few lines below.
+  - `stripRegisteredFieldProps` then removed the `emptyHint` key from what was
+    left. It is now forwarded to the four cascade option types, alongside
+    `dependentValues`. This stays an allow-list rather than a blanket
+    pass-through: every other registered widget spreads its leftover props onto a
+    DOM node, where an unknown `emptyHint` attribute is a React warning.
+  - the widgets themselves discarded it. Keeping it out of the `...props` spread
+    was correct; not using it afterwards was not.
+
+  User-visible effect: a dependency-gated option list now prompts with the
+  controlling field's **label** ("Select Country first") instead of its raw
+  metadata name, in the session's language; an unconfigured list says so in the
+  session's language too. The gate sentence is one i18n key shared by the renderer
+  and the widget fallback, so the two sides cannot word it differently.
+
+  Untouched: the built-in (unregistered) `select` branch of the form renderer,
+  which already consumed `emptyHint`. That is a separate live path.
+
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/sdui-parser@17.3.0
+  - @object-ui/react-runtime@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/components/package.json b/packages/components/package.json
index 0ade0e5127..2caf0e752f 100644
--- a/packages/components/package.json
+++ b/packages/components/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/components",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Standard UI component library for Object UI, built with Shadcn UI + Tailwind CSS",
diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md
index 161e109d13..3961bd526a 100644
--- a/packages/core/CHANGELOG.md
+++ b/packages/core/CHANGELOG.md
@@ -1,5 +1,58 @@
 # @object-ui/core
 
+## 17.3.0
+
+### Minor Changes
+
+- f833d3a: Retire `validation` from the action-param contract — it was declared on both
+  halves, read by neither, and rejected outright by the server (objectui#3201).
+
+  FROM: `validation?: string` was declared on the AUTHORING type
+  (`@object-ui/types`' `ActionParam`) and on the RESOLVED type (`@object-ui/core`'s
+  `ActionParamDef`). TO: it is declared on neither.
+
+  **Breaking for anyone who declared it — but it never did anything.** This is
+  marked `minor`, not `major`, per the repo's version-alignment policy (objectui's
+  major tracks `@objectstack`'s, so objectui's own breaking changes ship as `minor`
+  with the breaking semantics spelled out here).
+
+  **Migration: delete it.** If you authored `validation: '...'` on an action param,
+  it never took effect, and publishing that metadata to the server is a hard parse
+  failure — so any metadata that reached production either never carried the key or
+  never parsed. Removing it changes no runtime behaviour; it only moves the error
+  from "silent no-op, then rejected at publish" to a `tsc` error at the keystroke.
+
+  Why it could not work as authored:
+
+  - `ActionParamSchema` in `@objectstack/spec/ui` is `.strict()` and does not list
+    `validation`, so an authored key is a PARSE REJECTION on the server:
+    `Unrecognized key(s) on this action param: \`validation\``. Meanwhile `tsc`
+    against the public type accepted it — the type vouched for a key the platform
+    itself refuses.
+  - Nothing read it on the resolved side either: it was never a key of
+    `resolveActionParams()`'s `RawActionParam`, the runtime field metadata a
+    field-backed param inherits from carries no `validation` to source one from,
+    and `paramToField()` never mapped it — so it could not reach the field widgets,
+    whose rules `buildValidationRules()` builds from `required` / `minLength` /
+    `maxLength` / `pattern`.
+
+  Removed rather than implemented, on ADR-0049 enforce-or-remove. Giving it meaning
+  would mean first deciding what an "expression" is here (CEL? a formula? a regex?)
+  and adding it to `@objectstack/spec`, which is where such a capability has to
+  start — not accreted renderer-side around a key the contract does not have.
+
+  This also retires the last named exception in objectui#3174's drift guard
+  (`packages/types/src/__tests__/page-nav-misc-spec-parity.test.ts`), which carried
+  `validation` as the one key `ActionParam` added on top of the spec's set. The
+  rule it pins — **the authoring type declares exactly the spec's authorable
+  keys** — is now literal: the guard asserts the local-only key set is empty, so
+  any future addition fails the build instead of being waved through.
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/core/package.json b/packages/core/package.json
index ec1220e613..6640acdd4c 100644
--- a/packages/core/package.json
+++ b/packages/core/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/core",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
diff --git a/packages/create-plugin/CHANGELOG.md b/packages/create-plugin/CHANGELOG.md
index 42f306a195..7f0e0fd384 100644
--- a/packages/create-plugin/CHANGELOG.md
+++ b/packages/create-plugin/CHANGELOG.md
@@ -1,5 +1,7 @@
 # @object-ui/create-plugin
 
+## 17.3.0
+
 ## 17.2.0
 
 ## 17.1.0
diff --git a/packages/create-plugin/package.json b/packages/create-plugin/package.json
index 682c76ec52..d13a6ddbb0 100644
--- a/packages/create-plugin/package.json
+++ b/packages/create-plugin/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/create-plugin",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "CLI tool to scaffold ObjectUI plugins",
   "type": "module",
   "license": "MIT",
diff --git a/packages/data-objectstack/CHANGELOG.md b/packages/data-objectstack/CHANGELOG.md
index 9253dcd6dd..ee830ee2ac 100644
--- a/packages/data-objectstack/CHANGELOG.md
+++ b/packages/data-objectstack/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @object-ui/data-objectstack
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/data-objectstack/package.json b/packages/data-objectstack/package.json
index d27baebe7e..4ac97206bb 100644
--- a/packages/data-objectstack/package.json
+++ b/packages/data-objectstack/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/data-objectstack",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "ObjectStack Data Adapter for Object UI",
   "license": "MIT",
   "type": "module",
diff --git a/packages/fields/CHANGELOG.md b/packages/fields/CHANGELOG.md
index b6b24c2985..e2ba3e51fc 100644
--- a/packages/fields/CHANGELOG.md
+++ b/packages/fields/CHANGELOG.md
@@ -1,5 +1,259 @@
 # @object-ui/fields
 
+## 17.3.0
+
+### Minor Changes
+
+- 56409c2: Field widgets are finally told when their field fails validation, and the props
+  slot that carries it takes the name the published contract gives it
+  (objectui#3222).
+
+  **Breaking** for anyone implementing a field widget (see migration below). The
+  repo version policy keeps this a `minor` — objectui's major tracks
+  `@objectstack`'s — so read the bump as "breaking within objectui".
+
+  ## The a11y defect this fixes
+
+  `@objectstack/spec/ui`'s `FieldWidgetPropsSchema` — the published contract that
+  third-party and AI-authored field widgets are written against — has always
+  declared `error?: string`. `@object-ui/fields` declared its own slot as
+  `errorMessage`. That looked like a naming split; it was worse:
+
+  ```
+  producers of `errorMessage` anywhere in packages/ + apps/ :  0
+  reads of `errorMessage` in packages/fields/src            : 15  (7 widgets)
+  reads of `props.error`                                    :  0
+  ```
+
+  The slot was dead under BOTH spellings. No host ever passed it: the form
+  renderer showed validation text through its own `<FormMessage/>` and never
+  forwarded the prop. So `EmailField`, `CurrencyField`, `UrlField`,
+  `RichTextField`, `PercentField`, `TextAreaField` and `PhoneField` each computed
+  `aria-invalid={!!errorMessage}` from a value that was `undefined` forever —
+  **`aria-invalid` had never once been set, and a screen reader was never told
+  the field had failed validation.**
+
+  Worse than "never set": `<FormControl>` is a Radix `Slot` that hands its child a
+  CORRECT `aria-invalid`, but a widget's own attribute is written after the props
+  spread, so it wins. Those seven widgets were actively overwriting the right
+  answer with `false`.
+
+  FROM: `renderFieldComponent` received no validation state, and the widget props
+  type declared `errorMessage?: string`, which nothing produced.
+  TO: the form renderer passes react-hook-form's `fieldState.error?.message` down
+  as `error` when it renders a registered widget, and the props type declares
+  `error?: string`. Both ends of the contract are live for the first time; a
+  rename alone would only have swapped one dead key for another.
+
+  ## Migration for widget authors
+
+  ```diff
+  -export function MyField({ value, onChange, field, readonly, errorMessage }: FieldWidgetComponentProps< string >) {
+  -  return <Input value={value} aria-invalid={!!errorMessage} />;
+  +export function MyField({ value, onChange, field, readonly, error }: FieldWidgetComponentProps< string >) {
+  +  return <Input value={value} aria-invalid={!!error} />;
+  ```
+
+  No alias is kept. `errorMessage` was retained nowhere on purpose — a tolerant
+  second spelling is exactly the de-facto second contract AGENTS.md #0.1 forbids,
+  and it is what would let a missed call site go quiet again. Because
+  objectui#3221 had already removed the type's `[key: string]: any`, every missed
+  site is a compile error rather than a silent `any`, so the compiler — not grep
+  — validated this rename.
+
+  ## Responsibilities are split, not duplicated
+
+  The widget consumes `error` **only** to drive `aria-invalid` on the control it
+  renders (which only it can do — `aria-invalid` has to sit on the input element).
+  The message TEXT stays with `<FormMessage/>` in the form renderer. A widget that
+  also renders the text double-displays it, and the docs, the agent prompt and the
+  tests all now say so.
+
+  For the same reason `required` — also declared by the spec, also never delivered
+  — is deliberately NOT lowered into widget props: the required marker has exactly
+  one author, the renderer's `<FormLabel>`, and giving widgets the flag invites a
+  second asterisk. The a11y state a widget could legitimately carry is
+  `aria-required`, which needs no contract change at all (`AriaAttributes` is
+  already part of the type and widgets already forward it).
+
+  Builtin field types are unaffected: they render inside `<FormControl>`, whose
+  Slot already supplies `aria-invalid`, so `error` is stripped there rather than
+  leaking into the DOM as a stray attribute.
+
+  Docs updated to match: `content/docs/guide/plugin-development.md`,
+  `skills/objectui/guides/plugin-development.md` and
+  `.github/prompts/component.prompt.md` — the last of which additionally used the
+  spec's non-generic type alias as a generic (`FieldWidgetProps< number >`) and
+  destructured a `mode` prop that exists on neither type.
+
+- 042e09d: **BREAKING (v17)** — field widgets receive their metadata on ONE key, `field`.
+  `schema` is removed from the widget contract (objectui#3233).
+
+  ## What changed
+
+  `schema` was a second carrier for what `field` already means. Two producers fed
+  it: `SchemaRenderer` passed the authored node as `schema`, and the form
+  renderer's `renderFieldComponent` passed `schema={props.field || props.schema ||
+props}` _alongside_ `field`. The predictable result was ~30 widgets resolving
+  their config as `field || schema` — one concept, two spellings, a de-facto
+  second contract (AGENTS.md #0.1).
+
+  - `FieldWidgetComponentProps` no longer declares `schema`. Reading
+    `props.schema` is now a compile error, not a silent `any`.
+  - Both producers converged. The form renderer passes `field` only. The SDUI node
+    → `field` translation happens exactly once, in a new registration adapter
+    (`withFieldCarrier`), which every built-in field widget is registered through.
+  - All `field || schema` reads in `@object-ui/fields` are now plain `field` reads.
+
+  ## Migrating a widget you wrote
+
+  **Reading the metadata** — replace the fallback with the single key:
+
+  ```diff
+  -const config = field || (props as any).schema;
+  +const config = field;
+  ```
+
+  **Registering a widget** — if your widget can be rendered from a schema node
+  (anything `SchemaRenderer` dispatches, not just forms), wrap it once so it still
+  gets `field`:
+
+  ```diff
+  +import { withFieldCarrier } from '@object-ui/fields';
+  +
+  -ComponentRegistry.register('color', ColorField, { namespace: 'field' });
+  +ComponentRegistry.register('color', withFieldCarrier(ColorField), { namespace: 'field' });
+  ```
+
+  `withFieldCarrier` forwards the node **by reference** — nothing is copied,
+  narrowed or renamed — and consumes `schema` so it cannot reach the DOM through a
+  widget's `...props` spread.
+
+  A third-party widget that still reads `props.schema` and is **not** re-registered
+  through the adapter will read `undefined` in v17 and silently render an empty /
+  default state. That is the deliberate cost of a major boundary: one contract
+  beats N dialects, and a widget that picks the wrong spelling should fail at
+  compile time rather than work under one host and not another.
+
+  ## What did NOT change
+  - **Host metadata (SDUI JSON) is untouched.** No authored schema changes; this is
+    a change to how widgets are _written_, not to what apps declare.
+  - **`schema` is still the universal SDUI prop** every registered component
+    receives from `SchemaRenderer` (`element:*`, `page:*`, grids, reports). Only
+    the _field-widget_ contract retired it. In particular `renderFieldComponent`
+    still passes `schema` when a form field type resolves to a plain component
+    through the bare-name fallback (e.g. `type: 'text'` reaching the display text
+    widget) — that component's contract is the node, and dropping it there would
+    render `undefined.className`.
+
+  ## Payload equivalence
+
+  Every path that used to deliver a payload through `schema` now delivers the
+  identical object through `field`, and both halves are pinned by tests asserting
+  **object identity**, not shape:
+
+  - form path — `packages/components/src/renderers/form/__tests__/form-field-carrier.test.tsx`
+  - SDUI path — `packages/fields/src/__tests__/field-carrier-sdui.test.tsx`
+
+### Patch Changes
+
+- 825bbe3: The option widgets' "this list cannot be filled" message now has one source, and
+  it is translated (objectui#3231).
+
+  FROM: `SelectField`, `MultiSelectField`, `RadioField` and `CheckboxesField` each
+  carried their own copy of the empty/gated state, each destructured the declared
+  `emptyHint` prop into `_emptyHint` and dropped it, and each rendered a hardcoded
+  English literal (`'No options available'`, `` `Select ${…} first` ``) even in a
+  Chinese or Japanese session. TO: one shared `OptionsEmptyState` — the host's
+  `emptyHint` when it supplied one, otherwise a translated fallback
+  (`fields.options.empty` / `fields.options.selectFirst`, added to all ten locale
+  packs).
+
+  `emptyHint` was declared, produced by the form renderer and transported, then
+  lost three times over — so no registered widget could ever render it. All three
+  breaks are fixed, because closing only the last one delivers nothing:
+
+  - `isOptionField` compared the raw resolved type against `'select'` /`'radio'` /
+    `'multiselect'` / `'checkboxes'`. Object-derived forms emit
+    `mapFieldTypeToFormType`'s prefixed ids (`field:select`), which matched none of
+    them, so for every option field coming from an object schema — the normal case
+    in the console — the whole cascade block was skipped and no hint was computed
+    at all. It now normalizes the `field:` prefix, the same normalization
+    `stripRegisteredFieldProps` already applied a few lines below.
+  - `stripRegisteredFieldProps` then removed the `emptyHint` key from what was
+    left. It is now forwarded to the four cascade option types, alongside
+    `dependentValues`. This stays an allow-list rather than a blanket
+    pass-through: every other registered widget spreads its leftover props onto a
+    DOM node, where an unknown `emptyHint` attribute is a React warning.
+  - the widgets themselves discarded it. Keeping it out of the `...props` spread
+    was correct; not using it afterwards was not.
+
+  User-visible effect: a dependency-gated option list now prompts with the
+  controlling field's **label** ("Select Country first") instead of its raw
+  metadata name, in the session's language; an unconfigured list says so in the
+  session's language too. The gate sentence is one i18n key shared by the renderer
+  and the widget fallback, so the two sides cannot word it differently.
+
+  Untouched: the built-in (unregistered) `select` branch of the form renderer,
+  which already consumed `emptyHint`. That is a separate live path.
+
+- a321fa4: `TextAreaField`'s mobile fullscreen flag converges on its one real producer
+  (objectui#3232).
+
+  FROM: the widget resolved the "show the expand affordance" decision through a
+  four-way `??` chain — a `mobileFullscreen` (camelCase) prop, the field
+  metadata's `mobile_fullscreen`, a `mobile_fullscreen` prop, and
+  `schema.mobile_fullscreen`. TO: a single read of the field metadata's
+  `mobile_fullscreen`, resolved through the `field || schema` carrier pair every
+  widget in this package already uses.
+
+  No runtime behaviour changes, because three of those four reads were
+  permanently `undefined`:
+
+  - `mobileFullscreen` (camelCase) had **no producer anywhere in the repo** — the
+    only occurrences of that spelling were the widget's own read and the
+    destructure that kept it off the DOM spread. The doc comment nonetheless
+    claimed "the host form passes `mobileFullscreen`", so the contract it
+    described had never held.
+  - `mobile_fullscreen` as a **prop** cannot arrive: the form renderer's
+    `stripRegisteredFieldProps` explicitly removes `mobile_fullscreen` and
+    `fullscreen` from the props forwarded to registered field widgets.
+  - `schema.mobile_fullscreen` was the same object `field || schema` already
+    resolves, so it could only ever restate the metadata read.
+
+  What actually drives the affordance — and is now the only thing that does — is
+  the field metadata flag `ObjectForm` stamps onto long-text fields from
+  `ObjectFormSchema.mobile.fullscreenLongText`. That path is unchanged and is now
+  pinned by tests (button, dialog, and the committed edit), so the cleanup cannot
+  have silently removed the working behaviour.
+
+  Also untouched: the built-in (unregistered) `textarea` branch of the form
+  renderer, which reads `mobile_fullscreen || fullscreen` off the form-field
+  props and renders its own `FullscreenTextarea`. That is a separate live path.
+
+  Why this is worth a changeset rather than a silent tidy-up: reads that nobody
+  writes are not free. They document a contract that does not exist — the next
+  author follows the comment, passes the prop, and is ignored without a word —
+  and a `??` chain that accepts four spellings and rejects none is exactly where
+  a misspelled key hides. With one source, a wrong spelling has no read path left
+  to absorb it. Per AGENTS.md #0.1 and Prime Directive #12, divergence like this
+  converges at the producer, not by accumulating tolerance at the consumer. No
+  host-override prop was invented in its place: inventing a key with no producer
+  is the same mistake in the other direction.
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/providers@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/fields/package.json b/packages/fields/package.json
index 6082dac153..33b15f6be0 100644
--- a/packages/fields/package.json
+++ b/packages/fields/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/fields",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "Field renderers and registry for Object UI",
   "license": "MIT",
   "type": "module",
diff --git a/packages/i18n/CHANGELOG.md b/packages/i18n/CHANGELOG.md
index 17c6f58d56..6ddd9cd8cc 100644
--- a/packages/i18n/CHANGELOG.md
+++ b/packages/i18n/CHANGELOG.md
@@ -1,5 +1,49 @@
 # @object-ui/i18n
 
+## 17.3.0
+
+### Patch Changes
+
+- 825bbe3: The option widgets' "this list cannot be filled" message now has one source, and
+  it is translated (objectui#3231).
+
+  FROM: `SelectField`, `MultiSelectField`, `RadioField` and `CheckboxesField` each
+  carried their own copy of the empty/gated state, each destructured the declared
+  `emptyHint` prop into `_emptyHint` and dropped it, and each rendered a hardcoded
+  English literal (`'No options available'`, `` `Select ${…} first` ``) even in a
+  Chinese or Japanese session. TO: one shared `OptionsEmptyState` — the host's
+  `emptyHint` when it supplied one, otherwise a translated fallback
+  (`fields.options.empty` / `fields.options.selectFirst`, added to all ten locale
+  packs).
+
+  `emptyHint` was declared, produced by the form renderer and transported, then
+  lost three times over — so no registered widget could ever render it. All three
+  breaks are fixed, because closing only the last one delivers nothing:
+
+  - `isOptionField` compared the raw resolved type against `'select'` /`'radio'` /
+    `'multiselect'` / `'checkboxes'`. Object-derived forms emit
+    `mapFieldTypeToFormType`'s prefixed ids (`field:select`), which matched none of
+    them, so for every option field coming from an object schema — the normal case
+    in the console — the whole cascade block was skipped and no hint was computed
+    at all. It now normalizes the `field:` prefix, the same normalization
+    `stripRegisteredFieldProps` already applied a few lines below.
+  - `stripRegisteredFieldProps` then removed the `emptyHint` key from what was
+    left. It is now forwarded to the four cascade option types, alongside
+    `dependentValues`. This stays an allow-list rather than a blanket
+    pass-through: every other registered widget spreads its leftover props onto a
+    DOM node, where an unknown `emptyHint` attribute is a React warning.
+  - the widgets themselves discarded it. Keeping it out of the `...props` spread
+    was correct; not using it afterwards was not.
+
+  User-visible effect: a dependency-gated option list now prompts with the
+  controlling field's **label** ("Select Country first") instead of its raw
+  metadata name, in the session's language; an unconfigured list says so in the
+  session's language too. The gate sentence is one i18n key shared by the renderer
+  and the widget fallback, so the two sides cannot word it differently.
+
+  Untouched: the built-in (unregistered) `select` branch of the form renderer,
+  which already consumed `emptyHint`. That is a separate live path.
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/i18n/package.json b/packages/i18n/package.json
index 62e2b5ad57..bd8a86bc19 100644
--- a/packages/i18n/package.json
+++ b/packages/i18n/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/i18n",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
diff --git a/packages/layout/CHANGELOG.md b/packages/layout/CHANGELOG.md
index 174c5d4d79..da7c151796 100644
--- a/packages/layout/CHANGELOG.md
+++ b/packages/layout/CHANGELOG.md
@@ -1,5 +1,56 @@
 # @object-ui/layout
 
+## 17.3.0
+
+### Patch Changes
+
+- d2363e7: The legacy `page-header` alias stops advertising `description` as an authorable
+  key (objectui#3226).
+
+  FROM: `registerLayout()` declared `inputs: [title, description]`. TO:
+  `inputs: [title, subtitle]` — the key `@objectstack/spec/ui`'s `PageHeaderProps`
+  declares, and the one the canonical `page:header` renderer in
+  `@object-ui/components` already declares.
+
+  `inputs` is a DECLARATION surface, not documentation: the designer builds its
+  property palette from it, and the framework's `check:react-declaration-parity`
+  diffs it against the spec schemas. Declaring `description` therefore did not
+  merely tolerate a legacy spelling — it published a second dialect for the one
+  concept the protocol calls `subtitle`, and told authors (an AI author most
+  readily, since the registry is what it reads to learn the shape) that the
+  non-spec key was legal. Metadata that took the offer renders a subtitle under
+  `page-header` and silently loses it under `page:header`: same JSON, two results,
+  which is the outcome a single contract exists to prevent.
+
+  No runtime behaviour changes. `PageHeader` still reads `subtitle ?? description`,
+  deliberately: this alias exists for out-of-repo consumer schemas, so "no in-repo
+  author writes `description`" (verified — zero hits) is not evidence that nobody
+  does, and dropping the read today would delete an external page's second line
+  while its title kept rendering, the least reportable failure mode there is. That
+  read is retired together with an ADR-0087 D2 conversion entry
+  (`page-header-subtitle-alias`, `description` → `subtitle` rewritten at load
+  time), which lives in the framework repo and is tracked separately. Narrowing the
+  declaration did not need to wait on it and breaks no consumer; leaving the
+  declaration wrong in the meantime keeps minting the metadata the conversion would
+  then have to absorb.
+
+  New tests pin both halves so neither can drift back: the registration may not
+  declare `description`, must declare `subtitle`, and — checked against the spec's
+  own shape rather than a hand-written allowlist — may declare nothing
+  `@objectstack/spec` does not; while the runtime fallback is pinned as a sequencing
+  guard, to be deleted in the same change that lands the conversion entry.
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/layout/package.json b/packages/layout/package.json
index 9b9a9711ef..cf4c6a2dc4 100644
--- a/packages/layout/package.json
+++ b/packages/layout/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/layout",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "sideEffects": false,
   "main": "dist/index.umd.cjs",
diff --git a/packages/mobile/CHANGELOG.md b/packages/mobile/CHANGELOG.md
index e8f210ab8e..8fd8e38da5 100644
--- a/packages/mobile/CHANGELOG.md
+++ b/packages/mobile/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/mobile
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/mobile/package.json b/packages/mobile/package.json
index 6bd424e3ce..1db623e0a2 100644
--- a/packages/mobile/package.json
+++ b/packages/mobile/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/mobile",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Mobile optimization for Object UI with responsive components, PWA support, and touch gesture handling.",
diff --git a/packages/permissions/CHANGELOG.md b/packages/permissions/CHANGELOG.md
index 2d2bedfee5..0d44bb5ebd 100644
--- a/packages/permissions/CHANGELOG.md
+++ b/packages/permissions/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/permissions
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/permissions/package.json b/packages/permissions/package.json
index d977ecfb14..5ee0bc860f 100644
--- a/packages/permissions/package.json
+++ b/packages/permissions/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/permissions",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "RBAC permission system for Object UI with object/field/row-level access control, permission guards, and hooks.",
diff --git a/packages/plugin-ai/CHANGELOG.md b/packages/plugin-ai/CHANGELOG.md
index ccafe26652..e0b47eaac8 100644
--- a/packages/plugin-ai/CHANGELOG.md
+++ b/packages/plugin-ai/CHANGELOG.md
@@ -1,5 +1,20 @@
 # @object-ui/plugin-ai
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-ai/package.json b/packages/plugin-ai/package.json
index 2916971179..410f0bf4a2 100644
--- a/packages/plugin-ai/package.json
+++ b/packages/plugin-ai/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-ai",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "main": "dist/index.umd.cjs",
   "module": "dist/index.js",
diff --git a/packages/plugin-calendar/CHANGELOG.md b/packages/plugin-calendar/CHANGELOG.md
index 05f0e2b354..af23f6d780 100644
--- a/packages/plugin-calendar/CHANGELOG.md
+++ b/packages/plugin-calendar/CHANGELOG.md
@@ -1,5 +1,26 @@
 # @object-ui/plugin-calendar
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [12bf669]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/plugin-detail@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/mobile@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-calendar/package.json b/packages/plugin-calendar/package.json
index 8bc7ce8460..0031ab20b0 100644
--- a/packages/plugin-calendar/package.json
+++ b/packages/plugin-calendar/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-calendar",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Calendar view plugins for Object UI - includes both ObjectQL-integrated and standalone calendar components",
diff --git a/packages/plugin-charts/CHANGELOG.md b/packages/plugin-charts/CHANGELOG.md
index abf5bd3078..4a2fed1648 100644
--- a/packages/plugin-charts/CHANGELOG.md
+++ b/packages/plugin-charts/CHANGELOG.md
@@ -1,5 +1,21 @@
 # @object-ui/plugin-charts
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-charts/package.json b/packages/plugin-charts/package.json
index a8ff347ab8..1581292d1c 100644
--- a/packages/plugin-charts/package.json
+++ b/packages/plugin-charts/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-charts",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Chart components plugin for Object UI, powered by Recharts",
diff --git a/packages/plugin-chatbot/CHANGELOG.md b/packages/plugin-chatbot/CHANGELOG.md
index 5a59a6f862..396fab57bc 100644
--- a/packages/plugin-chatbot/CHANGELOG.md
+++ b/packages/plugin-chatbot/CHANGELOG.md
@@ -1,5 +1,21 @@
 # @object-ui/plugin-chatbot
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-chatbot/package.json b/packages/plugin-chatbot/package.json
index ba66517208..578078f283 100644
--- a/packages/plugin-chatbot/package.json
+++ b/packages/plugin-chatbot/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-chatbot",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Chatbot interface plugin for Object UI",
diff --git a/packages/plugin-dashboard/CHANGELOG.md b/packages/plugin-dashboard/CHANGELOG.md
index 412903ec2f..24d3060606 100644
--- a/packages/plugin-dashboard/CHANGELOG.md
+++ b/packages/plugin-dashboard/CHANGELOG.md
@@ -1,5 +1,23 @@
 # @object-ui/plugin-dashboard
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-dashboard/package.json b/packages/plugin-dashboard/package.json
index 424763d574..36064003ec 100644
--- a/packages/plugin-dashboard/package.json
+++ b/packages/plugin-dashboard/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-dashboard",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Dashboard plugin for Object UI",
diff --git a/packages/plugin-designer/CHANGELOG.md b/packages/plugin-designer/CHANGELOG.md
index ea00fe48dd..cc732ee3f1 100644
--- a/packages/plugin-designer/CHANGELOG.md
+++ b/packages/plugin-designer/CHANGELOG.md
@@ -1,5 +1,26 @@
 # @object-ui/plugin-designer
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/plugin-form@17.3.0
+  - @object-ui/plugin-grid@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/data-objectstack@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-designer/package.json b/packages/plugin-designer/package.json
index dd9a43788e..b399daa7ac 100644
--- a/packages/plugin-designer/package.json
+++ b/packages/plugin-designer/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-designer",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Visual designer plugin for Object UI with page, data model, process, and report designers plus collaborative editing.",
diff --git a/packages/plugin-detail/CHANGELOG.md b/packages/plugin-detail/CHANGELOG.md
index 1ab1662ee5..1a6632e86d 100644
--- a/packages/plugin-detail/CHANGELOG.md
+++ b/packages/plugin-detail/CHANGELOG.md
@@ -1,5 +1,57 @@
 # @object-ui/plugin-detail
 
+## 17.3.0
+
+### Patch Changes
+
+- 12bf669: The record discussion panel now says "loading" while it is loading, instead of
+  "No comments yet" (objectui#3209).
+
+  FROM: opening any record page showed the discussion/chatter panel asserting
+  `No comments yet` for the whole first leg of the page, then contradicting
+  itself when the comments appeared. TO: the panel shows the loading row until
+  the feed has actually answered, and only then commits to "this record has no
+  comments".
+
+  objectui#3205 gave `RecordActivityTimeline` the render branch that prefers a
+  loading row over the empty copy, and `RecordChatterPanel` already forwarded
+  `loading` to it in both positions — but on the chatter chain **nothing
+  produced the signal**, so that branch could never fire. `record:activity`
+  computes its own flag and was visibly fixed by #3205; chatter was not. The
+  four wiring points are one chain and are all closed here, because any one of
+  them left open still ships the empty copy to some user:
+
+  - `RecordDetailView` — the host that OWNS the feed fetch — now derives a
+    `feedLoading` flag from its two reads (`sys_comment` + `sys_activity`);
+  - `<DiscussionContextProvider loading={feedLoading}>` publishes it (the field
+    was already declared on `DiscussionContextValue`, and already read by
+    `record:activity`);
+  - the auto-appended `<RecordChatterPanel loading={feedLoading}>` — the panel
+    authored pages get when they place no discussion slot — receives it
+    directly;
+  - the `record:chatter` / `record:discussion` renderer forwards
+    `loading={discussion?.loading}`, so a hand-placed block is on the same
+    chain as the synthesized one.
+
+  The two reads run in parallel, so the flag closes over **both**: it clears on
+  `Promise.allSettled`, and a REJECTED read counts as an answer. A deployment
+  without the audit plugin 404s `sys_activity` and an object with
+  `enable.feeds: false` 403s `sys_comment`; neither may pin the panel in a
+  permanent spinner, which would be a worse bug than the one being fixed. The
+  flag is keyed by `object:recordId` rather than being a plain boolean, so the
+  first render of a record already reads as loading (no one-frame flash of the
+  empty state) and navigating between records cannot show the previous record's
+  settled answer.
+
+  No tolerance was added at the consumer. The timeline still does not guess that
+  "no items yet and just mounted" means loading — that guess is wrong the moment
+  a record genuinely has no comments, and the signal belongs to whoever owns the
+  fetch. Same shape as objectui#3165 / #3205: divergence converges at the
+  producer.
+
+- Updated dependencies [825bbe3]
+  - @object-ui/i18n@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-detail/package.json b/packages/plugin-detail/package.json
index f5e8b0ddf9..7153dbbe92 100644
--- a/packages/plugin-detail/package.json
+++ b/packages/plugin-detail/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-detail",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "DetailView plugin for Object UI - comprehensive detail page with sections, tabs, and related lists",
diff --git a/packages/plugin-editor/CHANGELOG.md b/packages/plugin-editor/CHANGELOG.md
index dc8a1c3ae4..7163a1283b 100644
--- a/packages/plugin-editor/CHANGELOG.md
+++ b/packages/plugin-editor/CHANGELOG.md
@@ -1,5 +1,20 @@
 # @object-ui/plugin-editor
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-editor/package.json b/packages/plugin-editor/package.json
index 4993a19c6e..22d5f95081 100644
--- a/packages/plugin-editor/package.json
+++ b/packages/plugin-editor/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-editor",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Rich text editor plugin for Object UI, powered by Monaco Editor",
diff --git a/packages/plugin-form/CHANGELOG.md b/packages/plugin-form/CHANGELOG.md
index 2ad26615b6..11b554a53e 100644
--- a/packages/plugin-form/CHANGELOG.md
+++ b/packages/plugin-form/CHANGELOG.md
@@ -1,5 +1,24 @@
 # @object-ui/plugin-form
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/permissions@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-form/package.json b/packages/plugin-form/package.json
index 960add3478..1fb8b83400 100644
--- a/packages/plugin-form/package.json
+++ b/packages/plugin-form/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-form",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Form plugin for Object UI",
diff --git a/packages/plugin-gantt/CHANGELOG.md b/packages/plugin-gantt/CHANGELOG.md
index b638ae0b83..fcaf8875f3 100644
--- a/packages/plugin-gantt/CHANGELOG.md
+++ b/packages/plugin-gantt/CHANGELOG.md
@@ -1,5 +1,25 @@
 # @object-ui/plugin-gantt
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [12bf669]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/plugin-detail@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-gantt/package.json b/packages/plugin-gantt/package.json
index 6ef2b719e7..09cb4b3cda 100644
--- a/packages/plugin-gantt/package.json
+++ b/packages/plugin-gantt/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-gantt",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Gantt chart plugin for Object UI",
diff --git a/packages/plugin-grid/CHANGELOG.md b/packages/plugin-grid/CHANGELOG.md
index c178b17f6e..fdb562fef4 100644
--- a/packages/plugin-grid/CHANGELOG.md
+++ b/packages/plugin-grid/CHANGELOG.md
@@ -1,5 +1,25 @@
 # @object-ui/plugin-grid
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/mobile@17.3.0
+  - @object-ui/permissions@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-grid/package.json b/packages/plugin-grid/package.json
index 39a890c66b..280c27a951 100644
--- a/packages/plugin-grid/package.json
+++ b/packages/plugin-grid/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-grid",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Grid plugin for Object UI",
diff --git a/packages/plugin-kanban/CHANGELOG.md b/packages/plugin-kanban/CHANGELOG.md
index c484043e26..6b6c419357 100644
--- a/packages/plugin-kanban/CHANGELOG.md
+++ b/packages/plugin-kanban/CHANGELOG.md
@@ -1,5 +1,25 @@
 # @object-ui/plugin-kanban
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [12bf669]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/plugin-detail@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-kanban/package.json b/packages/plugin-kanban/package.json
index 920236e49b..c2cb07c8bc 100644
--- a/packages/plugin-kanban/package.json
+++ b/packages/plugin-kanban/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-kanban",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Kanban board plugin for Object UI, powered by dnd-kit",
diff --git a/packages/plugin-list/CHANGELOG.md b/packages/plugin-list/CHANGELOG.md
index 0dc63b5460..929b6e1093 100644
--- a/packages/plugin-list/CHANGELOG.md
+++ b/packages/plugin-list/CHANGELOG.md
@@ -1,5 +1,7 @@
 # @object-ui/plugin-list
 
+## 17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-list/package.json b/packages/plugin-list/package.json
index 5a74a0c6da..967003f8b1 100644
--- a/packages/plugin-list/package.json
+++ b/packages/plugin-list/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-list",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "ListView plugin for Object UI - unified view component with view type switching",
diff --git a/packages/plugin-map/CHANGELOG.md b/packages/plugin-map/CHANGELOG.md
index 1239c94ca3..1917d7d6f5 100644
--- a/packages/plugin-map/CHANGELOG.md
+++ b/packages/plugin-map/CHANGELOG.md
@@ -1,5 +1,20 @@
 # @object-ui/plugin-map
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-map/package.json b/packages/plugin-map/package.json
index 2aeaec221e..a2462f1600 100644
--- a/packages/plugin-map/package.json
+++ b/packages/plugin-map/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-map",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Map visualization plugin for Object UI",
diff --git a/packages/plugin-markdown/CHANGELOG.md b/packages/plugin-markdown/CHANGELOG.md
index 7a0b97c262..17b779e792 100644
--- a/packages/plugin-markdown/CHANGELOG.md
+++ b/packages/plugin-markdown/CHANGELOG.md
@@ -1,5 +1,20 @@
 # @object-ui/plugin-markdown
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-markdown/package.json b/packages/plugin-markdown/package.json
index 30531b5031..e7fd0eabde 100644
--- a/packages/plugin-markdown/package.json
+++ b/packages/plugin-markdown/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-markdown",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Markdown rendering plugin for Object UI, powered by react-markdown",
diff --git a/packages/plugin-report/CHANGELOG.md b/packages/plugin-report/CHANGELOG.md
index fd23d80f7e..ac913f9615 100644
--- a/packages/plugin-report/CHANGELOG.md
+++ b/packages/plugin-report/CHANGELOG.md
@@ -1,5 +1,24 @@
 # @object-ui/plugin-report
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+- Updated dependencies [a321fa4]
+  - @object-ui/components@17.3.0
+  - @object-ui/fields@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/plugin-grid@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-report/package.json b/packages/plugin-report/package.json
index c20f14a75c..5efb65db70 100644
--- a/packages/plugin-report/package.json
+++ b/packages/plugin-report/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-report",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "main": "dist/index.umd.cjs",
   "module": "dist/index.js",
diff --git a/packages/plugin-timeline/CHANGELOG.md b/packages/plugin-timeline/CHANGELOG.md
index 0dd997a91d..3e962d2366 100644
--- a/packages/plugin-timeline/CHANGELOG.md
+++ b/packages/plugin-timeline/CHANGELOG.md
@@ -1,5 +1,22 @@
 # @object-ui/plugin-timeline
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+  - @object-ui/mobile@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/plugin-timeline/package.json b/packages/plugin-timeline/package.json
index 8bced11a49..0138f6dd77 100644
--- a/packages/plugin-timeline/package.json
+++ b/packages/plugin-timeline/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-timeline",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Timeline component plugin for Object UI",
diff --git a/packages/plugin-tree/CHANGELOG.md b/packages/plugin-tree/CHANGELOG.md
index 28547d051b..8f26e4991f 100644
--- a/packages/plugin-tree/CHANGELOG.md
+++ b/packages/plugin-tree/CHANGELOG.md
@@ -1,5 +1,20 @@
 # @object-ui/plugin-tree
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-tree/package.json b/packages/plugin-tree/package.json
index e5509561d5..16c08b9a7f 100644
--- a/packages/plugin-tree/package.json
+++ b/packages/plugin-tree/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-tree",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Tree / tree-grid visualization plugin for Object UI",
diff --git a/packages/plugin-view/CHANGELOG.md b/packages/plugin-view/CHANGELOG.md
index 4e3c6ca418..b6da4c5ecc 100644
--- a/packages/plugin-view/CHANGELOG.md
+++ b/packages/plugin-view/CHANGELOG.md
@@ -1,5 +1,23 @@
 # @object-ui/plugin-view
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/plugin-form@17.3.0
+  - @object-ui/plugin-grid@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/plugin-view/package.json b/packages/plugin-view/package.json
index cbd5ae3c27..1852c96812 100644
--- a/packages/plugin-view/package.json
+++ b/packages/plugin-view/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/plugin-view",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Object View plugin for Object UI",
diff --git a/packages/providers/CHANGELOG.md b/packages/providers/CHANGELOG.md
index 91fac63d39..fd2b2d44c4 100644
--- a/packages/providers/CHANGELOG.md
+++ b/packages/providers/CHANGELOG.md
@@ -1,5 +1,12 @@
 # @object-ui/providers — Changelog
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/providers/package.json b/packages/providers/package.json
index d8b389e0ab..b920bdd7f1 100644
--- a/packages/providers/package.json
+++ b/packages/providers/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/providers",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "Reusable context providers for ObjectUI applications",
diff --git a/packages/react-runtime/CHANGELOG.md b/packages/react-runtime/CHANGELOG.md
index cd44f51d1b..403cd27fa3 100644
--- a/packages/react-runtime/CHANGELOG.md
+++ b/packages/react-runtime/CHANGELOG.md
@@ -1,5 +1,7 @@
 # @object-ui/react-runtime
 
+## 17.3.0
+
 ## 17.2.0
 
 ## 17.1.0
diff --git a/packages/react-runtime/package.json b/packages/react-runtime/package.json
index 1943f6d365..f3d2c8c5d8 100644
--- a/packages/react-runtime/package.json
+++ b/packages/react-runtime/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/react-runtime",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
diff --git a/packages/react/CHANGELOG.md b/packages/react/CHANGELOG.md
index 671dc1f19a..96561fd2cd 100644
--- a/packages/react/CHANGELOG.md
+++ b/packages/react/CHANGELOG.md
@@ -1,5 +1,16 @@
 # @object-ui/react
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/i18n@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/data-objectstack@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/react/package.json b/packages/react/package.json
index 6c25f30315..9eebee3fef 100644
--- a/packages/react/package.json
+++ b/packages/react/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/react",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "license": "MIT",
   "description": "React bindings and SchemaRenderer component for Object UI",
diff --git a/packages/runner/CHANGELOG.md b/packages/runner/CHANGELOG.md
index 8ede3ce17a..e00b0e83a2 100644
--- a/packages/runner/CHANGELOG.md
+++ b/packages/runner/CHANGELOG.md
@@ -1,5 +1,22 @@
 # @object-ui/runner
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [680080a]
+- Updated dependencies [a7651e6]
+- Updated dependencies [56409c2]
+- Updated dependencies [042e09d]
+- Updated dependencies [825bbe3]
+- Updated dependencies [f833d3a]
+  - @object-ui/components@17.3.0
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+  - @object-ui/plugin-charts@17.3.0
+  - @object-ui/plugin-kanban@17.3.0
+  - @object-ui/react@17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/runner/package.json b/packages/runner/package.json
index 50c8ff6e37..37104cb219 100644
--- a/packages/runner/package.json
+++ b/packages/runner/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@object-ui/runner",
   "private": false,
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "Universal Object UI Application Runner",
   "type": "module",
   "homepage": "https://www.objectui.org/docs/utilities/runner",
diff --git a/packages/sdui-parser/CHANGELOG.md b/packages/sdui-parser/CHANGELOG.md
index 1ad1e23a2e..ef96e6a01b 100644
--- a/packages/sdui-parser/CHANGELOG.md
+++ b/packages/sdui-parser/CHANGELOG.md
@@ -1,5 +1,7 @@
 # @object-ui/sdui-parser
 
+## 17.3.0
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/sdui-parser/package.json b/packages/sdui-parser/package.json
index ad64541c05..8038645e92 100644
--- a/packages/sdui-parser/package.json
+++ b/packages/sdui-parser/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/sdui-parser",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "type": "module",
   "sideEffects": false,
   "license": "MIT",
diff --git a/packages/types/CHANGELOG.md b/packages/types/CHANGELOG.md
index 61ce5572ec..edece1ed05 100644
--- a/packages/types/CHANGELOG.md
+++ b/packages/types/CHANGELOG.md
@@ -1,5 +1,53 @@
 # @object-ui/types
 
+## 17.3.0
+
+### Minor Changes
+
+- f833d3a: Retire `validation` from the action-param contract — it was declared on both
+  halves, read by neither, and rejected outright by the server (objectui#3201).
+
+  FROM: `validation?: string` was declared on the AUTHORING type
+  (`@object-ui/types`' `ActionParam`) and on the RESOLVED type (`@object-ui/core`'s
+  `ActionParamDef`). TO: it is declared on neither.
+
+  **Breaking for anyone who declared it — but it never did anything.** This is
+  marked `minor`, not `major`, per the repo's version-alignment policy (objectui's
+  major tracks `@objectstack`'s, so objectui's own breaking changes ship as `minor`
+  with the breaking semantics spelled out here).
+
+  **Migration: delete it.** If you authored `validation: '...'` on an action param,
+  it never took effect, and publishing that metadata to the server is a hard parse
+  failure — so any metadata that reached production either never carried the key or
+  never parsed. Removing it changes no runtime behaviour; it only moves the error
+  from "silent no-op, then rejected at publish" to a `tsc` error at the keystroke.
+
+  Why it could not work as authored:
+
+  - `ActionParamSchema` in `@objectstack/spec/ui` is `.strict()` and does not list
+    `validation`, so an authored key is a PARSE REJECTION on the server:
+    `Unrecognized key(s) on this action param: \`validation\``. Meanwhile `tsc`
+    against the public type accepted it — the type vouched for a key the platform
+    itself refuses.
+  - Nothing read it on the resolved side either: it was never a key of
+    `resolveActionParams()`'s `RawActionParam`, the runtime field metadata a
+    field-backed param inherits from carries no `validation` to source one from,
+    and `paramToField()` never mapped it — so it could not reach the field widgets,
+    whose rules `buildValidationRules()` builds from `required` / `minLength` /
+    `maxLength` / `pattern`.
+
+  Removed rather than implemented, on ADR-0049 enforce-or-remove. Giving it meaning
+  would mean first deciding what an "expression" is here (CEL? a formula? a regex?)
+  and adding it to `@objectstack/spec`, which is where such a capability has to
+  start — not accreted renderer-side around a key the contract does not have.
+
+  This also retires the last named exception in objectui#3174's drift guard
+  (`packages/types/src/__tests__/page-nav-misc-spec-parity.test.ts`), which carried
+  `validation` as the one key `ActionParam` added on top of the spec's set. The
+  rule it pins — **the authoring type declares exactly the spec's authorable
+  keys** — is now literal: the guard asserts the local-only key set is empty, so
+  any future addition fails the build instead of being waved through.
+
 ## 17.2.0
 
 ### Minor Changes
diff --git a/packages/types/package.json b/packages/types/package.json
index fe69f4e7a3..78a39ff5c2 100644
--- a/packages/types/package.json
+++ b/packages/types/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@object-ui/types",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "description": "Pure TypeScript type definitions for Object UI - The Protocol Layer",
   "type": "module",
   "sideEffects": false,
diff --git a/packages/vscode-extension/CHANGELOG.md b/packages/vscode-extension/CHANGELOG.md
index fc49504e16..5f689d6f1e 100644
--- a/packages/vscode-extension/CHANGELOG.md
+++ b/packages/vscode-extension/CHANGELOG.md
@@ -1,5 +1,13 @@
 # Changelog
 
+## 17.3.0
+
+### Patch Changes
+
+- Updated dependencies [f833d3a]
+  - @object-ui/types@17.3.0
+  - @object-ui/core@17.3.0
+
 ## 17.2.0
 
 ### Patch Changes
diff --git a/packages/vscode-extension/package.json b/packages/vscode-extension/package.json
index 2bd58d0ecc..c5fafdf305 100644
--- a/packages/vscode-extension/package.json
+++ b/packages/vscode-extension/package.json
@@ -2,7 +2,7 @@
   "name": "object-ui",
   "displayName": "Object UI",
   "description": "VSCode extension for Object UI - Schema-driven UI development with IntelliSense, validation, and live preview",
-  "version": "17.2.0",
+  "version": "17.3.0",
   "publisher": "objectui",
   "private": true,
   "icon": "icon.svg",