fix(plugin-view): the host delegation reads a named view's remaining protocol members off the named view (objectui#10758)

[objectstack-fleet]

Fixes #10758
Clause-②: no

Claim 5861950053, seat domain:ui#4, PM session session_01MCg3z5cGrV51xEddpGcxEY (https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY). This is bucket ① of the objectui#7924 ruling (5690906005). densityMode and allowExport stay excluded, per the re-ruling 5852199633 as amended by 5856690997.

Re-sample (step 1), on objectui origin/main de1b879

Each reading was taken off disk and off the installed @objectstack/spec 17.4.0. A scratch script walked the spec schema, parsed the NamedListView interface with the TypeScript parser, and parsed both host literals. The types census re-derives the same partition on every run.

• The protocol's named view. ObjectListViewSchema declares 50 keys. Five of them are retirement tombstones, so 45 are live. NamedListView declares 64 members, and every one of the 45 live protocol keys is among them.
• What the renderer read off a named view: 20 names. They are appearance, calendar, chart, columns, data, fieldOrder, filter, gallery, gantt, grouping, kanban, label, map, name, rowColor, sort, timeline, tree, type and userActions.
  • The card says 21. PR objectui#10821 removed the options read after the card was filed, and options is not a protocol key.
  • The delegation itself (the renderListView literal) read 10 of the 20. Eight are read inside the fence: label, columns, grouping, userActions, rowColor, data, fieldOrder and appearance. filter and sort are read upstream, in authoredFilters and mergedSort.
• Bucket ①: 23 protocol members that no route read off a named view. These are the ruling's count and the ruling's names: addRecord, allowPrinting, aria, bulkActionDefs, bulkActions, compactToolbar, conditionalFormatting, description, emptyState, exportOptions, filterableFields, hiddenFields, inlineEdit, navigation, pagination, resizable, rowActions, rowHeight, searchableFields, selection, sharing, showRecordCount and userFilters.
  • tabs and pageName are also unread. They stay out because objectui#8980 ruled them declared-inert.
• The delegation's rungs for these 23, before this PR.
  • 19 read the host views entry, then the node (activeView?.X ?? (schema as any).X).
  • rowHeight read the host entry through the density fold.
  • description, exportOptions and bulkActionDefs had no rung at all.
• App-shell's object page relay drops none of the 23.
  • 22 have a rung that reads its active view (viewDef.X).
  • compactToolbar arrives through the plugin-view composition. ObjectView.relayRungCensus-7559.test.ts records it as relayed upstream.
  • So packages/app-shell/src/views/ObjectView.tsx is not touched (N4). App-shell hands its named view to plugin-view as the host views entry, not as listViews.
• The consumer (N3). ListView reads all 23 off the list-view node it is handed.
  • Most are read directly.
  • Seven are forwarded to the object-grid that ListView renders, and ObjectGrid reads each one: pagination, selection, resizable, rowActions, bulkActions (as batchActions), bulkActionDefs and conditionalFormatting.
  • No member reaches the node without a reader, so N3 has no declared-not-enforced gap to list.

What changed

• packages/plugin-view/src/ObjectView.tsx, in the renderListView({ schema: { … } }) literal inside the objectui#5097 HOST-COMPOSITION fence. Each of the 23 rungs now reads the active named view first (currentNamedViewConfig?.X). Then it reads the host views entry, and then the node, but only where the rung already read the node. This is the precedence grouping, rowColor and appearance use.
  • The three new rungs (description, exportOptions, bulkActionDefs) read the two views only. They never read the node.
  • A named view's rowHeight is read as itself: the strict record refuses densityMode, so there is nothing to fold. The host entry still goes through the fold (ruling A′).
  • ⛔ No rung gained a (schema as any) read, so the objectui#5097 exemption stays at 27 names. ⛔ No alias and no non-protocol key is read off the named view.
• What moves for a host. Only a host that supplies both listViews and its own renderListView sees a change.
  • Where the active named view and the host views entry both carry one of these members, the named view's value now wins.
  • A named view that carries none of them hands down exactly what it did before.
  • The registered object-view renderer passes no renderListView, so an authored node is unaffected.
• Changeset: 10758-named-view-protocol-members.md, patch for @object-ui/plugin-view.

