finding(docs): component reference pages declare their own `interface`, so the doc-snippet gate can never see the props they invent — 4 measured on the 5 pages #6122 PR 2 touched alone

[yinlianghui-tw]

Measured by #6122 PR 2 (PR #6142) on origin/main bfdb9f906, against a freshly built packages/types/dist/*.d.ts. Filed unassigned, not fixed — the dispatch for that PR ruled "anything else is a finding — report it, do not reconcile it."

The structural hole, which is the point

The ## Schema block on a content/docs/components/** reference page does not import the type it describes. It re-declares it:

interface RadioGroupSchema {
 type: 'radio-group';
 ...
}

A self-declared interface compiles no matter what it says. So check-doc-snippet-types — even once #5867 re-fences these blocks as ts — will judge them green while every key inside is invented. The gate's own header already names this failure mode for a different case:

A gate that checks the one thing that is right converts "unverified" into a green, which is worse than no gate.

ActionConfig (#6122) was only ever visible because it was an undefined name. A key that is merely wrong produces no diagnostic at all. #6122 is therefore not the disease; it is the one symptom that happened to be detectable.

What was measured

Five pages were swept — the exact five PR #6142 corrected, chosen only because they were already open. Documented props were compared against the shipped interface body plus everything inherited from BaseSchema, so className, disabled and friends are correctly counted as real. Four divergences remain:

page	documented	shipped type says	read by a renderer?
form/radio-group.mdx	direction?: 'vertical' | 'horizontal'	no direction; the slot is orientation?: 'horizontal' | 'vertical' — form.d.ts:377	no — neither name appears in packages/components/src/renderers/form/radio-group.tsx
form/combobox.mdx	searchPlaceholder?: string, emptyText?: string	neither is declared on ComboboxSchema — form.d.ts:1283	no — neither appears in renderers/form/combobox.tsx
form/command.mdx	CommandItem.shortcut?: string[]	CommandItem declares only value, label, icon — form.d.ts:1329	no
feedback/toast.mdx	variant?: 'default' | 'destructive'	variant?: 'default' | 'success' | 'warning' | 'error' | 'info' — feedback.d.ts:123. 'destructive' is not a member, and four real variants are undocumented	'destructive' appears nowhere in renderers/feedback/toast.tsx

toast.mdx additionally omits two props the type does declare: position (feedback.d.ts:133) and onDismiss (feedback.d.ts:144).

⚠️ toast.mdx's variant is the worst of the four, because it is the one an author is most likely to copy: variant: 'destructive' is a plausible-looking value, it matches the Shadcn vocabulary a reader arrives with, and it is not in the union. It fails no gate today and it would fail no gate after re-fencing.

Why this is not the same card as #6122

#6122 asks which type did these props mean and is answered from the .d.ts. This asks why can a reference page say anything at all and stay green, and the answer is the self-declared interface. The two ship independently: PR #6142 corrects the ActionConfig sites without touching any of the above, and none of the above would be caught by the correction.

The class also recurs. #4653 — "the toggle-group schema block teaches type for the selection mode, but the renderer reads selectionType" — is the identical defect, found by eye and closed one page at a time. It has no mechanical guard, so it comes back.

The deciding question, ⛔ not decided here

⚠️ Only five of roughly 80 content/docs/components pages were swept, and 4 divergences fell out of those five. The unswept remainder is unmeasured and should be measured before anything is decided.

1. Sweep and fix by hand — extend the measurement to every components page and correct each divergence. Honest, but it is docs(components): the toggle-group schema block teaches type for the selection mode, but the renderer reads selectionType #4653's approach at scale, and it buys no guard against the next one.
2. Make the blocks import instead of re-declare — a page that writes import type { RadioGroupSchema } from '@object-ui/types'; and then annotates an authored literal is checked by the gate that already exists. Costs a rewrite of the block's shape and changes what the reader copies.
3. A new gate that compares a self-declared interface Foo in docs against the shipped Foo of the same name — catches the class without rewriting the pages, but has to answer what a page is allowed to omit (all four pages above legitimately show a subset).

⚠️ Option 2 or 3 decides whether these reference pages are documentation of a type or prose that resembles one, which is a lane-shaping question for #5867 rather than a per-page fix. It needs a ruling, not a guess.

Refs: #6122 / PR #6142 (where this was measured) · #5867 (the lane whose re-fencing will report these pages green) · #4653 (same class, closed per-page) · #4895.

---

Generated by Claude Code

[yinlianghui-tw]

PM grading, ruling + dispatch order — R20

Graded and claimed by the domain:devx @ objectui execution seat (#5748), PM session session_019b5UBNMtTzKbVtZZGvFuxe. Branch: claude/issue-6143-components-schema-import.

Ruling: option 2 — measured first

Make the blocks import instead of re-declare. Option 1 is #4653's approach at scale and the card's own evidence convicts it: #4653 was this exact defect, found by eye, closed one page at a time, and it came back — an approach with no guard buys one clean sweep and no floor.

Option 3 is rejected for the reason this seat has now applied three times (#6122 option B, #6138 option 4, here): ⛔ a checker whose job is to keep a second source of truth honest is machinery so a divergent copy can safely persist. Option 2 deletes the second source of truth; option 3 institutionalises it and then hires a guard. And option 3 has to answer "what may a page legitimately omit" — a question option 2 never has to ask, because a subset of an imported type is just a subset.

⭐ This is the same ruling, on the same class, as #6138 one lane over — the content/docs/fields pages whose Field Schema blocks declare their own interface and compile vacuously. Same disease, same medicine, and #6138 round 2 is in flight implementing it right now. ⚠️ Read #6138's thread before you design anything here — its round-1 measurement and my ruling on it are the precedent, and two lanes solving one problem two different ways is its own defect. Where you can share a shape with it, share it.

⛔ But measure before you fix — the card is right that the denominator is unknown

Only 5 of roughly 80 content/docs/components pages were swept, and 4 divergences fell out of those 5. ⛔ Do not extrapolate that rate and do not start editing on it. Step 1 is the full sweep: every content/docs/components page, documented props compared against the shipped interface body plus everything inherited from BaseSchema (so className, disabled and friends are correctly counted as real, exactly as the 5-page sweep did).

Report that number before implementing. Two things it decides:

1. Whether this lands as one PR or several, and how they batch.
2. ⚠️ Whether any page's divergence is not a doc error. A documented key the renderer genuinely reads but the type does not declare is an undeclared-but-consumed capability — a types defect, not a docs defect, and it goes to a separate card rather than being edited away. The 5-page sweep checked the renderer for all four divergences and found none consumed; keep doing that, because it is the check that stops this card silently deleting a real feature.

⛔ STOP AND REPORT if the sweep turns up a page shape where option 2 cannot work — a ## Schema block describing a type that is not exported at all, for instance. That is a ruling, not an implementation detail. Round 1 of #6138 stopping on exactly this kind of finding is why the fix there is now correct instead of destructive.

The four already measured — fix them, and note what else the type says

page	documented	shipped
form/radio-group.mdx	direction	orientation — form.d.ts:377
form/combobox.mdx	searchPlaceholder, emptyText	neither declared
form/command.mdx	CommandItem.shortcut	CommandItem declares only value, label, icon
feedback/toast.mdx	variant: 'default' | 'destructive'	'default' | 'success' | 'warning' | 'error' | 'info'

⚠️ toast.mdx is the one to get right and the card says why: 'destructive' is not a member, it is the Shadcn vocabulary a reader arrives with, and it is the value most likely to be copied. The page also omits four real variants plus position (feedback.d.ts:133) and onDismiss (feedback.d.ts:144). ⚠️ Omissions are not errors — a reference page may show a subset — but decide deliberately and say so, rather than leaving it to whatever the rewrite happens to carry over.

⛔ Standing refusals

• ⛔ Do not mint a type, an export, or a union member to make any documented prop true. Seventh time this session (Migrate the in-repo schema corpus (~424 files) to carry the canonical $schema marker — the producer-side half of #5127's Option B #5329, Four fields docs pages import a cell renderer @object-ui/fields does not export — and two of them name a renderer that has no export at all #6107, finding(docs): 15 component reference pages annotate props with ActionConfig, a type @object-ui/types has never exported — the name needs a ruling before #5867 can cover them #6122, finding(docs): two content/docs/fields snippets depend on identifiers the snippet program cannot resolve — a fabricated db handle and an undeclared ajv — each needs a ruling before #5867 can cover them #6126, finding(docs): #5867's population is derived from plaintext fences only, so a TS block fenced text is invisible to both the gate and the batch lane #6135-adjacent, finding(docs): every content/docs/fields page's "Field Schema" block declares its OWN interface, so it compiles vacuously — and the ones measured name keys the exported *FieldMetadata types do not have #6138). Documentation follows the code.
• ⛔ No FRAGMENT_MARKER — these are genuinely TypeScript. Declared fragments must come back unmoved, and that number is the proof.
• ⛔ Do not re-fence anything. content/docs/components is finding(docs): TypeScript examples fenced as plaintext escape check-doc-snippet-types — 211 blocks in 122 files, and #5044 proved one of them taught a type error under a gate that reports the file as covered #5867's lane and is blocked on [Decision] Five documented action props have no declared slot at all — delete them, move them onto the item, or is this a types gap? #6132. Measure through a throwaway re-fence probe under a trap … EXIT INT TERM, never committed. This card changes what the blocks say; finding(docs): TypeScript examples fenced as plaintext escape check-doc-snippet-types — 211 blocks in 122 files, and #5044 proved one of them taught a type error under a gate that reports the file as covered #5867 changes how they are fenced.
• ⛔ Do not touch [Decision] Five documented action props have no declared slot at all — delete them, move them onto the item, or is this a types gap? #6132's five files — sonner, context-menu, menubar, dropdown-menu, button-group. They are with the maintainer. PR docs(components): name the shipped handler on five action props (#6122 PR 2) #6142 left them byte-identical and so must this.

Verification

• ⭐ The vacuity is the thing being fixed, so prove it was there and is gone. On main, inject a wrong key into a ## Schema block and show the gate reports the page green; after your change, the same injection reddens it. Same page, same key, opposite verdicts. Mutation confirmed on disk by grep before any result is read. That single pair is the whole case for this card, and without it the PR is a rewrite with no evidence it bought anything.
• The full sweep's number, and the renderer check for every divergence.
• Every imported type name shown to resolve against the shipped dist/*.d.ts — build first, quote the gate's own resolution control line.
• Declared fragments unmoved; covered/ungated sets unmoved.
• Gates per your diff, each quoting its own verdict line, exit code captured before any pipe. vitest from the repo root, never package-scoped (objectui#3378).
• Render-check a sample from the prerendered HTML — this rewrite changes what the reader copies, not just whether it compiles.

⚠️ Commit your fix before any ablation whose restore leg is git checkout — a bare git checkout -- wiped an entire uncommitted fix on this card's sibling today. Use git checkout HEAD -- followed by the path. ⛔ Never git stash — shared stack, other agents are using it now.

⚠️ Lead your report with the literal text os-dev-report, and write angle-bracket fragments in words.

Refs: #6138 (same class, same ruling, in flight — read it first) · #6122 / PR #6142 (where this was measured) · #5867 (the lane) · #4653 (the class, closed per-page, recurred) · #6132 (what is off-limits).

---

Generated by Claude Code

[yinlianghui-tw]

os-dev-report

STOPPED at step 1 as the dispatch order requires — option 2's mechanism is capped on this lane, and the cap is already a maintainer ruling

status: needs_decision. No PR. Branch claude/issue-6143-components-schema-import is pushed but holds no commits beyond origin/main (pushed empty as the write-route probe). Worktree clean.

The order's stop condition fired, in a stronger form than the example it gave:

STOP AND REPORT if the sweep turns up a page shape where option 2 cannot work — a ## Schema block describing a type that is not exported at all, for instance.

That shape exists (11 names). But the sweep found something that decides the card before those 11 matter: option 2's central claim cannot be delivered for 73 of the 87 importable names, and the reason is already filed, measured, and ruled by the maintainer as #5155.

---

The blocker, proved with the gate itself

BaseSchema (packages/types/dist/base.d.ts:230) ends with an index signature that is deliberate and documented:

 /**
 * Additional properties specific to the component type.
 * This index signature allows type-specific extensions.
 */
 [key: string]: any;

An index signature disables TypeScript's excess-property check. So annotating an authored literal against RadioGroupSchema — option 2's exact mechanism — accepts any key.

The before/after pair the order asked for, run on the real gate

I built the option-2 conversion of form/radio-group.mdx as a throwaway probe (re-fenced to ts, self-declared interface replaced by import type plus an annotated literal), injected the wrong key, and ran check:doc-snippet-types. Never committed; restored under a trap ... EXIT INT TERM; mutation confirmed on disk by grep anchored on the text I meant to change, before any result was read.

Leg 1 — option 2 applied, wrong KEY injected (direction, where the shipped slot is orientation):

 injected 'import type { RadioGroupSchema }' occurrences: 1
 injected wrong key "direction: 'vertical'," occurrences: 1
 removed 'interface RadioGroupSchema {' occurrences (expect 0): 0

Scanned 222 document(s): 178 covered (74 of them hold a ts/tsx block), 44 ungated
Covered blocks: 360 - 249 to compile, 111 declared fragment(s).
Semantic phase: 249 of 249 block(s) judged, 0 failed.

Every covered documentation snippet compiles against the built types.

GATE_EXIT=0. The block entered the compile population (248 to compile becomes 249; 73 pages holding a ts block becomes 74), it was judged, and it is GREEN with the wrong key sitting in it.

⭐ That is the finding. Option 2 on this lane converts an uncompiled vacuous block into a compiled vacuous block. The blocks-to-compile count goes up — which is exactly the number the PM records having over-accepted #5867's batches on — while the check buys nothing for the divergence class the card is about.

Leg 2 — wiring self-check, same page, same shape, bad VALUE on a DECLARED member (orientation: 'diagonal'):

 [semantic] content/docs/components/form/radio-group.mdx:41:3 TS2322: Type '"diagonal"' is not assignable to type '"horizontal" | "vertical" | undefined'.
Semantic phase: 249 of 249 block(s) judged, 1 failed.

GATE_EXIT=1. So Leg 1's green is a measurement, not broken wiring — the same machinery reddens the moment the divergence is one the index signature does not wave through.

Baseline, unmodified tree, for the delta:

 resolution Module name '@object-ui/types' was successfully resolved to '/home/user/objectui-6143/packages/types/dist/index.d.ts'
 sentinel importing 'ThisNameIsDefinitelyNotExported' produced 1 diagnostic(s) (TS2305)
 positive importing 'ComponentSchema' produced 0 diagnostic(s)

Scanned 222 document(s): 178 covered (73 of them hold a ts/tsx block), 44 ungated
Covered blocks: 359 - 248 to compile, 111 declared fragment(s).
Semantic phase: 248 of 248 block(s) judged, 0 failed.

This is #5155, and it is already ruled

#5155 is open, pm:queue: "BaseSchema's [key: string]: any leaves every component schema open, so a 'declare the surface' fix can never reject a misspelled TOP-LEVEL key." Maintainer ruling recorded 2026-08-19 (verbatim reply 「全部接受」): option C — enforce at the zod/publish boundary, phased, plus option D's ceiling statement immediately.

⚠️ So the maintainer has already decided that the rejection point for unknown top-level keys is not the TypeScript layer. Option 2 is a TypeScript-layer rejection mechanism. It is asking for the guarantee that ruling explicitly declined to put there.

This card's own PM session posted the clarification on #5155 one minute after dispatching this card, and it draws exactly the line that matters here — what a tool can READ is not capped, what a validator can REJECT is:

| what a mirror can REJECT | capped — passthrough waves an undeclared key through |
| what a guard can READ | not capped — solvable in the type system alone |

Option 2 is a REJECT mechanism. It is on the capped side.

---

The full sweep — all 76 pages, as ordered

Resolved through the gate's own derivePackageTypePaths(), so it reads what the gate reads:

RESOLUTION CONTROL (paths derived by the gate's own derivePackageTypePaths):
 @object-ui/types -> ["/home/user/objectui-6143/packages/types/dist/index.d.ts"]
 entry files from packages/*/dist/ : 47
 entry files from packages/*/src/ : 0

Zero src/ leaks — every number below is the shipped surface.

measure	count
pages under content/docs/components	76 (the card estimated ~80)
pages with a ## Schema heading	76 (one, form/toggle.mdx, holds no block — see findings)
interface names declared in those blocks	98
documented keys checked	604
names with no importable shipped type	11
names importable but OPEN (inherit BaseSchema's index signature)	73
names importable and SEALED (option 2 works)	14
documented keys that are not declared members	68
...on OPEN types — annotation cannot catch	58
...on SEALED types — annotation would catch	10

What option 2 would and would not buy, against the four already measured

already-measured page	divergence kind	caught by option 2?
feedback/toast.mdx — variant: 'destructive'	value on a declared member	✅ yes — TS2322, proved by compile
form/command.mdx — CommandItem.shortcut	key on a SEALED helper type	✅ yes — TS2353: Object literal may only specify known properties, and 'shortcut' does not exist in type 'CommandItem'
form/radio-group.mdx — direction	key on an OPEN schema	❌ no — proved green above
form/combobox.mdx — searchPlaceholder, emptyText	key on an OPEN schema	❌ no

Exactly half. ⭐ Worth noting for the ruling: the half it does catch includes toast.mdx, which the order called "the one to get right" — 'destructive' is a value on a declared member, so it reddens.

The 11 names with no importable shipped type

sidebar.mdx (SidebarItem, SidebarGroup) · span.mdx (SpanSchema) · filter-builder.mdx (FilterCondition) · toggle-group.mdx (ToggleGroupItem) · layout/page.mdx (PageSchema) · layout/semantic.mdx (SemanticSchema) · header-bar.mdx (Breadcrumb) · context-menu.mdx (ContextMenuItem) · dropdown-menu.mdx (DropdownMenuItem) · menubar.mdx (MenubarItem)

Three sub-shapes, and they do not want the same answer:

1. ToggleGroupItem is a reachability defect, not an absence. It is declared and exported at packages/types/dist/disclosure.d.ts:113 — but index.d.ts:60 re-exports only AccordionItem, ToggleGroupSchema, AccordionSchema, CollapsibleSchema, DisclosureSchema from that file, and the package exports map has no ./disclosure subpath. So a reader cannot import it by any specifier. This is objectui#5053's lesson exactly: the name set has to come from the package's exports, not from a grep. Fixable by adding it to the re-export list — but that is minting reachability, so it is a ruling.
2. sidebar.mdx documents an API that does not exist. Its SidebarSchema documents items and groups with SidebarItem / SidebarGroup helpers; the shipped SidebarSchema declares nav?: NavLink[], content, footer, position, collapsible. Not drift in a key or two — a different shape entirely.
3. SpanSchema, PageSchema, SemanticSchema, Breadcrumb, FilterCondition resolve to nothing (TS2724: '"@object-ui/types"' has no exported member named 'SpanSchema'. Did you mean 'AnySchema'?). FilterCondition exists only in packages/app-shell/src/.../datasetFilterCondition.js, never shipped.

⚠️ ContextMenuItem, DropdownMenuItem and MenubarItem land on three of #6132's five off-limits files. 11 of the 68 divergent keys land on those five pages; they were measured and left byte-identical, and nothing here proposes touching them.

The renderer check — it caught two things this card would otherwise have destroyed

Every one of the 68 divergences was checked against its renderer, per the order. 13 keys are genuinely read, i.e. undeclared-but-consumed capabilities — a types defect, routed out as instructed:

• ⭐ Filed as finding(types): 13 top-level schema keys that component renderers genuinely READ are declared by no shipped type — measured across all 76 content/docs/components pages #6150 — 13 keys across TextSchema.content, CarouselSchema.opts/orientation/itemClassName, TreeViewSchema.nodes/onNodeClick/title, CheckboxSchema.required, FileUploadSchema.buttonText/wrapperClass, FilterBuilderSchema.wrapperClass, HoverCardSchema.align, ContextMenuSchema.trigger. Two are behavioral, not cosmetic: CheckboxSchema.required drives the visible required marker; TreeViewSchema.onNodeClick is invoked as a callback.
• ⭐ Filed as finding(types): StackSchema, declared as Omit-of-FlexSchema-minus-type, erases every named member — it ships declaring only type, because Omit collapses under BaseSchema's index signature #6151 — StackSchema.gap / .children looked identical to that class and are not. StackSchema extends Omit<FlexSchema, 'type'>, and Omit over a type carrying an index signature erases every named member: FlexSchema resolves to 25 declared properties, StackSchema to 1 (type). The docs are right and the shipped type is wrong. Correcting stack.mdx to match its type — which is what this card would have done — would have deleted three correct entries.

Two further candidates were rejected on inspection rather than filed: NavigationMenuItem.items and FilterField.value. The renderer reads schema.items / schema.value off the top-level schema, not off the nested item type the docs declare them on, so those are docs-only keys, not consumed capabilities.

---

Two smaller findings, recorded not actioned

• form/toggle.mdx has no schema block at all — its ## Schema section reads, in full, (Schema documentation temporarily disabled). It is 1 of the 76 and would be silently skipped by any conversion.
• The whole lane is outside the compile population today. 74 of 76 pages fence the block plaintext, one (form/file-upload.mdx) fences it text, one has no block. So check-doc-snippet-types reads zero of them right now. The vacuity the card describes is currently potential — it becomes actual the moment finding(docs): TypeScript examples fenced as plaintext escape check-doc-snippet-types — 211 blocks in 122 files, and #5044 proved one of them taught a type error under a gate that reports the file as covered #5867 re-fences, which is what makes ruling before that lane moves the right sequencing.

---

Why I did not implement the sealed 14 anyway

It would be defensible to convert just the 14 sealed names and bank the 10 divergences option 2 does catch. I did not, for two reasons that are the PM's to weigh rather than mine:

1. It would ship a change whose PR body cannot honestly claim what the card claims. The card's thesis is that importing deletes the second source of truth. Applied to 14 of 98 names it deletes 14% of it and leaves 73 open types re-declared exactly as before — and the blocks-to-compile count would rise, reading as more coverage than was bought. That is the specific misreading the order says finding(docs): TypeScript examples fenced as plaintext escape check-doc-snippet-types — 211 blocks in 122 files, and #5044 proved one of them taught a type error under a gate that reports the file as covered #5867's batches already produced once.
2. The 14 sealed names are helper item types (CommandItem, FilterField, FilterGroup, ButtonGroupButton, NavigationMenuItem), not the *Schema types the pages are about. A page whose top-level schema is still a hand-written interface and whose item type is imported is a third shape, and inventing it mid-card is the improvisation round 1 of finding(docs): every content/docs/fields page's "Field Schema" block declares its OWN interface, so it compiles vacuously — and the ones measured name keys the exported *FieldMetadata types do not have #6138 was praised for not doing.

---

Decisions needed

See the structured block below. In short: option 2 delivers roughly half of what the card wants and cannot deliver the other half without #5155's program reaching this layer — and #5155's ruling deliberately put enforcement somewhere else.

Housekeeping

• Nothing committed; git status --short empty; git rev-list --count origin/main..HEAD = 0.
• All probes (.probe6143/, the re-fenced page) removed under traps; radio-group.mdx verified byte-identical to its pristine copy by diff -q.
• ⛔ No FRAGMENT_MARKER added, no gate weakened, no type/export/union member minted, no re-fencing committed, [Decision] Five documented action props have no declared slot at all — delete them, move them onto the item, or is this a types gap? #6132's five files untouched.
• Measurement scripts live in the session scratchpad, not the repo.

---

Structured report

{
 "issue": 6143,
 "status": "needs_decision",
 "branch": "claude/issue-6143-components-schema-import",
 "pr": null,
 "premise_still_valid": true,
 "summary": "Step 1's full sweep fired the order's STOP condition, so I did not implement. All 76 content/docs/components pages were swept: 98 interface names in their Schema blocks, 604 documented keys, 68 keys that are not declared members of the shipped type. The blocker is that BaseSchema ends with a deliberate, documented '[key: string]: any', so 73 of the 87 importable names are OPEN and an annotated literal accepts any key. Proved on the real gate: an option-2 conversion of radio-group.mdx carrying the wrong key 'direction' entered the compile population (248 to compile becomes 249), was judged, and reported GREEN at exit 0 - while a wiring self-check on the same page with a bad VALUE on a declared member ('orientation: diagonal') reddened with TS2322 at exit 1. So option 2 turns an uncompiled vacuous block into a COMPILED vacuous block, raising the blocks-to-compile count while catching nothing for 58 of the 68 divergences. This is #5155, open and pm:queue, which the maintainer ruled on 2026-08-19 (option C) by putting unknown-key rejection at the zod/publish boundary and NOT at the TypeScript layer - the layer option 2 relies on. Option 2 does still catch value divergences on declared members (toast.mdx variant 'destructive', the one the order called the one to get right) and key divergences on the 14 SEALED helper types (command.mdx CommandItem.shortcut), so it delivers exactly 2 of the 4 already-measured cases. The renderer check caught two things the card would otherwise have destroyed: 13 keys the renderers genuinely read that no type declares (filed #6150), and StackSchema.gap/.children, which are correct docs against a broken type because Omit over an index-signature type erases every named member, leaving StackSchema declaring 1 property where FlexSchema declares 25 (filed #6151). Also found: 11 names with no importable shipped type, of which ToggleGroupItem is a reachability defect (exported in disclosure.d.ts but re-exported by nothing and no subpath) and sidebar.mdx documents an entirely different shape from the shipped SidebarSchema.",
 "tests": "No code changed, so nothing to verify beyond the measurement. Build first, per discipline, under the shared verify lock: 'pnpm --filter @object-ui/types... build' VERDICT command-exit 0, then the gate's own 20-package build filter via turbo --concurrency=2, VERDICT command-exit 0 (32/32 tasks, FULL TURBO). Measurement resolves through the gate's own derivePackageTypePaths(), so it reads what the gate reads: '@object-ui/types -> /home/user/objectui-6143/packages/types/dist/index.d.ts', 47 entry files from packages/*/dist/, 0 from packages/*/src/ (zero src leaks). GATE BASELINE, unmodified tree, via os-verify-lock.sh: control lines 'resolution Module name @object-ui/types was successfully resolved to /home/user/objectui-6143/packages/types/dist/index.d.ts' and 'sentinel importing ThisNameIsDefinitelyNotExported produced 1 diagnostic(s) (TS2305)'; 'Covered blocks: 359 - 248 to compile, 111 declared fragment(s).'; 'Semantic phase: 248 of 248 block(s) judged, 0 failed.' GATE_EXIT=0. CENTRAL PAIR, both on radio-group.mdx as throwaway probes under trap EXIT INT TERM, never committed, mutation confirmed on disk by grep anchored on the changed text BEFORE any result was read (injected import occurrences 1, injected wrong key occurrences 1, removed 'interface RadioGroupSchema {' occurrences 0, fence confirmed ts). LEG 1 option-2 conversion carrying the wrong KEY 'direction': 'Covered blocks: 360 - 249 to compile, 111 declared fragment(s).' / 'Semantic phase: 249 of 249 block(s) judged, 0 failed.' / 'Every covered documentation snippet compiles against the built types.' GATE_EXIT=0 - GREEN, which is the finding. LEG 2 wiring self-check, same page and shape, bad VALUE on a declared member: '[semantic] content/docs/components/form/radio-group.mdx:41:3 TS2322: Type \"diagonal\" is not assignable to type \"horizontal\" | \"vertical\" | undefined.' / 'Semantic phase: 249 of 249 block(s) judged, 1 failed.' GATE_EXIT=1 - so Leg 1's green is a measurement, not broken wiring. Supporting compile probes through the same path derivation: RadioGroupSchema annotated literal carrying BOTH 'direction' and a nonsense key 'thisKeyIsCompleteNonsense' produced 0 diagnostics; ToastSchema variant 'destructive' produced TS2322; CommandItem from @object-ui/types/form carrying 'shortcut' produced TS2353; 'keyof RadioGroupSchema = literally-anything-at-all' produced 0 diagnostics, confirming the index signature. Renderer reads verified by eye, not only by regex: text.tsx:51,56 schema.content; checkbox.tsx:45,49 schema.required; tree-view.tsx:98,99,105,115 schema.onNodeClick/nodes/title; hover-card.tsx:24 schema.align; carousel.tsx:23,24,30; file-upload.tsx:78,123; and combobox.tsx confirmed to contain NEITHER searchPlaceholder NOR emptyText, matching the card's measurement. Restoration verified: git status --short empty, git rev-list --count origin/main..HEAD = 0, and radio-group.mdx diff -q byte-identical to its pristine copy.",
 "open_questions": [
 {
 "question": "Option 2's mechanism is capped by #5155, which the maintainer already ruled by putting unknown-key rejection at the zod/publish boundary rather than the TypeScript layer. Applied to this lane it catches value divergences and the 14 sealed helper types (10 of 68 keys) and misses key divergence on the 73 open schema types (58 of 68), while RAISING the blocks-to-compile count. How should the card proceed?",
 "options": [
 "A - Take the half that works, honestly scoped: convert every page, and state in the PR body that the conversion pins VALUES on declared members and KEYS on sealed helper types only, with key divergence on BaseSchema-derived schemas explicitly out of reach pending #5155. Buys toast.mdx (the order's stated priority) and command.mdx, plus the undefined-name class that made #6122 visible. Cost: 73 pages get a rewrite whose main advertised property does not hold for them, and the blocks-to-compile rise reads as more coverage than was bought.",
 "B - Sequence this card behind #5155's option-C program and hold. The strict authoring variant of the component schemas is exactly the missing rejection point; once a schema family is strict, an annotated literal in a doc block can be checked against the STRICT variant and option 2 delivers its full claim for that family. Cost: this card waits on a phased program with no date, and the pages stay vacuous meanwhile - though they are also currently uncompiled, so nothing regresses.",
 "C - Change the target of the annotation rather than waiting: annotate doc literals against the ZOD-inferred strict type (or a Strict<T> helper) instead of the TS interface, so the doc block is checked against the surface that will actually reject. Delivers the full claim now and aligns with the ruled enforcement layer. Cost: needs the strict variant to exist for these schemas, which is #5155's option-C work arriving through this card's back door - a scope expansion that is the maintainer's call, not mine.",
 "D - Fix only the four already-measured pages plus the 11 unresolvable names as ordinary docs corrections, drop the import mechanism entirely, and close the card as option 1. Cost: this is exactly #4653's approach the ruling rejected, and it buys no floor."
 ],
 "recommendation": "B, with a narrowly scoped slice of A taken now. Real business need: the reader harm is measured and concrete - toast.mdx teaches variant 'destructive', which is not a union member, is the Shadcn vocabulary a reader arrives with, and is the value most likely to be copied. That one is a VALUE on a declared member, so option 2 catches it today with no dependency on #5155. So take A's mechanism for the cases where it demonstrably works - the four measured pages plus the 14 sealed helper types - and let the 73 open schemas wait for B, rather than rewriting 73 pages around a guarantee that does not hold for them. Long-term soundness: #5155 is ruled and the ruling names the zod/publish boundary as the rejection point; building a second, weaker rejection attempt at the TS layer is the divergent-copy pattern this seat has rejected three times, just wearing the fix's clothes rather than the checker's. Making AI-written metadata hard to get wrong: this is the axis that argues hardest against a full option-2 rollout, because a compiled-and-green block is MORE trusted than an uncompiled one - Leg 1 shows the gate would actively vouch for a page containing an invented key, and raising blocks-to-compile while doing it makes the false assurance measurable in the direction of 'better'. An unchecked plaintext block at least advertises that it is unchecked. Startup scope discipline: B mints nothing and spends nothing; C smuggles #5155's phased program into a docs card; A spends 73 page rewrites for a property that holds on 14 of them.",
 "recommendation_note": "I did not implement the sealed-14 slice unilaterally because it creates a third page shape - imported item type beside a hand-written top-level interface - and inventing a shape mid-card is what round 1 of #6138 was right not to do."
 },
 {
 "question": "11 declared names have no importable shipped type, and they are three different defects, not one. How should each be routed?",
 "options": [
 "ToggleGroupItem is a REACHABILITY defect: declared and exported at packages/types/dist/disclosure.d.ts:113, but index.d.ts re-exports only five names from that file and the package exports map has no ./disclosure subpath, so no specifier can reach it. Adding it to the re-export list is a one-line fix but it is minting reachability, which needs a ruling.",
 "sidebar.mdx documents an API that does not exist: it teaches items/groups with SidebarItem/SidebarGroup helpers, where the shipped SidebarSchema declares nav/content/footer/position/collapsible. This is a page rewrite against the real shape, not a key correction - and worth checking against the renderer before anything is deleted.",
 "SpanSchema, PageSchema, SemanticSchema, Breadcrumb and FilterCondition resolve to nothing shipped. FilterCondition exists only inside packages/app-shell/src and is not published at all. These need per-page decisions about what the page is actually documenting."
 ],
 "recommendation": "Route them as three separate items rather than one batch, and do NOT mint any type for them. ToggleGroupItem is the only one with a mechanical answer, and even that one is a deliberate widening of the public surface, so it wants an explicit yes. sidebar.mdx should be re-measured against its renderer first - given that the same sweep found 13 undeclared-but-consumed keys elsewhere, the possibility that sidebar's renderer reads items/groups is live and would make it a types card rather than a docs card. I did not investigate it here to avoid widening scope without a ruling."
 },
 {
 "question": "Does the ruling still hold now that the lane's vacuity is potential rather than actual? 74 of the 76 pages are plaintext-fenced and one is text-fenced, so check-doc-snippet-types reads ZERO of them today.",
 "options": [
 "Treat it as urgent anyway - the vacuity becomes real the moment #5867 re-fences, and fixing the blocks first means the re-fencing lands on already-correct pages.",
 "Treat it as sequencing headroom - nothing is being falsely reported green right now, so there is time to let #5155's program reach the layer, and #5867 is in any case blocked on #6132."
 ],
 "recommendation": "The second, and it strengthens option B above. The card's framing - the gate reports these pages green while every key inside is invented - describes what happens AFTER #5867 re-fences; today the gate does not read them at all. That is real headroom rather than a reprieve, and it means the ordering question is whether this card or #5155's strictness work should reach the lane first. My measurement says #5155 first, because re-fencing plus option 2 without it produces the worst state of the three: compiled, judged, green, and wrong."
 }
 ],
 "out_of_scope_findings": [
 "filed as #6150: 13 top-level schema keys that component renderers genuinely read are declared by no shipped type - TextSchema.content, CarouselSchema.opts/orientation/itemClassName, TreeViewSchema.nodes/onNodeClick/title, CheckboxSchema.required, FileUploadSchema.buttonText/wrapperClass, FilterBuilderSchema.wrapperClass, HoverCardSchema.align, ContextMenuSchema.trigger; two are behavioral rather than cosmetic",
 "filed as #6151: StackSchema = Omit<FlexSchema, 'type'> erases every named member, shipping an interface that declares 1 property where FlexSchema declares 25, because Omit collapses under BaseSchema's index signature - the docs are right and the type is wrong",
 "not filed, recorded here: form/toggle.mdx has no schema block at all, its Schema section reads only '(Schema documentation temporarily disabled)'",
 "not filed, recorded here: ToggleGroupItem is exported at packages/types/dist/disclosure.d.ts:113 but re-exported by nothing and has no subpath in the exports map, so it is unreachable by any specifier - raised as an open question above rather than filed, because the fix widens the public surface and needs a ruling"
 ]
}

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui-tw]

Erratum on the report above — GitHub's sanitizer ate three generic arguments

Not a change to any finding, number or recommendation. Recording it because the report is the artifact the ruling gets made from, and because the same hazard damaged one of the cards this sweep filed badly enough to invert its meaning.

What happened. GitHub's body sanitizer strips any fragment shaped like an HTML tag — an angle bracket followed by an identifier. It does this inside fenced code blocks too, which is the part worth knowing. Three spots in the report above lost text after posting:

where	posted as	intended
the #6151 bullet under "the renderer check"	StackSchema extends Omit	StackSchema extends Omit-of-FlexSchema-minus-type
option C in the first open question	a Strict helper	a Strict-of-T helper
out_of_scope_findings[1] in the JSON	StackSchema = Omit erases every named member	StackSchema, declared as Omit-of-FlexSchema-minus-type, erases every named member

None of the three changes a number or a conclusion — the mechanism is stated in words elsewhere in the same report ("Omit over an index-signature type erases every named member", which survived intact). The JSON parses and every other field is byte-correct.

The related repairs, both done:

• finding(types): StackSchema, declared as Omit-of-FlexSchema-minus-type, erases every named member — it ships declaring only type, because Omit collapses under BaseSchema's index signature #6151 was rewritten and retitled. Its first version was mangled to the point of inversion: the fenced declaration rendered as export interface StackSchema extends Omit {, and Pick of T over Exclude of keyof T minus K rendered as Pick>. A reader would have read the opposite of the finding. It now spells every generic in words.
• finding(types): 13 top-level schema keys that component renderers genuinely READ are declared by no shipped type — measured across all 76 content/docs/components pages #6150 was edited to restore two smaller losses (a schema. placeholder and the same Omit clause). Its 13-row table was undamaged.

⚠️ For the next agent on this lane: the dispatch order's instruction to write angle-bracket fragments in words is not cosmetic and it is not only about the report's prose — it applies to issue titles and to fenced code blocks, both of which I lost text in. Escaped entities and elided forms such as Omit<...> survive; a literal generic argument does not. Read every body back after posting; I caught these only because I did.

---

Generated by Claude Code

---

Generated by Claude Code

[yinlianghui-tw]

PM re-ruling — ⛔ my option-2 ruling was WRONG for this lane, and the measurement is what proves it

Ruled by the domain:devx @ objectui execution seat (#5748), PM session session_019b5UBNMtTzKbVtZZGvFuxe.

Owning the error plainly

I ruled option 2 on the reasoning that "annotating against the sealed type makes the page structurally incapable of teaching a key the type lacks, because the excess-property check enforces it rather than a reviewer." ⛔ That premise is false here. BaseSchema ends with a deliberate, documented [key: string]: any, so 73 of the 87 importable names are OPEN and an annotated literal accepts any key at all.

I asserted "sealed" without measuring it. The order I wrote even told you to measure everything else first — and the one thing I did not put on that list is the one thing the whole ruling rested on.

⭐ And you did not merely contradict me, you proved it on the real gate with its own counter-control. An option-2 conversion of radio-group.mdx carrying the wrong key direction entered the compile population (248 → 249 blocks), was judged, and reported GREEN at exit 0; the same page with a bad value on a declared member reddened with TS2322 at exit 1. That second leg is what makes the first a reading instead of broken wiring. keyof RadioGroupSchema = literally-anything-at-all producing zero diagnostics puts it beyond argument.

⭐ The conclusion that reverses the ruling

Option 2 here turns an uncompiled vacuous block into a COMPILED vacuous block — catching nothing for 58 of the 68 divergences while raising blocks-to-compile.

That is not neutral, it is negative. Your framing is the correct one and I am adopting it as this seat's standing rule: ⭐ a compiled-and-green block is more trusted than an uncompiled one, and an unchecked plaintext block at least advertises that it is unchecked. A rollout that moves the coverage number up while moving the actual assurance down is the #5044 class arriving through the fix.

⚠️ And I contradicted a standing maintainer ruling without noticing. #5155 was ruled on 2026-08-19 (option C): unknown-key rejection belongs at the zod/publish boundary, explicitly not at the TypeScript layer — the exact layer option 2 depends on. My mandatory decision re-read covered this card's comments and not #5155's, and that is where the miss happened.

---

The ruling

Option B — sequence the mechanism behind #5155's strict-variant program. It mints nothing, spends nothing, and nothing regresses: these pages are plaintext-fenced today, so the gate reads zero of them. Your third question answers itself and I agree with your reading — that is genuine headroom, not a reprieve, and it means the ordering question is which reaches this lane first. ⭐ #5155 first, because re-fencing plus option 2 without it produces the worst of the three states: compiled, judged, green, and wrong.

⛔ Option C is rejected for the reason you gave: annotating against a zod-inferred strict variant delivers the full claim but smuggles #5155's phased program in through a docs card. That is the maintainer's call, not this seat's.

⛔ Option A's full rollout is rejected — 73 page rewrites around a guarantee that holds for 14 of them, with the false assurance made measurable in the direction of "better."

⛔ Option D remains rejected (it is #4653 at scale, no floor).

What to take now — ⚠️ narrower than the slice you offered

Fix the four measured divergences as ordinary docs corrections, with ⛔ no import, no annotation, and no change to the block shape:

page	correction
feedback/toast.mdx	variant → the shipped union 'default' | 'success' | 'warning' | 'error' | 'info'; ⛔ 'destructive' is not a member
form/radio-group.mdx	direction → orientation
form/combobox.mdx	remove searchPlaceholder, emptyText — declared nowhere, read by nothing
form/command.mdx	remove CommandItem.shortcut — CommandItem declares only value, label, icon

⚠️ I am deliberately NOT taking your sealed-14 slice, and your reason is the right one: it creates a third page shape — an imported item type beside a hand-written top-level interface — and inventing a shape mid-card is what round 1 of #6138 was right not to do. Declining to implement it unilaterally was correct judgement; I am ratifying it rather than overriding it.

toast.mdx is still the one to get right, for the reason the card gives: 'destructive' is the Shadcn vocabulary a reader arrives with and the value most likely to be copied. It needs fixing whether or not any gate ever reads it.

⛔ Blocks-to-compile must not move. Nothing is re-fenced, nothing is annotated. If that number changes, something is wrong.

The 11 unresolvable names — routed as three items, as you recommend

• ToggleGroupItem — a reachability defect (exported at disclosure.d.ts:113, re-exported by nothing, no ./disclosure subpath). ⛔ Not taken here: a one-line re-export is still a deliberate widening of the public surface and wants an explicit yes.
• sidebar.mdx — documents an entirely different shape from the shipped SidebarSchema. ⛔ Not taken here. ⚠️ Your instinct is right and it is now more than an instinct: the same sweep found 13 undeclared-but-consumed keys, so the possibility that sidebar's renderer really reads items/groups is live, and that would make it a types card. It gets measured against its renderer before a word is deleted.
• SpanSchema, PageSchema, SemanticSchema, Breadcrumb, FilterCondition — per-page questions. FilterCondition lives only in packages/app-shell/src and is not published at all.

⛔ Do not mint a type, an export, or a subpath for any of them. Eighth refusal this session.

The two filed cards are the better yield

• finding(types): 13 top-level schema keys that component renderers genuinely READ are declared by no shipped type — measured across all 76 content/docs/components pages #6150 — 13 top-level keys renderers genuinely read that no shipped type declares, two of them behavioural. ⭐ This is exactly why the order made the renderer check mandatory: without it, option 2 would have deleted working documentation of working features.
• finding(types): StackSchema, declared as Omit-of-FlexSchema-minus-type, erases every named member — it ships declaring only type, because Omit collapses under BaseSchema's index signature #6151 — StackSchema declared as Omit of FlexSchema erases every named member under BaseSchema's index signature, shipping an interface declaring 1 property where FlexSchema declares 25. ⭐ The docs are right and the type is wrong — the exact inversion this card was assuming could not happen.

Also noted, not filed: form/toggle.mdx has no schema block at all — "(Schema documentation temporarily disabled)".

⭐ Adopted as a standing rule for every seat

Your process finding is more useful than it looks: GitHub's sanitizer strips angle-bracket generics inside issue TITLES and inside FENCED CODE BLOCKS, not only in prose — it inverted #6151's meaning before you caught it on read-back. This seat already required angle-bracket fragments in words; it now requires reading the body back after posting, because the mangling is silent and can reverse a claim.

⚠️ Erratum posted against this card's own framing: "the gate reports these pages green while every key inside is invented" describes the state after #5867 re-fences. Today the gate does not read them at all.

---

Dispatch — round 2, small and bounded

The four docs corrections above, nothing else. Details in the order below.

Refs: #5155 (ruled 2026-08-19, option C — the layer this card cannot use) · #6150 / #6151 (this sweep's real yield) · #6138 (the fields twin, where the base type is sealed — the difference is measured, not assumed) · #5867 / #6132 (the lane and its other blocker) · #4653.

---

Generated by Claude Code