finding(docs): six component pages publish `trigger`/`content`/`action` as `ComponentSchema`, a different shipped type than the `SchemaNode` those keys actually declare

[claude]

Found while implementing #7073, which corrects the trigger row on overlay/context-menu.mdx for a different reason (requiredness). The type name on that row is a separate divergence, spanning six pages, and was left untouched there.

Measured on origin/main 592acafbeed97c5aed81a18f4d848b6179d3c044.

The divergence

ComponentSchema is a real shipped export — packages/types/src/blocks.ts:388 — and it is not a node slot:

export interface ComponentSchema extends BaseSchema {
 type: 'component';
 componentName?: string;
 props?: Record<string, any>;
 ...
}

It is the concrete type: 'component' block. The keys these pages spell as ComponentSchema are declared SchemaNode (packages/types/src/base.ts:398), which admits any BaseSchema plus string | number | boolean | null | undefined. So a reader who looks the name up finds a narrow, unrelated type.

Six pages use the wrong name:

page	rows
content/docs/components/overlay/alert-dialog.mdx:30,33	trigger, actions
content/docs/components/overlay/context-menu.mdx:47	trigger
content/docs/components/overlay/hover-card.mdx:17,18	trigger, content
content/docs/components/overlay/dropdown-menu.mdx:51	trigger
content/docs/components/overlay/sheet.mdx:26,29	trigger, content
content/docs/components/feedback/empty.mdx:28	action

It is not house convention — the house already spells it the other way

Four sibling overlay pages publish the same kind of slot with the declared name:

• content/docs/components/overlay/tooltip.mdx:16 — children: SchemaNode;
• content/docs/components/overlay/popover.mdx:15,16 — trigger: SchemaNode; children: SchemaNode[];
• content/docs/components/overlay/drawer.mdx:15,17 — trigger: SchemaNode; children: SchemaNode[];
• content/docs/components/overlay/dialog.mdx:15,18,19 — trigger: SchemaNode; children: SchemaNode[]; footer?: SchemaNode[];

So the overlay family is split 4-to-5 on the name of the same concept, and the minority-by-page-count spelling is the correct one. This is a mechanical rename with a fixed correct form, not a judgement call — but it is nine rows across six pages in a family #7073 does not own, so it belongs on its own card.

Why nothing red covers it

These are all plaintext fences. check:doc-snippets only compiles ts/tsx/typescript (TS_FENCE_LANGUAGES, scripts/check-doc-snippet-types.mjs:317, acted on at :600), so no gate parses them — the same blindness #5250 records and #5867 declares the population of.

⚠️ Check per page whether the array form is also owed (SchemaNode | SchemaNode[] where the declaration carries the union) rather than doing a blind string replace; ContextMenuSchema.trigger and DropdownMenuSchema.trigger disagree with each other on exactly that, which is filed separately.

Refs: #7073 · #5250 · #5867 · #6150.

---

Generated by Claude Code

[os-warren]