Beyond the claimed file surface, and why

1. packages/types/src/__tests__/object-view-unmirrored-keys-7779.test.ts, the types census. It pins every bucket-① member UNREAD by name, so the change turns it red by construction. Every pin that held one of these members unread is inverted. ⛔ None is deleted.
   • The census moves from 20 read / 44 unread to 43 read / 21 unread.
   • Bucket ① is asserted EMPTY, derived rather than listed. The 23 names are kept as the pinned reading of what moved, one READ assertion each.
   • The census's negative twin moves from rowHeight to allowExport, which is read off the host entry and the node and not off a named view.
   • The absence pin for bulkActionDefs / exportOptions becomes a read pin that also holds "no node read".
   • The densityMode pin and the two READ_TEXT rows follow the new rung text.
2. packages/plugin-view/README.md and content/docs/plugins/plugin-view.mdx each gain one prose paragraph describing the host-path precedence. This follows the docs-driven rule (AGENTS.md section 5, Add automated testing infrastructure and CI/CD workflows #2). Neither file gains a code fence.

Pins, one named view per member family

• ObjectView.namedViewProtocolKeys-8980.test.tsx, a new route-3 block. There are four families: list chrome (7), record actions (6), grid presentation (6), and search, filter and navigation (4). Each family runs four cases:
  • the named view parses under the strict ObjectListViewSchema, so every value is one a conforming author can write;
  • THE FIX: the named view's value reaches the list-view node the host renders, and wins over the host entry and the node;
  • CONTROL: with the family absent from the named view, the host entry supplies it;
  • CONTROL: with neither view declaring it, the node supplies it. The four rungs with no node read stay undefined.
  • The members already read (label, columns, fieldOrder, grouping) ride every fixture as the firing control. A last case holds rowHeight: the named value is read as itself, and the host entry's retired spelling still arrives through the fold.
• objectViewHostSurface.test.tsx, a new section 1b, derived with the TypeScript parser over the fence only:
  • the named-view read set inside the fence, by name;
  • the property that every rung for a protocol member reads the named view, except type (node identity) and filter / sort (read upstream);
  • no named-view read of a key the protocol does not declare there, with allowExport as the control;
  • no new cast read.
• "The rendered view" here is the list-view node that the host's renderListView receives. A plugin-view test cannot import ListView: @object-ui/plugin-list is not a plugin-view dependency, and check:phantom-deps refuses the import. The link from that node to the rendered list is ListView's own reads, listed under N3 above.

Verification at 5dc80e3

Every heavy run went through os-verify-lock.sh, and each exit code was captured redirect-first.

• vitest packages/plugin-view/ plus the types census: 53 files, 745 tests passed, VERDICT command-exit 0.
• vitest on the tests that read the three changed markdown files (from scripts/markdown-test-inputs.mjs --list), every app-shell ObjectView* test (the relay census included) and StudioDesignSurface.gridRefresh: 58 files, 1243 tests passed, VERDICT command-exit 0.
• type-check, exit 0 for @object-ui/plugin-view (tsc --noEmit && tsc -p tsconfig.test.json) and for @object-ui/types (plus tsconfig.examples.json). --listFilesOnly confirms the three edited test files are in those programs.
• ESLint --no-inline-config on the 4 edited TS/TSX files, which is the whole population: eslint.config.js covers them with files: ['**/*.{ts,tsx}'], and --format json reports 4 files.
  • 0 errors and 86 warnings, per file identical to the base (60 / 26 / 0 / 0).
  • Not type-aware: projectService / parserOptions count 0 against a languageOptions control of 1. So no untouched file's verdict can move.
• Gates, exit 0 each:
  • check-changeset-presence (4 source files of 2 released packages, 1 changeset), check-changeset-no-major, check-changeset-fixed, check-changeset-overwrite, and check-changeset-claims (report-only; the six pending paragraphs it names were read and are still true);
  • check:pending-changeset-literals, check:new-line-citations (0 new), check:control-bytes, check:test-path-roots, and the three check:vi-mock-* gates;
  • check:spec-symbols and check:phantom-deps;
  • check:doc-types, check:doc-fences, check:doc-example-ids, check-doc-expression-carriage, check-doc-links and check:doc-example-readers;
  • check-governed-queue-guard --test on the 7 paths: NOT GOVERNED.
• NOT MEASURED:
  • check:readme-exports: prerequisite not met (the workspace dists are not built). This diff adds no fenced block to any README.
  • check:doc-snippets / check:doc-examples: not run, because no fenced block was added.
  • The full @object-ui/types suite: only a test file changed there, and that file and the types tests that read the changed markdown ran.
  • The full app-shell suite and the Spec Main Shape Gate: CI runs them.

Reverse verification

Run once on the committed tree 59046a2 with ablation-replace.mjs. The whole HOST-COMPOSITION fence was replaced by its base text; the mutated blob e1e9557 equals the base blob. The directions were predicted before the run.

• Result: 64 failed, 225 passed.
  • 8980 pin: 7 red. These are the four THE FIX cases, the host-entry CONTROL of the two families holding a new rung, and the rowHeight case.
  • Host-surface pin: 3 red.
  • Census: 54 red. These are the 23 READ rows, the 23 BUCKET ① → READ rows, the counts, the partition, bucket ① empty, the inverted absence pin, the densityMode pin and the two READ_TEXT rows.
• The predicted-green controls stayed green: the host CONTROL of the other two families, all four node CONTROLs, the four protocol parses, the off-protocol pin, the 21 UNREAD rows, and the bucket ② / ③ rows.
• One prediction missed. The four-way partition test stayed green. It partitions the pinned literal, and the link from literal to derivation is the "43 read + 21 unread" test, which went red.
• The restore was proven: the blob equals HEAD (89b6c7e) and git diff HEAD is empty.
• The later commits (2960ef6, 5dc80e3) touch only a test title and the types of the probe helper. No assertion moved.

Acceptance notes

• Reach, measured on this tree. No in-tree host passes both listViews and renderListView. App-shell's object page passes its named view as the host views entry, and the Studio grid passes neither. So the new rungs serve an out-of-tree host that composes both, which is the same reach as the objectui#8980 rungs beside them. This is recorded, not claimed wider.
• Route 2 (the registered renderer's grid path) still reads only columns, filter, sort, grouping and rowColor off a named view.
  • A scratch probe, not committed: ObjectView without renderListView, which is exactly what the registered renderer mounts. A named grid view authored pagination, selection, hiddenFields, rowHeight, conditionalFormatting, rowActions, bulkActions and resizable, and the object-grid schema carried columns only. ObjectGrid reads each of those keys.
  • This is outside the claimed literal: the ruling sends bucket ① to "the object-view delegation".
  • ⚠️ The types census counts a member as read when ANY route reads it, so bucket ① now reads empty while route 2 still ignores these members.
  • No real producer was found: no authored object-view node with listViews in either repository.
  • Reported to the PM, not filed.
• The delegation does not relay a named view's eight view-kind blocks (kanban, calendar, gallery, timeline, gantt, map, chart, tree). Only options: activeView goes down, while ListView reads top-level schema.kanban and the others.
  • The same probe: a named type: 'kanban' view with kanban: { groupByField: 'stage' } handed the host viewType: 'kanban' and columns, and no kanban.
  • These members are counted read (route 1), so they are not bucket ①.
  • Same reach as above. Reported, not filed.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 6 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/6726-find-envelope-records-arms.md

• names plugin-view/src/ObjectView.tsx → packages/plugin-view/src/ObjectView.tsx — edited by this change

  | module | what it does | | --- | --- | | components/src/hooks/related-count-store.ts | related-list tab badge count | | components/src/renderers/basic/data-list.tsx | element:repeater rows | | components/src/renderers/basic/elements.tsx | element:number client-side aggregate | | components/src/renderers/basic/record-picker.tsx | element:record_picker options | | plugin-detail/src/renderers/record-activity.tsx | record:activity self-fetch | | plugin-detail/src/renderers/record-history.tsx | record:history self-fetch | | plugin-view/src/ObjectView.tsx | non-grid (kanban / calendar / gallery / timeline) fetch |

.changeset/7070-no-invented-gantt-date-fields.md

• names plugin-view/src/ObjectView.tsx → packages/plugin-view/src/ObjectView.tsx — edited by this change

  • app-shell/src/views/ObjectView.tsx — the console object page. The inline branch becomes ganttViewOptions, the sibling of calendarViewOptions and timelineViewOptions: the declared block spread whole, title floored at 'name', no date field invented. - plugin-list/src/ListView.tsx — the render branch AND the capability gate. - plugin-view/src/ObjectView.tsx — generateViewSchema, the authored object-view element route, which bypasses ListView entirely.

.changeset/7499-gantt-non-axis-floors-omitted.md

• names plugin-view/src/ObjectView.tsx → packages/plugin-view/src/ObjectView.tsx — edited by this change

  • plugin-list/src/ListView.tsx — the object-gantt render branch. - plugin-view/src/ObjectView.tsx — generateViewSchema, the authored object-view element route, which bypasses ListView entirely.

.changeset/8221-retire-legacy-string-sort.md

• names content/docs/plugins/plugin-view.mdx → content/docs/plugins/plugin-view.mdx — edited by this change

  Docs teach the array only: content/docs/plugins/plugin-map.mdx, content/docs/plugins/plugin-view.mdx and packages/plugin-view/README.md.

• names packages/plugin-view/README.md → packages/plugin-view/README.md — edited by this change

  Docs teach the array only: content/docs/plugins/plugin-map.mdx, content/docs/plugins/plugin-view.mdx and packages/plugin-view/README.md.

.changeset/8653-listview-title-retired-rowactiondefs-pinned.md

• names packages/plugin-view/src/ObjectView.tsx → packages/plugin-view/src/ObjectView.tsx — edited by this change

  title — retired. ListView resolved its export filename through schema.label || (schema as any).title. @objectstack/spec/ui's ListViewSchema refuses title by name (unrecognized_keys: ['title']) while ObjectGridPropsSchema accepts it; packages/types mirrors the platform contract rather than ruling over it, so declaring title on ListViewSchema would have made this repo accept what the platform save gate rejects. That asymmetry is also why objectui#6639 could take the declare branch for ObjectGridSchema.title one package over and this site could not. A parse-based census of apps/ examples/ content/ and packages/ found zero list-view nodes authoring title, so the retirement costs no author a filename. Over that same corpus the instrument reports three object-grid nodes carrying the key: two authored ones, both in content/docs/api/schema-reference.md, plus one that is not authored at all — packages/plugin-view/src/ObjectView.tsx composes title: schema.table?.title onto a grid node it builds, so it is a producer writing the key rather than an author declaring it. ObjectGrid's own title reads are untouched — they remain declared, ruled and read.

.changeset/object-view-unmirrored-keys-7779.md

• names packages/plugin-view/src/ObjectView.tsx → packages/plugin-view/src/ObjectView.tsx — edited by this change

  What was measured. Every reading was taken on the object-view node renderer (packages/plugin-view/src/ObjectView.tsx, registered by plugin-view/src/index.tsx) with schema.objectName / schema.layout as the positive controls of the same schema.KEY query, so each zero is a reading; the repo-wide census of viewTabBar finds the key in no source file outside @object-ui/types (two doc tables listed it as authorable and are corrected here). The spec side was read through the installed pin (@objectstack/spec@17.2.0, ui entry, 117 exported object schemas walked; control keys objectName / columns / navigation / listViews hit): the three spec-modelled keys are optional slots on ListViewSchema and ObjectListViewSchema; the six local keys have no spec slot anywhere.

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.

Compared the checked-out tree with c6678b1bd (merge-base with origin/main): 6 file(s) changed outside .changeset/, read against 1649 pending declaration(s) that publish a body (2240 pending in total). · run

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3087.5 KB	3104.5 KB
Main entry chunk (gzip)	148.4 KB	350 KB
Entry file	index-DeV4epry.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.17KB
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)	557.59KB	133.61KB
core (index.js)	9.93KB	3.94KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	225.01KB	62.50KB
fields (index.js)	261.26KB	66.37KB
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.73KB	14.72KB
plugin-charts (index.js)	83.99KB	22.86KB
plugin-chatbot (index.js)	197.67KB	46.90KB
plugin-dashboard (index.js)	136.82KB	36.44KB
plugin-designer (index.js)	216.42KB	44.47KB
plugin-detail (index.js)	233.48KB	61.79KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	161.21KB	41.41KB
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)	44.17KB	12.20KB
plugin-timeline (index.js)	31.00KB	9.09KB
plugin-tree (index.js)	11.21KB	3.89KB
plugin-view (index.js)	88.42KB	22.18KB
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.22KB
types (ai.js)	4.11KB	2.06KB
types (api-types.js)	0.20KB	0.18KB
types (app.js)	3.52KB	1.36KB
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.26KB
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.27KB	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

