feat(types,plugin-view,app-shell)!: retire NamedListView.densityMode; both relays read the density through the fold (objectui#7924)

[objectstack-fleet]

Fixes #7924
Clause-②: yes

Director ruling A′ on objectui#7924 (comment 5856690997, amending ruling A 5852199633). Claim 5856715104, seat domain:spec#1, session session_014fWVhLzhxR8qrFsJ5o8TYW. This PR is the card's last scope: bucket ① of ruling 5690906005 was split off as objectui#10758 and is not touched here.

What changes

• NamedListView.densityMode becomes densityMode?: never (packages/types/src/objectql.ts, the NamedListView block). The tombstone docblock names top-level rowHeight, warns off userActions.rowHeight (the boolean toolbar toggle), and says stored views keep rendering through the fold.
• Hop 1, the renderListView composition in @object-ui/plugin-view's ObjectView. The two rungs rowHeight: activeView?.rowHeight and densityMode: activeView?.densityMode become one rung that hands the active view to normalizeListViewSchema and relays the result's rowHeight.
• Hop 2, the object-page relay in @object-ui/app-shell's ObjectView (the fullSchema literal). The two rungs rowHeight: viewDef.rowHeight ?? listSchema.rowHeight and densityMode: viewDef.densityMode ?? listSchema.densityMode become one rung: the view's rowHeight read through normalizeListViewSchema, falling back to listSchema.rowHeight. That is view over list, the same shape the relay's userActions rung already uses.
• allowExport stays declared. Its docblock now names both relays that carry it (plugin-view's composition and app-shell's relay), which was the omission the first dev report found.
• @object-ui/react useDensityMode JSDoc @example now reads rowHeightToDensityMode(activeView?.rowHeight) and persists { rowHeight: DENSITY_MODE_TO_ROW_HEIGHT[m] } instead of { densityMode: m }. Docblock only, no behaviour change.
• Changeset .changeset/7924-density-mode-through-fold.md: minor for @object-ui/types and @object-ui/plugin-view, with the BREAKING banner, the third-party renderListView host note, and the ADR-0087 D2 disposition line.

After this change, the fold is the only code in packages/*/src that reads densityMode by name (const legacyDensity = s.densityMode; and delete next.densityMode; in normalizeListViewSchema). The zod ListViewSchema legacy-alias declaration also still names it; this ruling leaves that alone (see Acceptance notes).

Premise re-verified before the first edit

The ruling's own grep, run at BASE bf14b6460: git grep -n densityMode bf14b6460 -- 'packages/*/src/**' ':!**/__tests__/**' exits 0 with 34 hits. By class:

class	hits
app-shell relay (the code line and 1 comment)	2
plugin-view composition (the code line and 1 comment)	2
the fold (const legacyDensity = s.densityMode;, delete next.densityMode;, 4 docblock lines)	6
label namespace (10 locale toolbar.densityMode entries, plugin-list's grid.toolbar.densityMode default, 3 t() calls)	14
plugin-list comment	1
useDensityMode JSDoc example	2
types (the member, 2 objectql.ts docblocks, the zod README, 1 objectql.zod.ts docblock, the zod ListViewSchema line)	6
the co-located app-shell relay census test, which the __tests__ exclusion does not cover	1

The only code reads are the two hops and the fold, so the stop condition did not fire. Outside packages/*/src, git grep densityMode -- apps examples e2e content docs skills (CHANGELOG excluded) exits 1 with no hits. The firing control on the same trees, git grep -l listViews -- apps and git grep -l rowHeight -- content docs skills examples, does return hits.

Pins

• packages/types/src/__tests__/object-view-unmirrored-keys-7779.test.ts, re-pointed with no assertion deleted:
  • densityMode moves from BUCKET_LOCAL_ONLY_RETAINED into NAMED_LIST_VIEW_TOMBSTONES (16 → 17), and the AST-derived tombstone assertion follows.
  • The type pin _DensityModeRetained is re-pointed, not deleted. It is renamed _DensityModeTombstoned and now asserts that the member's type is undefined, with a comment recording what it used to assert.
  • A new @ts-expect-error refusal, _refusedDensityMode, is added, together with _acceptedDensityCanonical (rowHeight: 'compact' accepted on a named view). _acceptedRetained drops densityMode.
  • The densityMode is RETAINED case becomes densityMode is RETIRED by ruling A′. It asserts that the by-name line is absent at both relays, that the fold-through line is present at both (the firing control on the same files), and that the fold still names the key.
  • The bucket-③ intent case now also asserts that the tombstone text names top-level rowHeight and warns off userActions.rowHeight.
  • The named-view counter-control used to assert the literal text rowHeight: activeView?.rowHeight,. It now asserts the fold-through spelling off activeView. The claim it carries (rowHeight is read off activeView, not off a named view) is unchanged.
• packages/app-shell/src/views/ObjectView.relayRungCensus-7559.test.ts: a new densityMode row, { kind: 'legacy-alias', canonical: 'rowHeight', mentions: 'normalizeListViewSchema' }. Its evidence check requires the rowHeight rung to read the view AND to call normalizeListViewSchema. The showDensity row's reason no longer mentions a densityMode rung.
• New: packages/app-shell/src/views/ObjectView.densityModeThroughFold-7924.test.tsx, the retirement pin for H1. It mounts the real plugin-view ObjectView under the real object page, stubs only ListView to capture its schema, and pins plugin-view on its own through a spy renderListView. The effective density is normalizeListViewSchema(schema).rowHeight, which is what ListView renders. The file has 8 cases: 4 per host (SAME DENSITY ×2, THE CHANGE, CONTROL).

Tests

All at HEAD dd43c757c (git rev-parse --short HEAD), run after the final commit. Every exit code was captured before any pipe.

Build first. pnpm exec turbo run build --filter="@object-ui/app-shell^..." --concurrency=2 built the dependency closure of all six consumer packages: Tasks: 28 successful, 28 total, lock VERDICT command-exit 0.

package (direction: the edited @object-ui/types / core and its downstream consumers)	type-check	pnpm exec vitest run packages/PKG/
@object-ui/types	exit 0	exit 0 · Test Files 247 passed · Tests 5345 passed
@object-ui/core (the fold)	exit 0	exit 0 · Test Files 175 passed · Tests 3534 passed
@object-ui/react	exit 0	exit 0 · Test Files 99 passed · Tests 1333 passed
@object-ui/plugin-list	exit 0	exit 0 · Test Files 102 passed · Tests 1169 passed
@object-ui/plugin-view	exit 0	exit 0 · Test Files 51 passed · Tests 485 passed
@object-ui/app-shell	exit 0	exit 0 · Test Files 830 passed, 1 skipped · Tests 8408 passed, 9 skipped

tsc -p tsconfig.test.json --listFiles confirms that the test projects type-check the edited pins: the types project includes the 7779 test, and the app-shell project includes both the census and the new file. So the @ts-expect-error refusal is compiled, not skipped.

ESLint --no-inline-config --format json on the 7 touched TS/TSX files: 7 file results, 0 errors, 274 warnings (no-explicit-any and the other pre-existing warning rules; this repo's lint workflow sets no --max-warnings). This narrowing is a proof, not a skip:

• The population is the 7 touched files, all linted: none was reported as ignored.
• eslint.config.js enables no type-aware linting (no parserOptions.project or projectService), and no local rule under eslint-rules/ reads the disk. So this diff cannot move the verdict on any untouched file.

Gates: each exited 0.

• node scripts/check-changeset-presence.mjs (7 source files of 4 released packages changed, 1 changeset declared)
• node scripts/check-changeset-no-major.mjs
• pnpm check:new-line-citations (VERDICT 0 new citations)
• pnpm check:control-bytes
• pnpm check:spec-symbols
• pnpm check:test-path-roots
• node scripts/check-governed-queue-guard.mjs --test on the 8 changed paths (NOT GOVERNED)

A control-byte self-scan of the changed files and this body found nothing.

Reverse verification (both from the committed HEAD dd43c757c, every mutation through ablation-replace.mjs with its EXIT/INT/TERM restore, and every restore proven by blob hash equal to HEAD with an empty git diff HEAD)

1. The relays. Both by-name hop lines were restored on top of HEAD, which is the BASE shape of the two hops. The anchors hit x1 → x0, and on-disk grep -c of each restored line read 1. Predicted before the run: exactly the two THE CHANGE cases red, the census declares nothing that IS relayed and legacy-alias checks red, and the 7779 densityMode is RETIRED case and counter-control red, so 6 red in total. Every SAME DENSITY and CONTROL case stays green, because the fold inside ListView gives the same density on either shape.

Measured: Tests 6 failed | 256 passed (262). The 6 failures were exactly the 6 predicted cases, by name. All 6 SAME DENSITY / CONTROL cases in the new file stayed green, and that is the H1 pin: a stored densityMode: 'compact' view yields the same effective rowHeight at both hosts as it did on BASE. Both restores were proven.

2. The type face.

• (a) Consumer probe. A new file in @object-ui/app-shell held a NamedListView literal carrying densityMode: 'compact', and app-shell's tsc --noEmit ran against the rebuilt @object-ui/types. Result: error TS2322: Type 'string' is not assignable to type 'undefined'. The probe was removed by a trap, and git status was clean afterwards.
• (b) Tombstone widened back to the old three-value union. Predicted: 3 errors. Measured: _EveryTombstoneAdmitsOnlyAbsence TS2344, _DensityModeTombstoned TS2344, and _refusedDensityMode TS2578 (unused @ts-expect-error). The restore was proven.

Acceptance notes

• H2 (not this ruling). The zod ListViewSchema in packages/types/src/zod/objectql.zod.ts still declares densityMode as its legacy-alias line, and list-view-spec-parity.test.ts still ledgers it as input-only. NamedListView has no zod mirror, so the tombstone is on the TypeScript face only. This PR leaves the zod line as ruled.
• H3 held false, as the first report found. viewDef (app-shell) and the plugin-view views element are any-indexed, so the tombstone forced neither hop at compile time. Both hops were moved by hand, and the text pins above hold them.
• One precedence delta, confined to third-party renderListView hosts (read from source, not run). On BASE, a host whose list schema carried its own rowHeight beat a view that spelled its density densityMode: the relay merged the two into one schema, and the fold's rule "canonical wins" picked the host's value. Hop 2 now folds the view first and then applies view over list, so the view's density wins. In the Console this cannot arise, because the host is plugin-view's composition and its rowHeight comes from the same active view. The effective-density pins above were measured on that path. The changeset also says that a third-party host reading schema.densityMode now receives schema.rowHeight.
• The changeset from the earlier landing (.changeset/7924-named-list-view-retire.md, from PR objectui#10285, still pending release) says densityMode stays declared. This PR's changeset says in its body that it supersedes that line. The older file is outside this claim's file surface and is left untouched; the seat may prefer to amend it before release.
• normalize-list-view.ts needed no docblock change. Its fold behaviour is unchanged.
• Observation, not filed (承接者:无). The fold tests legacyDensity in DENSITY_MODE_TO_ROW_HEIGHT, and in walks the prototype chain. Measured on the built @object-ui/core: normalizeListViewSchema({ densityMode: 'toString' }) returns a rowHeight of type function and drops the key, while the control 'cozy' stays unfolded. rowHeightToDensityMode fixed the same shape in the other direction with hasOwnProperty. No producer writes such a value, so no public door gives a wrong answer, and it is noted here rather than filed.
• Concurrency. objectui#10770 edits the ObjectChartSchema block of objectql.ts, a disjoint region. objectui#10758 will edit plugin-view's delegation, a different region of the same file. Whichever lands later merges main.
• Spec Main Shape Gate: NOT MEASURED locally. The reason: the touched member is objectui-own (densityMode is not spec-derived), and the gate needs a spec tarball built from objectstack main. CI runs it.
• Commit trailers are model-free. The local commit was amended once, before its first push, to drop a model name from Co-Authored-By. No pushed history was rewritten.

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 24 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.

.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 app-shell/src/views/ObjectView.tsx → packages/app-shell/src/views/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.

• 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/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.

.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).

.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/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/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/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/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.

.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.

.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.

.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.

.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).

.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.

.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).

