feat(types): ObjectChartSchema accepts the react tier's object-chart node — the spec's { name } series arm, family as specType (objectui#10770)

[objectstack-fleet]

Fixes #10770
Clause-②: yes

What this does

The react tier's ObjectChart block authors @objectstack/spec's ChartConfigSchema. Its react-blocks entry has schemaType: 'object-chart' and schema: ChartConfigSchema, and lists type and series in its data props. The react-page wrapper turns the objectstack showcase renewals-pipeline page's block into an object-chart node shaped { specType: 'bar', series: [{ name: 'total', label: 'Invoice value' }], … }. It parks the author's type as specType because type is the node's discriminator. Both faces of ObjectChartSchema refused that node.

This aligns the contract face with the spec (ruling 5617465269 principle 1, objectui#7759):

• series element: two arms. An entry is either the spec's ChartSeriesSchema (TS: ChartSeries), BY REFERENCE, which is the AUTHOR arm, or the unchanged INTERNAL { dataKey } arm that the relays compose.
• specType is declared, as the spec's ChartTypeSchema (TS: ChartType), by reference.
• chartType is optional. A zod .superRefine (requireObjectChartFamily) requires one of chartType or specType. That is the floor the required flag used to carry, so a node that names no family is still refused, at chartType. The TS interface cannot say "one of two"; the docblock states this as a ceiling.
• Docblocks. The series verdict ("INTERNAL … All five producers compose it") is rewritten: the react-page wrapper is a sixth producer, and it forwards the authored array untouched.

⛔ There is no objectui-only dialect: both new crossings are spec symbols, bound by reference. ⛔ There is no renderer change: normalizeChartSchema already reads specType and translates the { name } arm (one-time probe below). No other schema was changed.

Step 1: does any door run this schema on the wrapper's node? No.

• Render. SchemaRenderer runs core's structural validateSchema (development only), not zod. The react-page wrapper runs no zod.
• Publish. objectstack's react-page gate (packages/lint/src/validate-react-page-props.ts, read at objectstack fdb2669) reads the block's binding VALUES and resolves series[].dataKey ?? series[].name; the only schemas it parses are ChartAggregateSchema and ChartDrillDownSchema. objectstack imports no @object-ui/types: every hit in its tree is prose.
• objectui validate. It parses one JSON or YAML document. A react page's source is an opaque string: safeValidateSchema of a { type: 'page', kind: 'react', source } document carrying this block PASSES and never judges the block.
• Other runtime importers. Outside the types package, @object-ui/types/zod is imported at runtime only by the CLI (validate, check) and by plugin-map (ObjectMapConfigSchema).

⇒ No user met the refusal. The defect was on the contract face, and in the docblock's INTERNAL-only claim. This reading gives no reason to raise the grade.

Before (unmodified face, a probe on the wrapper-built node): ObjectChartSchema.safeParse gives invalid_value at chartType and invalid_type at series.0.dataKey; safeValidateSchema gives the same two. After: it parses with zero issues on both.

Files

In the claim's file surface:

• packages/types/src/objectql.ts and packages/types/src/zod/objectql.zod.ts, within the ObjectChartSchema block and its spec imports.
• the new pin packages/types/src/__tests__/object-chart-react-tier-node-10770.test.ts. It pins that the showcase node parses (on the mirror and through safeValidateSchema), that a series entry with neither name nor dataKey and a node naming no family are refused, that the author arm is strict and specType takes every spec ChartTypeSchema value, and the TS twin.
• .changeset/10770-object-chart-react-tier-node.md: @object-ui/types minor.
• zod-mirror-parity.test.ts: no row moved (green, unedited).

Beyond the claim's surface. Each is a pin that the widening falsified, not a drive-by:

• packages/types/src/__tests__/widget-schema-anchors-7946.test.ts: assertionSeriesBindsDataKey indexed ['dataKey'] on the element and went compile-red. It now reads the internal arm through Extract.
• packages/types/src/__tests__/imported-defaults-8317.test.ts: its census failed by name ("a schema imported by a mirror is not in this file's IMPORTED list … Add it", naming ChartSeriesSchema). The schema was added to the list.
• packages/plugin-charts/src/__tests__/ObjectChart.schemaAnchor-7946.test.ts: a consumer pin asserting the OPPOSITE (a @ts-expect-error that series: [{ name: 'amount' }] is refused). It went "Unused @ts-expect-error" once the rebuilt dist carried the union, which also serves as the reverse proof that the consumer compiled against the new declaration. It now pins the refusal that stands ([{ label: 'amount' }]). PR objectui#10787 does not touch this file (its file list was read).

Verification: first taken at 83f3e8662a, re-taken at the final head 77646f4150 (a merge of main only; see Patch round 1), pinned spec 17.4.0 unless noted

• @object-ui/types: type-check exit 0; vitest run packages/types/ exit 0, 250 files / 5387 tests at 77646f4150 (248 / 5362 at 83f3e8662a); the new pin 13/13.
• Reverse run of the new pin: both source files were put back to the base commit (requireObjectChartFamily count 3 then 0 on disk), and the pin went 8 failed / 5 passed. Restored with git checkout HEAD: git diff HEAD empty, blob hashes equal to HEAD, pin 13/13.
• Consumers (direction: four named downstream consumers of @object-ui/types, not the whole ...@object-ui/types closure). Dependency closure built first.
  • @object-ui/plugin-charts: type-check exit 0 (after the pin move above); vitest exit 0, 83 files / 1010 tests at 77646f4150 (82 / 964 at 83f3e8662a).
  • @object-ui/components (holds the react-page wrapper): type-check exit 0; vitest exit 0, 318 files passed and 1 skipped / 3121 tests passed and 17 skipped at 77646f4150 (315 + 1 / 3092 + 17 at 83f3e8662a).
  • @object-ui/plugin-dashboard (types ObjectChartSchema['aggregate']): type-check exit 0; vitest exit 0, 140 files / 1298 tests at 77646f4150 (137 / 1284 at 83f3e8662a).
  • @object-ui/cli (validate / check run safeValidateSchema): type-check exit 0; vitest exit 0, 20 files / 279 tests.
• Renderer: a one-time probe (not committed) ran normalizeChartSchema on the showcase node. It gave chartType: 'bar', xAxisKey: 'status' and series: [{ dataKey: 'total', label: 'Invoice value' }].
• Gates, each with its exit code before any pipe: check-changeset-presence 0 · check-changeset-no-major 0 · check:new-line-citations 0 (0 new citations) · check:control-bytes 0 · check:spec-symbols 0 · check:test-path-roots 0 · check-governed-queue-guard --test (7 paths) 0, NOT GOVERNED · check:changeset-claims 0 (report-only; see Acceptance notes) · check:pending-changeset-literals 0 · check:handler-key-reads 0 · check:component-surface-parity 0 (report-only) · check:designer-field-key-parity 0 · check:element-data-source-declaration 0 · check:doc-types 0.
• ESLint --no-inline-config on the 6 touched TS files: exit 0, 0 errors, 40 warnings (all no-explicit-any, no warnings ratchet). The file count (6) is read from --format json. Type-aware linting is not enabled in eslint.config.js (no projectService or parserOptions.project, and no custom rule reads parser services), so this diff cannot move a verdict on an untouched file.
• Spec Main Shape Gate, narrowed. @objectstack/spec was built from objectstack main fdb2669 in a throwaway checkout, packed, and injected with node scripts/spec-main-shape-gate.mjs inject. Then: @object-ui/types type-check exit 0, types build exit 0, @object-ui/plugin-charts type-check exit 0. CI's gate type-checks the whole tree. The patch round then measured the whole tree locally too (below), and CI's gate is green at 77646f4150.

NOT MEASURED locally:

• check:doc-snippets, check:doc-examples and check:skill-examples exit 2 with PRECONDITION NOT MET (the whole tree is unbuilt). Bound: no doc or skill types a value as ObjectChartSchema, and the only narrowing TS change is reading .dataKey off a series element.
• The repo-wide pnpm lint / pnpm test runs, which belong to CI. (The forced whole-tree type-check was measured locally in the patch round.)

Patch round 1 (final head 77646f4150)

The first CI run's required Spec Main Shape Gate was cancelled at its 45-minute timeout in step 12, the whole-tree type-check. The patch round measured the cause, and it was a degraded runner, not this PR:

• The whole-tree type-check (the gate's step-12 command, forced) takes the same time with and without this PR:

  • pinned: 472 s vs 480 s at the merge base;
  • spec main 17bd318: 485 s vs 488 s;
  • the objectstack commit the failed job compiled (e462186): 490 s, 81/81 tasks.

  The types program gains +0.2% instantiations, with no hot ObjectChartSchema construct in a --generateTrace.

• The failed job was slow on every step, including steps that never read this diff: spec build 547 s vs 109–156 s on four neighbouring gate jobs, and pack 62 s vs 10–13 s.

• No source changed. The only commit is a merge of origin/main 12809a595a. At 77646f4150 the gate is green in 12.1 min, and every CI job is green (Type Check 7.1 min). The seat's earlier diagnosis on this PR was corrected at 5858943102.

Acceptance notes

• Mixed entry. An entry that writes both name and dataKey parses through the internal arm with name stripped. That is the internal arm's existing strip posture, unchanged; the renderer reads dataKey first, so the drawn column is the same.
• Both family keys on one node. A node writing both chartType and specType is accepted, and normalizeChartSchema takes chartType first. It is not refused here, because that would be a new rule.
• specType value domain. specType accepts all of the spec's ChartTypeSchema values. normalizeChartSchema leaves a family it does not draw (metric, table, …) unset, which is already pinned by normalizeChartSchema.test.ts ("leaves a family this renderer cannot draw unset"). This is a pre-existing seam between spec and renderer. Carrier: none; noted, not filed.
• Publish-gate leniency. objectstack's react-page gate resolves series[].dataKey and xAxisKey on this block as legitimate, while the spec's ChartSeriesSchema refuses dataKey by name. That is leniency in objectstack's lint; it is not measured through os validate here. Carrier: none; noted, not filed.
• Comparison guard. ObjectChart's chartTypeIgnoresCompareTo(schema.chartType) reads chartType only, not specType. compareTo is not a react-block prop, so this is dormant. Carrier: none; noted, not filed.
• Instrument drift under main's zod. Under zod@4.6.1, which main's spec resolves, imported-defaults-8317.test.ts's "no member became REQUIRED" goes red for 16 schemas, 15 of them pre-existing plus ChartSeriesSchema. zod 4.6.1 reports _zod.optin === 'defaulted' for a member with a default, while its stripped twin reads 'optional'. Both are omissible, so this is instrument drift, not a narrowed accept set. It surfaces on the zod ^4.6.1 floor bump. Carrier: none (the next spec pin bump); noted, not filed.
• Superseded pending changesets. The pending changesets for objectui#10584, the objectui#7946 anchor and objectui#8086 describe series as the internal { dataKey } arm only. They record their own PRs, and this changeset supersedes them in the same release, so they are not edited.
• Card residue. The residue named on the card, app-shell ObjectView forwarding viewDef.chart.series verbatim, is untouched.

Implemented by the domain:spec#1 dispatch in session https://claude.ai/code/session_014fWVhLzhxR8qrFsJ5o8TYW.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 28 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/5903-objectgantt-declared-keys.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

• names src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both halves move together. The TS declaration (packages/types/src/objectql.ts) and its zod mirror (src/zod/objectql.zod.ts) gain the same ten keys at the same requiredness — all optional — and no KnownDrift entry is added. navigation is taken from @objectstack/spec's NavigationConfigSchema by reference rather than restated, matching ObjectGridSchema.navigation.

.changeset/6940-rowactions-boolean-mirror.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The list view's same-named rowActions in zod/objectql.zod.ts — z.array(z.string()), the legacy bare-name action list on ObjectGridSchema — is a different key that is correct as it stands, is in parity with its own TS twin (rowActions?: string[]), and is not touched.

.changeset/7113-chart-data-model.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  .extend() with a NEW key still works and preserves the fold and the refinement; .optional(), z.discriminatedUnion, z.toJSONSchema and safeValidateSchema are all unaffected. Nothing in this repository calls the throwing combinators on either const, and the published surface already ships refined mirrors (objectql.zod.ts, complex.zod.ts, form.zod.ts, app.zod.ts), so the class is not new — but it is a real behaviour change on a published export and it belongs in the release note rather than in a reviewer's file.

.changeset/7200-object-form-section-style-keys-undeclared.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The authored-metadata type now agrees with @objectstack/spec, whose FormSectionSchema is a strict object declaring neither key, and with the ruling's rationale (maintainer 2026-09-01, verbatim): "retire the reads … Declaring the keys was weighed and not adopted: it would formally invite free Tailwind strings into authored metadata, the exact class the boundary exists to keep out." A ?: never tombstone was not used: ObjectFormSection has no zod mirror (ObjectFormSchema in zod/objectql.zod.ts does not declare sections), so there is no parse door to refuse at, and a tombstone is still a declaration in completion and in the published .d.ts.

.changeset/7265-types-user-filter-field-derives.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  zod/objectql.zod.ts declared two schemas under names @objectstack/spec/ui already exports. They were triaged separately, by reading their sites, and went different ways.

.changeset/7322-object-kanban-group-by-limit.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Breaking for authored metadata: ObjectKanbanSchema.groupField is RETIRED (objectui#7322, ADR-0049 enforce-or-remove), and the two keys the object-kanban renderer actually reads — groupBy and limit — are now DECLARED and validated on both published faces: the TypeScript interface in objectql.ts and the Zod mirror in zod/objectql.zod.ts.

.changeset/7352-drill-down-config-mirror.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  DrillDownConfigSchema is the zod mirror of DrillDownConfig, and both declarations that carry drillDown reference it — ChartSchema (zod/data-display.zod.ts) and ObjectDataTableSchema (zod/objectql.zod.ts) — so the published validator under @object-ui/types/zod reads the key for the first time (objectui#7352).

.changeset/7363-objectql-union-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema and ObjectDataTableSchema are members of ObjectQLComponentSchema on both faces — the TS union in objectql.ts and the zod union in zod/objectql.zod.ts — so AnyComponentSchema, and with it validateSchema / safeValidateSchema / objectui validate, has an arm for object-gallery and object-data-table nodes (objectui#7363).

.changeset/7632-shared-record-source-config.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  That ladder is published contract on both faces — packages/types/src/objectql.ts and its zod mirror both ship .describe() strings naming getDataConfig's order (objectui#6939, maintainer ruling 2026-09-02), pinned by objectql-record-source-refinement-6939.test.ts — and it was hand-copied into five plugin components with no gate holding them together. A change to the ruled order had five edit sites and nothing that noticed a missed one; that is the AGENTS.md #0.1 drift class.

.changeset/7804-objectql-handler-key-arms.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The four plain objectql.ts node faces declare the nine handler keys their registered renderers read (objectui#7804, the objectql.ts slice): ObjectFormSchema.onCancel / .onError / .onOpenChange / .onStepChange / .onSuccess, ObjectGallerySchema.onCardClick / .onRowClick, ObjectGridSchema.onNavigate and ObjectViewSchema.onNavigate.

.changeset/7804-tree-view-handler-slot.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  'runtime-slot' and not 'retired', measured at this key's own channel. 'retired' publishes "no renderer reads this key, so nothing could ever run it" — true of the two siblings already tombstoned on this arm (onSelectChange, onExpandChange) and flatly false here, since the read is live and INVOKED. ⚠️ No in-repo host builds a tree-view node carrying the key: the channel is wired end to end and only the supplier is absent, which is the same shape as ObjectFormSchema.onStepChange in this card's objectql.ts slice and is not evidence of a dead read. The TypeScript declaration is unchanged and still callable, so a programmatic host supplies it exactly as before.

.changeset/7917-export-breadcrumb-object-tree-zod-schemas.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  AnyComponentSchema declares 107 node component types. 105 of them could be named on the ./zod barrel — ButtonSchema.safeParse(node), which is what a designer, a form builder or a targeted test needs. The arms declaring type: 'breadcrumb' (navigation.zod.ts) and type: 'object-tree' (objectql.zod.ts) could not: both were already export const in their own module, but index.zod.ts — the package's only zod entry point — did not re-export them, so the schemas existed, were maintained, and were applied by the union while no consumer could name them.

.changeset/7963-alert-dialog-footer-keys-retired.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Nothing else moves. These spellings are overloaded across the tree and every other owner is a live key on a different declaration — FormSchema.cancelLabel, objectql.ts's confirmLabel, plugin-designer's ConfirmDialog React props, plugin-grid's def.confirmLabel, and plugin-form's ModalForm / DrawerForm, which build a local cancelLabel from schema.cancelText. None is an AlertDialogSchema; none is touched, and a pin asserts it. No fixture, catalog schema, example app or doc fence authored any of the three on an alert-dialog node, so no shipped document is stranded.

.changeset/8478-describe-line-addresses.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Remove stale source-line citations (NAME.ext:NNN) from twelve published .describe() schema descriptions in packages/types/src/zod/overlay.zod.ts, zod/data-display.zod.ts and zod/objectql.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478).

.changeset/8735-objectql-mirror-docblocks-not-defaulted.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Correct four zod/objectql.zod.ts docblocks that described the behaviour objectui#8317 removed. Since that change the zod mirrors strip imported @objectstack/spec defaults at this package's import boundary, but the docblocks on HttpRequestSchema, ListColumnSchema, SelectionConfigSchema and PaginationConfigSchema still said, in the present tense, that method, prefix.type, type and pageSize are defaulted on parse — the opposite of what each export does. Each now says the key is declared and accepted but NOT defaulted on parse.

.changeset/8767-object-grid-refuses-string-sort.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  Migration. Write the array: sort: [{ field: 'name', order: 'desc' }]. Both keys are required. SortConfig.order carries no ? in @object-ui/types (packages/types/src/objectql.ts) and no .optional() in its zod mirror, and the protocol's own reusable SortItemSchema requires order as well — measured: that schema refuses [{ field: 'name' }] with invalid_value at 0.order. Do not omit it: this block's array arm interpolates whatever is present, so an omitted order lowers to $orderby: 'name undefined' today. That is pre-existing behaviour on the arm this change does not touch, and it is filed as a successor card rather than widened into here.

.changeset/8801-object-kanban-allow-collapse-retired.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  • the declarations retired here — packages/types/src/objectql.ts and its mirror packages/types/src/zod/objectql.zod.ts; - the pins that assert the retirement — object-kanban-allow-collapse-retired-8801.test.ts and bare-kanban-node-key-retired-8802.test.ts; - a comment in packages/types/src/zod/complex.zod.ts, recording that the deleted retiredZeroReadKanbanKey helper once carried this spelling on the SIBLING arm; - one row of content/docs/api/schema-reference.md; - the .changeset/ release notes that discuss it — this one, the two historical entries covering the sibling arm's own spelling, and objectui#9629's note recording the correction to this paragraph.

.changeset/8885-object-chart-drilldown-title-compareto.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectChart.tsx reads all three off schema, and until now neither published copy declared any of them: not the TS interface (packages/types/src/objectql.ts) and not the zod mirror (packages/types/src/zod/objectql.zod.ts). They rode BaseSchema's index signature / .passthrough() and arrived unvalidated. drillDown was the sharpest case — this component's registry inputs advertise it to the designer palette, and @objectstack/spec publishes ChartDrillDownSchema for exactly this carrier, so an author was offered a key that neither published shape mentioned.

.changeset/8913-object-kanban-columns-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  What moved. ObjectKanbanSchema gains columns on both halves that move together — the TypeScript interface (objectql.ts) and its Zod mirror (zod/objectql.zod.ts). Retiring the bare kanban node type key (objectui#8802) removed the only face that judged a lane, and object-kanban had never declared the key, so it rode BaseSchema's [key: string]: any / .passthrough(): read by the renderer at three sites, named by no published face.

.changeset/8990-object-kanban-groupby-optional.md

• names packages/types/src/objectql.ts → packages/types/src/objectql.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

• names packages/types/src/zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  @objectstack/spec declares the key optional — groupBy: z.string().optional() on ObjectKanbanPropsSchema — while this package required it on the TypeScript declaration (packages/types/src/objectql.ts) and on the Zod mirror (packages/types/src/zod/objectql.zod.ts). objectui was therefore narrower than the protocol on a published key: ObjectKanbanSchema.safeParse and safeValidateSchema refused an object-kanban node the protocol accepts, and such a node could not be annotated with its own type.

.changeset/8992-user-actions-collapse-and-docblock.md

• names objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  objectql.zod.ts's UserActionsSchema read stripImportedDefaults(Spec).extend({ group, hideFields, rowColor }), an extension that existed only because @objectstack/spec did not declare those three keys while normalizeListViewSchema folded objectui's legacy showGroup / showHideFields / showColor onto them. The protocol adopted all three in 17.3.0 (objectui#5435's ruling), so the extension is now a second local copy of a protocol declaration — the shape two faces start drifting from — and it collapses into the plain by-reference re-export its own note always said it would become.

.changeset/9092-inline-locale-declared-face.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  • AppComponentSchema.label (app.ts) - ObjectGridSchema.label and .description (objectql.ts) - PageNodeSchema.aria.ariaLabel (layout.ts)

.changeset/9309-object-gallery-filter-destination-typed.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectGallerySchema.filter is typed as the destination its own docblock names — QueryParams['$filter'] — on both faces, the TS interface in objectql.ts and the zod mirror in zod/objectql.zod.ts (objectui#9309).

.changeset/9511-record-id-is-a-string.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  The three authorable keys, each on BOTH faces. ObjectFormSchema.recordId (objectql.ts + zod/objectql.zod.ts), DetailViewSchema.resourceId (views.ts + zod/views.zod.ts) and DetailSchema.resourceId (crud.ts + zod/crud.zod.ts). ⚠️ The crud pair is DetailSchema, not DetailViewSchema, and it reaches the same renderer — not by symbol but by data flow: plugin-detail registers the 'detail' node type onto DetailView. A read that follows TypeScript symbols alone finds two keys and is incomplete.

.changeset/9549-tree-filter-declared.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  ObjectTreeSchema.filter is declared on both faces, in the shape objectui#9309 settled for ObjectGallerySchema.filter: QueryParams['$filter'] by indexed access on the TS interface in objectql.ts, and the same two-arm union (array first) on the zod mirror in zod/objectql.zod.ts (objectui#9549).

.changeset/9550-object-tree-root-barrel.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  ObjectQLComponentSchema declares the node types an ObjectQL block may be. Every one of its arms was a named export of this package's root barrel except ObjectTreeSchema, which was declared in objectql.ts, applied by the union, and re-exported by the ./zod barrel (objectui#7917) — while no TypeScript consumer could name it. There is no ./objectql subpath to reach around the barrel: the package's exports map is pinned by packages/types/src/__tests__/package-exports-manifest.test.ts, and the root barrel was the only route to this type.

.changeset/9606-object-kanban-card-title.md

• names zod/objectql.zod.ts → packages/types/src/zod/objectql.zod.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  Both published faces of the object-kanban arm now name the key: the zod mirror ObjectKanbanSchema in zod/objectql.zod.ts and its TypeScript twin, the ObjectKanbanSchema interface in objectql.ts. Both declare it OPTIONAL, at the same requiredness the other face uses, so the two faces accept and refuse the same documents. (Located and cited by SYMBOL: line addresses in zod/objectql.zod.ts have drifted before, and this change is itself about a drifted mirror.)

.changeset/9628-kanban-column-collapsed-honoured.md

• names objectql.ts → packages/types/src/objectql.ts — edited by this change

  The key was declared on both published faces of the object-kanban arm — the lane element of ObjectKanbanSchema (objectql.ts and its Zod mirror) and the runtime lane KanbanColumn (complex.ts and its mirror) — and read by KanbanEnhanced alone, a module no production source imports. An authored { "id": "todo", "title": "To Do", "collapsed": true } therefore parsed green on both faces and reached a board that did nothing with it: KanbanImpl's only collapse is the SWIMLANE row's, held in viewer state under objectui:kanban-collapsed:ANGLE-BRACKETS(swimlaneField) and never keyed to a lane's declared value. That is the ADR-0049 declared-but-unhonoured shape.

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 12809a595 (merge-base with origin/main): 6 file(s) changed outside .changeset/, read against 1619 pending declaration(s) that publish a body (2208 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3076.6 KB	3104.5 KB
Main entry chunk (gzip)	148.3 KB	350 KB
Entry file	index-uyntmMqA.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.57KB	6.15KB
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.17KB	10.58KB
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.39KB	1.21KB
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)	556.35KB	133.07KB
core (index.js)	9.57KB	3.81KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	224.98KB	62.48KB
fields (index.js)	259.68KB	65.89KB
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 (translateFn.js)	0.20KB	0.18KB
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.65KB	14.69KB
plugin-charts (index.js)	83.58KB	22.75KB
plugin-chatbot (index.js)	198.40KB	47.22KB
plugin-dashboard (index.js)	134.11KB	35.62KB
plugin-designer (index.js)	216.25KB	44.39KB
plugin-detail (index.js)	233.23KB	61.74KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	158.35KB	40.47KB
plugin-gantt (index.js)	169.75KB	41.96KB
plugin-grid (index.js)	218.12KB	59.72KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	114.70KB	28.42KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.55KB	11.99KB
plugin-timeline (index.js)	30.91KB	9.05KB
plugin-tree (index.js)	10.58KB	3.72KB
plugin-view (index.js)	87.83KB	22.01KB
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.81KB	3.58KB
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)	119.16KB	39.05KB
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)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
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)	2.52KB	1.31KB
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

[objectstack-fleet]

Contract review ABSENT at head 83f3e8662a, so this PR stays draft and out of the queue. domain:spec#1 @ objectui · session_014fWVhLzhxR8qrFsJ5o8TYW · 2026-09-27T15:53Z.

• Where the PR stands. ObjectChartSchema now accepts the spec's { name } series arm and specType, both by reference, and a refinement requires chartType or specType. It is Clause-②: yes, with an @object-ui/types minor. The dev measured that no render, publish or objectui validate path runs the schema on the react-tier node, so the grade holds. Three pins beyond the claim moved because the widening falsified them, and the PR body names them.
• Why no record. The isolated at-tier reviewer could not start: its model returned HTTP 429, 「reached your Fable limit」. Under the contract-review rule, a reviewer that cannot start means the review is absent. The PR carries needs:contract-review and stays draft. The only bypass is the maintainer reviewing it personally.

---

Generated by Claude Code

[objectstack-fleet]

Required check red at head 83f3e8662a: Spec Main Shape Gate hit its 45-minute job timeout while type-checking. This PR is the cause, so a patch round is queued. domain:spec#1 @ objectui · session_014fWVhLzhxR8qrFsJ5o8TYW · 2026-09-27T16:34Z.

• What failed. Job 108652348491 (run 36330849718). Steps 1–11 were green: the spec was built from objectstack main and injected. Step 12, 「Type-check objectui against it」 (TURBO_FORCE=true pnpm type-check --continue, whole tree), ran from 2026-09-27T15:59Z and was cancelled at 2026-09-27T16:32Z by timeout-minutes: 45.

• Why it is this PR's. The same gate took 12.3 min in total on PR feat(types,plugin-view,app-shell)!: retire NamedListView.densityMode; both relays read the density through the fold (objectui#7924) #10793 (dd43c757c8) and 12.9 min on PR docs(skills): the plugin guide's tombstone comment lists the serializer key list with of (objectui#10337) #10780 (b57c8a84df); on those, the type-check step takes a few minutes. The regular Type Check, against the pinned 17.4.0, also slowed here: 10.4 min, against 6.9 min on feat(types,plugin-view,app-shell)!: retire NamedListView.densityMode; both relays read the density through the fold (objectui#7924) #10793. The one type-level change is this PR's by-reference union: the spec's ChartSeriesSchema / ChartSeries { name } arm, or the internal { dataKey } arm, plus specType. Against spec main's types, the union apparently drives a type-instantiation blow-up somewhere in the whole-tree check. The dev's narrowed local run of this gate covered only @object-ui/types and @object-ui/plugin-charts, so it did not see it.

• Not a flake, so no re-run. It reached the type-check body and ran past four times the normal time.

• Next. A patch round root-causes it:

  • find the package and the construct that explodes under the spec-main build (tsc --extendedDiagnostics / --generateTrace);
  • fix the type without narrowing the ruled accept set;
  • prove the fix with the full-tree gate within budget.

  The maintainer asked this seat to run one dev at a time, so the patch round starts when the seat's in-flight dev (objectui#7928) is done, ahead of the next card. The PR stays draft with needs:contract-review.

---

Generated by Claude Code

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3078.7 KB	3104.5 KB
Main entry chunk (gzip)	148.3 KB	350 KB
Entry file	index-BFOUPLZ4.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.57KB	6.15KB
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.17KB	10.58KB
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.39KB	1.21KB
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)	556.80KB	133.32KB
core (index.js)	9.92KB	3.93KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	224.95KB	62.49KB
fields (index.js)	260.77KB	66.22KB
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 (translateFn.js)	0.20KB	0.18KB
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.67KB	14.70KB
plugin-charts (index.js)	83.58KB	22.75KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	134.64KB	35.75KB
plugin-designer (index.js)	216.25KB	44.39KB
plugin-detail (index.js)	233.12KB	61.68KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	158.35KB	40.47KB
plugin-gantt (index.js)	169.83KB	41.99KB
plugin-grid (index.js)	218.66KB	59.90KB
plugin-kanban (index.js)	48.43KB	15.11KB
plugin-list (index.js)	114.78KB	28.44KB
plugin-map (index.js)	22.90KB	7.62KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.55KB	11.99KB
plugin-timeline (index.js)	30.91KB	9.05KB
plugin-tree (index.js)	10.64KB	3.75KB
plugin-view (index.js)	87.89KB	22.03KB
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.81KB	3.58KB
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)	119.16KB	39.05KB
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)	7.50KB	3.05KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	6.16KB	2.71KB
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.84KB	1.90KB
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)	2.52KB	1.31KB
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

[objectstack-fleet]

Correction to this seat's comment 5857715528: its diagnosis was wrong. The cancelled Spec Main Shape Gate was a degraded runner, not this PR. domain:spec#1 @ objectui · session_014fWVhLzhxR8qrFsJ5o8TYW · 2026-09-27T19:15Z.

5857715528 said 「This PR is the cause」 and 「Not a flake, so no re-run」. The patch round measured the opposite. Its report is the newest os-dev-report on objectui#10770.

• No type cost from this PR. The gate's step-12 command, a forced whole-tree turbo run type-check, takes the same time with and without the PR:

  • pinned 17.4.0: 472 s vs 480 s at the merge base;
  • spec main 17bd318: 485 s vs 488 s;
  • the exact objectstack commit the failed job compiled (e462186): 490 s, 81/81 tasks, 0 TS errors.

  The types program gains +0.2% instantiations, and a --generateTrace shows no hot ObjectChartSchema construct.

• The runner was slow on every step, including steps that never read this PR's diff. Failed job 108652348491 against four neighbouring gate jobs:

  step	failed job	neighbours
  spec build from objectstack	547 s	109–156 s
  pack	62 s	10–13 s
  setup-node	34 s	6–12 s
  checkout	12 s	2–5 s

  A uniform 3–6× slowdown is enough to push the type-check past the 45-minute ceiling. The regular Type Check at 10.4 min matched a docs-only PR running at the same time (10.4 min).

• Where it stands. Head 77646f4150 is a merge of main only; no source changed. The gate is green in 12.1 min, and every CI job is green (Type Check 7.1 min).

The seat's error was comparing whole-job durations without the per-step control that tells a degraded runner apart from a PR-caused blow-up. The PR still needs its at-tier review (needs:contract-review), which is unchanged by this correction.

---

Generated by Claude Code

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 77646f4150f1d8ffcc459447f6696b2138ad5dbb

① Derived judgments

Diff read three-dot against objectui origin/main a7fd877c3c (merge-base 12809a595a): 7 files, +436 / −62. The head is the reviewed increment 83f3e8662a plus one merge of main; the increment is unchanged (the patch round changed no source, 5858924713).

1. The accept set widens on ObjectChartSchema in three places, each bound to the spec by reference. (i) series element becomes z.union([stripImportedDefaults(SpecChartSeriesSchema), <the internal { dataKey } object>]): the author arm is @objectstack/spec's ChartSeriesSchema (a strictObject, chart.zod.ts:238, name the column, dataKey refused by name), the internal arm is byte-unchanged (still without the per-series type, per objectui#10584). (ii) specType: stripImportedDefaults(SpecChartTypeSchema).optional(), the spec's ChartTypeSchema enum (chart.zod.ts:110). (iii) chartType becomes optional, and .superRefine(requireObjectChartFamily) refuses a node with neither key, issue at ['chartType']. The TS twin follows (chartType?, specType?: SpecChartType, series?: Array<SpecChartSeries | { dataKey … }>); the spec exports both types (chart.zod.ts:181, :1029).
2. The producer the old verdict missed is real. packages/components/src/renderers/layout/react-page.tsx:97-99 spreads a react block's props into the node and parks a type that differs from the tag as specType; the spec's react-blocks entry for object-chart has schema: ChartConfigSchema with type and series among its data props (pinned by the new test against the installed spec); the objectstack showcase writes series={[{ name: 'total', label: 'Invoice value' }]}. So the wrapper is a sixth producer, and the "INTERNAL, five producers" docblock was false for it; the docblock is rewritten to two arms, one verdict each.
3. No renderer change was needed, and none was made. normalizeChartSchema.ts:607-610 already reads chartType ?? specType ?? type … (so chartType wins when a node writes both, as the describe says) and translates the { name } arm.
4. The floor is kept and the widening is exact. Pins in object-chart-react-tier-node-10770.test.ts: the showcase node parses with zero issues on the mirror and through safeValidateSchema; the authored series comes back as written (no spec default injected); an entry with neither name nor dataKey → invalid_union at series.0; a node with neither family key → custom at chartType; either key alone parses; the author arm is strict (an unknown field refused by name); specType takes every ChartTypeSchema value and refuses a bogus one; the internal arm is unchanged; two @ts-expect-error probes on the TS face.
5. Doors, measured by the dev and read here. No render path runs zod on the wrapper's node (SchemaRenderer runs the structural validateSchema), objectstack's react-page publish gate parses only aggregate and drill-down schemas, and objectui validate treats a react page's source as opaque; the runtime importers of @object-ui/types/zod are the CLI and plugin-map. So no user met the old refusal; it was on the contract face and in the docblock, which is why minor is the right grade for a widening.
6. Three pins beyond the claim moved because the widening falsified them, none deleted: ObjectChart.schemaAnchor-7946 narrows with 'dataKey' in first and its bad entry becomes { label } (since { name } is now legal); widget-schema-anchors-7946 uses Extract<…, { dataKey: string }>; imported-defaults-8317 registers the new crossing ChartSeriesSchema.
7. Mergeability and CI. git merge-tree --write-tree origin/main refs/pull/10802/head at a7fd877c3c exits 0; pairwise clean with feat(types,plugin-view,app-shell)!: retire NamedListView.densityMode; both relays read the density through the fold (objectui#7924) #10793; conflicts with feat(types,plugin-view,app-shell)!: ObjectViewSchema.listViews mirrors the spec's ObjectListViewSchema by reference; ViewPreview folds a stored options bag (objectui#7928) #10821 in imported-defaults-8317.test.ts (both register a crossing) — ③. Check runs on 77646f4150: 40 success, 3 skipped, 0 red; the cancelled Spec Main Shape Gate at the previous head was a degraded runner (every step 3-6× slower, including the spec build that never reads this diff), measured per step by the patch round and corrected by the seat at 5858943102; green at head in 12.1 min.

② Semver level

'@object-ui/types': minor, Clause-②: yes — a runtime widening, with the two TS-face moves that can stop a consumer compiling stated in the changeset (chartType now includes undefined; a series element is a union, so .dataKey needs narrowing). Every changeset sentence checks out against items 1-6, including "no render, publish or objectui validate path ran ObjectChartSchema on the wrapper's node".

③ Boundary flags

• Mixed entry: { name, dataKey } fails the strict author arm and parses through the internal arm with name stripped — the internal arm's pre-existing strip, now reachable through the union. Dev-noted in the Acceptance notes. Not blocking; the describe could say it, and the seat carries it into the next chart-face change.
• The PR body's "Verification: HEAD 83f3e86" heading is stale after the merge (dev-listed); seat-owned prose, not a contract matter.
• Landing order: this PR and feat(types,plugin-view,app-shell)!: retire NamedListView.densityMode; both relays read the density through the fold (objectui#7924) #10793 land first; feat(types,plugin-view,app-shell)!: ObjectViewSchema.listViews mirrors the spec's ObjectListViewSchema by reference; ViewPreview folds a stored options bag (objectui#7928) #10821 conflicts with both and lands after a base merge.
• The seat's ABSENT note 5857410146 waited on at-tier quota; this record is that review.

Implemented-by: claude/issue-10770-object-chart-name-arm
Reviewed-by: session_01AsCNgFBs8HCjwhyHQsFbx3

VERDICT: PASS

Rendered at tier by the director seat (summon #30 续 2) on the fetched head. Not a governed path; the landing pre-checks are met (fresh PASS, CI green, no conflict with main), so needs:contract-review comes off and ready + auto-merge follow through the relay.

---

Generated by Claude Code