Served-tier: 209/209 CONTRACT_REVIEW_TIER
Head-sha: 5dc80e39981133d955377a72544f9ce9be727916

Read: card objectui#10758 body and its four comments (seat notes 5856946147, 5861063883, claim 5861950053, and the os-dev-report 5862298983, treated as claims to test); the objectui#7924 ruling 5690906005, re-ruling 5852199633 and amendment 5856690997; merged PR objectui#10793 (66e8b2ab3) and objectui#10821 (b93e245) metadata and diffs; PR objectui#10884 body, file list and diff at head 5dc80e3 (fetched as refs/review/pr-10884; merge-base with origin/main is de1b879a6bdc7feb7b9f8a16fcb8abdca1004873, the dev's stated re-sample base; origin/main is now 1c5ee334); packages/plugin-view/src/ObjectView.tsx at base and head (whole file, the HOST-COMPOSITION fence at lines 2399–2584 of the head); the three edited test files and their diffs; the changeset, README and mdx diffs; the published @objectstack/spec 17.4.0 tarball (the lockfile's resolved version; objectui has no node_modules, so I pulled the registry tarball plus zod 4.4.3 into scratch and evaluated ObjectListViewSchema directly); packages/types/src/objectql.ts at base (NamedListView, ObjectViewSchema.listViews); packages/plugin-list/src/ListView.tsx, packages/plugin-grid/src/ObjectGrid.tsx, packages/app-shell/src/views/ObjectView.tsx and ObjectView.relayRungCensus-7559.test.ts at base; packages/core/src/utils/normalize-list-view.ts (the density fold); packages/plugin-view/src/index.tsx (the registered renderer); examples/byo-backend-console/src/App.tsx, packages/app-shell/src/views/metadata-admin/previews/ViewPreview.tsx, packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx; objectstack examples/**, apps/**, packages/** grepped for listViews; objectui AGENTS.md (§5 commandments, §9 changeset rule at line 168, 测试纪律, 版本号策略), .changeset/config.json, every pending .changeset/*.md grepped for claims the change could falsify; the head's check-runs at three polls. Not re-run: the dev's ablation and the three test files locally (a run would need a full pnpm install and a build of plugin-view's dependency closure; CI's eight test shards and Type Check on this exact sha are green, see ③).

