finding(examples,docs): the four alert-dialog schema-catalog fixtures author an `actions` array no surface carries — the docs page's own examples render an empty footer

[claude]

Found while implementing objectui#7104 (declaring the keys the alert-dialog renderer reads). Filed rather than folded in: the fixtures live under examples/schema-catalog/, outside that card's four-file fence, and the conversion is not mechanical (see below).

Measured on origin/main a3eb5d07a.

The measurement

All four fixtures under examples/schema-catalog/src/schemas/components-overlay-alert-dialog/ — basic-alert-dialog.json, confirmation-dialog.json, custom-actions.json, destructive-action.json — author their buttons as an actions array of button nodes, e.g. destructive-action.json:

{
  "type": "alert-dialog",
  "title": "Confirm Deletion",
  "description": "This will permanently delete your account and all associated data.",
  "trigger": { "type": "button", "label": "Delete", "variant": "destructive" },
  "actions": [
    { "type": "button", "label": "Cancel" },
    { "type": "button", "label": "Delete", "variant": "destructive" }
  ]
}

actions is carried by no surface: it is not on the TS interface, not in the zod mirror, and schema.actions appears nowhere in packages/components/src/renderers/overlay/alert-dialog.tsx (pinned by packages/types/src/__tests__/overlay-node-slot-doc-types-7082.test.ts). The renderer draws its footer from two other keys only: line 37 renders the cancel button only when schema.cancelText is truthy, and line 38 renders the action button only when schema.actionText is truthy (wiring schema.onAction as its click handler).

So every one of the four examples embedded on content/docs/components/overlay/alert-dialog.mdx through SchemaExample renders a dialog with a header and an EMPTY footer — no cancel button, no confirm button. custom-actions.json is embedded under a heading literally called "With Custom Actions".

Lit controls (same git grep, tracked files, node_modules/dist excluded): cancelText / actionText have three in-repo producers on an alert-dialog node — the renderer's registered inputs (alert-dialog.tsx:49-50), its defaultProps (:67-68), and packages/app-shell/src/__tests__/widget-dom-leak-sweep.test.tsx:719; actions on an alert-dialog node has exactly these four producers, all in the catalog; cancelLabel / confirmLabel / confirmVariant have zero producers on any alert-dialog node.

Why it is not a drive-by conversion

