finding(types,plugin-kanban): the ruled `KanbanSchema` carries three zero-read members (`allowCollapse`, `cardTemplates`, `columnWidths`) and the board reads an undeclared `titleField` — enforce-or-remove on the shape objectui#7664 declared

[claude]

Filed by the dev seat executing objectui#7664 (ruling (a): the plugin dialect is the authoritative 'kanban' arm). Measured on the branch claude/issue-7664-kanban-plugin-dialect-authoritative at bd1fc7111, whose read census is the same on origin/main because the PR moves the declaration without touching a read site. Out of scope there: the ruling's execution list says "import the declared type instead of its local one; behaviour unchanged", so the shape was carried member for member and each row below is its own ADR-0049 decision.

The facts

Read census over packages/plugin-kanban/src (non-test files), per member of the now-declared KanbanSchema (packages/types/src/complex.ts):

member	declared	read sites in the plugin (non-test)
allowCollapse	yes	0 — KanbanEnhanced collapses lanes off column.collapsed, never off the board flag
cardTemplates	yes	0 — CardTemplates.tsx takes templates as a component prop; nothing reads schema.cardTemplates
columnWidths	yes	0 — useColumnWidths takes a ColumnWidthConfig option; nothing reads schema.columnWidths
titleField	no (rides BaseSchema's index signature)	ObjectKanban.tsx — `schema.cardTitle

The other 15 declared members each have at least one read site (objectName 25, groupBy 14, columns 6, data 4, cardTitle 3, swimlaneField, grouping, cardFields, limit, className, quickAdd, onQuickAdd, coverImageField, conditionalFormatting via KanbanRenderer, onCardMove via KanbanRenderer). filter is the other read-but-undeclared key and is already carded: objectui#7712.

Probe used, so the zeros are readings: grep -o of schema.MEMBER and bare MEMBER over ObjectKanban.tsx + index.tsx, and grep -l of the bare word over every non-test file under src/ excluding types.ts; a same-shaped control on coverImageField returns 2 files / 7 hits.

Why it is a card

The whole point of the objectui#7664 ruling is that "declared = rendered" for the 'kanban' key. Three declared members that no registered board reads are the declared-but-unenforced class ADR-0049 targets: an author who writes allowCollapse: true validates green and gets a board that never collapses. And one read that the declaration does not name means cardTitle and titleField are two spellings for one thing, only one of which the validator can see.

Docs half (same class, adjacent)

The root README.md "Kanban Board" example authors columns: [{ value, label, color }] plus titleField — a column shape no renderer reads (KanbanColumn is { id, title, cards, … }; value / label have zero read sites, and a column color is now a named refusal after objectui#7664). It is not validated by any gate (json fence, root README), so it stayed green while teaching a shape that renders empty lanes.

Not decided here

Each row is enforce-or-remove: retire the three (tombstone + refusal, changeset), or wire them (a read site each); and for titleField, either declare it as the alias it is or retire the fallback and let cardTitle be the one spelling. Two of the four move a published surface, so this is a triage-and-rule card, not a dispatchable fix.

Refs: objectui#7664 (ruling (a)) · objectui#7712 (filter, the other undeclared read) · objectui#7322 (the sibling object-kanban arm) · ADR-0049.

Filed from Claude Code session https://claude.ai/code/session_01KbJQ1y1J12nZxYzFWhP8Q3.

---

Generated by Claude Code

[os-sam]

The undeclared-read table extended — re-measured, five rows added

From the dev seat remediating the contract review of PR #7743. The review found this card's census incomplete; I re-measured it from scratch at head f88304691 rather than inheriting either count. The card's body stands — every row in it is confirmed below. What follows adds the rows it missed and corrects two counts, mine included.

Why the first census missed them

It matched schema.KEY. The board also reads through a cast — (schema as any).KEY — and that form is invisible to that pattern. Re-run over packages/plugin-kanban/src (non-test) matching both forms, then each hit classified as code or comment by reading the line:

key	real reads	site(s)	comment-only mentions	status
titleField	2	ObjectKanban.tsx:303, :977	2 (:306, :323)	already a row on this card
filter	2	ObjectKanban.tsx:263, :291	1 (index.tsx:374)	carded as objectui#7712
navigation	1	ObjectKanban.tsx:689	0	ADDED
objectFields	1	index.tsx:200	0	ADDED
onColumnToggle	1	index.tsx:338	0	ADDED
enableVirtualScrolling	1	index.tsx:339	0	ADDED
virtualScrollThreshold	1	index.tsx:340	0	ADDED

The five new rows are not all the same kind — do not triage them as one

• navigation is the one that behaves like titleField: an authored key the board reads and the declaration does not name. ObjectKanban.tsx:689 reads it as (schema as any).navigation and defaults it to a drawer, so a board can author an overlay mode that validates green only because nothing judges it.
• objectFields is an INTERNAL channel, not an authoring surface. ObjectKanban writes it onto the schema it hands KanbanRenderer (objectFields: objectDef?.fields) and index.tsx:200 forwards it on; no author writes it. KanbanRendererProps already documents it as such. Its disposition is plausibly "declare it as internal, or leave it undeclared deliberately and say so" rather than enforce-or-remove.
• onColumnToggle / enableVirtualScrolling / virtualScrollThreshold belong to a DIFFERENT registered type. All three are read only inside the 'kanban-enhanced' registration, which has no declared arm in @object-ui/types at all. They are undeclared relative to KanbanSchema because that is the wrong denominator for them: the open question is whether 'kanban-enhanced' gets an arm, which is a bigger question than this card's.

Two corrections

1. ⭐ onCardClick (index.tsx:194) was an undeclared read, and PR feat(types): the kanban arm declares the plugin dialect; the DeclarativeKanban* trio retires (objectui#7664) #7743 declares it. KanbanRenderer has always forwarded onCardClick={schema.onCardClick}, while this package's own KanbanSchema never had the member — measured on origin/main: zero occurrences of the name in plugin-kanban/src/types.ts. Carrying that dialect member-for-member into @object-ui/types therefore reproduced the hole, and because BaseSchema is .passthrough() it turned a REFUSED document into an ACCEPTED one. It is now declared as a finding(types): 28 zod-mirror keys are declared z.function(), which NO JSON document can satisfy — 14 in-repo corpus files author them and are silently invalid #6124 RUNTIME SLOT. Recorded here because the row would otherwise have died silently when PR feat(types): the kanban arm declares the plugin dialect; the DeclarativeKanban* trio retires (objectui#7664) #7743 closes objectui#7664.
2. bind is NOT an undeclared read. ObjectKanban.tsx:199 reads it, but bind?: string is a live member of BaseSchema (packages/types/src/base.ts:248) and KanbanSchema extends BaseSchema. It belongs on neither this table nor any count of undeclared reads.

The zero-read half, re-confirmed

allowCollapse, cardTemplates and columnWidths still have zero read sites in the plugin — the card's three rows hold. type also reads zero in this package and is not a finding: the registry dispatches on it, the board never reads it.

Measured with the TypeScript compiler for the member sets (20 live + 3 tombstoned on KanbanSchema after PR #7743; 21 on BaseSchema) and with a both-forms regex plus per-line classification for the reads.

Refs: objectui#7664 · PR #7743 · objectui#7712 · objectui#7753 (why no ratchet saw the deleted key).

Filed from Claude Code session https://claude.ai/code/session_01KbJQ1y1J12nZxYzFWhP8Q3.

---

Generated by Claude Code