.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 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.

.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.

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

[github-actions]

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3068.8 KB	3104.5 KB
Main entry chunk (gzip)	148.3 KB	350 KB
Entry file	index-DZg4pI6d.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)	554.95KB	132.67KB
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.81KB	22.00KB
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)	116.21KB	38.14KB
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 dd43c757c, so this PR stays draft and out of the queue. domain:spec#1 @ objectui · session_014fWVhLzhxR8qrFsJ5o8TYW · 2026-09-27T15:24Z.

• Where the PR stands. It executes director ruling A′ (5856690997) in 8 files, all inside claim 5856715104, and it is Clause-②: yes. The dev's report is on the card. The premise grep found no third code read. The reverse verification reddens exactly the 6 named cases. The type face gives TS2322 on a consumer literal and TS2344 ×2 / TS2578 on a widened tombstone.
• 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.
• Seat decision on the dev's open question (the earlier .changeset/7924-named-list-view-retire.md says densityMode stays declared): B, leave it as written. This PR's changeset states in its body that it 「supersedes the earlier objectui#7924 entry in this release」. Editing another PR's pending changeset trips the check-changeset-overwrite report and would cost a patch round for a sentence the new entry already corrects.

---

Generated by Claude Code

[objectstack-fleet]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: dd43c757c8cae27fd56e3863dd337259d697963c