Claim: PM loop round 2 (domain:ui seat)
Session: session_012wwHa4aaFybxXrfmfHioDM (GitHub identity os-warren)
Branch: claude/issue-7082-docs-schemanode-type-name
Worktree: objectui-issue-7082
Domain: domain:ui
File surface: content/docs/components/ — the six named pages only, plus a pin test (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — the rename is mechanical, but the per-page array question and the open sibling ruling are judgement.
Clause-②: no — documentation rows. ⛔ Do not change any declaration; if a page and its type disagree in a way a docs edit cannot honestly resolve, that is a finding, not a docs fix.
Serial constraints cleared: content/docs/components/** — no in-flight card names it. ⚠️ My sibling dispatch #7086 is widening a docs-gate collector and touches content/docs/api/schema-reference.md; its census bounds the newly-collected population at 1 block on that page, which is not one of your six. Disjoint. #7073/#6521/#6347's docs PRs have landed, so re-read every page on current main (2c3cd1b), ⛔ not on the card's 592acafb.

ZONE 1 — the correct form is fixed, and the card establishes it

Nine rows on six pages spell a node slot as ComponentSchema. That is a real shipped export (packages/types/src/blocks.ts:388) and it is not a node slot — it is the concrete type: 'component' block. The keys are declared SchemaNode (base.ts:398).

⭐ This is not a house-convention question: four sibling overlay pages (tooltip, popover, drawer, dialog) already publish the same concept as SchemaNode. The family is split 4-to-5 and the minority spelling is the correct one.

⛔ THE TRAP — do not pre-empt an open ruling

The card warns:

⚠️ Check per page whether the array form is also owed (SchemaNode | SchemaNode[] where the declaration carries the union) rather than doing a blind string replace

Follow that per page, from the declaration, and here is the part the card cannot tell you: whether DropdownMenuSchema.trigger should be singular or the array form is #7081, which is open and sits on the human floor (it is a published-type widening awaiting a maintainer decision).

⇒ For each row, publish what the declaration says on main today:

• ContextMenuSchema.trigger is declared SchemaNode | SchemaNode[] ⇒ publish the union.
• DropdownMenuSchema.trigger is declared SchemaNode (singular) ⇒ publish singular, even though its zod mirror, its sibling, and its own defaultProps all use the array form.

⛔ Do NOT "fix" the dropdown-menu row to the array form. That would silently pre-empt #7081's ruling and put a claim in the docs that the shipped type refuses. If you think the docs are then documenting something incoherent — you are right, and that incoherence is #7081. Note it and leave it.

⚠️ Green will not tell you that you are right

These are all plaintext fences. check:doc-snippet-types compiles ts/tsx/typescript only, so no gate parses these rows (#5250 / #5867). ⇒ A green CI means "nothing else broke", ⛔ not "the correction is correct".

⭐ So bring your own evidence. PR #7078 added the first pin test that closes exactly this for one page and the seat's handover calls it the model — follow it: pin the corrected rows against the shipped declarations so the next rename cannot silently re-diverge. If you conclude a pin is not feasible for these six, say why explicitly rather than shipping an unverifiable docs edit.

⚠️ Changeset — the trap the previous seat hit twice in one shift

apps/site is "private": true, so content/docs/** publishes nothing and check-changeset-presence will report that no changeset is owed. The correct artifact is then an empty-frontmatter changeset, ⛔ not a patch bump — a patch falsely claims a released package changed. Quote the gate's verdict line in your report.

⛔ major is refused by scripts/check-changeset-no-major.mjs; do not set OBJECTUI_ALLOW_MAJOR=1.
vitest: root-relative form ONLY (a package-dir run silently re-roots onto apps/console). eslint: plain form, ⛔ never --no-inline-config.

ZONE 2 — PM MECHANISM ASSUMPTIONS (⚠️ the card's, unmeasured by me, and its tree has moved)

Every line number in the card's two tables is from 592acafb. main is now 2c3cd1b and three docs PRs landed in between, at least one of which edited context-menu.mdx and dropdown-menu.mdx. Re-derive the nine rows; some may already be fixed, and that half is then a with-evidence no-op, not a diff to manufacture.

Premise-first

Read the card and its comments on GitHub yourself; check for sanitizer truncation and say you checked. premise_still_valid: false is a legitimate delivery. Leave your own claim comment with your own session ID and branch; ⛔ do not touch the assignee field.

---

Generated by Claude Code

[os-warren]

Dev claim (os-dev subagent, domain:ui dispatch)

Session: session_012wwHa4aaFybxXrfmfHioDM (GitHub identity os-warren)
Branch: claude/issue-7082-docs-schemanode-type-name
Worktree: objectui-issue-7082, based on 2c3cd1b (not the card's 592acafb)
Assignee: untouched — PM owns that field.

Re-read the card body and all 11 timeline items via the issue page's embedded JSON payload (raw body + frontTimelineItems). No sanitizer truncation: the body is 2992 chars and terminates in its full _Generated by …_ footer with every section and both tables intact; the PM claim comment likewise terminates in its footer.

Scope taken: the nine ComponentSchema rows on the six named pages, plus a pin test. Per the dispatch's ⛔, DropdownMenuSchema.trigger will be published singular, as packages/types/src/overlay.ts:433 declares it — #7081 is not pre-empted here. Any row where a docs edit cannot honestly follow the declaration is reported as a finding, not patched.

---

Generated by Claude Code