fix(fields): the retired-field tombstone names the spelling it was resolved under

[objectstack-fleet]

Fixes #10471
Clause-②: no

Summary

RetiredFieldTombstone took the spelling it names from the field it was handed: field.type, then schema.type, then type. When a retired spelling arrives through an authored widget, both form hosts resolve the widget first. So the owner tombstone was chosen, but it was handed a field whose type is a live type. It then said "Field type user was retired", put user in data-retired-field-type, lost the prescription for owner, and logged nothing, because reportRetiredFieldType('user') does nothing for a live type.

The change is in @object-ui/fields only:

• RetiredFieldTombstone reads a new optional prop, retiredFieldType, first. The old derivation from the field is used only when the prop is absent.
• A private retiredFieldTombstoneFor(spelling) returns the tombstone with that prop bound by a closure. It is cached, so each spelling has one stable component.
• Both resolvers that answer a retired key with the tombstone now hand out the bound one: getLazyFieldWidget (which FormPage, ActionParamDialog and the bulk dialog render through) and the field: registrations made by registerAllFields() (the record form's lookup).
• RETIRED_FIELD_TYPES is unchanged. There is no second table and no second prescription: the tombstone still reads the prescription from the table, by the spelling.
• reportRetiredFieldType still fires once per spelling. It dedupes on the spelling, and the spelling is now the right one.

Which hosts can receive a retired key through a key other than field.type

Read and measured at base c5d715fc1, before any edit.

Host	How it picks the key	Can the key differ from field.type?	Change here
FormPage (apps/console)	resolveFieldWidgetKey reads field.widget first, then calls getLazyFieldWidget(key)	Yes. Reproduced on both routes	None in the host. Fixed through getLazyFieldWidget
Record form (form.tsx in @object-ui/components)	f.widget, else f.field.widget, else f.type, then the field:KEY registry entry	Yes. Reproduced (the card had this path as a source reading only)	None in the host. Fixed through the registration
InlineFieldInput (@object-ui/plugin-detail)	editType = field.type, then renders RetiredFieldTombstone directly with field	No. Its key is field.type	Left alone. The fallback derivation serves it
ActionParamDialog, BulkActionDialog	getLazyFieldWidget(field.type)	No	None. They now get the bound tombstone, which names the same spelling

Reproduction, before the change (base c5d715fc1, pins added, the change not yet made)

FormPage, real widgets, both /forms/:name and /f/:slug: 4 failed, 3 passed.

form-view field { field: 'who', widget: 'owner' } over a `user` object field
  data-retired-field-type = "user"    text = "[object-ui] Field type `user` was retired."
object field { type: 'text', widget: 'owner' }
  data-retired-field-type = "text"    text = "[object-ui] Field type `text` was retired."
CONTROL: object field { type: 'owner' }
  data-retired-field-type = "owner"   text = the table's `owner` prescription     (green)

Record form (form.tsx, real renderer, registerAllFields()): 7 failed, 5 passed. The ObjectForm shape (type: 'field:user', widget: 'owner', raw metadata as field) named user. A standalone { type: 'text', widget: 'owner' } named text. widget: 'field:owner' over a user field named user. The console prescription for owner was written 0 times, not once. The type: 'owner' control stayed green.

The pins

• apps/console/src/components/FormPage.retiredWidget-10471.test.tsx: both routes. For each retired spelling it checks the card's two reproductions, plus a control row whose type is the retired spelling. Every row must render a tombstone with role="alert", data-retired-field-type equal to the spelling, and text equal to RETIRED_FIELD_TYPES[spelling]. The spellings and prescriptions are read from the table at runtime, never restated. It sits beside the objectui#10176 pin, which covers the type path.
• packages/fields/src/__tests__/retired-widget-spelling-10471.test.tsx: the same facts at the resolver level. getLazyFieldWidget(spelling) and the field: registry entry are each rendered with a live-typed field. The test checks that both return one stable component per spelling, and that the prescription is written to the console exactly once for two rendered rows. The explicit prop wins over the field, and the fallback still reads field.type. Record-form reproductions: the ObjectForm shape, a standalone text field, and widget: 'field:SPELLING', plus the type control.
• packages/fields/src/__tests__/owner-retired.test.tsx: two assertions compared the registry entry by identity with RetiredFieldTombstone. The entry is now the bound tombstone. One assertion now renders the registry entry and checks the spelling it names. The survivor assertion now compares field:user with the field:owner entry, which keeps it meaningful.

Ablation (committed state 1fcca8f96, restored by blob)

This removes the key hand-off. The mutation ran through node ../objectstack/scripts/ablation-replace.mjs in wrap mode, under a restore trap:

• anchor: RetiredFieldTombstone {...props} retiredFieldType={spelling} inside the bound component's JSX, replaced by RetiredFieldTombstone {...props}
• on-disk proof: anchor count 1 to 0, replacement count 0 to 1, and the blob went from 022261ef6513 to 62e3f6f6de25. All three were read again from disk inside the wrapped command before vitest ran.
• result: 10 failed, 27 passed across the two new pins, the objectui#10176 pin and owner-retired.test.tsx
  • red: the 4 FormPage reproductions, which named user or text; the 3 record-form reproductions; getLazyFieldWidget and the registry entry, which named user and text; the console-once check, which counted 0 instead of 1
  • green: both FormPage type: 'owner' controls, the record-form type control, the explicit-prop and fallback tests, the stable-identity test, all of objectui#10176, and all of owner-retired.test.tsx
• restore: the blob is 022261ef6513 again, equal to the HEAD blob. git diff HEAD is empty and git status --porcelain is empty.
• The same ablation at 0c611ec25, before a types-only cleanup commit, gave the same 10 failed and 27 passed.

Every @object-ui/* specifier resolves to src/ through the root vitest.config.mts and the console vite.config.ts aliases, so no build sits between the mutation and the tests.

Gates (at 1fcca8f96 unless noted)

• pnpm exec vitest run packages/fields/ from the repo root: 195 files passed, 1 skipped, 3231 tests passed, 7 skipped.
• pnpm exec vitest run apps/console/src/components/: 31 of 31 files and 410 of 410 tests passed.
• The 5 retired-type pin files, verbose, at 0c611ec25: 47 of 47 passed. This includes packages/plugin-detail/src/__tests__/InlineFieldInput.retiredFieldType.test.tsx, run as a check on the unchanged direct-render host.
• pnpm --filter @object-ui/fields type-check after building @object-ui/fields^...: exit 0. tsconfig.test.json lists both new or edited pin files (--listFilesOnly).
• pnpm --filter @object-ui/console type-check after building @object-ui/console^...: exit 0. It was re-run at 1fcca8f96 after rebuilding @object-ui/fields, and again exited 0. tsc --listFilesOnly lists the new FormPage pin.
• eslint over the 4 touched files with --no-inline-config: 0 errors. Per-rule counts on packages/fields/src/index.tsx equal the base's (react-refresh/only-export-components 93, no-explicit-any 44, no-unused-vars 1). owner-retired.test.tsx has 0 at base and head, and the two new files have 0. No type-aware linting is configured (no parserOptions.project in eslint.config.js), so this diff cannot change the verdict on any untouched file.
• node scripts/check-changeset-presence.mjs: exit 0 (4 source files in 2 released packages, 1 changeset).
• pnpm check:changeset-claims: exit 0 (report-only). It named 4 pending changesets that mention packages/fields/src/index.tsx: 6625-retire-fieldmeta-decimals, 6694-dashboard-lookup-reference-meta, 6837-reference-to-arm-deletion and 7166-retire-inert-fieldmeta-copies. I read each paragraph. They describe cell renderers and lookup metadata, which this diff does not touch, so none of them became false. The self-contradiction reading passed.
• pnpm check:control-bytes: OK. pnpm check:new-line-citations: 0 new citations.
• Also run, all exit 0: check:registry-bare-names, check:vi-mock-specifiers, check:vi-mock-inherit, check:vi-mock-override-shape, check:pending-changeset-literals, check:test-path-roots.
• NOT MEASURED: check:sdui-registration-pins. It needs a built apps/console/dist and answered exit 2 (prerequisite not met), so it is left to CI.

Changeset

.changeset/10471-tombstone-names-resolved-spelling.md: '@object-ui/fields': patch. apps/console changes only by one test file. It is in the fixed release group and is not private, and the one declaration satisfies the presence gate.

Fences held

• The objectui#10529 region of packages/fields/src/index.tsx is untouched: RepeaterCellRenderer, buildStandardCellRendererMap and the export near the top. The hunks sit in getLazyFieldWidget, the tombstone, and the retired loop of registerAllFields.
• FormPage's fallback for an unregistered widget is untouched. widget: 'field:owner' on a FormPage row still renders a text input: that is objectui#10472's case, and objectui#10472 remains open.

Acceptance notes

• Observation, not filed (owner: none): InlineFieldInput routes by field.type and reads no widget hint except permission-facet-link. So { type: 'user', widget: 'owner' } would inline-edit as a person picker, while the record form refuses it. This comes from reading the source only; it was not run. Whether inline edit should honour widget hints at all is a separate question.
• The field:owner registry entry is no longer RetiredFieldTombstone itself but the bound component in the same family (its displayName is RetiredFieldTombstone(owner)). A search found no production code that compares it by identity.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 4 pending changeset(s) describe a file this change touches

Their bodies publish verbatim into the CHANGELOG at the next release, so this is a request to re-read them against your diff — addressed here because you are the one seat that can answer it without re-deriving anything.

⛔ Nothing here blocks, and nothing here is a verdict on your change. This gate exits 0, is not a required context, and judges name resolution, never meaning: it asked whether a pending body names a file you touched. "Is this sentence still true?" is the one question it will not answer, and the one you are being asked to answer.

.changeset/6625-retire-fieldmeta-decimals.md

• names fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  buildFieldMeta computed decimals: overrides.decimals ?? meta?.decimals ?? meta?.scale on every call and the value reached nothing. Re-measured on this branch's base (efdc6c62): zero .decimals member reads across @object-ui/fields, @object-ui/i18n, @object-ui/components, @object-ui/core and plugin-dashboard itself — the only non-comment occurrence was the write being removed here. The positive control in the same query shape fires: .scale member reads hit NumberField.tsx, GridField.tsx and fields/src/index.tsx. So the zero is a finding, not a broken query. The overrides.decimals ?? head of that chain had already lost its only feeder when objectui#6425's ruling removed the authored read from ObjectDataTable.enrich(); RecordDetailDrawer, the only other buildFieldMeta caller, passes no overrides at all. Both halves retire together, so the key leaves in one move.

.changeset/6694-dashboard-lookup-reference-meta.md

• names packages/fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  ⚠️ The copy set is three keys where ObjectGrid's RELATIONAL_META_KEYS is nine, and the difference is measured per key, not preferred. The grid's cells are EDITABLE, so its extra keys drive the inline picker's query (LookupField / UserField read id_field, description_field, lookup_filters, lookupFilters); these two widgets are read-only and their render path ends at a cell renderer. packages/fields/src/index.tsx reads exactly reference_to, reference and display_field off a cell's field prop; titleFormat is never read off a field meta at all (its readers take it off the object schema, which arrives here through useRefObjectSchema(reference_to)), and reference_to_field has zero member reads anywhere in the repo. Copying the other six would mint six members written on every call and read by nothing — precisely what objectui#6625 (decimals) and objectui#6597 (referenceTo) retired from this same file.

.changeset/6837-reference-to-arm-deletion.md

• names fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  Three readers were deliberately left alone. LookupCellRenderer (fields/src/index.tsx), LookupField and UserField read FieldMetadata — ObjectUI's OWN contract, whose LookupFieldMetadata declares reference_to and never declares reference. They are fed by the emitters above and by published example schemas (examples/schema-catalog/src/schemas/fields-lookup/*.json), so narrowing them would break in-repo producers, and plugin-grid's relationalMetaCopySet.derivation.test.ts re-derives its read set from exactly those three sources — where reference_to is recorded with verdict adapter-stamped. DetailViewFieldSchema is likewise untouched.

.changeset/7166-retire-inert-fieldmeta-copies.md

• names packages/fields/src/index.tsx → packages/fields/src/index.tsx — edited by this change

  applyRelationalMeta writes the copy set onto the fieldMeta that generateColumns hands to ANGLE-BRACKETS(CellRenderer) as the field prop — six JSX passes across the three column-building paths, and nowhere else. For a relational column that resolves to LookupCellRenderer, which reads exactly reference_to, reference, display_field, displayField, reference_field and options; a user column resolves to UserCellRenderer, which destructures { value } and reads no field meta at all. Measured by receiver rather than by count: packages/fields/src/index.tsx, the file holding every cell renderer, contains zero occurrences of the three retired keys, against a control of 22 occurrences of the display_field / displayField / reference_to spellings the cell does read.

Read the paragraph, not the line: both false halves of the objectui#8617 claim sat in one paragraph, and correcting either alone would have left it asserting the same wrong thing.

If a claim did go false, correct the body. That is precedented and prose-only, frontmatter untouched; check-changeset-overwrite.mjs will report the correction as its own case 2 ("correcting a declaration on purpose … legitimate"), which is the intended shape — one gate asks for the read, the other records the write.

Not covered, stated so nobody reads this as more: a born-false claim that spells no line address at all (objectui#9495 coordinated one by ORDINAL — "a grep finds that member first" — and deciding that means reading what the sentence means), a claim spelled as a symbol or a package rather than a backticked file name, and a file named ambiguously.

Angle-bracketed names in the quoted prose above are rewritten as ANGLE-BRACKETS(name): GitHub deletes tag-shaped fragments from a stored body, and a quote that silently loses the identifier it is about is worse than a visible repair.

Compared the checked-out tree with 51d18f161 (merge-base with origin/main): 4 file(s) changed outside .changeset/, read against 1430 pending declaration(s) that publish a body (2012 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3046.3 KB	3104.5 KB
Main entry chunk (gzip)	147.7 KB	350 KB
Entry file	index-DIj8UtF3.js	—
Status	PASS	—

The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it.

---

📦 Bundle Size Report

Package	Size	Gzipped
app-shell (consoleActionDispatch.js)	0.20KB	0.19KB
app-shell (index.js)	16.68KB	6.20KB
app-shell (runtime-config.js)	20.68KB	7.36KB
app-shell (types.js)	0.01KB	0.04KB
app-shell (urlParams.js)	10.06KB	3.86KB
auth (ActiveOrganizationStorage.js)	27.95KB	10.04KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.18KB	10.59KB
auth (AuthShell.js)	3.49KB	1.40KB
auth (ForgotPasswordForm.js)	12.21KB	3.45KB
auth (LoginForm.js)	18.15KB	5.39KB
auth (PreviewBanner.js)	0.90KB	0.50KB
auth (RegisterForm.js)	6.65KB	2.22KB
auth (SocialSignInButtons.js)	9.61KB	3.89KB
auth (UserMenu.js)	3.41KB	1.23KB
auth (auth-gate-events.js)	1.29KB	0.66KB
auth (authStyles.js)	5.04KB	1.72KB
auth (createAuthClient.js)	40.21KB	10.80KB
auth (createAuthenticatedFetch.js)	8.52KB	3.45KB
auth (index.js)	3.63KB	1.64KB
auth (invitation-status.js)	1.22KB	0.70KB
auth (org-roles.js)	6.66KB	2.78KB
auth (phone-identifier.js)	1.11KB	0.66KB
auth (types.js)	0.59KB	0.35KB
auth (useAuth.js)	5.30KB	1.02KB
auth (useWorkspaceAdminStatus.js)	11.08KB	4.58KB
collaboration (CommentThread.js)	27.13KB	7.95KB
collaboration (LiveCursors.js)	3.17KB	1.27KB
collaboration (PresenceAvatars.js)	6.49KB	2.64KB
collaboration (PresenceProvider.js)	2.79KB	1.13KB
collaboration (index.js)	1.68KB	0.73KB
collaboration (useCollaborationTranslation.js)	6.05KB	2.52KB
collaboration (useCommentSearch.js)	1.98KB	0.88KB
collaboration (useConflictResolution.js)	7.75KB	1.86KB
collaboration (useMentionNotifications.js)	1.81KB	0.68KB
collaboration (usePresence.js)	6.33KB	1.84KB
collaboration (useRealtimeSubscription.js)	7.91KB	2.01KB
components (index.js)	544.97KB	130.34KB
core (index.js)	9.22KB	3.71KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	223.86KB	62.25KB
fields (index.js)	257.29KB	65.14KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	2.59KB	1.22KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.24KB	2.27KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	39.40KB	12.91KB
i18n (useDisplayLocale.js)	3.52KB	1.76KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	39.28KB	11.09KB
mobile (MobileProvider.js)	0.92KB	0.49KB
mobile (ResponsiveContainer.js)	0.94KB	0.38KB
mobile (breakpoints.js)	1.51KB	0.70KB
mobile (createOfflineDataSource.js)	5.61KB	1.75KB
mobile (index.js)	1.99KB	0.87KB
mobile (offlineQueue.js)	3.91KB	1.35KB
mobile (pwa.js)	0.97KB	0.49KB
mobile (serviceWorker.js)	1.48KB	0.62KB
mobile (serviceWorkerSource.js)	3.41KB	1.48KB
mobile (useBreakpoint.js)	1.54KB	0.65KB
mobile (useGesture.js)	6.96KB	1.98KB
mobile (useOfflineSync.js)	1.99KB	0.72KB
mobile (usePullToRefresh.js)	6.62KB	2.45KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	5.52KB	2.10KB
mobile (useTouchTarget.js)	1.01KB	0.54KB
permissions (MePermissionsProvider.js)	13.52KB	4.88KB
permissions (PermissionContext.js)	0.31KB	0.25KB
permissions (PermissionGuard.js)	0.89KB	0.45KB
permissions (PermissionProvider.js)	6.24KB	2.16KB
permissions (discardProofCache.js)	1.04KB	0.55KB
permissions (evaluator.js)	8.33KB	3.07KB
permissions (index.js)	0.93KB	0.41KB
permissions (store.js)	0.91KB	0.42KB
permissions (useFieldPermissions.js)	1.28KB	0.53KB
permissions (usePermissions.js)	4.83KB	2.27KB
plugin-ai (index.js)	16.01KB	3.93KB
plugin-calendar (index.js)	51.38KB	14.60KB
plugin-charts (index.js)	74.95KB	20.88KB
plugin-chatbot (index.js)	198.36KB	47.20KB
plugin-dashboard (index.js)	133.56KB	35.38KB
plugin-designer (index.js)	216.25KB	44.39KB
plugin-detail (index.js)	232.25KB	61.40KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	146.50KB	37.51KB
plugin-gantt (index.js)	169.37KB	41.83KB
plugin-grid (index.js)	215.49KB	58.91KB
plugin-kanban (index.js)	49.30KB	15.39KB
plugin-list (index.js)	114.55KB	28.29KB
plugin-map (index.js)	23.82KB	7.42KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.55KB	11.99KB
plugin-timeline (index.js)	30.64KB	8.94KB
plugin-tree (index.js)	10.52KB	3.69KB
plugin-view (index.js)	88.00KB	21.97KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.66KB	3.50KB
providers (index.js)	0.45KB	0.23KB
providers (types.js)	0.01KB	0.04KB
react-runtime (index.js)	5.62KB	2.34KB
react (LazyPluginLoader.js)	4.47KB	1.63KB
react (SchemaRenderer.js)	114.58KB	37.60KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.03KB	1.86KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (body-dialect.js)	4.78KB	2.09KB
sdui-parser (codegen.js)	6.58KB	2.74KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	5.78KB	2.56KB
sdui-parser (input-type.js)	2.84KB	1.40KB
sdui-parser (kanban-quick-add.js)	3.89KB	1.87KB
sdui-parser (parse.js)	25.28KB	7.80KB
sdui-parser (provenance.js)	3.66KB	1.82KB
sdui-parser (types.js)	0.28KB	0.23KB
sdui-parser (validate.js)	18.27KB	6.20KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	2.87KB	1.00KB
types (base.js)	0.20KB	0.18KB
types (blocks.js)	0.20KB	0.18KB
types (complex.js)	2.93KB	1.49KB
types (crud.js)	0.20KB	0.18KB
types (dashboard-filter-alias.js)	6.23KB	2.74KB
types (data-display.js)	3.75KB	1.85KB
types (data-protocol.js)	0.20KB	0.19KB
types (data.js)	0.20KB	0.18KB
types (designer.js)	1.85KB	0.85KB
types (disclosure.js)	0.20KB	0.18KB
types (error-code.js)	1.54KB	0.88KB
types (expression.js)	0.20KB	0.18KB
types (feedback.js)	0.20KB	0.18KB
types (field-types.js)	0.20KB	0.18KB
types (form.js)	0.20KB	0.18KB
types (http-inflight.js)	8.87KB	3.73KB
types (http-retry.js)	4.32KB	2.02KB
types (icon-key-migration.js)	4.26KB	1.63KB
types (index.js)	4.74KB	2.25KB
types (layout.js)	0.20KB	0.18KB
types (managed-by.js)	0.19KB	0.18KB
types (mobile.js)	5.00KB	2.39KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	0.20KB	0.18KB
types (plugin-scope.js)	0.20KB	0.18KB
types (record-components.js)	0.20KB	0.19KB
types (record-semantics.js)	1.28KB	0.67KB
types (registry.js)	0.20KB	0.18KB
types (reports.js)	0.20KB	0.18KB
types (select-option.js)	0.20KB	0.19KB
types (spec-report.js)	5.05KB	1.93KB
types (spec-ui-namespace.js)	0.20KB	0.19KB
types (strict-authoring-face.js)	17.15KB	6.32KB
types (system-fields.js)	3.33KB	1.54KB
types (theme.js)	6.28KB	2.87KB
types (ui-action.js)	8.11KB	3.32KB
types (views.js)	0.20KB	0.18KB
types (widget.js)	0.20KB	0.18KB

Size Limits

• ✅ Core packages should be < 50KB gzipped
• ✅ Component packages should be < 100KB gzipped
• ⚠️ Plugin packages should be < 150KB gzipped