① Derived judgments

Diff read three-dot against objectui origin/main a7fd877c3c (merge-base bf14b64608): 8 files, +402 / −55. The PR implements director ruling A′ on objectui#7924 (5856690997, amending 5852199633); the reviewer is the session that ruled, the implementer is the domain:spec#1 seat's dev on the branch below.

1. Public surface: one declaration narrows, exactly as ruled. NamedListView.densityMode becomes densityMode?: never (packages/types/src/objectql.ts:2369); its docblock names top-level rowHeight and warns off userActions.rowHeight (the boolean toolbar toggle). allowExport stays declared, its docblock now naming both relays. Emitted .d.ts: a TS author writing densityMode fails at the key (pins: _DensityModeTombstoned = Expect<Equal<NamedListView['densityMode'], undefined>>, the @ts-expect-error _refusedDensityMode, the accepted _acceptedDensityCanonical with rowHeight). No zod face changes: NamedListView has no mirror, and the list-view node's own ListViewSchema legacy alias (objectql.zod.ts:1456) is outside the card and left as ruled.
2. Both relay hops read through the fold. plugin-view ObjectView.tsx:2402: rowHeight: (normalizeListViewSchema(activeView ?? {}) …).rowHeight, the densityMode: rung deleted; app-shell ObjectView.tsx:2719-2721: normalizeListViewSchema(viewDef ?? {}).rowHeight ?? listSchema.rowHeight, view over list, the same shape as the userActions rung. At head, git grep densityMode over packages/*/src non-test code lights only the fold (normalize-list-view.ts:449, :517), the tombstone, the list-view zod alias, i18n label keys and prose — the ruling's own premise, re-run first-hand.
3. Stored views render the same density. The fold is unchanged (DENSITY_MODE_TO_ROW_HEIGHT). The new pin ObjectView.densityModeThroughFold-7924.test.tsx mounts the real plugin-view ObjectView under the real object page, stubs only ListView, and holds 8 cases: a stored densityMode: 'compact' renders compact on both hosts; 'spacious' arrives at ListView as rowHeight: 'tall' with no densityMode key; an authored rowHeight still wins over a legacy densityMode on the same view; a view with no density hands down none, and an off-vocabulary 'cozy' is not coerced. The THE CHANGE cases go red if either hop's by-name rung is restored; the SAME DENSITY cases go red if the fold is bypassed.
4. Census pins re-pointed, none deleted. relayRungCensus-7559: a densityMode row legacy-alias → rowHeight, evidence requiring the rowHeight rung to read the view and call normalizeListViewSchema; object-view-unmirrored-keys-7779: tombstones 16 → 17, BUCKET_LOCAL_ONLY_RETAINED = ['allowExport'], the text assertions on both relays inverted to the fold-through spelling, the bucket-③ intent case asserting the tombstone text.
5. The one behaviour delta is confined and written down. A third-party renderListView host that read schema.densityMode off its argument now receives the same density as schema.rowHeight and no densityMode key; and hop 2 now folds the view before applying view-over-list, where before a host list schema's own rowHeight could beat a view's legacy densityMode. Unreachable in the Console (the host's rowHeight comes from the same active view); stated in the changeset and the PR. Accepted: it is the ruled shape.
6. useDensityMode JSDoc reads rowHeightToDensityMode(activeView?.rowHeight) and persists { rowHeight: DENSITY_MODE_TO_ROW_HEIGHT[m] }; both are exported by @object-ui/core (normalize-list-view.ts:36, :83). Docblock only.
7. Mergeability and CI. git merge-tree --write-tree origin/main refs/pull/10793/head at a7fd877c3c exits 0; pairwise with PR feat(types): ObjectChartSchema accepts the react tier's object-chart node — the spec's { name } series arm, family as specType (objectui#10770) #10802 also clean; with PR feat(types,plugin-view,app-shell)!: ObjectViewSchema.listViews mirrors the spec's ObjectListViewSchema by reference; ViewPreview folds a stored options bag (objectui#7928) #10821 it conflicts in object-view-unmirrored-keys-7779.test.ts (③). Check runs on dd43c757c8: 40 success, 3 skipped (dependabot, the two coverage rows), 0 red.

② Semver level

minor for @object-ui/types and @object-ui/plugin-view with a **BREAKING** banner, the before/after literal, the third-party host note and an ADR-0087 D2 disposition line (the fold is the load-time conversion) — right for a TS-face retirement under the version-alignment rule; Clause-②: yes is the objectui retirement convention. Every sentence checks out against items 1-6. @object-ui/app-shell's ObjectView.tsx also changed and the entry does not name it: the presence gate is satisfied by one declaration and the fixed group versions all 40 packages together, so nothing ships wrong, but app-shell's CHANGELOG will not carry this relay change. Non-blocking; ③.

③ Boundary flags

• Landing order: this PR and feat(types): ObjectChartSchema accepts the react tier's object-chart node — the spec's { name } series arm, family as specType (objectui#10770) #10802 are pairwise clean and 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 older pending changeset .changeset/7924-named-list-view-retire.md (PR feat(types)!: retire sixteen NamedListView members as ?: never tombstones (objectui#7924) #10285) still says densityMode stays declared because it is read; this entry says it supersedes that line. The seat chose to leave the older paragraph (5857169505). Two contradictory sentences will publish in one release; a dated note on the older entry (the repository's pure-insertion convention) before Version Packages is the cleaner form. Non-blocking; carried to the seat.
• The app-shell changeset omission above: a one-line '@object-ui/app-shell': minor on the same entry in the seat's next push that touches this family, or a dated note; non-blocking.
• Dev's out-of-scope finding (carrier none): the fold tests legacyDensity in DENSITY_MODE_TO_ROW_HEIGHT, and in walks the prototype chain, so densityMode: 'toString' folds to a function. No producer writes it; filed by the director seat as a hygiene card with this batch.
• The seat's ABSENT note 5857169505 waited on at-tier quota; this record is that review.

Implemented-by: claude/issue-7924-density-mode-through-fold
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