feat(types)!: retire ChatbotSchema.body on both published faces (objectui#8572) by hotlong · Pull Request #9639 · objectstack-ai/objectui

hotlong · 2026-09-16T16:36:41Z

Executes maintainer ruling A on objectui#8572 (decision batch #137, item 4, 2026-09-15, verbatim 「同意」 — comment 5689209004): ChatbotSchema.body becomes an ADR-0049 retirement tombstone on both published faces, pointing the author at requestBody. B (keep and document) and C (narrow to the children slot) were refused by that ruling and are not built here.

What landed, file by file

file	change
`packages/types/src/complex.ts`	new `body?: never` member on `ChatbotSchema`, beside the `children` tombstone objectui#9256 / ADR-0049 already put there
`packages/types/src/zod/complex.zod.ts`	`body: z.record(z.string(), z.unknown()).optional()` → `retirementTombstone(…)`; the `ChatbotSharedMirrorShape` note that said the ruling was "a separate question and is not decided here" now records that it was decided
`packages/types/src/__tests__/node-recursion-point-8344.test.ts`	the two load-bearing pins INVERTED, not deleted
`packages/types/src/__tests__/zod-mirror-parity.test.ts`	`KnownDrift` row loses `body` and records the ruling; the `WiderThanDeclared` entry goes (its whole content left); `WIDER_ARMS` row goes; header figures re-derived by this file's own pins
`.changeset/8572-chatbot-body-retired.md`	`minor` on `@object-ui/types`, BREAKING banner, ADR-0087 D2 disposition line
`.changeset/8344-…` · `.changeset/9256-…`	prose-only amendments — see the changeset-claim section below
`packages/types/src/__tests__/content-channel-family-d-9256.test.ts`	surface extension, granted — the two hold-out controls RE-POINTED at a twin face
`packages/types/src/__tests__/strict-authoring-face-8345.test.ts`	surface extension, granted — the root half of one case INVERTED
`packages/types/src/zod/base.zod.ts`	prose only — the comment block whose three sentences this diff falsifies, including a live instruction citing this card
`content/docs/plugins/plugin-chatbot.mdx`	prose only — the `requestBody` row's mechanism half (AGENTS.md #2, docs-driven)

⭐ The ruling's last sentence, answered with measurements

The report names the delivery surface of the refusal (parse-time) and whether any consumer path skips the root parse.

Delivery surface: parse-time on the zod mirror, compile-time on the TypeScript face — and nowhere else.

YES — a consumer path skips the root parse, and it is the one authors hit most. The runtime render path never parses through these mirrors at all. SchemaRenderer (@object-ui/react) validates in dev builds only, through @object-ui/core's hand-written validateSchema, which walks base keys and recurses into content and knows no per-component key. Traced to the end:

consumer path	engine it validates with	does the tombstone arrive?
`objectui validate` / `objectui check` (`@object-ui/cli`)	`safeValidateSchema` = `AnyComponentSchema.safeParse` on the document root	YES
a TypeScript author writing a `ChatbotSchema` literal	`tsc`	YES (compile-time)
`SchemaRenderer` render path (dev build)	`@object-ui/core`'s `validateSchema` — hand-written, no mirror	NO
`SchemaRenderer` render path (production build)	nothing — `__DEV__` gates the whole pass	NO
VS Code extension `SchemaValidator`	its own walker (recurses `body` only), never imports the zod face	NO
`plugin-map` / `plugin-view` / `plugin-list` / `plugin-detail` imports of `@object-ui/types/zod`	`ObjectMapConfigSchema.shape` key lists, not parses	n/a — no parse on the path

The readings, with their controls

1. The refusal, on the BUILT artifacts (@object-ui/cli and its dependency closure built from this branch — the dist bytes a consumer installs, not src):

objectui validate   FIXTURE: root chatbot + body: { model: 'gpt-4', temperature: 0.2 }
  exit 1 · "Path: body" · "Code: invalid_type" · message names `requestBody`     <- SUBJECT
objectui validate   FIXTURE: the same document spelled requestBody
  exit 0 · "✓ Schema is valid!"                                                  <- LIT CONTROL
objectui validate   FIXTURE: the same chatbot nested in card.body[]
  exit 1 · refused through the node union                                        <- DEPTH

2. The render path, rendered (@testing-library/react, dev build, console.warn spied):

chatbot + body: { model: 'gpt-4' }   warns "schema.children.type: type is required"
chatbot + requestBody: { … }         (no warning)                                <- LIT CONTROL
chatbot, neither key                 (no warning)                                <- LIT CONTROL
card + body: [{ label: 'x' }]        warns "schema.children[0].type: type is required"
                                                                                 <- FIRING CONTROL

⚠️ That warning is not this retirement arriving. It is the generic child walker mistaking the API params for a child node: it names children for a key the author spelled body, and it prescribes adding a type to the params. It says the same thing before and after this change. (The probe rendered through the fallback component — plugin-chatbot is not registered in it — which does not affect the validation reading, since validation runs before component resolution. Only the warnings are cited.)

3. The same document through the render-path validator directly (@object-ui/core's validateSchema):

SUBJECT   chatbot + record body        valid:false  ["schema.children.type: type is required" MISSING_REQUIRED]
SUBJECT   the same node in card.body[] valid:false  ["schema.children[0].children.type: …"]
CONTROL   chatbot, no body             valid:true                                <- LIT CONTROL
FIRING    validateSchema(null)         valid:false  INVALID_SCHEMA
FIRING    form field without a name    valid:false  MISSING_FIELD_NAME
FIRING    card child without a type    valid:false  MISSING_REQUIRED

⇒ the retirement is delivered where documents are authored and checked, and ⛔ not where they are rendered. Making the render path agree is a change to @object-ui/core on a different card and is not made here.

Re-taken reachability (the card's own table, re-measured on this branch — ⛔ not cited from the card)

AnyComponentSchema.safeParse, this branch's source:

document	before this change	after
chatbot + record `body` at the ROOT	ACCEPTED	REFUSED — `invalid_type` at path `body`, message names `requestBody`
the same node inside `card.body[]`	REFUSED	REFUSED
the same node inside `div.children[]`	REFUSED	REFUSED
the same node with `requestBody` instead	ACCEPTED	ACCEPTED (LIT CONTROL)
chatbot with neither key, root and nested	ACCEPTED	ACCEPTED (NON-VACUITY)

⚠️ The card's older reading said the width was reachable "at the root and in child slots". That half is no longer the tree's state and was not cited: PR objectui#8501 had already eliminated the nested half with a superRefine on the installed arm, so what this card actually retires is the ROOT.

Corpus impact: zero documents

Every tracked file carrying a chatbot node is in examples/schema-catalog/src/schemas/plugin-chatbot/ (3 files). Each was parsed and its node key sets read structurally (⛔ not grepped — a tombstone leaves a comment behind and grep -c counts it):

basic-chatbot.json          body:absent  requestBody:absent  messages:present  <- LIT CONTROL
chatbot-with-timestamps.json body:absent  requestBody:absent  messages:present <- LIT CONTROL
customer-support-chat.json  body:absent  requestBody:absent  messages:present  <- LIT CONTROL

Pin inventory — what moved, and in which direction

node-recursion-point-8344.test.ts, two pins INVERTED (⛔ neither deleted):

is still ACCEPTED at the ROOT — the published mirror is untouched → is REFUSED at the ROOT too — objectui#8572 retired the published record arm. The inverted leg asserts the issue's code and that the message names requestBody — the named remedy, ⛔ not the sentence carrying it.
ArmsNotAssignableToSchemaNode ≡ 'chatbot' → ≡ never. ⚠️ Measured, not assumed: the alias's bare projection — the exclusion projected through an extends { type: infer K } conditional — resolves to unknown — not never — when the exclusion set is empty, because never satisfies the probe shape and K is inferred from nothing. Written that way the inverted pin could only ever be red. It now answers the empty case first with a tuple-wrapped extends [never] guard and keeps the projection for its diagnostic value: it still NAMES the arm when there is one.

Unchanged and still green (the legs that make this a measurement rather than an echo): is REFUSED one slot down, NON-VACUITY: the same node without body is accepted at both depths, names body in the refusal, and the whole the fill is LIVE suite.

zod-mirror-parity.test.ts: KnownDrift['complex.zod.ts#ChatbotSchema'] 'body' | 'onError' | 'onSend' → 'onError' | 'onSend' (the entry survives; the ruling is recorded in its docblock — this is the row the ruling says "becomes 「ruled」"); WiderThanDeclared['complex.zod.ts#ChatbotSchema'] and its WIDER_ARMS row are gone, per that ledger's own clause 4 ("a key DISAPPEARED — the faces agree again; correct or delete the entry"), with the departure recorded in place as a standalone note in the ledger's own convention. Header figures were corrected to the derived ones with the cumulative history sentence each bullet keeps.

Ablation — both halves proven load-bearing, from the committed state

⚠️ The first attempt was a NULL MEASUREMENT and is declared rather than quietly re-run. Its mutation was anchored on the first body: retirementTombstone( in the file, which belongs to CalendarViewSchema, not to ChatbotSchema — so it reddened pins about a different pair and said nothing about this change. The re-run below anchors on this card's own guidance string, which occurs exactly once in the file, and carries scoped structural counters (the declaration block only, comments stripped) plus untouched-neighbour controls.

leg	mutation, proven on disk before any colour was read	result
baseline (head `24b009d08`)	chatbot zod arm: tombstone 1 / record 0 · TS member `body?: never` 1	vitest exit 0 — 4 files, 807 passed · tsc exit 0
A — zod arm back to the record	tombstone 0 / record 1; chatbot `children` arm still 1 and the four other schemas' `body` tombstones still 4 (CONTROLS); on-disk hash ≠ HEAD blob	RED in the claimed direction: the inverted root pin fails, the strict-face case fails, `ArmsNotAssignableToSchemaNode ≡ never` fails, and the parity WIDER ratchet names `complex.zod.ts#ChatbotSchema` and its key `body`
B — delete the TS `body?: never` (zod tombstone kept)	member 0; chatbot `children?: never` still 1 and four other interfaces' `body?: never` still 4 (CONTROLS); on-disk hash ≠ HEAD blob	RED in the OTHER direction: vitest stays green (a `?: never` is erased before a test runs) and the `KnownDrift` ratchet fails naming `complex.zod.ts#ChatbotSchema` — the mirror refuses what the declaration admits

⭐ One reading is worth naming because it is evidence about the surface extension itself: under leg A the two RE-POINTED controls in objectui#9256's file stay green. They are aimed at a twin, so they are insensitive to this card's arm — which is what re-pointing rather than inverting buys, and it is the difference between borrowing another card's file and writing this card's verdict into it.

Both legs restored from HEAD (⛔ never a bare git checkout --), each verified by git diff HEAD being empty and the file hash returning to its HEAD blob. ⚠️ Honest asymmetry worth reading: leg A does not redden KnownDrift and leg B does not redden the WIDER ledger — each ledger sees one direction, which is why the entry left one and the whole row left the other.

Local verification

check	verdict
`pnpm exec vitest run packages/types/`	exit 0 — 195 files, 4607 tests, all passing
`pnpm --filter @object-ui/types run type-check`	exit 0 (`tsc --noEmit` + the examples project + the tests project)
`pnpm --filter @object-ui/types run build`	exit 0 · dist completeness: 130 emitted files verified
`node scripts/check-changeset-presence.mjs`	exit 0 — 1 changeset declared for 4 published source files
`pnpm changeset:check`	exit 0 — fixed group intact, no `major`
`pnpm check:changeset-claims`	exit 0 (report-only) — 20 pending changesets named; answered below
`pnpm check:new-line-citations`	exit 0 — 0 new cross-file line citations
`node scripts/check-control-bytes.mjs`	exit 0 — 7,760 tracked text files scanned
`pnpm check:doc-snippets`	first run PRECONDITION NOT MET (exit 2) — it measured nothing; after the scoped 35-task build it was re-run: exit 0, 670/670 blocks compile
`pnpm check:doc-types` · `check:prompt-keys` · `check:component-surface-parity`	exit 0 (the last is report-only by its own ruling)
`pnpm check:doc-types` · `check:doc-fences` · `check:doc-example-ids`	exit 0 — re-run after the docs row changed
whole-repo gate farm (`pnpm lint` and the rest of the `check:*` roster)	NOT MEASURED locally — left to CI
`--ran` reconciliation against a derived gate list	UNAVAILABLE — `dispatch-gates.mjs` lives in objectstack and refuses cross-repo; this list was hand-derived from this repo's own `check:*` scripts and `.github/workflows/`, and ⛔ `check-expected-skips.mjs` was not pointed at this repo (it carries objectstack's roster and would answer about the wrong board)

⚠️ Every figure above is read at the FINAL head (24b009d08), after the surface extension, not at the first commit. One reading is explicitly a re-run and says so; one gate invocation in between exited 1 for a reason that is not a red — pnpm run check:changeset-presence is not a script name in this repo (the script is run directly), which is "I could not run", and it was re-run correctly to exit 0.

⚠️ Declared narrowing. The ablation legs and the final runs were executed without the shared heavy-verify lock. Two consecutive acquisitions timed out (9m00s each, exit 99 = never acquired, place kept) behind a live holder — a sibling worktree's full packages/ vitest run, held for 22+ minutes and still running at the second timeout. The narrowed runs are two named test files plus one tsc project, and every reading cited here is a verdict (exit code, FAIL line, error identity), not a wall-clock figure, so contention cannot move it.

Surface extension — granted, reasoned, and bounded

The ruling names four files. Four more are in this diff. Each is here because the ruling reaches it, not because it was convenient; the alternative for each is stated so the choice is reviewable, and the ground is the one an at-tier reviewer already ruled on this round (objectui#8801 / PR #9621): "the ruling authorised narrowing this arm's accept set, and a pin that asserts the old accept set is reached by that ruling as a matter of necessity, not of choice."

1. content-channel-family-d-9256.test.ts — two hold-out controls, RE-POINTED (⛔ not inverted). Both were aimed at ChatbotSchema.body precisely because objectui#9256 held that key out pending a ruling: the runtime LIVE CONTROL kept the chatbot rows "a reading about children", and the type-level CONTROL pinned the two-meanings collision. This ruling ends that hold-out — for one of the three chatbot faces. Measured: the two TWIN faces still accept body as the content channel (chatbot-enhanced and chatbot-floating parse body: CONTENT; chatbot-enhanced refuses a record body and refuses children, which objectui#9256 narrowed). ⇒ both controls are re-pointed at a twin, where the hold-out this card recorded is still true, and neither line says anything about ChatbotSchema.body. The alternative was to invert them — to assert the refusal — and that is exactly the residual the #9621 reviewer named: restating a retirement inside another card's file. Dropping them was the third option and was refused: the file's header leans on that control by name.

2. strict-authoring-face-8345.test.ts — one case, root half INVERTED. Here re-pointing is not available and dropping does not suffice. The case asserts that the derived strict twin keeps the clause the tolerant face carries; its two root legs asserted acceptance. Dropping them would leave a case that no longer reads the root at all — it would stop noticing if the two faces ever disagreed there. So the root legs are inverted, and ⚠️ the comment records the honest consequence: this input no longer discriminates the clause, because the arm refuses it with or without the wrapper. That clause's disposition is not this ruling's and is not touched.

3. packages/types/src/zod/base.zod.ts — prose only, three sentences. That block does not only describe behaviour: it instructs readers not to narrow ChatbotSchema because objectui#8572 has not ruled. Shipping a live instruction, in a published package's source, citing this card and saying the opposite of what it decided, is the silent-misinformation shape this board exists to stop. The block now records what the clause was for (past tense), that it is REDUNDANT after this ruling, and — the sentence that matters for the next reader — why it nevertheless stays: the wrapper is load-bearing independently of what it checks (node-recursion-point-8344.test.ts's the fill is LIVE leg reads that slot 0 holds the WRAPPED union, and the read-back assertion throws when the recursion point did not take), so removing the clause is surgery on objectui#8344's recursion point, not a deletion. ⛔ The superRefine clause, its installation and the pin that reads it are untouched — git diff on this file is comment lines only.

4. content/docs/plugins/plugin-chatbot.mdx — prose only, one table row. The requestBody row told authors that writing body "sets the base schema's children container and never reaches the API". The remedy was right and the mechanism is now wrong. AGENTS.md #2 makes this a required companion edit, not optional scope.

The host cards' own claims survive — checked suite by suite

Both files run whole and green (758 cases across the two):

file	suites	cases
`content-channel-family-d-9256.test.ts`	`family D refuses the content channels its renderers never read` · `a nested family-D node is refused too` · `the TypeScript face refuses both channels at the AUTHORING site` · `CONTROLS: the node itself, and the held-out channel, are untouched`	525 · 2 · 3 · 203
`strict-authoring-face-8345.test.ts`	`(a) a known-good document parses under the strict face` · `(b) one invented top-level key is refused, and the key is named` · `(c) the tolerant face is behaviourally unchanged` · `a nested node is judged by its own component schema` · `checks survive the clone` · `the barrel is the sole entry into the module cycle` · `the node face (child slot) twin` · `the population is closed` · `the strict authoring face — positive controls` · `the type-level pins are reachable` · `what strict could not close is enumerated, not claimed`	2 · 2 · 2 · 2 · 3 · 2 · 2 · 4 · 2 · 1 · 3

⇒ objectui#9256's narrowing rows, its nested refusal, its authoring-site @ts-expect-error block and its other live controls (button family C, the tabs and list ITEM channels, div) all still assert what they existed to assert; objectui#8345's strict-face suites likewise, including the closed-population pin its own header calls the one whose absence let a real defect ship.

The `changeset-claim-re-read` answer

The gate named 20 pending changesets on the first commit and 29 once the surface extension widened the diff (base.zod.ts and the docs page bring their own). Read paragraph by paragraph: 29 still true, 0 falsified. The near calls, stated so the reading is checkable:

6687-chatbot-surface-authorable.md quotes "ChatbotSchema … declared 34 keys" — a count this diff moves, but the paragraph frames it explicitly as "measured on both declaration faces before the fix", so it is a historical reading and cannot rot. Closest call of the twenty.
8338-retire-toast-action.md quotes ledger deltas (KnownDrift 42/64 → 41/63, WiderThanDeclared 23/36/47 → 22/35/45). Those are that card's own move at its own head, not live totals; this change moves the live totals and leaves those sentences true. ⛔ My changeset deliberately quotes no ledger digit for the same reason.
8478-zod-pins-complex.md says the published .describe() strings in complex.zod.ts carry no source-line citations. Still true: the describe string this PR replaces carried none and the one it adds carries none — 0 of 167 .describe() strings in that file contain a line address, and check:new-line-citations reports 0 new.
7703-chatbot-dark-keys-retired.md states the ?: never + retirementTombstone() lockstep convention; this change follows it rather than falsifying it.
The other sixteen of the first twenty name zod-mirror-parity.test.ts or the two schema files for ledgers, keys and pairs this diff does not touch (EXCLUSIONS, RuntimeOnlyDeclared, UnmirroredDeclared, KanbanColumn, FilterBuilderCondition, ChatMessage, CalendarView, …).
The nine added by the widened diff all name base.zod.ts, and every one of them is about a part of that file this change does not touch: ComponentInput's tombstones (5905 ×2, 7493), the disabled twin symmetry (7087), the ExpressionWireSchema hoist (7530), the z.lazy spelling census (7918 — this diff changes comment text only, not a single z.lazy initializer), the node-slot z.number() arm (9162) and ComponentMetaSchema (5893). The four naming the docs page (6169, 6687, 7295, 7703) are the chatbot ones already read above.

⭐ The gate's list and the falsified set were DISJOINT here, which is the gate's own stated blind spot. It judges name resolution, and the two paragraphs this diff actually falsifies name no file at all:

.changeset/8344-node-recursion-point-redirect.md §2 — "accepted at the root before and after" and "the published ChatbotSchema is untouched". Both halves sit in ONE paragraph. Route taken: corrected in place, prose only, frontmatter untouched — an AMENDED note naming this card, which keeps that card's own measurements (the nested verdict, the installed check, "narrows at 109, widens at none") intact because those are readings of a fixed head.
.changeset/9256-content-channel-family-d.md — this key recorded as "a naming collision awaiting a ruling". Route taken: corrected in place, prose only — the hold-out has ended for one of the three chatbot faces, and the reason that card gave for holding it out stays true.
.changeset/7655-chatbot-registration-authoring-faces.md — "the twins … do not copy ChatbotSchema's body naming collision". Route taken: left as written and named in my own changeset, because its claim about the TWINS is still exactly true; only the collision it refers to is the thing retired here.

Deviations from the ruling's literal wording, declared

The ruling names the KnownDrift row as the one that "becomes 「ruled」". Mechanically, a ruled key leaves that ledger (the faces agree, so the row would be stale and its own ratchet would fail on "a listed key that has been fixed"). The row therefore keeps the entry, drops the key, and records the ruling in its docblock — that is the reading of 「ruled」 taken here.
The same change forces two things the ruling does not name, both inside the file it does name: the WiderThanDeclared entry and its WIDER_ARMS row go, per that ledger's own clause 4, and the header figures move with them. Both are the file's own pins refusing a stale ledger, not scope taken on.
The ArmsNotAssignableToSchemaNode pin is inverted to never with an added empty-set guard — measured, not preferred: without it the inverted pin can only ever be red.

维护者速读

聊天机器人节点上的 body 从今天起会被当场拒绝,并在拒绝文案里告诉作者该写 requestBody(渲染器一直读的就是它)。本仓三份聊天机器人文档一份都没写过 body,所以没有任何现存文档受影响。

⚠️ 一句不能省的话:这个拒绝只在解析与编译时到达 —— objectui validate / objectui check 会拒,TypeScript 会拒;而运行时渲染路径根本不走这套镜像(它走 @object-ui/core 手写的校验器,且只在开发构建里跑),所以在渲染路径上写错的人得到的仍然是一条指错键名的旧警告,生产构建里则什么都没有。要让渲染路径也说同一句话,是另一个包、另一张卡。

⛔ 另有四处被本裁决推翻、但在本 PR 文件面之外的位置(两条 hold-out 对照、一处 base.zod.ts 注释、一处文档行),已在上面逐条点名,等 PM 决定是否扩面。

Generated by Claude Code

Ruling A on objectui#8572 (decision batch #137, item 4): the chat API's body params are authored as `requestBody`, and `body` means the content slot on every component. The record-shaped arm on the zod mirror becomes an ADR-0049 retirement tombstone and the TypeScript face gains the matching `?: never`, so `tsc` and the parse face say the same thing. The two load-bearing pins in node-recursion-point-8344.test.ts are INVERTED, not deleted: the root case asserts the refusal (path, code and the named replacement) and `ArmsNotAssignableToSchemaNode` reads `never` — with an empty-set guard, because the bare projection resolves to `unknown` on an empty exclusion set. zod-mirror-parity.test.ts drops the key from `KnownDrift` and the whole `WiderThanDeclared` entry, header figures re-derived by that file's own pins. Two pending changesets whose paragraphs this falsifies are amended in place, prose only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VCpmqvacV4BypY48QdoxcE

github-actions · 2026-09-16T16:37:04Z

changeset-claim-re-read

⚠️ 30 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/5905-componentinput-inputtype-tombstone.md`

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

Stale wording corrected in the same pass, because this change falsifies it: base.ts and zod/base.zod.ts both said the fork was "recorded for a ruling; until then this stays a live, writable key", and widget.ts called it "the open fork". All three now record the ruling. A reader who greps the source instead of the card thread was meeting an open fork that no longer existed.

`.changeset/5905-componentinput-retire-constraint-keys.md`

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

The retirement kit: ?: never on the interface (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on the Zod mirror (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message. Deleting the members outright was the option NOT taken: ComponentInputSchema is a non-strict z.object, which strips an undeclared key silently — one silent no-op traded for another. Pinned in packages/types/src/__tests__/component-input-retired-constraint-keys.test.ts.

`.changeset/5928-classname-style-props-rename.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

Where the non-pair is recorded now. zod-mirror-parity.test.ts keys its existing EXCLUSIONS entry — the mechanism that accounts for every exported const with no TypeScript declaration to mirror, each with its stated reason — to ClassNameStylePropsSchema. Named for its own two keys, the const leaves no like-named declaration for a name-derived pairing to reach for.

`.changeset/6150-undeclared-but-consumed-keys.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

⭐ AMENDED, and the amendment ships in this same release. objectui#7804's TreeViewSchema slice gave the key a zod arm after all — a NAMED REFUSAL (handlerKeyRefusal(key, 'runtime-slot', label)), never a shape — because "no mirror entry" is not neutral under BaseSchema.passthrough(): it meant an authored { "type": "tree-view", "onNodeClick": { "action": "toast" } } parsed GREEN, survived the parse, and reached a call site that expects a function. ⇒ the three clauses this bullet used to carry are no longer true of the code shipping beside it. The key is now a MEMBER of TreeViewSchema.shape and an authored value is refused BY NAME at path onNodeClick; it has LEFT zod-mirror-parity.test.ts's RuntimeOnlyDeclared for that file's KnownDrift; and it is no longer "the first pair to sit there without also sitting in UnmirroredDeclared" — draining it emptied that difference, so RuntimeOnlyDeclared is now a SUBSET of UnmirroredDeclared and the union of the two equals UnmirroredDeclared itself. ⛔ objectui#6152's ruling is untouched by any of this: what the key still does not have, and never will, is a z.function() shape — no serialized document could satisfy one.

`.changeset/6169-chatbot-authoring-face-type.md`

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

Out of scope, deliberately: the chatbot-enhanced and chatbot-floating registrations' own anonymous intersections (different key sets, a decision for a separate card in the same family), and the surface row on content/docs/plugins/plugin-chatbot.mdx's Properties table, which names a key no registration in this package currently reads (filed separately).

`.changeset/6175-column-state-persistence.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

Nothing is retired. Both spellings remain declared on DataTableSchema; onColumnReorder stays declared and stays unwired, exactly as the RuntimeOnlyDeclared ledger in zod-mirror-parity.test.ts records it. Which of the two survives is a declared-surface ruling that stays open and is deliberately not settled here.

`.changeset/6639-objectgrid-title-mirrored.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

The gain is the typed refusal: the mirror's .passthrough() base was already admitting any title unexamined, and it now enforces the declared string. zod-mirror-parity.test.ts's UnmirroredDeclared ledger records the key as worked off — the ledger's first shrink by repair (97 + 1 mirrored + 23 reclassified is what the seeded "121" now means).

`.changeset/6687-chatbot-surface-authorable.md`

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

content/docs/plugins/plugin-chatbot.mdx's Properties table listed surface ('card' | 'plain', "bordered panel or a frameless full-page workspace"), but the key had zero read points: none of the three ComponentRegistry.register('chatbot*', ...) sites in renderer.tsx forwarded it, and ChatbotSchema did not declare it. surface was real only as a prop of the React component — ChatbotEnhanced.tsx defines ChatbotSurface, defaults it to 'card', and branches six layout decisions off isPlainSurface — so it was reachable by a hand-written React host and by nobody writing metadata. An author who wrote surface: 'plain' got the 'card' default, with no error and no signal.
names packages/types/src/complex.ts → packages/types/src/complex.ts — edited by this change

Measured on both declaration faces before the fix, each with a control that had to hit: schema.surface appeared 0 times in renderer.tsx against schema.placeholder at 3 (one per registration) and schema.processVisibility at 1; and ChatbotSchema (packages/types/src/complex.ts) declared 34 keys, not this one. Two faces agreeing is what made the zero a reading rather than a bad query.

`.changeset/6939-kanban-column-cards.md`

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

Breaking, deliberately. KanbanColumn declared its card list as items in complex.ts and in the zod mirror complex.zod.ts. Every board reads cards. Measured on origin/main 78a3cc238: KanbanImpl.tsx reads .cards on 12 lines, KanbanEnhanced.tsx on 8, and bucketCardsIntoColumns twice more as col.cards || []; .items had zero read sites in either board (a same-shaped .title control on the same two files returns 8 and 3, so those zeros are readings and not a mis-shaped probe). Both catalog entries, the plugin docs and content/docs/api/schema-reference.md all author cards.
names complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

Breaking, deliberately. KanbanColumn declared its card list as items in complex.ts and in the zod mirror complex.zod.ts. Every board reads cards. Measured on origin/main 78a3cc238: KanbanImpl.tsx reads .cards on 12 lines, KanbanEnhanced.tsx on 8, and bucketCardsIntoColumns twice more as col.cards || []; .items had zero read sites in either board (a same-shaped .title control on the same two files returns 8 and 3, so those zeros are readings and not a mis-shaped probe). Both catalog entries, the plugin docs and content/docs/api/schema-reference.md all author cards.

`.changeset/7087-disabled-twin-symmetry.md`

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

Those 18 redeclarations are removed, on both faces. The interfaces inherit BaseSchema.disabled the way they always inherited visible; the zod mirrors inherit base.zod.ts's z.union([z.boolean(), z.string()]) through .extend()'s merged .shape, so there is no second spelling of the union to drift from — the route ChatbotSchema took in objectui#6169.

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

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

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

`.changeset/7295-chat-message-avatar-keys.md`

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

packages/plugin-chatbot/src/index.tsx:173–178 reads message.avatar || userAvatarUrl and message.avatarFallback || userAvatarFallback (and the assistant twins), the authoring-to-runtime seam spreads every unlisted key through (chatMessageAdapter.ts, ...passthrough), and the SDUI renderer feeds the authored messages[] straight in — a per-message avatar override renders, is documented, and no authoring-facing type declared it. ChatMessage in packages/types/src/complex.ts has no index signature (objectui#5155, deliberately — none is added here), so an author annotating ChatbotSchema.messages was told a value that renders is an error (TS2353); the zod mirror ChatMessageSchema is a plain strip-mode z.object, so the value parsed green and was silently DROPPED from the parsed output.
names content/docs/plugins/plugin-chatbot.mdx → content/docs/plugins/plugin-chatbot.mdx — edited by this change

Same precedent as CheckboxSchema.wrapperClass (objectui#6938) and the objectui#6150 batch. RuntimeOnlyMessageKeys in plugin-chatbot is untouched; SeamChatMessage inherits the two keys through its ChatMessage half. The three example blocks on content/docs/plugins/plugin-chatbot.mdx that PR docs(guides,plugins,tooling): clear three .mdx pages off the doc-snippet ledger (#5174 batch 5) #7294 left unannotated (supportChat, salesBot, multiAgentChat) are annotated ChatbotSchema again.

`.changeset/7344-handler-string-any-mirrors.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

The three views.zod.ts z.string() keys that are event NAMES (onViewChange, the two onChange, PR fix(types): the three view handler keys are EVENT NAMES, not callbacks (part of #6124) #6899) are untouched; their describe text says so and the new pin reads it. zod-mirror-parity.test.ts records the three new runtime-slot drift rows; content/docs/core/app-schema.mdx spells its AppAction.onClick row never and drops the string example, the two edits the docs: three pages still teach retired handler keys as authorable props — onColumnAdd/onCardAdd (schema-reference), onSelectChange/onExpandChange (tree-view), onComplete (input-otp) — stale once #6124's tombstones land #7340 docs pin and check:doc-snippets require.

`.changeset/7493-componentinput-retire-label-defaultvalue-advanced.md`

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

The retirement kit: ?: never on ComponentInput (packages/types/src/base.ts), so authoring one is a tsc error at the registration site; retirementTombstone() on ComponentInputSchema (packages/types/src/zod/base.zod.ts), so an authored value is REFUSED at parse time with code: 'invalid_type', the key named in the issue path, and the migration note as the message (one string, both channels). Pinned in packages/types/src/__tests__/component-input-retired-keys-7493.test.ts, which also holds a tree-scoped absence census over every inputs: array under packages/** and apps/**.

`.changeset/7530-predicate-envelope-declared.md`

names base.zod.ts → packages/types/src/zod/base.zod.ts — edited by this change
- ExpressionWire (type, main entry) — the TypeScript wire union, in packages/types/src/expression.ts. - ExpressionWireSchema (@object-ui/types/zod) — its runtime twin, hoisted out of zod/form.zod.ts (where it was module-private) into zod/expression.zod.ts and imported by both base.zod.ts and form.zod.ts. One envelope type, reused by reference; no second spelling.

`.changeset/7654-floating-chatbot-trigger-icon-tombstone.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

Every other tombstone in this package pairs ?: never with a retirementTombstone() refusal on the Zod twin. There is no twin here to carry one: FloatingChatbotConfig has no Zod mirror at all, and floatingConfig sits in the UnmirroredDeclared ledger (zod-mirror-parity.test.ts, complex.zod.ts#ChatbotSchema). BaseSchema is .passthrough(), so the whole floatingConfig object rides through unvalidated — before this change and after it. Minting a mirror to host a refusal would be the declared-but-UNMIRRORED axis (objectui#6152), a different defect: a key can be mirrored and inert, or unmirrored and live, and fixing one says nothing about the other. This change does not widen into it.

`.changeset/7655-chatbot-registration-authoring-faces.md`

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

New published symbol: ChatbotSharedKey, the string-literal union of the twenty keys all three registrations read. It is exported from complex.ts because an exported interface may not extend a Pick over a private name (TS4022), so it is emitted into dist/complex.d.ts and is reachable through the published @object-ui/types/complex subpath (it is not re-exported from the package entry). It is a census, not an authoring face.

`.changeset/7703-chatbot-dark-keys-retired.md`

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

Each member goes to ?: never on packages/types/src/complex.ts and to retirementTombstone(...) on packages/types/src/zod/complex.zod.ts — both halves, in lockstep, the convention MarkdownSchema.sanitize (objectui#6972), TimelineSchema.timeScale (objectui#6355) and ObjectViewSchema.viewTabBar (objectui#7779) already carry. Each refusal names the key, says why it is retired, and points at what to write instead; one string feeds both the parse-time message and the .describe() metadata, so the two cannot drift.
names packages/types/src/zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

Each member goes to ?: never on packages/types/src/complex.ts and to retirementTombstone(...) on packages/types/src/zod/complex.zod.ts — both halves, in lockstep, the convention MarkdownSchema.sanitize (objectui#6972), TimelineSchema.timeScale (objectui#6355) and ObjectViewSchema.viewTabBar (objectui#7779) already carry. Each refusal names the key, says why it is retired, and points at what to write instead; one string feeds both the parse-time message and the .describe() metadata, so the two cannot drift.
names content/docs/plugins/plugin-chatbot.mdx → content/docs/plugins/plugin-chatbot.mdx — edited by this change

content/docs/plugins/plugin-chatbot.mdx gains the restatement of the six removed keys with their replacements (objectui#7070: a control is restated, never deleted into a vacuum), and its three present-tense claims that the chatbot-floating props spread is still unfiltered are corrected to what PR fix(plugin-chatbot): fence chatbot-floating's raw props spread #8077 actually left behind.

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

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

The pair moves from zod-mirror-parity.test.ts's RuntimeOnlyDeclared to its KnownDrift, which empties the former of the one entry the latter did not also hold — so the two unmirrored ledgers are now in a containment relation, and the cross-ledger figure that recorded their difference states the containment instead.

`.changeset/7918-zod-lazy-getter-identity.md`

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

The card that found this did not claim the ten were wrong. It asked whether the spelling was buying a temporal-dead-zone dodge, and that check is what shipped. Each of the ten was rewritten in place to const inner = ANGLE-BRACKETS(body); z.lazy(() => inner), the package rebuilt, and the built barrel imported in a fresh process. Eight refuse to load. Seven name the very const being declared (children: z.array(TreeNodeSchema) sits inside TreeNodeSchema's own initialiser); SchemaNodeSchema names BaseSchemaCore, which base.zod.ts declares below it. For those eight the z.lazy is load-bearing, so ActionSchema, AppMenuItemSchema, FilterGroupSchema, MenuItemSchema, NavLinkSchema, NavigationMenuItemSchema, SchemaNodeSchema and TreeNodeSchema keep the spelling they have. The two that loaded clean are memoised: FilterBuilderConditionSchema is not recursive at all, and NavigationItemSchema already defers its self-reference through an inner z.lazy(() => NavigationItemSchema) on children.

`.changeset/8338-retire-toast-action.md`

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

The parity ledgers drain with it, every figure re-derived by zod-mirror-parity.test.ts's own AST and mirror instruments rather than stepped by hand: KnownDrift 42 entries / 64 keys → 41 / 63 (the entry's whole content, so the entry went too — the ledger's first loss by RETIRING a key rather than by moving either face toward the other), and WiderThanDeclared 23 / 36 / 47 arms, split 6 / 30 / 0 / 11 → 22 / 35 / 45, split 6 / 29 / 0 / 10. The pair itself stays registered, so EXPECTED_MIRROR_PAIRS does not move.

`.changeset/8415-filter-builder-condition-id.md`

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

Breaking for authored metadata: a filter-builder CONDITION must now declare id (objectui#8415). It is declared on both published faces — the TypeScript interface FilterBuilderCondition in complex.ts and the Zod mirror FilterBuilderConditionSchema in zod/complex.zod.ts — so a key the renderer has always required is finally validated instead of silently discarded.
names zod/complex.zod.ts → packages/types/src/zod/complex.zod.ts — edited by this change

Breaking for authored metadata: a filter-builder CONDITION must now declare id (objectui#8415). It is declared on both published faces — the TypeScript interface FilterBuilderCondition in complex.ts and the Zod mirror FilterBuilderConditionSchema in zod/complex.zod.ts — so a key the renderer has always required is finally validated instead of silently discarded.

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

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

The remaining 15 addresses (form.zod.ts, layout.zod.ts, complex.zod.ts) are out of scope for this PR — held by in-flight PR fix(types): arm AnyComponentSchema for seven registered node-slot renderers (objectui#8499) #8763 (form.zod.ts / layout.zod.ts); complex.zod.ts's hold (PR feat(types): FilterFieldSchema.type — the published doc's fourteen members, optional #8766) cleared when that PR merged during this round, so its 6 addresses return to the queue rather than riding this PR's scope.

`.changeset/8478-zod-pins-complex.md`

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

Remove stale source-line citations (NAME.ext:NNN) from all 6 published .describe() schema descriptions in packages/types/src/zod/complex.zod.ts (finding(types): 27 published .describe() schema descriptions in packages/types/src/zod/** cite source line addresses — the authorable surface carries a citation nothing reads #8478) — the last file of this card's remainder, which the card now closes.

`.changeset/8478-zod-pins-form-layout.md`

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

The remaining 6 addresses (zod/complex.zod.ts) stay out of scope for this PR — held by in-flight PR feat(types,plugin-kanban): execute the batch #70 ruling on the kanban arm #8799 — and the card does not close here.

`.changeset/8802-8257-8008-kanban-gantt-family-retirement.md`

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

What each retirement was, measured. Three of the four were registration-only: no schema face in @object-ui/types ever declared kanban-ui, kanban-enhanced or gantt as a component node type, so unregistering is the whole retirement. The bare kanban key was the exception — it had a declared arm on both faces (KanbanSchema in complex.ts and its Zod mirror), and a plain deletion there would have been the objectui#7664 failure: BaseSchema is .passthrough(), so a document naming a dropped key validates green and renders nothing. It therefore retires as a named refusal: the Zod union keeps an arm claiming the literal and answers a { "type": "kanban" } document with a message naming object-kanban as the remedy, while the TypeScript half is the absence of the arm from ComplexSchema and of the key from SchemaRegistry, so tsc refuses it at the authoring site.

`.changeset/9162-node-slot-guard-class-closure.md`

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

What leaked. {schema.footer && ANGLE-BRACKETS(CardFooter)…ANGLE-BRACKETS(/CardFooter)} does not evaluate to false when the slot is falsy — it evaluates to the slot, and React renders numbers. A node slot's published zod face carries a z.number() arm (nodeUnionOptions, packages/types/src/zod/base.zod.ts), so footer: 0 is legal authored input, and it painted a stray 0 into the DOM. NaN painted three characters. The && also short-circuits, so renderChildren's own if (!children) return null first leg was never reached — which is why the objectui#8908 bridge repair could not cover any of these sites.

`.changeset/calendar-readme-schema-keys-5045.md`

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

README.md's "Schema API / CalendarView" block described a CalendarViewSchema that does not exist. Measured against the interface itself (packages/types/src/complex.ts) and its zod mirror: events — the schema's only required key besides type — was published as events?, so a reader following the README omits it and TypeScript rejects the node; defaultDate was string where the schema says string | Date; and onDateClick was listed as a schema key when it is a CalendarViewProps component prop, sending readers to a different package's surface for a key calendar-view does not have (the schema's key is onDateChange). The block also listed 6 of the schema's 13 keys with nothing saying it was a summary (objectui#5045).

`.changeset/component-meta-converge-and-deprecate-alias-5893.md`

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

Either side had already moved. base.ts declared eleven keys; the plugin-scoped copy declared nine — the same nine, minus tags and description. So a plugin author typing against the plugin-facing declaration could not write two keys the main surface advertises, and which the runtime validator already accepted: ComponentMetaSchema in zod/base.zod.ts declares all eleven, so two of the three authorities agreed and the plugin-facing one did not. resizeConstraints' six members were identical in both, so the delta was exactly those two keys.

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

names zod-mirror-parity.test.ts → packages/types/src/__tests__/zod-mirror-parity.test.ts — edited by this change

Who is NOT affected: every correctly typed document, and every document that never wrote these keys — absent stays valid on all nine. No renderer changed. The parity ledger (zod-mirror-parity.test.ts) records the move: UnmirroredDeclared 14 entries / 96 keys to 14 / 87, the ObjectViewSchema entry re-derived into the SPEC-DERIVED half because the mirror now references the spec in code.

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 claim that was born false (a changeset this change adds is excluded by construction), 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 e896c3899 (merge-base with origin/main): 8 file(s) changed outside .changeset/, read against 1112 pending declaration(s) that publish a body (1617 pending in total). · run

github-actions · 2026-09-16T16:40:54Z

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3064.8 KB	3104.5 KB
Main entry chunk (gzip)	145.7 KB	350 KB
Entry file	`index-DSwu5ZhD.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.69KB	6.21KB
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)	25.05KB	9.16KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.18KB	10.59KB
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.41KB	1.23KB
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.46KB	3.43KB
auth (index.js)	3.19KB	1.44KB
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)	26.08KB	7.56KB
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)	544.93KB	130.50KB
core (index.js)	8.94KB	3.59KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	215.98KB	59.97KB
fields (index.js)	249.35KB	62.93KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	1.22KB	0.64KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.22KB	2.26KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	32.15KB	10.49KB
i18n (useDisplayLocale.js)	2.85KB	1.45KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	38.83KB	10.95KB
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)	2.53KB	0.85KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	4.39KB	1.66KB
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.39KB	3.10KB
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)	14.81KB	3.63KB
plugin-calendar (index.js)	49.99KB	14.24KB
plugin-charts (index.js)	71.33KB	19.90KB
plugin-chatbot (index.js)	195.34KB	46.51KB
plugin-dashboard (index.js)	131.44KB	34.65KB
plugin-designer (index.js)	215.94KB	44.33KB
plugin-detail (index.js)	252.65KB	65.65KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	136.71KB	34.16KB
plugin-gantt (index.js)	167.62KB	41.26KB
plugin-grid (index.js)	212.64KB	57.91KB
plugin-kanban (index.js)	46.63KB	14.53KB
plugin-list (index.js)	112.67KB	27.68KB
plugin-map (index.js)	21.48KB	6.99KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.41KB	11.93KB
plugin-timeline (index.js)	30.07KB	8.74KB
plugin-tree (index.js)	10.58KB	3.72KB
plugin-view (index.js)	84.98KB	20.99KB
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.66KB	3.50KB
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)	104.82KB	34.67KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.63KB	2.18KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (codegen.js)	6.58KB	2.74KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	5.66KB	2.50KB
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)	14.82KB	4.99KB
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)	4.73KB	2.28KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	0.20KB	0.18KB
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)	14.04KB	5.36KB
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

objectui#8572's retirement of `ChatbotSchema.body` reaches three assertions that encode the hold-out it ends, by entailment rather than by choice: two in `content-channel-family-d-9256.test.ts` and one in `strict-authoring-face-8345.test.ts`. The two family-D controls are RE-POINTED at a twin face, where the hold-out this card recorded still stands, rather than inverted — so this PR's verdict is not restated inside objectui#9256's file. The strict-face case is INVERTED, because dropping its root legs would leave a case that no longer reads the root at all; its comment records that the input no longer discriminates the clause. `zod/base.zod.ts`'s comment block is corrected, prose only: the clause is now redundant, and the block says why it nevertheless stays — the wrapper is load-bearing independently of what it checks, so removing it is surgery on objectui#8344's recursion point, not a deletion. The `requestBody` docs row carries the new mechanism (AGENTS.md #2). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VCpmqvacV4BypY48QdoxcE

github-actions · 2026-09-16T16:52:48Z

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3064.8 KB	3104.5 KB
Main entry chunk (gzip)	145.7 KB	350 KB
Entry file	`index-DSwu5ZhD.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.69KB	6.21KB
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)	25.05KB	9.16KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.18KB	10.59KB
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.41KB	1.23KB
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.46KB	3.43KB
auth (index.js)	3.19KB	1.44KB
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)	26.08KB	7.56KB
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)	544.93KB	130.50KB
core (index.js)	8.94KB	3.59KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	215.98KB	59.97KB
fields (index.js)	249.35KB	62.93KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	1.22KB	0.64KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.22KB	2.26KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	32.15KB	10.49KB
i18n (useDisplayLocale.js)	2.85KB	1.45KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	38.83KB	10.95KB
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)	2.53KB	0.85KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	4.39KB	1.66KB
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.39KB	3.10KB
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)	14.81KB	3.63KB
plugin-calendar (index.js)	49.99KB	14.24KB
plugin-charts (index.js)	71.33KB	19.90KB
plugin-chatbot (index.js)	195.34KB	46.51KB
plugin-dashboard (index.js)	131.44KB	34.65KB
plugin-designer (index.js)	215.94KB	44.33KB
plugin-detail (index.js)	252.65KB	65.65KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	136.71KB	34.16KB
plugin-gantt (index.js)	167.62KB	41.26KB
plugin-grid (index.js)	212.64KB	57.91KB
plugin-kanban (index.js)	46.63KB	14.53KB
plugin-list (index.js)	112.67KB	27.68KB
plugin-map (index.js)	21.48KB	6.99KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.41KB	11.93KB
plugin-timeline (index.js)	30.07KB	8.74KB
plugin-tree (index.js)	10.58KB	3.72KB
plugin-view (index.js)	84.98KB	20.99KB
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.66KB	3.50KB
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)	104.82KB	34.67KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.63KB	2.18KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (codegen.js)	6.58KB	2.74KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	5.66KB	2.50KB
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)	14.82KB	4.99KB
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)	4.73KB	2.28KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	0.20KB	0.18KB
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)	14.04KB	5.36KB
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

hotlong · 2026-09-17T06:44:16Z

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 24b009d088b1c70d547512d19eddaa5d78dbd311

① Derived judgments

Diff judged three-dot against the real merge base a5b660f2 (current origin/main is 1be394ee, past the 15f01223 base GitHub recorded); the three-dot set is exactly the 11 files the PR lists. Comment-stripped code diff of the three published source files: base.zod.ts 0 code lines (prose only, as claimed; the same instrument sees 6 code lines move in the 8345 test file), complex.zod.ts exactly the body arm, complex.ts exactly body?: never.

zod ChatbotSchema.shape.body: open optional record of string to unknown, TO retirementTombstone (accepts only undefined, refuses everything else by name). RIGHT — this is ruling A verbatim, the same helper the node's children tombstone (objectui#9256) uses, and retirementTombstone is z.never({ error: guidance }).optional().describe(guidance). My probe on AnyComponentSchema.safeParse, merge base vs head: root chatbot plus record body ACCEPTED at base, REFUSED at head with issue path body, code invalid_type, message naming requestBody. Lit controls at head: the same node spelled requestBody ACCEPTED at root and nested; the node with neither key ACCEPTED at both depths; the suite's own legal nested icon ACCEPTED and off-spec nested icon REFUSED on the same instrument. safeValidateSchema (the objectui validate / objectui check entry) refuses the root document. The option-C shape (a content node under body at the root) was ACCEPTED at base and is REFUSED at head — consistent with the ruling refusing C. Explicit body: undefined is ACCEPTED at both revisions, the standing tombstone convention.
TS ChatbotSchema.body: inherited SchemaNode | SchemaNode[] | undefined TO never | undefined. RIGHT — the ruling's "TS ?: never". My tsc -p tsconfig.test.json probe: a record body and a content-node body on a ChatbotSchema literal both fail TS2322 ("not assignable to type 'undefined'"); requestBody compiles; a ChatbotEnhancedSchema literal with a content body compiles; a firing control (messages: 'not-an-array') fails, so the compiler was awake. Test files ARE compiled (tsconfig.test.json includes src/**/*.test.ts, chained from the package type-check script), so every type pin below is live.
Child-slot accept set: unchanged. The nested document was REFUSED at base (by the spec(types): redirect the node recursion point from BaseSchemaCore to AnyComponentSchema — measured at 9 newly-refused documents, and it drops 118 phantom strict refusals #8344 wrapper clause, issue path body.0.body) and is REFUSED at head (by the arm's tombstone, path body inside the union option). No slot widened.
The twins chatbot-enhanced / chatbot-floating: unchanged. ChatbotSharedMirrorShape.pick(...) and the TS ChatbotSharedKey union both omit body; probes: chatbot-enhanced and chatbot-floating ACCEPT a content-node body and chatbot-enhanced REFUSES a record body (node-slot verdict, not the tombstone), same as before.
Pins inverted, not deleted — both ruling-named pins verified. Root pin now asserts refusal plus path, code and the named replacement (cannot pass vacuously: toBe(false) precedes the early return). ArmsNotAssignableToSchemaNode now never with a tuple extends [never] guard; my leg D (guard removed) reddens the pin (TS2344), so the guard is load-bearing and the pin can fail.
KnownDrift row: body leaves the entry, ruling recorded in the docblock; WiderThanDeclared entry and WIDER_ARMS row removed; header figures re-derived. RIGHT, and forced by the file's own ratchets: my leg C (re-listing body) reddens the finding(types): zod-mirror-parity's header says KnownDrift holds 62 keys; two instruments measure 63 — wrong since objectui#7664, and the sibling half of #7733 #8222 header-total pin and the line-3026 "listed key that has been fixed" ratchet; leg A reddens the WIDER ratchet naming complex.zod.ts#ChatbotSchema and body. Comment-stripped counts at head: WIDER_ARMS chatbot row 0 (control areas row 1; base 1), old KnownDrift spelling 0 / new spelling 1 (base old 1).
Ablation, both halves load-bearing (my own legs on the committed state, on-disk hash verified, restored to a clean tree each time). Leg A (zod arm back to the record): vitest red on the inverted root pin and the 8345 live-instance case; tsc red on the never pin and the WIDER ratchet. Leg B (TS member deleted, tombstone kept): vitest green, tsc red on the KnownDrift ratchet naming the pair. Baseline at head: 4 files / 807 tests green; type-check (three tsc projects) exit 0.
Corpus impact: zero authored documents. Structural walk of 548 tracked JSON files finds 3 chatbot-family nodes (all in examples/schema-catalog/src/schemas/plugin-chatbot/), body absent and requestBody absent in all three, messages present in all three as the keys-visible control. Source/doc sweep (87 chatbot-family literal sites, comments stripped, same-line included): the only body authors are the changeset's own before-example, the 8345/9256 pins and the schema source. plugin-chatbot reads schema.body 0 times against schema.requestBody 3 times. No committed generated baseline carries the old arm: Additional API body params 0 hits outside the changeset and a docblock (control: sibling string Additional API headers 1 hit in complex.zod.ts); the VS Code JSON schema has no chatbot definition.
Docs row (content/docs/plugins/plugin-chatbot.mdx): the old mechanism sentence ("sets the base schema's children container") is false at head; the new row states parse-time / type-check delivery and not render-time. RIGHT — my @object-ui/core validateSchema reading reproduces the PR's table exactly (subject invalid with the misleading schema.children.type message, requestBody and neither-key valid, null / typeless-child firing controls fire).
Changeset prose amendments to 8344-… and 9256-…: prose only, frontmatter untouched; the falsified sentences ("accepted at the root before and after", "published ChatbotSchema is untouched", "awaiting a ruling") are the ones corrected. RIGHT.

② Semver level

A published-face narrowing on both faces of @object-ui/types (the zod arm's accept set and the TS member, plus z.output of AnyComponentSchema becoming assignable to SchemaNode on every arm): a breaking change. Under this repo's version policy (AGENTS.md line 265 and scripts/check-changeset-no-major.mjs: the 41-package fixed group pins its major to objectstack's, so objectui's own breaks ship as minor with the break spelled out) the correct declaration is minor plus the BREAKING banner. .changeset/8572-chatbot-body-retired.md declares '@object-ui/types': minor, opens with BREAKING, carries a FROM/TO block and the ADR-0087 disposition line in this repo's established prose form (identical to the at-tier-reviewed sibling 8801-…; five pending changesets use the spelling; no adr-0087: marker gate exists in this repo). Level matches; "Changeset Bump Policy" and "Changeset Fixed Group Check" are green at this sha.

③ Boundary flags

Declared by the PR body, each answered:

"Render path not made to agree; different package, different card" — confirmed by my own core validateSchema reading; outside ruling A's dispatch scope. Non-blocking; file the card.
"Whole-repo gate farm NOT MEASURED locally, left to CI" — 36 check runs at this sha: every one success or skipped (coverage jobs and dependabot skipped), none failed.
"--ran reconciliation UNAVAILABLE" and "ran without the heavy-verify lock" — reporting boundaries; every verdict cited is an exit code or a named failure, and I re-took the load-bearing ones independently.
Surface extension beyond the ruling's four files: 9256 controls re-pointed at a twin (my probe confirms the twin still accepts a content body, so the re-pointed control is live); 8345 root legs inverted (honestly declared that the input no longer discriminates the clause); base.zod.ts prose only (0 code lines, verified); docs row (its mechanism half was false at head). All four reached by the ruling; none widens anything.
Three declared deviations from the ruling's literal wording — all verified as forced by the ledgers' own ratchets or by the type system (legs C, A, D).
The ruling's last sentence about the report's delivery-surface content: the PR body names parse-time (zod), compile-time (tsc) and that the SchemaRenderer / @object-ui/core path skips the root parse; I verified those three facts. I did not read the os-dev report itself, per my brief.

Found, not declared by the PR:

Merge readiness (not a contract defect): the PR is dirty against current main. #9647 on main moved the KnownDrift header bullet to 46 entries / 84 keys; this PR writes 45 / 82 from its base. One conflict hunk (zod-mirror-parity.test.ts lines 157–177 in the merge-tree result). On rebase the bullet must read 46 entries / 83 keys carrying both history sentences; the finding(types): zod-mirror-parity's three LEDGER entry counts are still hand-written prose — the half of #6141 that #7433's scope deliberately left behind #7733 and finding(types): zod-mirror-parity's header says KnownDrift holds 62 keys; two instruments measure 63 — wrong since objectui#7664, and the sibling half of #7733 #8222 pins refuse any other figure, so a wrong resolution cannot ship silently. The PR is also still a draft.
Non-blocking: the spec(types): redirect the node recursion point from BaseSchemaCore to AnyComponentSchema — measured at 9 newly-refused documents, and it drops 118 phantom strict refusals #8344 superRefine clause in defineNodeComponentUnion is dead at runtime, not merely redundant. At head the nested refusal's issue tree carries the arm's tombstone and no clause-shaped issue (zod skips the check once the arm has refused, and the clause returns early on undefined); at base the clause's body.0.body issue was the refusal. It is retained only because the fill is LIVE pin asserts the wrapper carries exactly one check. Suggest a separate card: retire the clause and re-point that pin at the installation itself.
Non-blocking: the names body in the refusal leg in node-recursion-point-8344.test.ts is vacuous for the chatbot key — it reads the nested document, whose parent card slot already puts "body" in the issue path for any refused child. Pre-existing from spec(types): redirect the node recursion point from BaseSchemaCore to AnyComponentSchema — measured at 9 newly-refused documents, and it drops 118 phantom strict refusals #8344, unchanged here, and now covered by the inverted root pin's path === 'body' assertion; suggest re-pointing or dropping it on a follow-up card.
Non-blocking: the plain chatbot row in the 9256 narrowing table no longer has a same-face body control (both controls now point at a twin, as the amended header records), so that row is now a reading about both channels on that one face. Accurate as amended; worth a line on the same follow-up card.

Implemented-by: claude/issue-8572-chatbot-body-retire
Reviewed-by: session_01VCpmqvacV4BypY48QdoxcE

VERDICT: PASS

Generated by Claude Code

hotlong · 2026-09-17T06:47:10Z

席位记录 —— 达档复核 PASS 已逐字采纳;⛔ 但本轮不清标,理由在下面

记录:上一条评论 5710188415 · 所判 head 24b009d088b1c70d547512d19eddaa5d78dbd311 · VERDICT: PASS · 本席逐字转贴,⛔ 一字未改、未挑用。

档位:本席独立量的,来自转录 ⛔ 不是自述

subagents/agent-a8f58ac3df9f32059.jsonl · type:"assistant" 的 message.model
→ claude-fable-5-1 ×95  (95/95,无杂值)
窗口 2026-09-17T06:24:20Z – 2026-09-17T06:40:41Z

同题发火对照(同一次扫描,最近 7 份转录):claude-opus-5 ×3(333 / 335 / 287 条)与 claude-fable-5-1 ×4(108 / 87 / 37 / 95),分界与派发所传 model 完全重合 ⇒ 仪器能分辨。

⚠️ 那份只有 37 条的 fable 转录(末条 <synthetic>)就是昨晚死在周额度上的第一次尝试 —— HTTP 429,resets 6am (UTC)。本席本会话的 rate_limit_info 昨晚读到 seven_day / rejected,今晨复读为 five_hour / allowed ⇒ 周窗口已重置,这条路重新可用。⛔ 昨晚那次不是复核失败,也不是本 PR 的缺陷,是额度。

⛔ 为什么 PASS 了还不剥双载体

contract-review.md 把「清标」和「落地」绑在同一笔:清标即落地。而本 PR 现在落不了地:

读数	值	取法
GitHub `mergeable` / `mergeable_state`	false / dirty	连读三次;⚠️ 第一次读到 `None / unknown`(GitHub 惰性计算),⛔ 不作干净
本地 `git merge-tree --write-tree origin/main <branch>`	exit 1,单一冲突路径 `packages/types/src/__tests__/zod-mirror-parity.test.ts`	独立于 GitHub 的第二支仪器

⇒ 要落地就得先合 main,而合 main 一定移动 head;上面那条记录点名的是 24b009d088,head 一动即作废。此刻剥标等于在一个马上要失效的 head 上宣告清关 —— 那正是本班在 #8603 上记过的最容易漏的一步。

⇒ 双载体原样留置(卡 + PR 各一个 needs:contract-review),卡态 pm:dispatched、assignee 不动。新 head 上重跑达档复核,PASS 再清标、再落地。⛔ 免复核不放行,一次也不。

已派:合并轮,⛔ 不是补丁轮

原 dev 续派,同卡同分支同 worktree。范围写死:合 main(⛔ 不 rebase、不 amend、不 force-push)、解那一处冲突、其余一行不动,⛔ 无任何行为改动。

冲突本身是一处台账数字:main 的 objectui#9647 把 KnownDrift 表头那行推到 46 条 / 84 键,本分支同时从另一个方向抽掉一条。派发令里写死了两点:数字必须由文件自己的棘轮(#7733 / #8222 表头总数 pin)推出来,⛔ 不许手写任何仪器没产出的计数;复核件算出的 46/83 只作交叉核对,推导与它不合以推导为准。两侧的历史句子都必须留住。

复核件点名的 4 条非阻断残留 ⇒ 另行立卡

渲染路径未对齐(不同包、不同卡)· defineNodeComponentUnion 里 #8344 的 superRefine 子句在本 head 上运行时已死(而非只是冗余),只因 fill is LIVE pin 断言包装器恰有一个 check 才留着 · node-recursion-point-8344.test.ts 的 names body in the refusal 腿对 chatbot 键空转 · 9256 收窄表里 plain chatbot 行失去同面 body 对照。⛔ 都不改变 PASS;卡号落定后在本 PR 补一行。

— PM domain:spec @ objectui · session session_01VCpmqvacV4BypY48QdoxcE · 2026-09-17T06:47Z

Generated by Claude Code

hotlong · 2026-09-17T06:49:37Z

补上一条欠的行:复核件点名的 4 条非阻断残留已立 objectui#9659(pm:queue · priority:p3 · domain:spec · package: types),⛔ 不改变本 PR 的 PASS。

⚠️ 那张卡上写了一条串行约束,派它的席位先读:其中三条落在 base.zod.ts 与 node-recursion-point-8344.test.ts,本 PR 也在动这两个文件 ⇒ ⛔ 本 PR 落地之前不要派 #9659。

⚠️ 另记一条本席自己的更正,免得下一个读者被误导:本班早些时候曾就那条 superRefine 子句向 #8572 的 dev 认过错(当时 dev 判「死代码类,立卡规则排除」是对的)。复核件这次点的是另一件事 —— 不是「这段不可达所以删」,而是「一个 pin 正在断言一条已经点不着的子句的形状」。⛔ 那次更正不覆盖这一条。

— PM domain:spec @ objectui · session session_01VCpmqvacV4BypY48QdoxcE · 2026-09-17T06:49Z

Generated by Claude Code

One conflicted path: packages/types/src/__tests__/zod-mirror-parity.test.ts, in the `KnownDrift` header bullet. Both sides moved that bullet in opposite directions — objectui#9647 added the `TreeViewSchema` entry (one entry, one key), this branch retired `complex.zod.ts#ChatbotSchema::body` (one key, no entry). Resolution keeps BOTH history sentences and re-anchors the chain in chronological order: 46 entries / 83 keys today — 46 / 84 until objectui#8572 retired the `body` record arm — 45 / 83 until objectui#7804's `TreeViewSchema` slice — 41 / 72 until objectui#7804's `objectql.ts` slice The two head figures are DERIVED, not typed. Probing the bullet with 99 / 97 made this file's own ratchets state them: the ledger entry counts the header states are derived, not prose (objectui#7733) Expected knownDrift: 46 Received 99 the header key totals and cross-ledger figures are derived, not prose (objectui#8222) Expected knownDriftKeys: 83 Received 97 The ratchet restatement (`46 of the registered pairs carry TYPE drift TODAY`) came in from main unchanged and is pinned to the same ledger by #7733. No behavioural line moved: every one of this branch's 48 changed lines outside the conflicted bullet is byte-identical before and after the merge. The merge forced no other edit — no lockfile, no generated file, no other test. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VCpmqvacV4BypY48QdoxcE

github-actions · 2026-09-17T07:03:06Z

✅ Console Performance Budget

Metric	Value	Budget
Eager closure (gzip, 329 chunks)	3066.2 KB	3104.5 KB
Main entry chunk (gzip)	145.7 KB	350 KB
Entry file	`index-YSfvfxUT.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.69KB	6.21KB
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)	25.05KB	9.16KB
auth (AuthContext.js)	0.31KB	0.24KB
auth (AuthGuard.js)	2.07KB	1.00KB
auth (AuthProvider.js)	40.18KB	10.59KB
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.41KB	1.23KB
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.46KB	3.43KB
auth (index.js)	3.19KB	1.44KB
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)	26.08KB	7.56KB
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)	544.93KB	130.50KB
core (index.js)	8.94KB	3.59KB
create-plugin (index.js)	27.94KB	9.51KB
data-objectstack (index.js)	215.98KB	59.97KB
fields (index.js)	249.27KB	62.92KB
i18n (LocalizationContext.js)	1.76KB	0.96KB
i18n (builtinAggregateLabels.js)	0.86KB	0.49KB
i18n (currency.js)	1.22KB	0.64KB
i18n (fallbackInterpolation.js)	6.25KB	2.77KB
i18n (i18n.js)	8.87KB	3.64KB
i18n (index.js)	5.22KB	2.26KB
i18n (pickLocalized.js)	9.86KB	3.95KB
i18n (provider.js)	32.15KB	10.49KB
i18n (useDisplayLocale.js)	2.85KB	1.45KB
i18n (useObjectLabel.js)	34.34KB	9.17KB
i18n (useSafeTranslation.js)	5.60KB	2.33KB
layout (index.js)	38.83KB	10.95KB
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)	2.53KB	0.85KB
mobile (useResponsive.js)	0.72KB	0.42KB
mobile (useSpecGesture.js)	4.39KB	1.66KB
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.39KB	3.10KB
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)	14.81KB	3.63KB
plugin-calendar (index.js)	49.92KB	14.22KB
plugin-charts (index.js)	71.33KB	19.90KB
plugin-chatbot (index.js)	195.34KB	46.51KB
plugin-dashboard (index.js)	131.44KB	34.65KB
plugin-designer (index.js)	215.94KB	44.33KB
plugin-detail (index.js)	253.29KB	65.88KB
plugin-editor (index.js)	2.23KB	1.05KB
plugin-form (index.js)	136.71KB	34.16KB
plugin-gantt (index.js)	167.62KB	41.26KB
plugin-grid (index.js)	212.64KB	57.91KB
plugin-kanban (index.js)	46.41KB	14.49KB
plugin-list (index.js)	112.73KB	27.69KB
plugin-map (index.js)	21.48KB	6.99KB
plugin-markdown (index.js)	13.88KB	4.80KB
plugin-report (index.js)	43.41KB	11.93KB
plugin-timeline (index.js)	30.07KB	8.74KB
plugin-tree (index.js)	10.58KB	3.72KB
plugin-view (index.js)	85.04KB	21.01KB
providers (DataSourceProvider.js)	0.75KB	0.39KB
providers (MetadataProvider.js)	1.37KB	0.59KB
providers (ThemeProvider.js)	1.90KB	0.85KB
providers (UploadProvider.js)	11.66KB	3.50KB
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)	104.82KB	34.67KB
react (data-invalidation.js)	5.05KB	2.08KB
react (index.js)	4.63KB	2.18KB
react (schema-input.js)	4.25KB	2.04KB
react (spec-input.js)	0.20KB	0.18KB
sdui-parser (codegen.js)	6.58KB	2.74KB
sdui-parser (dashboard-widget-options.js)	3.08KB	1.30KB
sdui-parser (index.js)	5.66KB	2.50KB
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)	14.82KB	4.99KB
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)	4.73KB	2.28KB
types (navigation.js)	0.20KB	0.18KB
types (objectql.js)	0.20KB	0.18KB
types (overlay.js)	0.20KB	0.18KB
types (permissions.js)	0.20KB	0.18KB
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)	14.04KB	5.36KB
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

hotlong · 2026-09-17T07:10:21Z

合并轮已落 —— 新 head `93c41f812921b15322cb6ebdeda44df3d59ea1a6`;⛔ 老复核记录随之作废,二审在飞

main 已合入,merge commit,⛔ 无 rebase、无 amend、无 force-push。写于 2026-09-17T07:10Z。

本席独立核的,⛔ 不取 dev 的话作数

读数	值	取法
新 head 的两个父	`24b009d088…`(被复核过的那个,parent 1)+ `e896c3899…`(`main` 的一个 tip)	`git rev-list --parents -n1`
两父的 merge-base	`a5b660f21005235b603b0f7f08476ae231b8a129`	`git merge-base` —— 与旧贡献 diff 的基准一致
文件集	11 个,前后完全相同	两侧 `--name-only` 排序后 `diff` 无输出
⭐ 冲突文件之外,分支自身的贡献逐字节相同	573 行 diff,两侧完全一致	`diff(a5b660f2..24b009d088)` 与 `diff(e896c3899..93c41f812)` 各自剥掉 `index` 行、排除 `zod-mirror-parity.test.ts` 后逐字节比

⇒ 「合并没有顺手带进任何别的改动」不是 dev 的自述,是本席这一支仪器的读数。

冲突解法:台账链的算术逐节闭合,两侧历史句子都还在

唯一的冲突 hunk 是 KnownDrift 表头那行。解出来的链条:

今天         46 条 / 83 键
← 46 / 84    直到 objectui#8572 退役 ChatbotSchema 的 body 记录臂(键 -1,条目不变)
← 45 / 83    直到 objectui#7804 的 TreeViewSchema 切片(新条目 +1,键 +1)
← 41 / 72    直到 objectui#7804 的 objectql.ts 切片(条目 +4,键 +11)

每一节的差都对得上。main 侧(objectui#9647)的那句 45 / 83 的历史原字保留,只是从「表头开头」重锚到一条 It was 链上;本分支的句子同样在。⇒ ⛔ 没有一侧的意思被悄悄丢掉。

⭐ 数字是推出来的,不是写的:dev 先把表头故意填成 99 / 97,让文件自己的棘轮报数 —— objectui#7733 的块回 expected 99 to deeply equal 46,objectui#8222 的块回 expected 97 to deeply equal 83。两支仪器各自点名了 46 和 83,然后才落笔。

⚠️ 门② 本来根本不可判 —— 而且原因是本席自己

--pair 9639 第一次读到的是 exit 4 / C2 无读数,⛔ 不是绿也不是红,是读不出来:本席昨天写的认领行,在声明的同一行里又把拼法引了一遍(为了说明「裁决自己写死了这一行」),于是那一行出现两次键名,判据按 markdown 结构读 ⇒ 它成了对协议的引用,不是声明。

按脚本给出的第四种动作(⛔ 不改认领、⛔ 不加第二条 Claim:)贴了一条专用更正评论(5710468879),复读 exit 0,两载体一致。

⚠️ 那段 remedy 文案里给的号是脚本自己源码里的例子(同一常量在 check-clause2-carriers.mjs 里出现三处),⛔ 不是本卡的认领号 —— 照抄它会指向一条不存在的评论,而脚本会带理由忽略整条更正。本席核过源码才落的号。⭐ 工具给的示例数字,和工具给的读数,是两种东西。

C6-RECORD 行缺席 = 机读确认「这个 head 上没有复核记录」

⇒ 5710188415 判的是 24b009d088,已被取代,⛔ 不继承。双载体继续原样挂着。

二审已起,同样是隔离的达档复核子代理,简报里写死了「老记录判的是已被取代的 head,⛔ 不许继承,要在新 head 上自己重推」,并把冲突解法点成本轮最该对抗性看的地方。

— PM domain:spec @ objectui · session session_01VCpmqvacV4BypY48QdoxcE · 2026-09-17T07:10Z

Generated by Claude Code

hotlong · 2026-09-17T07:25:40Z

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 93c41f812921b15322cb6ebdeda44df3d59ea1a6

① Derived judgments

Judged three-dot. git diff e896c3899 93c41f812 (head over the main it merged) and git diff a5b660f21 24b009d08 (the branch over its pre-merge base) are identical except for the KnownDrift header bullet hunk and hunk offsets: 11 files, +383/−87 both ways. The merge brought no lockfile, generated file or other test.

1. Conflict resolution — zod-mirror-parity.test.ts KnownDrift bullet — RIGHT. Mechanical check: the head bullet is byte-identical to the branch's #8572 sentence followed by main's #9647 TreeViewSchema sentence, with exactly four tokens changed: the two head figures (46 / 83) and the two chain anchors ("46 / 84 until", "It was 45 / 83 until"). Neither side's history prose was dropped. The chain closes link by link: 41/72 +4 entries/+11 keys (objectql slice) = 45/83; +1/+1 (TreeView slice) = 46/84; +0/−1 (this retirement, one key, no entry) = 46/83; chronological order is correct. The figures were stated by the file's own ratchets, not read: probing 46/83 with 99/97 failed the #7733 pin (Expected knownDrift 46, Received 99) and the #8222 pin (Expected knownDriftKeys 83, Received 97); probing the WiderThanDeclared line (19/29/36 and 5/24/0/7) with 98/96/95 and 8/90/1/9 failed the #8252 pin; probing the ratchet restatement "46 of the registered pairs" with 99 failed #7733 again. Baseline: 32/32 green; each probe: exactly the named pin red, file restored to its HEAD blob after each.

2. packages/types/src/zod/complex.zod.ts — ChatbotSchema.body record arm → retirementTombstone(…) — RIGHT (ruling A, letter for letter). Comment-stripped diff of the file is exactly that one member. Accept set NARROWED on the published mirror: root chatbot + record body ACCEPTED before → REFUSED now, invalid_type at path body, message names requestBody (re-taken from source through AnyComponentSchema.safeParse, the same object safeValidateSchema returns per index.zod.ts). Node-shaped and array body are refused too (option C is not built — correct). Controls on the same instrument: requestBody spelling ACCEPTED root and nested; neither key ACCEPTED root and nested (non-vacuity); nested record body REFUSED before and after; card + untyped child REFUSED (firing). Tombstone text points at requestBody as the ruling requires.

3. packages/types/src/complex.ts — body?: never on ChatbotSchema — RIGHT. Comment-stripped diff is exactly that one member; tsc on the package (main, examples and tests projects) exit 0 at head. Both faces now say the same thing. Ablation re-run on this head, anchored on ChatbotSchema by line (the first attempt by pattern hit CalendarViewSchema — same trap the PR body reports — and was discarded): deleting the member leaves vitest green (49/49) and turns the type-level LedgerMismatch ratchet red naming complex.zod.ts#ChatbotSchema. Restoring the record arm on the mirror (anchored on the unique #8572 guidance string; the four other body tombstones untouched) turns red: the inverted root pin, the strict-face case, the never type pin (TS2344) and the WIDER type ratchet naming complex.zod.ts#ChatbotSchema and body; the two re-pointed #9256 controls stay green, as the PR states. Baseline for both legs: 807/807 across the four touched test files, tsc exit 0.

4. node-recursion-point-8344.test.ts — two pins INVERTED, not deleted — RIGHT. Root case now asserts refusal with code and named replacement; ArmsNotAssignableToSchemaNode pin reads never with a tuple extends [never] guard. Measured: without the guard the pin is red (TS2344) and a probe Equal(bare projection, unknown) compiles green, so the bare spelling resolves to unknown exactly as the PR claims; the guard is load-bearing. Flipping the pin to 'chatbot' goes red (firing control).

5. zod-mirror-parity.test.ts ledgers — RIGHT. KnownDrift['complex.zod.ts#ChatbotSchema'] loses body, keeps onError | onSend, ruling recorded in the docblock. The ruling's word 「ruled」 cannot be executed as "keep the key": the ratchet fires on a listed key that has been fixed (proven by leg A/B above), so the key leaving with the ruling recorded is the only lawful reading. WiderThanDeclared entry and WIDER_ARMS row removed per that ledger's own clause 4 ("a key DISAPPEARED — correct or delete the entry"), with an in-place departure note in the ledger's established convention (precedent notes at the DashboardComponentSchema.title and ChartSchema.drillDown departures).

6. content-channel-family-d-9256.test.ts — two controls RE-POINTED to chatbot-enhanced — RIGHT. Re-taken: ChatbotEnhancedSchema accepts body as a content node, refuses a record body, refuses children; ChatbotFloatingSchema accepts body as content. The controls still assert what #9256 needed (its narrowing was children, body left alone) without restating this card's verdict. Whole file green.

7. strict-authoring-face-8345.test.ts — root legs INVERTED — RIGHT, with a declared consequence (see ③ flag 2).

8. packages/types/src/zod/base.zod.ts — comment only — RIGHT. Comment-stripped diff: 0 lines. The stale instruction citing this card as undecided is corrected.

9. .changeset/8344-… and .changeset/9256-… — prose amendments — RIGHT. Frontmatter byte-identical to main; only AMENDED paragraphs added. .changeset/7655-… left as written: its sentence about the twins re-measures true.

10. content/docs/plugins/plugin-chatbot.mdx — one table row — RIGHT. The row's delivery-surface claim re-verifies: packages/core/src/validation/schema-validator.ts imports no zod mirror, SchemaRenderer gates validation on __DEV__, objectui check imports safeValidateSchema.

11. Corpus impact — zero, re-taken. Structural walk of 518 JSON files under examples/content/packages/apps/docs: 3 chatbot-family nodes, all plain chatbot, body absent ×3, requestBody absent ×3, messages present ×3 (lit control); firing control on the same reader: 15 sidebar-menu-item nodes carry body. Docs mdx and README chatbot examples author no node-level body (the one body: hit is a fetch option inside onSend); no plugin-chatbot test authors it. Full packages/types suite at head: 198 files, 4656 tests, all green; CI at head: 36/36 check runs completed, none failed.

② Semver level

The change is BREAKING for a consumer that authored a record body on a chatbot node (refused where it was accepted, on both faces). Under this repo's version policy (AGENTS.md §版本号策略, enforced by scripts/check-changeset-no-major.mjs) major is forbidden and a breaking change ships as minor with the break spelled out. The changeset declares '@object-ui/types': minor with a BREAKING banner, FROM → TO mapping, one-line fix, and the ADR-0087 disposition line in the same spelling as the repo's precedent retirement changesets (8355, 8801, 9040). Deserved level under this policy: minor + BREAKING — declared correctly. Gates re-run locally at head: no-major, fixed-group, presence (7 published source files, 1 changeset), pending-changeset-literals — all exit 0.

③ Boundary flags

Declared by the PR body, each answered:

Render path does not deliver the refusal (core validateSchema, dev-only, no mirror) — confirmed by reading the code paths; correctly left to another package and card.
Surface extension beyond the ruling's four files (9256 controls, 8345 case, base.zod.ts comment, docs row) — each is reached by the ruling as a matter of necessity; verified nothing behavioural moved in base.zod.ts and the host cards' own assertions survive (files whole and green).
Deviation 1 (KnownDrift 「ruled」 = key leaves, ruling recorded) — right, see ①5.
Deviation 2 (WiderThanDeclared entry and WIDER_ARMS row go) — right, per that ledger's clause 4 and precedent.
Deviation 3 (empty-set guard on the type pin) — measured necessary, see ①4.
Whole-repo gate farm left to CI — CI at this head is fully green (36/36 completed, 0 failed).
Ablation run outside the heavy-verify lock — immaterial; both legs re-run here on this head with the same verdicts.

Not declared as boundaries by the PR body, found here — all NON-BLOCKING, to be filed as separate cards:

NON-BLOCKING — the prescribed remedy is refused by the strict authoring face. ChatbotSchema (the mirror) does not declare requestBody (UnmirroredDeclared carries displayMode | floatingConfig | requestBody for this pair); it is accepted on the tolerant face only through .passthrough(). Measured: StrictAnyComponentSchema.safeParse of a chatbot with requestBody → REFUSED unrecognized_keys; the same on chatbot-enhanced → ACCEPTED (control). The tombstone text now sends authors to a key the strict face rejects. Pre-existing ledger state, not introduced here, and the ruling itself names requestBody; but a card should mirror requestBody on ChatbotSchema (draining one UnmirroredDeclared key) so the remedy parses on both faces.
NON-BLOCKING — the superRefine clause in defineNodeComponentUnion is now dead code and its only live-instance test no longer discriminates it. The arm refuses every defined body, so the wrapper's chatbot branch can never run; the 8345 "live instance" leg passes with or without the clause (the PR states this honestly). The wrapper's installation is still pinned by the the fill is LIVE leg. A card should retire the clause (or re-anchor the recursion-point pin on a wrapper with a live check) rather than leave a redundant check in a published module.
NON-BLOCKING — CHANGELOG-bound prose inaccuracies in .changeset/8572-chatbot-body-retired.md. (a) "41 packages in one fixed group": .changeset/config.json lists 40 (the gate header and AGENTS.md say 39 — all three figures disagree with the config). (b) "Every tracked file carrying a chatbot node is in examples/schema-catalog/…": the docs page, the plugin README, ADR-0057 and several tests also carry chatbot nodes; the substantive claim (none authors body) holds under the wider census above, so only the sentence's scope is overstated.
NON-BLOCKING — no literal Clause-②: yes (narrowing) line in the changeset. The ruling names Clause-②: yes; the objectstack convention wants the line in the changeset body, but objectui has no gate reading it and the same-round precedent (8801) omits it too; the clause's substance — this contract review — is honoured.

Implemented-by: claude/issue-8572-chatbot-body-retire
Reviewed-by: session_01VCpmqvacV4BypY48QdoxcE

VERDICT: PASS

Generated by Claude Code

hotlong · 2026-09-17T07:28:01Z

清标 provenance —— 条款②双载体已剥(二审,新 head,PASS)

记录:5710643280 · 所判 head 93c41f812921b15322cb6ebdeda44df3d59ea1a6 · VERDICT: PASS · 本席逐字转贴,⛔ 未改一字。清标于 2026-09-17T07:28Z。

这张卡走的路

轮次	head	裁决	处置
一审	`24b009d088`	PASS	⛔ 没有清标 —— 同时读到 PR 对 `main` 是 dirty,而合 `main` 必然移动 head、必然作废这条记录。剥标等于在一个马上失效的 head 上宣告清关
合并轮	→ `93c41f812`	—	merge commit,⛔ 无 rebase;冲突只有台账表头一处,数字由文件自己的棘轮推出
二审	`93c41f812`	PASS	本次清标

⭐ 一审那次「PASS 了却不清标」是本班学到的一条:清标即落地,落不了地就不能清标。

档位:本席独立量的,来自转录 ⛔ 不是自述

二审转录 · type:"assistant" 的 message.model
→ claude-fable-5-1 ×85  (85/85,无杂值,2026-09-17T07:07:53Z – 2026-09-17T07:24:26Z)

同题发火对照,同一小时内并排跑的两个子代理:合并轮的 dev 读 claude-opus-5 ×160(2026-09-17T06:46:13Z – 2026-09-17T07:05:56Z),二审复核件读 claude-fable-5-1 ×85。分界与派发所传 model 完全重合 ⇒ 仪器能分辨,且这次对照是同场的,不靠回溯历史扫描。

⚠️ 一审(95/95 fable)与二审是两个独立复核件,⛔ 二审没有被喂一审的记录:它的简报写死了「那条记录判的是已被取代的 head,⛔ 不许继承」。它在交回时自述从未遇到过那条记录。

落地前检三条

闸门	读数
① 席内条款②复核 PASS 在案	记录 `5710643280`,同形、`Served-tier:` 写常量名、head 独占码段
② 双载体已清 + 机读	剥标后取的落地读数:`--pair 9639` exit 0,且 C6-RECORD 行点名了这条记录与这个 head(⚠️ 剥标前同样 exit 0 —— 但那次输出里 C6-RECORD 行缺席,那是「这个 head 上还没有记录」的机读确认)
③ 全部 check	head 上 36 个:33 success / 3 skipped / 0 非绿 / 0 在跑。⚠️ 读的是 `/commits/<sha>/check-runs`,⛔ 不是 `check_suite.completed` 事件(它自己的小字排除 cancelled)

受管面:check-governed-merges.mjs --test 对 GitHub 自己给的 11 个路径(三点语义,/pulls/9639/files)→ 0 of 11,NOT governed ⇒ 走普通队列落地。
⚠️ --pr 9639 这条腿在本容器里答不了:脚本按自己检出的 origin 解仓,于是去 objectstack 找 #9639 并 404。它拒绝回退到两点差并说明了理由(两点差会把 main 自己的新文件算进来)—— ⭐ 一个拒答比一个错答好,这正是本班记的那三种跨仓行为里「响亮拒绝」的那一种。

复核件点名的 4 条非阻断残留

⇒ 已补进 objectui#9659(评论 5710660358),其中最实的一条:碑文让作者改写的 requestBody,被严格授权面拒收(StrictAnyComponentSchema 回 unrecognized_keys,而 chatbot-enhanced 对照 ACCEPTED)。⛔ 不是本 PR 引入的,⛔ 不改变 PASS。

⚠️ #9659 的串行约束因此又紧了:它的四条里有三条落在本 PR 动过的文件上 ⇒ ⛔ 本 PR 落地前不要派它。

— PM domain:spec @ objectui · session session_01VCpmqvacV4BypY48QdoxcE · 2026-09-17T07:28Z

Generated by Claude Code

…g SelectOptionSchema (objectstack-ai#7759 group F) (objectstack-ai#10307) Closes objectstack-ai#10296 Part of objectstack-ai#7759 Clause-②: yes ## What this does `views.zod.ts#DetailViewFieldSchema.options` now reads the spec's AUTHORING `SelectOptionSchema` (`@objectstack/spec/data`) by reference, wrapped in `stripImportedDefaults` like every other crossing. That follows ruling F1 on objectui#7759 (5617221514, adopted in 5617465269): a structural mirror points at the spec's authoring schema, ⛔ never at the declaration's runtime read model (`SelectOptionMetadata`). The TypeScript declaration is unchanged. Before: an inline option shape. It admitted a number or boolean `value`, which the declaration refuses, and silently stripped every other key. After: the spec's strict schema. `value` must be a machine identifier. `icon` and `disabled` are refused by name (`unrecognized_keys`). `description`, `default` and `visibleWhen` are accepted as the spec declares them. ## Re-derived population (origin/main `8b1f06619`, `WIDER_ARMS`, CONCRETE rows only) Sibling branches were fetched into private refs, and each row was checked for whether it disappears there. | row | group | owner | this PR | | --- | --- | --- | --- | | `DashboardComponentSchema::header` / `::globalFilters` | D | objectstack-ai#2231, twin region PR objectui#10273 | excluded | | `DashboardComponentSchema::dateRange` | F | inside the excluded `DashboardComponentSchema` region (PR objectui#10273) | STOP, reported | | `FilterBuilderSchema::fields`, `FilterFieldSchema::operators`, `ContainerSchema::maxWidth`, `HeaderBarSchema::variant` | C/D | objectui#10286 (all four gone on its branch) | excluded | | `FormSchema::mode` | D | objectui#10286 region | excluded | | `FormSchema::layout` | C | renderer feature | excluded | | `CalendarSchema::defaultValue` / `::value` | D | objectui#10293 (gone on its branch) | excluded | | `SliderSchema::defaultValue` / `::value`, `TooltipSchema::content` | B | PR objectui#10292 (gone on its branch) | excluded | | `DataTableSchema::columns` / `::renderCellEditor`, `TableColumnSchema::cell`, `FieldConditionSchema::custom`, `FieldConstraintsSchema::validate`, `FormFieldSchema::condition` / `::validation`, `FormSchema::fields` | E (+F, D) | PR objectui#10294 (all gone on its branch) | excluded | | `HeaderBarSchema::logo` | F | inside the excluded `HeaderBar` region; still present on the objectui#10286 branch | STOP, reported | | `DetailViewFieldSchema::options` | F | this card | **settled per F1** | `ChatbotSchema.body` is already settled on `main`. objectui#8572 (PR objectstack-ai#9639) retired it on both faces as a `?: never` tombstone, and the row left the ledger. Nothing is left to do for it here. ## The ledger reading: an expected divergence, not a zero After the mirror points at the authoring schema, the two faces differ on exactly one member: `visibleWhen`. The spec's input envelope requires `dialect`. The read model's wire (objectui#2212) makes `dialect` optional and `source` required. Measured with `tsc`, this is the only incompatibility. `label`, `value` and the whole-object check agree otherwise. - ⛔ I did not override `visibleWhen` locally to reach a zero-row ledger. That would narrow and widen a spec-declared shape inside objectui, which the ordering note 5617614225 forbids. - The row stays in `WiderThanDeclared` and `WIDER_ARMS`, re-annotated as EXPECTED DIVERGENCE (read model). The old reason, the inline shape, is gone. - `KnownDrift` gains `DetailViewFieldSchema: 'options'`. The same cause is measured one level up, so it also gains `DetailViewSectionSchema: 'fields'` (new entry), and `DetailViewSchema` gains `fields` and `sections`. The header figures were re-derived to 48 entries / 89 keys. The restated figure under "KNOWN_DRIFT is a ratchet" was updated too. - `SPEC_DERIVED_PAIRS` gains `views.zod.ts#DetailViewFieldSchema`, because the census test derived it from the source. ## Evidence (HEAD `a8446a2ae`) - `pnpm --filter @object-ui/types type-check` (all three tsconfigs): exit 0. `pnpm exec vitest run packages/types/` gave `Test Files 215 passed (215)` and `Tests 4929 passed (4929)`. These ran under the verify lock, on bytes identical to the commit. - New pin `packages/types/src/__tests__/detail-view-field-options-10296.test.ts`: 6 tests. It asserts `code` and `path` for each refusal, next to an accepting control, plus verdict parity with the spec schema. - Reverse verification (committed first, trap-guarded): I restored the mirror file from the base commit. The inline marker count was 1 and the spec-reference count was 0. Results: the pin gave `5 failed | 1 passed (6)` (the accepting control stays green), and `tsc -p tsconfig.test.json` failed with exit 2 on `LedgerMismatch` naming `views.zod.ts#DetailViewFieldSchema`. After `git checkout HEAD -- FILE`: `git diff HEAD` was 0 bytes and the blob hash matched HEAD. - Downstream: built the closure of `@object-ui/plugin-detail` (turbo, 11 tasks). `pnpm --filter @object-ui/plugin-detail type-check` exit 0. Its two tests that import the zod `DetailViewSchema` / `DetailViewSectionSchema` passed: `2 passed`, `21 passed`. - eslint `--no-inline-config` on the 3 changed source files: `--format json` gave 3 files, 0 errors, and 2 warnings on lines this diff does not touch. Type-aware linting is not configured, so the diff cannot move any verdict on an untouched file. - `check-changeset-presence`, `check:spec-symbols`, `check:new-line-citations` (0 new), `check:control-bytes`, `check-changeset-no-major`, `check:changeset-claims`, `check:pending-changeset-literals`, `check:installed-pin-claims`: all exit 0. - `check:spec-floors`: NOT MEASURED. It needs a whole-workspace build (`no-artifact`), so it is left to CI. ## Acceptance notes - `DashboardComponentSchema::dateRange`: STOP, because it sits in PR objectui#10273's excluded region. For whoever takes it: `@objectstack/spec` 17.4.0 exports `DATE_RANGE_DEFAULT_RANGES` / `DateRangeDefaultRange` from `@objectstack/spec/ui`, so rule 1 likely applies (the mirror takes the spec's vocabulary). That is not measured here. - `HeaderBarSchema::logo`: STOP, because it sits in objectui#10286's `HeaderBar` region. Proposal F routed it to ADR-0049 enforce-or-remove together with `variant`. - A reviewer can reopen the choice between recording `visibleWhen` as an expected divergence (this PR) and overriding it with objectui's wire, which would give a zero-row ledger but a local reshaping of a spec-declared key. The session is `https://claude.ai/code/session_01877XiBYSaRCk2CU7cMSg3S` (PM seat `domain:spec#1`, dispatched dev). --- _Generated by [Claude Code](https://claude.ai/code/session_01877XiBYSaRCk2CU7cMSg3S)_ --------- Co-authored-by: Claude <noreply@anthropic.com>

hotlong added the needs:contract-review label Sep 16, 2026 — with Claude

github-actions Bot added package: types tests labels Sep 16, 2026

hotlong mentioned this pull request Sep 16, 2026

ChatbotSchema.body accepts more than the declared contract #8572

Closed

hotlong mentioned this pull request Sep 17, 2026

objectui#9639 post-PASS residuals (4): a #8344 superRefine clause dead at runtime while a pin asserts its shape, a vacuous refusal leg, a narrowing row that lost its same-face control, and the render path that skips the root parse #9659

Closed

hotlong removed the needs:contract-review label Sep 17, 2026

hotlong marked this pull request as ready for review September 17, 2026 07:28

hotlong added this pull request to the merge queue Sep 17, 2026

Merged via the queue into main with commit c42554e Sep 17, 2026
38 checks passed

hotlong deleted the claude/issue-8572-chatbot-body-retire branch September 17, 2026 07:49

Navigation Menu

Repository navigation

feat(types)!: retire ChatbotSchema.body on both published faces (objectui#8572) - #9639

feat(types)!: retire ChatbotSchema.body on both published faces (objectui#8572)#9639
hotlong merged 3 commits into
mainfrom
claude/issue-8572-chatbot-body-retire

hotlong commented Sep 16, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 16, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Sep 16, 2026

Uh oh!

github-actions Bot commented Sep 16, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

github-actions Bot commented Sep 17, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

hotlong commented Sep 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What landed, file by file

⭐ The ruling's last sentence, answered with measurements

The readings, with their controls

Re-taken reachability (the card's own table, re-measured on this branch — ⛔ not cited from the card)

Corpus impact: zero documents

Pin inventory — what moved, and in which direction

Ablation — both halves proven load-bearing, from the committed state

Local verification

Surface extension — granted, reasoned, and bounded

The host cards' own claims survive — checked suite by suite

The changeset-claim-re-read answer

Deviations from the ruling's literal wording, declared

维护者速读

Uh oh!

github-actions Bot commented Sep 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ 30 pending changeset(s) describe a file this change touches

.changeset/5905-componentinput-inputtype-tombstone.md

.changeset/5905-componentinput-retire-constraint-keys.md

.changeset/5928-classname-style-props-rename.md

.changeset/6150-undeclared-but-consumed-keys.md

.changeset/6169-chatbot-authoring-face-type.md

.changeset/6175-column-state-persistence.md

.changeset/6639-objectgrid-title-mirrored.md

.changeset/6687-chatbot-surface-authorable.md

.changeset/6939-kanban-column-cards.md

.changeset/7087-disabled-twin-symmetry.md

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

.changeset/7295-chat-message-avatar-keys.md

.changeset/7344-handler-string-any-mirrors.md

.changeset/7493-componentinput-retire-label-defaultvalue-advanced.md

.changeset/7530-predicate-envelope-declared.md

.changeset/7654-floating-chatbot-trigger-icon-tombstone.md

.changeset/7655-chatbot-registration-authoring-faces.md

.changeset/7703-chatbot-dark-keys-retired.md

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

.changeset/7918-zod-lazy-getter-identity.md

.changeset/8338-retire-toast-action.md

.changeset/8415-filter-builder-condition-id.md

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

.changeset/8478-zod-pins-complex.md

.changeset/8478-zod-pins-form-layout.md

.changeset/8802-8257-8008-kanban-gantt-family-retirement.md

.changeset/9162-node-slot-guard-class-closure.md

.changeset/calendar-readme-schema-keys-5045.md

.changeset/component-meta-converge-and-deprecate-alias-5893.md

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

Uh oh!

github-actions Bot commented Sep 16, 2026

✅ Console Performance Budget

📦 Bundle Size Report

Size Limits

Uh oh!

github-actions Bot commented Sep 16, 2026

✅ Console Performance Budget

📦 Bundle Size Report

Size Limits

Uh oh!

hotlong commented Sep 17, 2026

Contract review

① Derived judgments

② Semver level

③ Boundary flags

Uh oh!

hotlong commented Sep 17, 2026

席位记录 —— 达档复核 PASS 已逐字采纳;⛔ 但本轮不清标,理由在下面

档位:本席独立量的,来自转录 ⛔ 不是自述

⛔ 为什么 PASS 了还不剥双载体

已派:合并轮,⛔ 不是补丁轮

复核件点名的 4 条非阻断残留 ⇒ 另行立卡

Uh oh!

hotlong commented Sep 17, 2026

Uh oh!

github-actions Bot commented Sep 17, 2026

✅ Console Performance Budget

📦 Bundle Size Report

Size Limits

hotlong commented Sep 16, 2026 •

edited

Loading

The `changeset-claim-re-read` answer

github-actions Bot commented Sep 16, 2026 •

edited

Loading

`.changeset/5905-componentinput-inputtype-tombstone.md`

`.changeset/5905-componentinput-retire-constraint-keys.md`

`.changeset/5928-classname-style-props-rename.md`

`.changeset/6150-undeclared-but-consumed-keys.md`

`.changeset/6169-chatbot-authoring-face-type.md`

`.changeset/6175-column-state-persistence.md`

`.changeset/6639-objectgrid-title-mirrored.md`

`.changeset/6687-chatbot-surface-authorable.md`

`.changeset/6939-kanban-column-cards.md`

`.changeset/7087-disabled-twin-symmetry.md`

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

`.changeset/7295-chat-message-avatar-keys.md`

`.changeset/7344-handler-string-any-mirrors.md`

`.changeset/7493-componentinput-retire-label-defaultvalue-advanced.md`

`.changeset/7530-predicate-envelope-declared.md`

`.changeset/7654-floating-chatbot-trigger-icon-tombstone.md`

`.changeset/7655-chatbot-registration-authoring-faces.md`

`.changeset/7703-chatbot-dark-keys-retired.md`

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

`.changeset/7918-zod-lazy-getter-identity.md`

`.changeset/8338-retire-toast-action.md`

`.changeset/8415-filter-builder-condition-id.md`

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

`.changeset/8478-zod-pins-complex.md`

`.changeset/8478-zod-pins-form-layout.md`

`.changeset/8802-8257-8008-kanban-gantt-family-retirement.md`

`.changeset/9162-node-slot-guard-class-closure.md`

`.changeset/calendar-readme-schema-keys-5045.md`

`.changeset/component-meta-converge-and-deprecate-alias-5893.md`

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

合并轮已落 —— 新 head `93c41f812921b15322cb6ebdeda44df3d59ea1a6`;⛔ 老复核记录随之作废,二审在飞