① Derived judgments

1. The re-sample — RIGHT. The published spec 17.4.0 ObjectListViewSchema has 50 keys; 5 are never tombstones (bordered, performance, responsive, striped, virtualScroll), so 45 are live (my own evaluation of the dist, not the dev's). NamedListView at the merge-base declares every one of the 45 (0 missing). At the merge-base the whole of ObjectView.tsx reads 19 distinct currentNamedViewConfig?.KEY names plus view.name in the tab strip: appearance calendar chart columns data fieldOrder filter gallery gantt grouping kanban label map name rowColor sort timeline tree type userActions = 20, not 21; options is not among them (the base fence carries options: activeView, the host entry only, with the objectui#7928 comment, and PR objectui#10821's diff is what removed the named-view read). 45 live minus those 20 leaves 25; minus tabs and pageName (ruled declared-inert at objectui#8980, the census's BUCKET_DECLARED_INERT) leaves exactly the ruling's 23: addRecord allowPrinting aria bulkActionDefs bulkActions compactToolbar conditionalFormatting description emptyState exportOptions filterableFields hiddenFields inlineEdit navigation pagination resizable rowActions rowHeight searchableFields selection sharing showRecordCount userFilters. Every one is a live protocol key under its protocol name; no alias. densityMode and allowExport are outside the list, and the strict schema refuses both on a named view (my parse: REFUSED, REFUSED).

2. The rungs — RIGHT. The source diff touches only the renderListView({ schema: { … } }) literal inside the objectui#5097 fence. Nineteen existing rungs gained currentNamedViewConfig?.X ?? in front of an unchanged activeView?.X ?? (schema as any).X tail; rowHeight became currentNamedViewConfig?.rowHeight ?? (normalizeListViewSchema(activeView ?? {}) as { rowHeight?: string }).rowHeight, the named view read as itself before the host fold; the three rungs with no prior rung (description, exportOptions, bulkActionDefs) read currentNamedViewConfig?.X ?? activeView?.X and never the node. Counted: the set of (schema as any).K reads inside the fence is byte-identical at base and head — 31 real reads (plus the letter K in the header comment), which is OBJECT_VIEW_HOST_COMPOSITION_KEYS (27 names, unchanged) plus OBJECT_VIEW_DECLARED_FORWARDED_KEYS (4: data filterableFields navigation searchableFields, unchanged). The fence's named-view read set grew from 8 (appearance columns data fieldOrder grouping label rowColor userActions) to 31, the difference being exactly the 23. The eight pre-existing named-view rungs and the upstream filter / sort reads are untouched, so no already-read member changed precedence. Fall-through is safe: currentNamedViewConfig is the raw schema.listViews[active] entry typed NonNullable‹ObjectViewSchema['listViews']›[string] (the spec's z.input), nothing in core, react, plugin-view or app-shell parses or normalizes listViews entries before this read, and no bucket-① member carries a zod .default() (a minimal named view parses to columns label type only), so an unauthored member is undefined and ?? yields exactly the old chain. App-shell's objectViewSchema memo carries no listViews at all, so on the console's object page currentNamedViewConfig is null and every new rung falls through; the Studio surface passes renderListView without listViews. The only page whose render moves is an out-of-tree host that passes both listViews and renderListView and whose named view authors one of the 23 — which is the fix.

3. N3 and N4 — RIGHT. ListView at the merge-base has a schema.X read for 22 of the 23 (counts from 1 to 8 per member) and forwards bulkActionDefs into the object-grid node through (schema as any).bulkActionDefs; it maps bulkActions to the grid's batchActions. ObjectGrid reads pagination (6 sites), selection (3), resizable (1), rowActions (2), batchActions (1), bulkActionDefs (1), conditionalFormatting (4). So each of the 23 has a reader in the rendered list. App-shell's relay has a viewDef rung for 22 (rowHeight through normalizeListViewSchema(viewDef ?? {}), hiddenFields gated on activeViewDeclaresColumns, bulkActionDefs through a cast) and its census row for compactToolbar is relayed-upstream with upstreamReads: ['activeView']. The relay drops none; app-shell is untouched by the PR, correctly.

4. Pins — RIGHT. ObjectView.namedViewProtocolKeys-8980.test.tsx adds a route-3 block: four families (list chrome 7, record actions 6, grid presentation 6, search/filter/navigation 4), each with a strict-spec parse, THE FIX (named wins over host and node), a host CONTROL (family absent from the named view, host entry supplies) and a node CONTROL (neither view; node supplies, and the four no-node-rung members must arrive undefined); a coverage test asserts the families hold 23 distinct protocol names with allowExport as the refused control; a rowHeight case checks named 'tall' wins and a host densityMode: 'compact' still arrives as 'compact' through the fold (the fold maps compact to compact). The already-read label columns fieldOrder grouping ride every fixture through expectControl. I parsed all four family fixtures plus the control against the published schema myself: all OK, and the rowHeight enum is compact short medium tall extra_tall, covering every fixture value. objectViewHostSurface.test.tsx section 1b walks the fence with the TypeScript parser: the named-view read set pinned by name (31 entries, equal to my count), the property that every protocol-member rung reads the named view except filter / sort / type (with the upstream reads asserted by text), the converse (no off-protocol named-view read, allowExport as control), and the cast count equal to 27 + 4. typescript is a declared devDependency of plugin-view. The census object-view-unmirrored-keys-7779.test.ts is inverted honestly: 12 expect lines removed, each with an inverted counterpart (20 to 43, 44 to 21, 23 to 0, not.toContain(member) to toContain(member), the absence pin to a read-plus-no-node-read pin, the negative twin rowHeight to allowExport with its rung text asserted); bucket ① empty is derived from the live protocol keys minus reads with BUCKET_DECLARED_INERT as the expected remainder and a control on the same derivation; the 23 names are kept as BUCKET_ONE_READ_SINCE_10758 with a per-member READ assertion. The 21 remaining unread names contain none of the 43 the head file reads (checked against my whole-file grep). Each new pin fails on base by construction (the base fence has 8 named reads, not 31; the base census partition is 20/44). No timeout raised, no skip/only/todo, no heavyDomTests entry (0 hits in the added lines). The dev's ablation report is structurally consistent with this (the one missed prediction, the partition test staying green because it partitions the pinned literal, is disclosed); I did not re-run it.

5. Prose and shape — RIGHT. Every sentence of .changeset/10758-named-view-protocol-members.md holds at the head: the 23 never came off the named view on that node (base fence); named first, then host, then the node where the rung already read it (diff); the four families list all 23; the three new rungs read the two views only (no (schema as any).description|exportOptions|bulkActionDefs at head) and the exemption keeps 27 names (counted); rowHeight read as itself with the host entry through the fold (diff); named wins where both carry, a named view carrying none hands down exactly what it did (no defaults, no upstream normalization); the registered renderer passes no renderListView (index.tsx mounts ‹ObjectView schema dataSource› only). The README and mdx paragraphs say the same and name the pin file. patch for @object-ui/plugin-view is the right level: a renderer starts honouring members its contract already declares, no export, type or accept set moves. The types change is test-only; AGENTS.md's rule (line 168, enforced by check-changeset-presence) is "declare once" for any src/ change in a released package, satisfied by the one changeset, and the fixed group of 40 publishes together anyway; Changeset Declaration, Changeset Bump Policy and Changeset Fixed Group Check are green. No major. The PR body's first line is Fixes #10758 and its second Clause-②: no, which holds: NamedListView, ObjectViewSchema, OBJECT_VIEW_HOST_COMPOSITION_KEYS (27) and OBJECT_VIEW_DECLARED_FORWARDED_KEYS (4) are unchanged, and the strict named-view schema is the spec's own.

6. The dev's open question — facts verified, with one correction. Route 2 is real: the registered renderer mounts ObjectView without renderListView, and off a named view that path reads only columns, filter, sort, grouping, rowColor and the eight kind blocks (kanban calendar gallery timeline gantt map chart tree), while the new rungs sit inside if (renderListView). The delegation does not relay the eight kind blocks (no such rung in the fence; only options: activeView goes down). Producers: the dev's "no authored object-view node carries listViews in either repo" is WRONG for objectui. (i) examples/byo-backend-console/src/App.tsx (ObjectPage) authors listViews: { default: { label: 'All', type: 'grid', columns } } on an object-view node rendered through ‹ObjectView› without renderListView — route 2 — though that named view authors no bucket-① member. (ii) packages/app-shell/src/views/metadata-admin/previews/ViewPreview.tsx spreads the whole stored ViewItem body (...foldStoredListOptions(body)) into listViews[id] and renders through SchemaRenderer, i.e. the registered renderer, route 2; a stored view carrying rowHeight, hiddenFields, inlineEdit or pagination (keys the console persists per view, by app-shell's own comments) is therefore an in-tree producer whose bucket-① grid members route 2 ignores. In objectstack, listViews appears only on config.views[] containers (app-crm, app-showcase, app-todo view files, the CLI); those reach objectui as objectDef.listViews, then app-shell's mergedViews, then the host views prop, whose relay covers all 23 — no object-view node with listViews exists there. No in-tree host passes both listViews and renderListView (app-shell: views plus renderListView; Studio: renderListView only; byo and ViewPreview: listViews only), so the dev's reach statement for the new rungs holds. The seat decides; option A's stated premise (zero producers on route 2) does not survive ViewPreview.

② Semver level

patch on @object-ui/plugin-view (fixed group of 40, so the group bumps together). No major, no minor needed: nothing declared, exported or accepted moves; a host composing listViews with its own renderListView gets the named view's authored value where it previously got the host entry's, which is the contract the spec already declared.

③ Boundary flags

• CI on 5dc80e3: poll 1 at 2026-09-28T02:42:24Z — 42 runs: 29 success, 10 in progress (Spec Main Shape Gate, Test shards 1–8, Type Check), 3 skipped, 0 failure. Poll 2 at 02:53:53Z — 43 runs: 40 success, 3 skipped, 0 in progress, 0 failure (the Test rollup appeared, success 02:49:30Z; Type Check success 02:47:15Z; Spec Main Shape Gate success 02:44:30Z; shards 1–8 all success by 02:49:17Z). Poll 3 at 02:55:08Z — unchanged. The 3 skipped are the coverage-shard matrix placeholder, Test (coverage) and dependabot. Green includes Lint, Build & E2E, Build Docs, Doc Snippet Type Check, README Export Check, Line Citation Gate, all five changeset gates, Governed Surface Queue Guard, Pre-Install Import Graph Check.
• Not re-run here: the three edited test files (no node_modules in the checkout; would need a full install plus dependency build) and the dev's ablation. CI's shards and Type Check on this exact sha stand in.
• The PR is behind origin/main (1c5ee334), but git diff de1b879 origin/main over the seven touched files is empty and git merge-tree is clean.
• Pending changesets that publish verbatim carry census figures this PR inverts: 7924-named-list-view-liveness-census.md ("21 read and 43 unread of 64 today"), 7924-named-list-view-disposition-buckets.md ("43 unread … 23 + 8 + 10 + 2"), object-view-unmirrored-keys-7779.md ("renderer reads 21 off a named view", "43 unread members", and "listViews stays unmirrored", the last already false since objectui#10821). All three were stale before this PR (20/44 at the merge-base) and check-changeset-overwrite forbids amending a pre-existing changeset, so this is not a defect of the change; but the dev's report that the 7779 paragraphs were "read, still true" is inaccurate for those figures. The seat may want a carrier for the CHANGELOG-time correction.
• Pin boundary, disclosed by the dev: "carried through to the rendered view" is pinned at the list-view node renderListView receives, not at a mounted ListView (@object-ui/plugin-list is not a plugin-view dependency and check:phantom-deps would refuse it). The link is N3's reads, verified above by reading.
• The mdx paragraph cites src/__tests__/ObjectView.namedViewProtocolKeys-8980.test.tsx without a package prefix; in content/docs that path is relative to nothing. Cosmetic; the link gate is green.
• The types census counts a member read when any route reads it, so bucket ① reads empty while route 2 (with ViewPreview as a live in-tree producer) still ignores the grid members — disclosed by the dev under "open questions", corrected here on the producer fact (item 6).
• Item 6's kind-block gap (the delegation relays no kanban etc.) has the same reach limit: no in-tree host passes both listViews and renderListView.
• No model identifier in the diff (0 hits); commit trailers carry Claude-Session and Co-authored-by: Claude. No worktree was created by this review; nothing to remove.

Implemented-by: claude/issue-10758-named-view-protocol-members
Reviewed-by: session_01MCg3z5cGrV51xEddpGcxEY

VERDICT: PASS

[objectstack-fleet]

Merge-queue ejection: not this PR's. domain:ui seat 4 · session_01MCg3z5cGrV51xEddpGcxEY · 2026-09-28T04:04Z.

• Failing check: Test (shard 7/8) on the queue commit cc7098f9b (origin/main b2683a2 plus this PR). The failing case is packages/plugin-detail/src/__tests__/RelatedList.unmaterializedSort.test.tsx › "keeps that button in client mode": Unable to find an accessible element with the role "button" and name /Total/.
• Why it is not this PR's: this PR changes only plugin-view's ObjectView.tsx, its tests and docs, and packages/plugin-detail/src has no path to them. The file passed 12 of 12 runs across the merge with current main, the exact queue tree, plain main and this head.
• Root cause, reproduced deterministically: the case does not wait for the object schema, and the sort button exists only after it lands (since objectui#10728). Delaying getObjectSchema by 50 ms gives exactly the CI signature; adding await settleObjectSchema(dataSource) makes it pass.
• Fix: none exists yet on main. It is filed with the ready patch as objectui#10895. It is not ported here, because it is test code this PR does not touch.
• Re-run: the one re-run allowed for a failure established as not this PR's; auto-merge is re-enabled in this act, so the PR re-enters the queue.