@@ -0,0 +1,39 @@
+---
+'@object-ui/types': minor
+'@object-ui/plugin-kanban': patch
+---
+
+**BREAKING (scored `minor` per this repo's version-alignment convention)** —
+`ObjectKanbanSchema.onQuickAdd` is retired on `object-kanban` (objectui#11234).
+This completes ruling B of the director seat's decision batch #91
+(objectui#8285): the object-bound board does not grow an inline record-creation
+write path, and the Quick Add pair stays with a React host.
+
+**Why it did nothing.** After objectui#8285 retired `quickAdd`, `onQuickAdd`
+stayed a runtime slot. A host-supplied function reached the board by identity,
+and on `object-kanban` it was never called, because the Quick Add control is
+gated on both halves of the pair. A TypeScript host or an AI that wrote the key
+compiled and got nothing.
+
+- **`@object-ui/types`** — `ObjectKanbanSchema.onQuickAdd` is `?: never` on the
+  TypeScript face, and `handlerKeyRefusal('onQuickAdd', 'retired', …)` on the
+  zod mirror. An authored value is refused BY NAME (`custom` at `onQuickAdd`,
+  the same code as before), and the message now says RETIRED instead of RUNTIME
+  SLOT. This narrows a published TypeScript face: a typed host that wrote the
+  key on an `object-kanban` node now gets a type error.
+- **`@object-ui/plugin-kanban`** — `ObjectKanban` renders an internal board
+  that takes the Quick Add pair only as explicit props, and it supplies neither
+  half. The internal board is not exported. `check:handler-key-reads` refuses a
+  tombstone while a renderer on the registration still reads the key off the
+  document, and this change removes that read from the `object-kanban` path.
+  `KanbanRenderer` is unchanged for a host: it reads `schema.quickAdd` and
+  `schema.onQuickAdd` exactly as before, and the control draws and calls the
+  host's function.
+
+**Migration.** Delete `onQuickAdd` from `object-kanban` nodes and from any
+`ObjectKanbanSchema` object a host builds. It was never called there. To offer
+Quick Add, mount `KanbanRenderer` from `@object-ui/plugin-kanban` in a React
+host and pass both `quickAdd` and `onQuickAdd` on its `schema`.
+
+The objectui#8285 entry's closing note, which said `onQuickAdd` stayed a runtime
+slot on `object-kanban`, is amended in this change to match.
@@ -4,10 +4,11 @@
 
 `ObjectKanbanSchema` now judges two of the three handler keys the kanban board reads off the
 authored document (the `plugin-kanban` slice; director seat ruling of
-2026-09-07, decision batch #69): `onCardClick` and `onQuickAdd` are declared as objectui#6124
-RUNTIME SLOTS — callable on the TypeScript face, refused BY NAME in the zod mirror because
-JSON has no function value — and the message points at the node-type spelling an author can
-write instead.
+2026-09-07, decision batch #69): `onCardClick` is declared as an objectui#6124 RUNTIME SLOT —
+callable on the TypeScript face, refused BY NAME in the zod mirror because JSON has no function
+value — and the message points at the node-type spelling an author can write instead.
+`onQuickAdd` was declared the same way here; objectui#11234 retires it on `object-kanban` in the
+same release, so it is `?: never` on the TypeScript face and refused BY NAME as RETIRED.
 
 Until now neither was declared anywhere. `BaseSchema` is `.passthrough()`, so a key no arm
 declares is not refused: it stops being judged and the value is KEPT, then reaches the
 
@@ -5,8 +5,10 @@
 html tier: name the inert `quickAdd` on `object-kanban` / `kanban` instead of calling it unknown
 
 The Quick Add control is gated on BOTH `quickAdd` and an `onQuickAdd` handler, and
-`onQuickAdd` is a runtime slot — a function — that no parsed page can write and that
-`ObjectKanban` supplies none of its own for. So an authored `quickAdd: true` on either
+`onQuickAdd` takes a function, which no parsed page can write and which `ObjectKanban`
+supplies none of its own for. objectui#11234 retires `onQuickAdd` on `object-kanban` in the
+same release; it remains a host-supplied prop on `KanbanRenderer`'s `schema`. So an authored
+`quickAdd: true` on either
 `ObjectKanbanRenderer` tag has never produced a control.
 
 Until now the only thing the tier said about it was `unknown-prop`, "has no prop
 
@@ -40,5 +40,6 @@ control there. To offer Quick Add, mount `KanbanRenderer` from
 diagnostic code, or imported one of the four removed names, drops that branch:
 the key now draws `unknown-prop` like any other prop the block does not have.
 
-Unchanged: `ObjectKanbanSchema.onQuickAdd` stays a runtime slot. It still reaches
-the board, and on `object-kanban` it is never called, because its partner is gone.
+`ObjectKanbanSchema.onQuickAdd` is retired on `object-kanban` too, by objectui#11234
+in the same release: on that element it was never called, because its partner is
+gone. The Quick Add pair on `KanbanRenderer` is unchanged.
@@ -981,15 +981,15 @@ A drag-and-drop Kanban board. The `object-kanban` type key validates the shape t
 
 > `groupField` is refused by name (objectui#7322): the renderer reads `groupBy`.
 
-> **`quickAdd` and `allowCollapse` were rows of the table above and are not authorable on this board.** `allowCollapse` is **refused by name** by the strict authoring face, which does not declare it at all — a document carrying it fails validation rather than merely going unread, and `@object-ui/plugin-kanban` has no read site for it. `quickAdd` is **retired** on this board (objectui#8285, director seat, decision batch 91): the Quick Add control is gated on an `onQuickAdd` runtime slot and no `object-kanban` path supplies one, so the key never drew anything, and the ruling retired it rather than add inline record creation. The strict face tombstones it (refused by name), `ObjectKanban` no longer forwards it, and `@object-ui/sdui-parser` answers it with the ordinary `unknown-prop` warning. `@object-ui/types` mirrors this face and agrees on both: each is `never` on its TypeScript face and a retirement tombstone on its Zod face (objectui#8801, objectui#8285). The Quick Add pair itself lives on the `KanbanRenderer` component, which a React host mounts directly.
+> **`quickAdd` and `allowCollapse` were rows of the table above and are not authorable on this board.** `allowCollapse` is **refused by name** by the strict authoring face, which does not declare it at all — a document carrying it fails validation rather than merely going unread, and `@object-ui/plugin-kanban` has no read site for it. `quickAdd` is **retired** on this board (objectui#8285, director seat, decision batch 91): the Quick Add control is gated on an `onQuickAdd` handler as well, and no `object-kanban` path supplies one, so the key never drew anything, and the ruling retired it rather than add inline record creation. The strict face tombstones it (refused by name), `ObjectKanban` no longer forwards it, and `@object-ui/sdui-parser` answers it with the ordinary `unknown-prop` warning. `@object-ui/types` mirrors this face and agrees on both: each is `never` on its TypeScript face and a retirement tombstone on its Zod face (objectui#8801, objectui#8285). The Quick Add pair itself lives on the `KanbanRenderer` component, which a React host mounts directly.
 
 > `columns` is declared on this face since objectui#8913, as the pair of array shapes `@objectstack/spec` declares — an array of `{ id, title }` lanes, **or** an array of bare value strings. A **mixed** array is refused: the renderer decides which shape it has from the first element alone, so a mix yields a blank lane and mis-bucketed cards. A lane accepts `id`, `title`, `cards`, `limit`, `className` and `collapsed`, which are the members the board implementations read; `id` is a **string** — the authored face keeps that narrowing, and since objectui#8993 a non-string lane id no longer renders every card twice: the bucketer's leftover sweep keys membership the way the injection already did (a lane `1` takes the group `'1'`). When a lane carries `cards`, each card is judged — a card with no `title` is refused. An undeclared lane key is accepted and dropped, not refused, which is this tolerant face's posture; the strict authoring face refuses it by name.
 >
 > ⚠️ The **bare-string array applies only to a board with no `groupBy`.** It is declared so this package does not refuse an authoring the protocol allows. The renderer reads a bare-string lane list only when a board has no `groupBy` — so on a board that *does* declare one the strings are ignored and the lanes come from the group field's picklist options or from the data. Since objectui#8990 made `groupBy` optional, a lane-less board is a valid authoring and this arm is live on it: the lanes are drawn, titled by the **raw strings** (a grouped board titles its lanes with the picklist *labels* instead). ⚠️ Such a board holds **no cards** — with no lane key the records are never distributed — and dragging a card writes nothing back. It is lane headings, not a populated board; to control the lanes of a working board, declare `groupBy` and write the `{ id, title }` array.
 >
 > The other keys the retired `kanban` arm alone declared — `cardTitle`, `swimlaneField`, `grouping` and `navigation` — are still undeclared on this face. The renderer reads them, so a board may carry them; they are simply not judged.
 
-> **Handler keys are not authorable in JSON, and all three now say so by name.** Since objectui#7804 this face declares `onCardClick` and `onQuickAdd` as objectui#6124 **runtime slots**: a React host supplies the function through the TypeScript interface or as a React prop, and this validator **refuses the key by name** with a message pointing at the node-type spelling (`{ "type": "toast", … }`, an `action:button` node). Until then an authored `onCardClick: { "action": "toast" }` parsed **green** — `BaseSchema` is `.passthrough()`, so a key no arm declares is not refused, it stops being judged and the value is kept, then reaches a call site expecting a function. ⭐ The third key, `onCardMove`, is a **tombstone** since objectui#9342, not a runtime slot: an authored one reached **nothing** even as a function, because an object-bound board substitutes its own mover — so the TypeScript twin is `?: never` rather than callable, and the mover lives on `KanbanRenderer`'s React prop of the same name, a sibling of its `schema`.
+> **Handler keys are not authorable in JSON, and all three now say so by name.** Since objectui#7804 this face declares `onCardClick` as an objectui#6124 **runtime slot**: a React host supplies the function through the TypeScript interface or as a React prop, and this validator **refuses the key by name** with a message pointing at the node-type spelling (`{ "type": "toast", … }`, an `action:button` node). Until then an authored `onCardClick: { "action": "toast" }` parsed **green** — `BaseSchema` is `.passthrough()`, so a key no arm declares is not refused, it stops being judged and the value is kept, then reaches a call site expecting a function. ⭐ The other two keys are **tombstones**, not runtime slots, so their TypeScript twins are `?: never` rather than callable. `onCardMove` has been one since objectui#9342: an authored one reached **nothing** even as a function, because an object-bound board substitutes its own mover, and the mover lives on `KanbanRenderer`'s React prop of the same name, a sibling of its `schema`. `onQuickAdd` has been one since objectui#11234: a supplied one reached the board and was never called, because its partner `quickAdd` is retired here. `ObjectKanban` renders an internal board that takes the Quick Add pair only as explicit props and supplies neither half; the pair lives on `KanbanRenderer`'s `schema`, for a React host.
 
 > `data` and `bind` are [`BaseSchema`](#baseschema) members, not narrowed here, but this face requires **one of** `bind`, `data`, `objectName` — the renderer's own record-source ladder (an external `data` prop → `bind` via `useDataScope` → this schema's own `data` → a fetch keyed by `objectName`). A purely static board (lanes carrying their own cards, no record source) authors `"groupBy"` and `"data": []`. ⚠️ The record-source rule is **separate** from the lane key and is unaffected by objectui#8990: omitting `groupBy` is fine, omitting all of `bind` / `data` / `objectName` is still refused, at the refinement rather than at `groupBy`.
 
 
@@ -82,15 +82,21 @@ const onCardMove = (cardId: string, fromCol: string, toCol: string, index: numbe
 has no function value), never a member of the schema object below —
 `packages/plugin-kanban/README.md` documents this the same way.
 
-Neither are `onCardClick` and `onQuickAdd`, and since objectui#7804 the
-`object-kanban` validator **says so by name**: both are declared as
-objectui#6124 **runtime slots**, so an authored `onCardClick: { "action":
-"toast" }` is now refused with a message pointing at the node-type spelling,
-where before it parsed green and was handed to a call site expecting a function.
-A React host still supplies either function through the TypeScript interface or
-as a React prop; only the JSON face refuses them. ⚠️ On `object-kanban` a
-supplied `onQuickAdd` reaches the board and is never called, because its partner
-`quickAdd` is retired there — see "Quick Add is a React-host capability" below.
+Neither is `onCardClick`, and since objectui#7804 the `object-kanban` validator
+**says so by name**: it is declared as an objectui#6124 **runtime slot**, so an
+authored `onCardClick: { "action": "toast" }` is now refused with a message
+pointing at the node-type spelling, where before it parsed green and was handed
+to a call site expecting a function. A React host still supplies the function
+through the TypeScript interface or as a React prop; only the JSON face refuses
+it.
+
+⭐ `onQuickAdd` is a **tombstone** on `object-kanban` since objectui#11234, not a
+runtime slot. A supplied one used to reach the board and was never called,
+because its partner `quickAdd` is retired there. `ObjectKanban` now renders an
+internal board that takes the Quick Add pair only as explicit props, and it
+supplies neither half. So the TypeScript twin is `?: never` and the validator
+refuses the key by name. The pair lives on `KanbanRenderer` — see "Quick Add is
+a React-host capability" below.
 
 ⭐ `onCardMove` is declared too, since objectui#9342 — but as a **tombstone**,
 not a runtime slot. An authored one used to be accepted and silently dropped,
@@ -473,25 +479,27 @@ export function useBoard(initialColumns: KanbanColumn[]) {
 ### Quick Add is a React-host capability, not a document one
 
 The Quick Add button at the bottom of a lane is gated on **both** halves of a
-pair: `quickAdd`, and an `onQuickAdd` handler. `onQuickAdd` is a runtime slot —
-a function — so it can only be supplied by a React host that mounts the board
-component directly: `KanbanRenderer`, exported from `@object-ui/plugin-kanban`,
-forwards both halves by identity.
+pair: `quickAdd`, and an `onQuickAdd` handler. `onQuickAdd` is a function, so it
+can only be supplied by a React host that mounts the board component directly:
+`KanbanRenderer`, exported from `@object-ui/plugin-kanban`, reads both halves off
+its `schema` and forwards them by identity.
 
 ⚠️ There is **no node type key** that reaches it. The `kanban-ui` registration
 retired with objectui#8257, so a document naming that tag is now an
 `unknown-component` **error** rather than a board with a working pair. Import the
 component instead.
 
 An **object-driven** board (`object-kanban`, or a kanban view inside `ListView` /
-`ObjectView`) has no Quick Add control, and `quickAdd` is **retired** on it
-(objectui#8285): the board does not create records inline. Both
-`ObjectKanbanSchema` faces in `@object-ui/types` refuse the key by name, as
-`@objectstack/spec` does, and `ObjectKanban` does not forward it — so even a
+`ObjectView`) has no Quick Add control, and **both** halves of the pair are
+**retired** on it: `quickAdd` since objectui#8285, and `onQuickAdd` since
+objectui#11234. The board does not create records inline. Both
+`ObjectKanbanSchema` faces in `@object-ui/types` refuse both keys by name, and
+`@objectstack/spec` refuses `quickAdd`. `ObjectKanban` renders an internal board
+that takes the pair only as explicit props, and it supplies neither — so even a
 host that hands the board both halves of the pair gets no control. A page
-written as constrained JSX draws the ordinary `unknown-prop` **warning** for it
-(`validateTree` in `@object-ui/sdui-parser`), since the block has no such prop.
-Delete the key; to offer Quick Add, mount `KanbanRenderer` as above.
+written as constrained JSX draws the ordinary `unknown-prop` **warning** for
+`quickAdd` (`validateTree` in `@object-ui/sdui-parser`), since the block has no
+such prop. Delete both keys; to offer Quick Add, mount `KanbanRenderer` as above.
 
 ## Bundle Size
Original file line number	Diff line number	Diff line change
@@ -981,15 +981,15 @@ A drag-and-drop Kanban board. The `object-kanban` type key validates the shape t
`981`	`981`
`982`	`982`	> `groupField` is refused by name (objectui#7322): the renderer reads `groupBy`.
`983`	`983`
`984`		-> `quickAdd` and `allowCollapse` were rows of the table above and are not authorable on this board. `allowCollapse` is refused by name by the strict authoring face, which does not declare it at all — a document carrying it fails validation rather than merely going unread, and `@object-ui/plugin-kanban` has no read site for it. `quickAdd` is retired on this board (objectui#8285, director seat, decision batch 91): the Quick Add control is gated on an `onQuickAdd` runtime slot and no `object-kanban` path supplies one, so the key never drew anything, and the ruling retired it rather than add inline record creation. The strict face tombstones it (refused by name), `ObjectKanban` no longer forwards it, and `@object-ui/sdui-parser` answers it with the ordinary `unknown-prop` warning. `@object-ui/types` mirrors this face and agrees on both: each is `never` on its TypeScript face and a retirement tombstone on its Zod face (objectui#8801, objectui#8285). The Quick Add pair itself lives on the `KanbanRenderer` component, which a React host mounts directly.
	`984`	+> `quickAdd` and `allowCollapse` were rows of the table above and are not authorable on this board. `allowCollapse` is refused by name by the strict authoring face, which does not declare it at all — a document carrying it fails validation rather than merely going unread, and `@object-ui/plugin-kanban` has no read site for it. `quickAdd` is retired on this board (objectui#8285, director seat, decision batch 91): the Quick Add control is gated on an `onQuickAdd` handler as well, and no `object-kanban` path supplies one, so the key never drew anything, and the ruling retired it rather than add inline record creation. The strict face tombstones it (refused by name), `ObjectKanban` no longer forwards it, and `@object-ui/sdui-parser` answers it with the ordinary `unknown-prop` warning. `@object-ui/types` mirrors this face and agrees on both: each is `never` on its TypeScript face and a retirement tombstone on its Zod face (objectui#8801, objectui#8285). The Quick Add pair itself lives on the `KanbanRenderer` component, which a React host mounts directly.
`985`	`985`
`986`	`986`	> `columns` is declared on this face since objectui#8913, as the pair of array shapes `@objectstack/spec` declares — an array of `{ id, title }` lanes, or an array of bare value strings. A mixed array is refused: the renderer decides which shape it has from the first element alone, so a mix yields a blank lane and mis-bucketed cards. A lane accepts `id`, `title`, `cards`, `limit`, `className` and `collapsed`, which are the members the board implementations read; `id` is a string — the authored face keeps that narrowing, and since objectui#8993 a non-string lane id no longer renders every card twice: the bucketer's leftover sweep keys membership the way the injection already did (a lane `1` takes the group `'1'`). When a lane carries `cards`, each card is judged — a card with no `title` is refused. An undeclared lane key is accepted and dropped, not refused, which is this tolerant face's posture; the strict authoring face refuses it by name.
`987`	`987`	`>`
`988`	`988`	> ⚠️ The bare-string array applies only to a board with no `groupBy`. It is declared so this package does not refuse an authoring the protocol allows. The renderer reads a bare-string lane list only when a board has no `groupBy` — so on a board that does declare one the strings are ignored and the lanes come from the group field's picklist options or from the data. Since objectui#8990 made `groupBy` optional, a lane-less board is a valid authoring and this arm is live on it: the lanes are drawn, titled by the raw strings (a grouped board titles its lanes with the picklist labels instead). ⚠️ Such a board holds no cards — with no lane key the records are never distributed — and dragging a card writes nothing back. It is lane headings, not a populated board; to control the lanes of a working board, declare `groupBy` and write the `{ id, title }` array.
`989`	`989`	`>`
`990`	`990`	> The other keys the retired `kanban` arm alone declared — `cardTitle`, `swimlaneField`, `grouping` and `navigation` — are still undeclared on this face. The renderer reads them, so a board may carry them; they are simply not judged.
`991`	`991`
`992`		-> Handler keys are not authorable in JSON, and all three now say so by name. Since objectui#7804 this face declares `onCardClick` and `onQuickAdd` as objectui#6124 runtime slots: a React host supplies the function through the TypeScript interface or as a React prop, and this validator refuses the key by name with a message pointing at the node-type spelling (`{ "type": "toast", … }`, an `action:button` node). Until then an authored `onCardClick: { "action": "toast" }` parsed green — `BaseSchema` is `.passthrough()`, so a key no arm declares is not refused, it stops being judged and the value is kept, then reaches a call site expecting a function. ⭐ The third key, `onCardMove`, is a tombstone since objectui#9342, not a runtime slot: an authored one reached nothing even as a function, because an object-bound board substitutes its own mover — so the TypeScript twin is `?: never` rather than callable, and the mover lives on `KanbanRenderer`'s React prop of the same name, a sibling of its `schema`.
	`992`	+> Handler keys are not authorable in JSON, and all three now say so by name. Since objectui#7804 this face declares `onCardClick` as an objectui#6124 runtime slot: a React host supplies the function through the TypeScript interface or as a React prop, and this validator refuses the key by name with a message pointing at the node-type spelling (`{ "type": "toast", … }`, an `action:button` node). Until then an authored `onCardClick: { "action": "toast" }` parsed green — `BaseSchema` is `.passthrough()`, so a key no arm declares is not refused, it stops being judged and the value is kept, then reaches a call site expecting a function. ⭐ The other two keys are tombstones, not runtime slots, so their TypeScript twins are `?: never` rather than callable. `onCardMove` has been one since objectui#9342: an authored one reached nothing even as a function, because an object-bound board substitutes its own mover, and the mover lives on `KanbanRenderer`'s React prop of the same name, a sibling of its `schema`. `onQuickAdd` has been one since objectui#11234: a supplied one reached the board and was never called, because its partner `quickAdd` is retired here. `ObjectKanban` renders an internal board that takes the Quick Add pair only as explicit props and supplies neither half; the pair lives on `KanbanRenderer`'s `schema`, for a React host.
`993`	`993`
`994`	`994`	> `data` and `bind` are [`BaseSchema`](#baseschema) members, not narrowed here, but this face requires one of `bind`, `data`, `objectName` — the renderer's own record-source ladder (an external `data` prop → `bind` via `useDataScope` → this schema's own `data` → a fetch keyed by `objectName`). A purely static board (lanes carrying their own cards, no record source) authors `"groupBy"` and `"data": []`. ⚠️ The record-source rule is separate from the lane key and is unaffected by objectui#8990: omitting `groupBy` is fine, omitting all of `bind` / `data` / `objectName` is still refused, at the refinement rather than at `groupBy`.
`995`	`995`