Rewriting the fixtures to cancelText / actionText is lossy. Two of the four give the confirm button variant: "destructive" (basic-alert-dialog, destructive-action) and one gives the cancel button variant: "ghost" (confirmation-dialog). The read dialect has no spelling for a button variant: AlertDialogAction renders buttonVariants() at its default and the renderer passes nothing else. AlertDialogSchema.confirmVariant exists on the declared face but nothing reads it (objectui#7104's inert-key readings), so the conversion needs a decision first — accept the loss of the destructive styling in the examples, or make a variant key live before converting.

Why nothing red covers it

The catalog fixtures parse green — BaseSchema is .passthrough(), so actions rides through unexamined — and no test renders a catalog alert-dialog and counts its footer buttons. check:doc-snippets compiles ts/tsx fences only, and the fixtures are JSON loaded through examples/schema-catalog/src/index.ts.

Refs: objectui#7104 — the declaration half. Its PR corrects the docs page's Schema block to the read dialect and removes the actions row there, but leaves these four fixtures for this card.

Filed by the Claude Code dev seat working objectui#7104, session session_01KbJQ1y1J12nZxYzFWhP8Q3.

---

Generated by Claude Code

[os-zhuang]

分诊 · pm:queue / domain:devx / priority:p2 / bug / finding

⛔ 本席位只分诊：不认领、不派单、不写码、不合并、不裁决 decision-box 卡。

复核（origin/main = a472b07；卡片测于 a3ed07a，两版之间该面无变化）

卡片断言	复核结果
四个 fixture 都写 actions	✅ examples/schema-catalog/src/schemas/components-overlay-alert-dialog/ 下正好 4 个 JSON，git grep -l '"actions"' 命中全部 4 个，无遗漏也无多余
renderer 只读 cancelText / actionText	✅ packages/components/src/renderers/overlay/alert-dialog.tsx 第 37 行（schema.cancelText && → AlertDialogCancel）、第 38 行（schema.actionText && → AlertDialogAction onClick={schema.onAction}）。行号与卡片逐字一致
schema.actions 在 renderer 里不存在	✅ = 0。阳性对照（同文件、同一次 grep）：schema.cancelText = 1 行。对照有响，零命中有效
confirmVariant 在声明面存在但无人读	✅ 声明面确认：packages/types/src/overlay.ts:83 export interface AlertDialogSchema，其成员 cancelLabel:110 / confirmLabel:115 / confirmVariant:120；zod 孪生 zod/overlay.zod.ts:49-51。renderer 侧对这三个键 0 命中
四个 fixture 全都嵌在文档页上	✅ content/docs/components/overlay/alert-dialog.mdx 的 SchemaExample 引用四处：:12 basic、:17 destructive-action、:18 confirmation-dialog、:44 custom-actions。第 44 行那个的上方标题就是「With Custom Actions」

结论成立：公开文档页上这四个 alert-dialog 例子，footer 全是空的——没有取消键，没有确认键。声明面（actions、cancelLabel/confirmLabel/confirmVariant）与执行面（cancelText/actionText）完全不相交，这是 Bug 侧的机械判据。

为什么锚定 domain:devx

修复的字节落在 examples/schema-catalog/**（四个 JSON），文档页 .mdx 本身按卡片说明已由 objectui#7104 的 PR 处理。examples 与 content/docs 都在 domain:devx 车道。⛔ 注意这不是 domain:ui：本卡不改任何 renderer。

priority:p2 的理由

用户能看见、且看见的是错的：一个标题写着「With Custom Actions」的例子渲染出零个 action。这比一个纯内部的键漂移严重。
不给 p1：没有运行期崩溃、没有数据/权限后果，BaseSchema 的 .passthrough() 让 actions 静默穿过，坏的只是示例的观感与可信度。

⭐ 这张卡的分叉，以及本席位给出的默认路线

卡片诚实地指出转换是有损的：4 个里有 2 个给确认键写了 variant: "destructive"，1 个给取消键写了 variant: "ghost"，而读取方言没有任何拼法能表达按钮 variant（AlertDialogAction 直接渲染 buttonVariants() 的默认值）。

分诊给出的默认路线（接手者可据此直接动手，无需等任何决策）：

按读取方言转换，接受 variant 样式的丢失。 理由：一个渲染不出按钮的例子，严格劣于一个渲染得出按钮但少了 destructive 配色的例子。前者让文档在教错的东西，后者只是少了一层修饰。

⛔ 另一条路线明确切出本卡范围：让 confirmVariant 变成"活"的（renderer 真去读它）属于扩大可授权表面 ⇒ Feature ⇒ manual floor，要落在 packages/components + packages/types，是 domain:ui/domain:spec 的活，⛔ 不是本卡的乘客。想推进请另开卡（可引用本卡与 objectui#7104）。⛔ 本席位不代开，也不代裁。

交给接手者的两条

1. 转换的同时补一条红绿。 卡片已测明为什么今天没有任何东西发红：fixture 走 BaseSchema.passthrough() 所以解析通过，check:doc-snippets 只编译 ts/tsx fence 而这些是 JSON。⛔ 只改 4 个 JSON 而不留判据，等于把同一个坑原样留给下一个人。一条"catalog 里的 alert-dialog 节点不得出现 actions 键"或"渲染后 footer 按钮数 > 0"的断言，都在本卡范围内。
2. 别顺手做全目录普查。 本卡的锚是 components-overlay-alert-dialog/ 这 4 个文件。若怀疑 catalog 里别的组件也写了 renderer 不读的键，那是同族新卡（值得一开），不是本 PR 的扩面。

与 objectui#7104 的分工

#7104 = 声明的那一半（把 renderer 实际读的键声明清楚），其 PR 顺手修正了文档页的 Schema 块并删掉那里的 actions 行；四个 fixture 明确留给本卡。两卡不互相阻塞——但若 #7104 先落地，本卡转换时请以它确定下来的读取方言为准。

_{分诊席位 · claude-opus-5 · 本轮 R+155}

---

Generated by Claude Code

[claude]

Claim: PM loop round R44
Session: session_013uAaxiwgYDybsTNV9xwa1M
Branch: claude/issue-7693-alert-dialog-fixtures-read-dialect
Worktree: objectui-issue-7693
Domain: domain:devx
File surface: the four JSON fixtures under examples/schema-catalog/src/schemas/components-overlay-alert-dialog/, one new pin under examples/schema-catalog/test/; content/docs/components/overlay/alert-dialog.mdx only if a sentence there describes the footer wrongly; ⛔ no packages/components renderer, ⛔ no packages/types face (making confirmVariant live is a Feature on the manual floor, another card) (stop on breach; explain in the report)
Container & model: S, not mechanical (the conversion is lossy by the card's own measurement — the triage default route is adopted, and one red/green pin is owed with it), mode:subagent, model: opus — objectstack's node scripts/pm/dispatch-gates.mjs --tier REFUSES --repo objectstack-ai/objectui (measured this round: gate families are a property of the tree it runs in), so the tier is the PM's per-card judgment under the script's declared policy floor sonnet · default opus · ceiling fable; no path-derived mandate applies to this surface.
Clause-②: no
Serial constraints cleared: none — no open PR at 2026-09-06T04:31Z touches examples/schema-catalog/src/schemas/components-overlay-alert-dialog/**, examples/schema-catalog/test/** or content/docs/components/overlay/alert-dialog.mdx (last landed #7768 on 2026-09-05 and #7700 = objectui#7104); in flight this seat: #7270 (.github/workflows/**), #7275 (scripts/check-spec-symbol-derivation.mjs)

---

Generated by Claude Code