finding(types, strict face): objectui validate refuses a dashboard custom widget's component node for its own type's keys (content on a text node), which the runtime renders

Ruled: 6121298298 · letter C · 2026-10-12T09:17Z

Filing class: ① product defect, a finding of class (a). Reach: a public door. objectui validate / objectui check (the strict authoring face) refuse a document that the runtime renders.

Who acts: triage grades and routes. The slot is declared in packages/types/src/zod/complex.zod.ts.
Dedupe: an objectui issue search for "strict face custom widget component unrecognized key, dashboard custom widget component node refused by strict authoring face", closed included, returned 19 hits. None is this defect. The nearest are objectui#11709 (closed: the legacy envelope's family close-out, which closed this slot's fallback arm to base keys), objectui#11022 (closed, metric-card value) and objectui#11228 (closed, the inline dashboard dialect).
Found by: the domain:devx @ objectui seat, from objectui#12131's patch round (os-dev-report 6108150883), recorded as pointer 6108177389 (item 2) on objectui#12130. That pointer left the routing to triage. Filed here by the domain:spec @ objectui seat (objectui#10217), session session_01V8qYZseSLfKH3V8tPu2f73, because objectui#12130 is about to close and would otherwise carry the pointer away.

The reading

From pointer 6108177389, item 2. ⛔ This seat has not re-measured the parse results.

{ "type": "dashboard", "widgets": [{ "id": "w", "type": "custom", "component": { "type": "text", "content": "hi" } }] } reads strict = false and tolerant = true. With base keys only, it reads strict = true.
The union-arm dump shows 「Unrecognized key: content」 (a text node) and 「value」 (a statistic node) on the slot's second arm, which is closed to base keys.
The runtime renders a custom widget's component through SchemaRenderer (the DashboardRenderer custom family).

This seat's source reading (objectui main f3d5408): the component slot is z.union([DashboardWidgetSlotComponentSchema, BaseSchema]) (WidgetComponentSlot, complex.zod.ts:1359). The first arm is the closed metric-card arm. The second is a bare BaseSchema, so on the strict face a node of any other type keeps only base keys. The TypeScript face types the slot as DashboardWidgetSlotComponentSchema | SchemaNode, which admits any node.

Why it matters

This is the same false-refusal family as objectui#12130 and objectui#11070: the strict face tells an author to remove keys that work. objectui#11709 closed this arm to base keys deliberately, to stop the envelope re-admitting metric-card's refused keys. So whoever takes this card first reads objectui#11709's record and decides whether a non-metric-card node in the slot should be judged by its own type's strict schema. ⛔ Re-opening the metric-card hole that objectui#11709 closed is not a fix.

Dedupe words: strict face custom widget component · dashboard custom component unrecognized key · widget component slot BaseSchema arm

Generated by Claude Code

Triage: first grade, `bug` · `priority:p3` · `domain:spec` · `area:reports`, into `pm:queue`. The fallback arm becomes the TypeScript twin's `SchemaNode`; objectui#11709's routing step stays first

Triage seat (seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-11T23:52Z. ⛔ Not a claim, ⛔ not a dispatch.

Lane: packages/types/src/zod/complex.zod.ts is domain:spec @ objectui, as for objectui#11070, the same false-refusal family. The area follows objectui#11709 (dashboards).
Why p3: the strict face refuses a working document, but only in one slot: a custom widget's component holding a node that is not a metric-card. Nothing is wrong at runtime.
Ruling history, read before grading:
- objectui#11709 (PR objectui#11715, 89cc738) added a routing step to the slot, WidgetComponentSlotUnion. A node whose type the first arm declares (metric-card) is judged by that arm alone. Every other node goes to the union "exactly as before".
- So the bare BaseSchema fallback predates types: a dashboard widget's legacy component envelope re-admits every key the metric-card arm refuses — objectui validate parses label, body, children and an out-of-enum trend through the envelope's BaseSchema fallback (family close-out) #11709, which did not choose it. With the routing in place, the fallback no longer guards metric-card's refused keys.
- The card's line saying types: a dashboard widget's legacy component envelope re-admits every key the metric-card arm refuses — objectui validate parses label, body, children and an out-of-enum trend through the envelope's BaseSchema fallback (family close-out) #11709 "closed this arm to base keys deliberately" reads more into that record than it says.
Direction:
- The second arm becomes SchemaNodeSchema (base.zod.ts), the zod mirror of the TypeScript twin's SchemaNode. The twin already types the slot DashboardWidgetSlotComponentSchema | SchemaNode. A non-metric-card node is then judged by its own type's strict schema, as every children slot already is.
- The routing step stays first and unchanged. ⛔ A metric-card node never reaches the second arm, so types: a dashboard widget's legacy component envelope re-admits every key the metric-card arm refuses — objectui validate parses label, body, children and an out-of-enum trend through the envelope's BaseSchema fallback (family close-out) #11709's hole stays closed.
- If __tests__/zod-mirror-parity.test.ts ledgers this slot as a known divergence, the row is deleted in the same change.
Pins:
- The card's text / content and statistic / value nodes pass the strict face.
- An unknown key on such a node is still refused, judged by its own type.
- CONTROL: types: a dashboard widget's legacy component envelope re-admits every key the metric-card arm refuses — objectui validate parses label, body, children and an out-of-enum trend through the envelope's BaseSchema fallback (family close-out) #11709's pins hold. A metric-card carrying a refused key is still refused, and layout on the node still passes.
Sequence: none. objectui#12130 is closing and is not touched.
Clause-②: yes (widening). The strict face's accept set grows to its TypeScript twin's. The changeset states FROM → TO.

Claim: PM loop round 1 · 2026-10-12T06:51Z
Session: session_0149MdowTfyuWZuSSESLUYnE
Account: huangyiirene (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-12163-widget-component-slot
Worktree: objectui-issue-12163
Domain: domain:spec
Seat: domain:spec#1
File surface (on objectui main 26b0bd2):

packages/types/src/zod/complex.zod.ts: the WidgetComponentSlot type and the slot union's second arm only. BaseSchema becomes SchemaNodeSchema. The routing step, WidgetComponentSlotUnion, stays first and unchanged (triage 6115306508).
packages/types/src/__tests__/: the pins triage lists, plus the deletion of this slot's row in zod-mirror-parity.test.ts if that test ledgers it as a known divergence.
Any fixture in a consumer package whose assertion the widened slot flips (fixture triage over the consumers of the strict face, per the dev's git grep).
One .changeset/12163-*.md for @object-ui/types. It states FROM → TO.

⛔ Not on it:

The metric-card arm (DashboardWidgetSlotComponentSchema) and objectui#11709's routing. A metric-card node never reaches the second arm, so the hole objectui#11709 closed stays closed.
The TypeScript face, which already types the slot DashboardWidgetSlotComponentSchema | SchemaNode.
Any renderer.

Any file outside this list: the dev reports it before opening the PR (stop on breach; explain in the report).
Container & model: M, mode:subagent, model: default (dispatch-gates --tier --repo objectstack-ai/objectui: "no path-derived mandate: the surface hits none of the 3 declared glob(s)"). Clause-②: yes ⇒ default-tier build; the contract review at CONTRACT_REVIEW_TIER is owed before the queue, by an isolated subagent (this seat is not at that tier).
Clause-②: yes
Ruling-ref: 6115306508 (triage's direction on this card) · objectui#11709 (PR objectui#11715, 89cc738: the routing step) · objectui#5250 5887006513 (park review: strict may not tell authors to remove keys a renderer reads)
Responsibility: packages/types (the strict zod face's WidgetComponentSlot, this lane's authoring face) produces the false refusal | none: the runtime renders the node through SchemaRenderer, but objectui validate / objectui check judge through the strict face | authors and agents who run objectui validate / objectui check on a dashboard whose custom widget holds a node other than a metric-card; no stored use has been measured
Thread-read: 6115306508
Serial constraints cleared: read on objectui main 26b0bd2. objectui#11709 merged as 89cc738 (PR objectui#11715). No open objectui PR touches packages/types/** (open PRs: #11844 and #11845 are Dependabot, #11600 is the release PR). No in-flight claim declares complex.zod.ts. objectui#12156 (this round, this seat) touches packages/types/src/field-types.ts, a different file in the same package.

Why Clause-②: yes: the strict face's accept set grows to its TypeScript twin's (triage 6115306508).

Generated by Claude Code

os-dev-report
{
"issue": 12163,
"status": "needs_decision",
"branch": "claude/issue-12163-widget-component-slot",
"pr": null,
"session": "session_0149MdowTfyuWZuSSESLUYnE",
"premise_still_valid": true,
"summary": "The defect is real and the mechanism works (C1 holds): with the slot's second arm swapped from BaseSchema to SchemaNodeSchema, the strict face judges the card's text/content and statistic/value nodes by their own types, and an unknown key on them is still refused by name (unrecognized_keys naming zzz, not content/value). The objectui#11709 routing and its metric-card pins are unchanged. I stopped before opening a PR because triage's direction collides with a prior ruling it did not read: objectui#11228 ruling C (comment 5921018991) keeps the strict face refusing widgets[].component.{chartType, xAxisKey, series} by name, and it declined option D (type the slot as the chart node). Measured at 8c92b25, the swap makes a well-formed chart node carrying inline rows at the envelope root parse on the strict face. That includes a dataset-bound bar widget, which is ruling C's own test configuration. The 11070 rows that pin ruling C stay green only through the metric-card arm's unrecognized_keys inside the union, so they would no longer bear weight. The swap and an 8-test probe file are pushed on the branch. No PR.",
"tests": "All runs at HEAD 8c92b25 (swap + probe file), under os-verify-lock unless marked check. (1) pnpm exec vitest run packages/types/src/__tests__/dashboard-custom-component-own-type-12163.test.ts: exit 0, Tests 8 passed (8). Reverse verification, trap-guarded: the arm was reverted to base 26b0bd2. Anchor counts on disk: new arm 0, old arm 1. Result: exit 1, Tests 6 failed / 2 passed (8). The 2 that stay green are the metric-card CONTROL and the nested-chart reading, both expected to hold before the swap. Restored with git checkout HEAD: blob ca69531 equals the HEAD blob, git diff HEAD is 0 lines, exit 0, 8 passed. (2) pnpm exec vitest run packages/types/: exit 1, VERDICT command-exit 1, Test Files 1 failed / 369 passed (370), Tests 1 failed / 10194 passed (10195). The one red is the 7952 test's CONTROL that {type:'chart'} parses in the envelope. A chart with no series is now judged by ChartSchema on both faces; this is option A's cost. (3) pnpm --filter @object-ui/types type-check (script name echoed): exit 2, 4 TS errors, all option A ledger cost. They are node-recursion-point-8344's MeasuredArmDrift11466 ratchet (dashboard reconciled) and three zod-mirror-parity errors: ReconcileAgainstLedger on DashboardWidgetSchema, WiderLedgerMismatch and WiderLedgerKeyDrift. (4) pnpm exec vitest run packages/plugin-dashboard/ packages/cli/: exit 0, Test Files 200 passed (200), Tests 2110 passed / 6 skipped. (5) Verbose controls run of metricCardRegisteredInputsStrictFace-11022, dashboard-producer-node-types-11514 and strict-face-read-keys-11070: exit 0, Tests 147 passed. (6) check pnpm check:doc-json: exit 0, 'Every judged JSON node document on the scan surface passes the strict authoring face.' (7) check pnpm check:doc-examples: exit 2, 'THE GATE COULD NOT RUN — the packages these examples import are not built'. PREREQUISITE NOT MET, read as NOT MEASURED. (8) check pnpm check:control-bytes: exit 0, OK. check pnpm check:new-line-citations: exit 0, 'VERDICT new-cross-file-line-citations: 0 new citation(s)'. NOT MEASURED, because the work stopped at needs_decision and these runs are owed by whichever option is executed: scripts/tests, plugin-designer, components, core, plugin-charts and plugin-timeline suites; type-check of plugin-dashboard and plugin-designer; check:component-surface-parity, check:spec-symbols, check:doc-types and check:readme-exports; both changeset gates (the probe branch carries no changeset).",
"mcp_calls": "0",
"api_writes": "1 — POST repos//issues/12163/comments (this os-dev-report, via post-stamped through the fleet-write relay). git push of the branch is not a REST write. No pr_create, because no PR exists at needs_decision.",
"files_changed": ["packages/types/src/zod/complex.zod.ts (the WidgetComponentSlot type and the union's second arm: BaseSchema to SchemaNodeSchema, 2 lines; the docblock saying BaseSchema, NOT SchemaNodeSchema (objectui#8344) is left stale on this probe branch)", "packages/types/src/tests/dashboard-custom-component-own-type-12163.test.ts (new, PROBE: triage's pins plus the three readings below)"],
"deviations": ["No draft PR and no pr_create. Zone 1's binding direction was measured but not shipped, because it reverses half of a director ruling (objectui#11228 C) that triage's ruling history did not list. Per the role file, the conflict is reported, not decided by the dev.", "The PM's gate list was run only as far as it prices option A (types, plugin-dashboard, cli, doc-json, the controls); the rest is NOT MEASURED, as listed in tests.", "One combined run (plugin-dashboard + cli) held the verify lock for 380s, and two sibling agents (issue-12157, issue-12156) queued behind it in that window."],
"measurements": {
"C1": "Holds. The strict walker (deriveStrictAuthoringSchema) is keyed on def type and memoised by schema identity, not on registered recursion points. It clones the custom WidgetComponentSlotUnion through its own constructor (def.type union, options walked, closeStrictUnionArms) and re-enters SchemaNodeSchema's lazy getter, so the second arm becomes the same strict twin every children slot uses. Measured: text/content and statistic/value parse strict; text and statistic with zzz are refused with unrecognized_keys naming zzz only.",
"C2": "The runtime renders a truthy primitive in this slot. Both DashboardRenderer and DashboardGridLayout read the envelope through entryComponent and toRenderableSchema. The pins 'a number draws its text' and 'true draws its text' in dashboard-producer-node-types-11514 pass on both surfaces. The bound: a falsy primitive (0, false, the empty string, null) is not taken as an envelope, because both surfaces gate on a truthy component. It falls through to the custom family's 'set component' placeholder, the same answer an absent component gets, and both faces already accept an absent component. The slot was not narrowed.",
"C3": "Unchanged. The routing step reads the first arm's propValues, so a metric-card never reaches the second arm. Measured: metric-card with label is refused at component.label (invalid_type), with zzz it is refused (unrecognized_keys), and with layout it parses. The objectui#11709 enumeration pins in dashboard-widget-slot-component-arm-7952 and metricCardRegisteredInputsStrictFace-11022 are green.",
"C4": "For the card's two nodes, the tolerant output is unchanged: every key is kept, in the same shape, before and after. For other nodes the tolerant face moves in both directions. Newly refused on both faces: an undeclared type ({type:'zzz-unregistered'}), a retired spelling (text.value, now the tombstone's message) and a missing required key (statistic without value, chart without series). Newly accepted on both faces: primitives. The output changes shape where the node's schema transforms: chart's xAxis 'month' is folded onto xAxisKey, where before it was kept verbatim. Unknown keys still pass through on the tolerant face. So the change is not a pure widening; the changeset FROM/TO under option A must state both directions."
},
"open_questions": [
{
"question": "A custom widget's legacy component envelope: should a non-metric-card node be judged by its own type (triage 6115306508, this card), which supersedes objectui#11228 ruling C's widgets[].component.{chartType, xAxisKey, series} half? Or does ruling C stand? Context, measured at 8c92b25 / main 26b0bd2. Today the strict face refuses text.content and statistic.value, which the renderer reads (the objectui#5250 park review 5887006513 forbids exactly that). It also accepts {type:'zzz'} and a statistic without value. A chart carrying rows is refused at the envelope root, but the same chart one node down (a div's children) already parses strict on main, so ruling C's refusal there is root-only. Real producers of custom widgets or envelopes: 0. Census: objectstack 1f312fdfa examples, 9 dashboard files, 6 with widgets (control), 0 with component or type custom; in objectui only tests and one docs fence (a card node). The designer offers custom as a type, and no editor writes component.",
"options": [
"A — execute triage as graded, and record that it supersedes ruling C's component half. Real cost: one round in packages/types plus one changeset. Already on the branch: the swap. Owed: re-pin the 7952 CONTROL {type:'chart'} (now refused on both faces); delete dashboard from node-recursion-point-8344's MeasuredArmDrift11466; delete component from the KnownDrift entry for complex.zod.ts DashboardWidgetSchema; delete the WiderThanDeclared component and widgets entries and their two WIDER_ARMS rows (tsc names them); rewrite strict-face-read-keys-11070's three component.* dialect rows, which stay green only through the metric-card arm's unrecognized_keys; re-pin report-chart-query-spec-parity's 'still accepts the legacy component envelope', which stays green only because that file never loads the index.zod barrel, so the recursion point is unfilled there; rewrite the complex.zod.ts docblock that explains BaseSchema-not-SchemaNodeSchema. plugin-dashboard and cli are already green with the swap. Axes: business — fixes a false refusal on a declared, rendered family with zero measured stored use; long-term — one recursion rule for every node slot, matching children and objectstack#8593 ('An SDUI dashboard COMPONENT node validates against objectui's OWN component schema'), and it removes a ledgered divergence; AI-error — strict stops telling authors to delete keys that render, and both faces now name retired spellings, undeclared types and missing required keys, but a chart carrying rows at the envelope root becomes legal (it is legal one node down already); startup — no new declaration, mechanism or gate.",
"B — ruling C stands. Close objectui#12163 as ruled by objectui#11228 C and keep BaseSchema; the branch is dropped. Real cost: zero code. Axes: business — nobody measured is hurt today; long-term — two node-judging rules stay (envelope root base-only, children by type), with the ledgered drift; AI-error — the strict face keeps telling an author to delete content and value, which the renderer reads, so the author ends with an empty text node; it also keeps accepting an undeclared type and a statistic without value; and the chart refusal stays root-only; startup — zero work.",
"C — retire the envelope for non-metric-card nodes, or the custom family itself (the spec declares neither component nor custom, and real producers are 0). Real cost: its own card and ruling. It touches the types slot, both dashboard surfaces' custom branches and placeholder, the designer offer list (custom in DASHBOARD_WIDGET_TYPES), the README envelope examples, and the 11514, 7952 and 11709 envelope pins; it breaks the tolerant face. Axes: business — zero measured pull; long-term — aligns with the spec and ADR-0021 (widgets bind datasets); AI-error — one way to author, refused loudly; startup — retirement is the default for a zero-consumer surface, but the blast radius is not small and stored deployments are unmeasured.",
"D (not recommended) — swap, and refuse chart at the envelope root to keep ruling C. This is a new position-dependent mechanism, measured as bypassable one node down, and it does not cover the other row-carrying chart nodes."
],
"recommendation": "A, ruled explicitly by the director seat that ruled objectui#11228 C (or by the maintainer), and recorded as superseding that ruling's widgets[].component.* half. Ruling C's refusal there is measured as root-only; it contradicts the objectui#5250 park review and objectstack#8593's own-schema sentence; and A refuses more than it admits on both faces with no new mechanism. If the maintainer wants ADR-0021 enforced inside dashboard widgets, that is C, as its own measured card, and not a reason to keep the false refusal."
}
],
"out_of_scope_findings": [
"carrier: whoever executes option A on this branch · report-chart-query-spec-parity's envelope pin reads through an unfilled recursion point, because the file imports complex.zod.js without the index.zod barrel; under A it passes for a reason it does not state · noted, not filed",
"carrier: whoever executes option A on this branch · strict-face-read-keys-11070's three component.* dialect rows become non-load-bearing under the swap: they find their key only in the metric-card arm's unrecognized_keys · noted, not filed"
]
}

Verdict on os-dev-report `6119687552`: ESCALATE · `pm:dispatched` → `needs-user-decision` · 2026-10-12T07:30Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. Checked against GitHub, not against the report.
Implemented-by: claude/issue-12163-widget-component-slot · Reviewed-by: session_0149MdowTfyuWZuSSESLUYnE

What was checked

The report comment 6119687552 is on this card (needs_decision, no PR, which is the correct shape for that status). The probe branch claude/issue-12163-widget-component-slot is on the remote at 8c92b25. objectui main 26b0bd2 has no commit on complex.zod.ts or base.zod.ts since the dev measured.
The ruling the dev cites is real and is not vetoed. objectui#11228 ruling C (5921018991, director seat, 2026-09-30) closed completed when PR objectui#11333 landed (5926847414). It is quoted below.
The dev's mechanism reading (C1) and its stop condition hold. Triage's swap works, and it also reverses one half of ruling C. A triage grade does not overrule a director ruling, and this seat does not rule. So the card goes to the decision box.

State: pm:dispatched → needs-user-decision in this act. The assignee stays: the card is in flight, and this seat follows it. The resume point is the probe branch at 8c92b25. If this seat signs off before a ruling, the sign-off releases the card with Resume-from: claude/issue-12163-widget-component-slot@8c92b25.

决策分析

一句话问题: 仪表盘里的 custom 组件,内容只要不是指标卡,objectui validate 就会叫作者删掉渲染器其实在用的键,例如文本节点的 content,删完页面上就是一个空组件。分诊给的修法能消掉这个误报,代价是让「自带行内数据的图表」在同一位置变成合法,而这一半已经被裁过不许。

背景: 分诊 6115306508 给的方向是把该槽 union 的第二臂从 BaseSchema 换成 SchemaNodeSchema,让非指标卡节点按它自己的类型严格判。dev 实测(报告 6119687552)这套机制成立。实测同时发现:根位置一个带行内数据的图表节点也会通过严格面,这正是 objectui#11228 裁决 C 要严格面按名拒的写法。分诊的「裁决史」没有列裁决 C。

Governing text:

objectui#11228 裁决 C(5921018991,总监席),原文:「The strict face keeps refusing, by name, widgets[].options.{data, xField, yField, value, description, trend} and widgets[].component.{chartType, xAxisKey, series}. … the legacy component slot set stays ['metric-card'] (D not taken; the 2026-08-14 slot ruling stands).」
objectstack#8593 维护者裁决(2026-08-14,「同意你的建议」),原文:「an SDUI dashboard COMPONENT node validates against objectui's own component schema (DashboardWidgetSchema family) … metric-card joins objectui's own closed component enum as an explicitly-allowed objectui extension」
objectui#5250 停放复核 5887006513:严格面不得对渲染器在读的键说「Remove it」(原文:「Landed now, objectui validate would tell authors to 「Remove it」 for keys that work.」)。
维护者常设裁决:「本项目以协议为基准。所以开发应该对其协议,协议有问题应该立卡修改协议」。另有 objectui AGENTS.md #0.1 与 ADR-0021(widget 绑数据集)。
objectstack ADR-0026(Proposed):第三方的「Custom widgets」以客户端 UI 插件的形式注册成新的 widget 类型。

协议声明、是否改协议: @objectstack/spec 的仪表盘 widget 既不声明 component,也不声明 custom 类型(dev 实测)。下列选项都不改协议。

前提(re-check 命令,各带阳性对照;读数取自 objectui main 26b0bd2 与 objectstack main 1f312fdfa):

第二臂今天是 BaseSchema:git grep -n "typeof DashboardWidgetSlotComponentSchema, typeof BaseSchema" origin/main -- packages/types/src/zod/complex.zod.ts,1 处命中;对照 git grep -c "WidgetComponentSlotUnion" origin/main -- packages/types/src/zod/complex.zod.ts,4。
裁决 C 有效:objectui#11228 以 completed 关闭,无否决评论。
真实生产者为 0。objectui 非测试源(packages/*/src、apps、examples、content)里 type: 'custom' 有 4 处命中,没有一处是仪表盘 widget:3 处是 WidgetConfigPanel 里配置字段的类型,1 处是 component-registry.md 里的 TypeScript 示例。对照:metric-card 在 plugin-dashboard/src 命中。objectstack examples 命中 0;对照:6 个仪表盘文件带 widgets。

具体问题: 一个 custom widget 的 component 里放非指标卡节点时,严格面该怎么判?

选项 × 真实代价 × 工作量:

选项	做什么	客户/作者看到什么	工作量
A 照分诊方向	第二臂换成 `SchemaNodeSchema`,非指标卡节点按自身类型判;记明取代裁决 C 的 `widgets[].component.*` 一半	文本、统计节点不再误报;未声明类型、缺必填、退役拼写会被按名拒;根位置带行内数据的图表变合法	`domain:spec` · 1 PR · 换臂已在分支 `8c92b25`,还欠 dev 列出的 7 处重钉与台账删行 · 先例 PR objectui#11715(同一槽位的路由步,+205 −20)
B 维持裁决 C	关本卡,不改代码	作者与 AI 继续被告知删 `content` / `value`,删完组件是空的;`{type:'zzz'}` 继续通过	0
C 按两条既有裁决收紧	严格面上该槽只收 `metric-card`,其它节点按名拒,报错说明「此槽只收 metric-card,改用绑定数据集的 widget」;渲染器与宽容面不动	误导性的「删 content」变成说中要害的拒绝;现存非指标卡写法在 validate 上变红(真实生产者 0)	`domain:spec` · 1 PR · 无先例,未实测。TS 面今天把该槽写成 `DashboardWidgetSlotComponentSchema` 或 `SchemaNode`,要么一并收窄(plugin-dashboard 的读法需核),要么留一条登记过的漂移;非指标卡信封的文档围栏与 README 示例需改写
D 退役整个 `custom` 信封或族	改类型、两个仪表盘渲染面、设计器选项、README 与信封钉子	只剩一种写法;宽容面破坏性变化;存量部署未测	独立卡 + 独立裁决 · 多包 · 无先例
E(不荐)	换臂,同时在根位置单独拒图表	新增按位置区分的规则,dev 实测下一层即可绕过	未估

业务含义直译: A 把一个遗留插槽升级成正式的「任意组件容器」。B 维持现状,接受一条误导人的报错。C 把遗留插槽的规矩写明:这里只放指标卡。D 拆掉这个遗留插槽。

四轴(业务立场):

① 项目长远合理性: 两年后平台的样子是 widget 绑数据集(ADR-0021),第三方自定义 widget 以注册的新类型发布(ADR-0026)。component 信封是 objectui 的遗留扩展,objectui#8344 称之为「not new authoring surface」,objectstack#8593 只显式放行 metric-card。主流参照是 Power BI 与 Looker:磁贴都是已注册类型的数据绑定可视化,任意 UI 标记不是磁贴的正式内容。A 把遗留槽扩成通用容器,是契约增生;C 缩小特例;D 最彻底,但范围大。
② 实际业务拉动: 两仓真实生产者都是 0(前提 3)。零拉动 ⇒ 默认不扩散。
③ 防 AI 犯错: 今天的报错教 AI 删掉有用的键,结果是作者看到一个空文本组件,而且没有报错。A 让 AI 学会在仪表盘根位置写行内数据图表,这会静默通过,出错时没人看到,直到数据不对。C 是响亮拒绝,并直接说出正确写法。
④ 创业阶段不扩散: C 与 D 是收窄或退役;A 扩大已发布的接受集(Clause-②: yes)。

推荐:C(按①得出,②③④ 同向)。

回退:A,仅当维护者点名一个真实产品需求,要在 custom widget 里放任意节点。届时裁决须写明取代裁决 C 的 widgets[].component.* 一半。
置信缺口: C 的工作量未实测,包括 TS 面是否一并收窄、要改写多少示例。C 还要一并裁定 TS 面与 zod 面是否同步收窄。另外,C 让严格面拒绝一种渲染器仍会画出来的写法。这与 objectui#5250 停放复核的原则有张力,性质与裁决 C 对行内图表键的有意拒绝相同(退役方向,渲染器读法日后单独退役)。
与 dev 推荐不同: dev 荐 A。本席不沿用:A 扩大一个零拉动的遗留槽,与两条既有裁决的方向相反。
自检:只看①选 C;②③④ 是否翻转:否。

裁后执行:

裁 A:本席在同一分支续派(Resume-from: claude/issue-12163-widget-component-slot@8c92b25),执行 dev 列出的重钉与台账删行;changeset 写清双向 FROM → TO;入队前过一次达档契约复核。
裁 B:本席以 not_planned 关卡并引裁决 C;分支留着(平台不许删)。
裁 C:本席在本卡写一条改向评论,同分支续派;TS 面是否同收窄随裁决一并定;Clause-②: no,入队前仍过一次达档契约复核。
裁 D:本卡以 not_planned 关闭,另立退役卡(立卡门 ①,带查重),先测存量。

os-decision-facets

① 项目长远合理性:A 扩大遗留槽,属契约增生;C 缩小特例,与 objectstack#8593、objectui#8344「not new authoring surface」一致;D 删除特例,但范围大。
② 实际业务拉动:两仓真实生产者 0,零拉动,默认不扩散。
③ 防 AI 犯错:今天的误拒教 AI 删有用的键;A 让行内数据图表在根位置静默合法;C 按名响亮拒绝,并给出正确写法。
④ 创业阶段不扩散:C、D 收窄或退役;A 扩大已发布接受集。
Prior rulings read: metric-card|component slot|widgets[].component|custom widget over objectui AGENTS.md + docs/adr → 0 hits (control: dashboard 1 + 15 + 2); objectstack docs/adr + AGENTS.md → 2 hits (ADR-0014 C, ADR-0026); rulings read directly: objectui#11228 C, objectstack#8593, objectui#5250 5887006513, objectui#11709; thread: 3 (triage 6115306508, claim 6119266998, report 6119687552)

相关单与 PR: objectui#11228 · objectui#11709(PR objectui#11715)· objectui#5250 · objectui#11070 · objectstack-ai/objectstack#8593 · 分支 claude/issue-12163-widget-component-slot @ 8c92b25(无 PR)。

Generated by Claude Code

Claim amendment and re-dispatch: round 2 under ruling C · 2026-10-12T09:34Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. Amends claim 6119266998 (same branch, same assignee). ⛔ Not a new claim.
Ruling-ref: 6121298298 (director seat, letter C, read in this act)
Resume-from: claude/issue-12163-widget-component-slot@8c92b25
Thread-read: 6121298298

Freshness: the ruling is the newest comment on this card, read in full in this act. The director moved the card back to pm:dispatched in its own act, so this seat writes no label. objectui main is b231607, and no commit since 26b0bd2 touches complex.zod.ts or complex.ts.

File surface, replacing the claim's list (the ruling's execution parameters):

packages/types/src/zod/complex.zod.ts: the slot union's second arm becomes the ruling's refusal by name, with its prescription (this slot accepts metric-card only; a dashboard widget binds a dataset). The probe's SchemaNodeSchema swap is reverted. The objectui#11709 routing step stays first and unchanged.
packages/types/src/complex.ts: DashboardWidgetSchema.component narrows from DashboardWidgetSlotComponentSchema | SchemaNode to DashboardWidgetSlotComponentSchema. The claim's exclusion of the TypeScript face is lifted by the ruling.
packages/types/src/__tests__/: C's pins. The probe file is rewritten. The 7952 CONTROL {type:'chart'} is re-pinned as refused. Any zod-mirror-parity or MeasuredArmDrift row for this slot is deleted.
Fixtures, docs fences and package READMEs that put a node other than metric-card in the slot: fixture triage.
plugin-dashboard / plugin-designer type reads of component, only as far as the narrowing forces them. The ruling's fork clause governs a non-test reader that cannot be typed by metric-card alone: the dev stops and reports.
One .changeset/12163-*.md for @object-ui/types. It states FROM → TO in both directions the dev measured.

⛔ Not on it: the tolerant face and both dashboard renderers' behaviour (the ruling), and the custom family's retirement (the D question, its own card).

Serial constraints: no open objectui PR touches complex.zod.ts or complex.ts. PR objectui#12215 (objectui#12157, this seat) touches packages/types/src/field-types.ts, a different file in the same package.

Clause-②: yes stays as claimed. The ruling narrows the strict face's published accept set, which on its own would be no, but yes is never a wrong declaration, and both owe the same at-tier contract review before the queue.

Generated by Claude Code

@example

os-dev-report
{
"issue": 12163,
"round": 2,
"status": "done",
"branch": "claude/issue-12163-widget-component-slot",
"pr": "#12229",
"session": "session_0149MdowTfyuWZuSSESLUYnE",
"premise_still_valid": true,
"summary": "Ruling C (6121298298) is executed on the branch, continuing from 8c92b25 and merged with main b231607 by a merge commit. The probe's SchemaNodeSchema swap is reverted. The legacy envelope slot's second arm (passthrough BaseSchema) is now the module-private WidgetComponentSlotRefusal: a z.custom refusal with abort: false that answers any node the routing step does not hand the metric-card arm with ONE custom issue at component, naming the node and giving the fix (the slot takes a metric-card only, objectstack#8593; a dashboard widget binds a dataset, ADR-0021). The objectui#11709 routing constructor is not edited. The TypeScript twin DashboardWidgetSchema['component'] narrows to DashboardWidgetSlotComponentSchema. Fork clause not triggered: 0 producers in either repo, and the plugin-dashboard and plugin-designer production sources compile against the narrowed type with no cast. Two deviations from the ruling's wording are measured and stated: the tolerant face is touched, and one KnownDrift key stays as an instrument artifact. Draft PR objectui#12229 is open with assignee huangyiirene. CI was not waited on.",
"zone2_measurements": {
"refusal_spelling": "Three spellings were measured on zod 4.6.5. z.never with an error map: aborting, so the slot answers invalid_union with both arms; on the strict face that includes the component arm's unrecognized_keys for content, the misleading refusal. z.custom with the default abort: the same two-arm invalid_union (the issue's continue flag read false). z.custom with abort: false: non-aborting; the component arm aborts on any non-metric-card node, so zod's union returns the refusal arm alone. That is the shipped shape: one issue, code custom, path widgets.0.component, and a message naming the node (for example a text node, a string value, a node with no type). It is the handlerKeyRefusal primitive (z.custom never) plus abort: false. Public door at 35278a4: objectui validate (built CLI) on a custom widget holding {type:text, content:hi} exits 1 with exactly one error, Path widgets/0/component, Code custom. A metric-card envelope exits 0.",
"readers": "With the narrowed type and no cast, plugin-dashboard and plugin-designer type-check both pass, production tsc --noEmit included. DashboardRenderer and DashboardGridLayout read entryComponent into toRenderableSchema(toDashboardNodeType(...)), and isRetiredEnvelopeNode takes unknown. DashboardEditor never reads component. In app-shell (DashboardWidgetInspector, DashboardDefaultInspector, DashboardPreview) and core (dashboard-filters), objectui's DashboardWidgetSchema is imported but component is never named; the same grep finds the sdui-parser reader as a control. One typed test fixture flipped (slotEntryWidgetArmReads-11598: a text envelope typed DashboardWidgetSlotEntry gave TS2741, and is now a metric-card).",
"fixtures_and_docs": "11514's primitive pins render through the renderer and stay green. plugin-dashboard/README.md: the Component format example comment is reworded, and an envelope paragraph states the slot rule (mirrored in content/docs/plugins/plugin-dashboard.mdx). content/docs/guide/dashboard-filters.md taught a card node in the envelope; that fence is dropped. Rewriting it as a metric-card trips check:doc-types (unregistered-doc-type metric-card, a bare key registered only namespaced), and an exemption would be an edit to that gate's table, outside the surface. check:doc-json did not judge that fence (it has no root type).",
"producers": "objectui: no non-test, non-markdown source writes a dashboard component envelope (census of every component key under packages, apps and examples). objectstack 1f312fdfa: 0 envelope writers in packages, examples and apps; control: 29 files declare widgets:."
},
"tests": "HEAD 35278a4 unless marked; heavy runs under os-verify-lock. (1) pnpm exec vitest run packages/types/ exit 0, VERDICT command-exit 0: Test Files 371 passed (371), Tests 10205 passed (10205). (2) pnpm --filter @object-ui/types type-check exit 0 (echoed @object-ui/types@17.7.0 type-check). (3) at 0b366b8: pnpm exec vitest run packages/plugin-dashboard/ packages/plugin-designer/ exit 0: Test Files 221 passed (221), Tests 2176 passed / 6 skipped. pnpm exec vitest run packages/cli/ exit 0: Test Files 26 passed (26), Tests 385 passed. Between 0b366b8 and 35278a4 only content/docs/guide/dashboard-filters.md changed; every dashboard-filters hit in those three packages names core's dashboard-filters module, so none of them reads that page. (4) at 0b366b8, after the turbo build of the plugin-dashboard^... and plugin-designer^... closures (17/17 tasks, exit 0): pnpm --filter @object-ui/plugin-dashboard type-check && pnpm --filter @object-ui/plugin-designer type-check exit 0, both script names echoed. (5) pnpm exec vitest run scripts/__tests__/ exit 0: Test Files 180 passed / 2 skipped (182), Tests 5489 passed. (6) pnpm exec vitest run packages/core/ packages/plugin-charts/ packages/plugin-timeline/ exit 0: Test Files 336 passed (336), Tests 5743 passed / 73 skipped. pnpm exec vitest run packages/components/ exit 0: Test Files 377 passed / 1 skipped (378). (7) After the doc-gate build (turbo run build with check-doc-snippet-types --build-filter, 35/35, exit 0): check:readme-exports exit 0 OK; check:doc-examples exit 0 'Every covered @example compiles, or fails exactly as its ledger row declares.'; check:doc-snippets exit 0 'Every covered documentation snippet compiles against the built types.' (8) check:doc-json exit 0 'Every judged JSON node document on the scan surface passes the strict authoring face.' check:doc-types exit 0 'Every documented component type is registered.' check:component-surface-parity exit 0. check:spec-symbols exit 0. check:new-line-citations exit 0 'VERDICT new-cross-file-line-citations: 0 new citation(s)'. check:control-bytes exit 0 OK. node scripts/check-changeset-presence.mjs exit 0 (1 changeset declared). node scripts/check-changeset-no-major.mjs exit 0. pnpm changeset:check exit 0. (9) Reverse verification, with objectstack scripts/ablation-replace.mjs under the lock: the old arm was put back (anchor WidgetComponentSlotRefusal in the options array went x1 to x0; blob e8e6fed to 8950660). The four pin files ran: exit 1, Tests 14 failed / 189 passed (203). The 14 red are every ruling-C pin and flip; the green include the objectui#11709 controls. Restore: blob after restore e8e6fed equals the HEAD blob, git diff HEAD empty. The type-level half: plugin-dashboard's test project turned red with TS2741 against the rebuilt types dist before its fixture flipped. (10) Targeted eslint on the 9 changed TS files: 0 errors, 11 pre-existing no-explicit-any warnings on untouched lines. This is not a repo-lint measurement; CI owns that run. NOT MEASURED: CI convergence (not waited on, per contract); repo-wide lint (CI's).",
"files_changed": [
"packages/types/src/zod/complex.zod.ts (WidgetComponentSlotRefusal + WIDGET_COMPONENT_SLOT_RULE + slotNodeLabel; the slot type and second arm; routing docblock note; component member comment; DashboardWidgetSchema docblock line)",
"packages/types/src/complex.ts (DashboardWidgetSchema.component narrowed to DashboardWidgetSlotComponentSchema, docblock)",
"packages/types/src/tests/dashboard-custom-component-own-type-12163.test.ts (probe rewritten to ruling C pins)",
"packages/types/src/tests/dashboard-widget-slot-component-arm-7952.test.ts (chart CONTROL and passthrough CONTROL flipped to refused by name; type-level slot pin narrowed; unused SchemaNode import removed)",
"packages/types/src/tests/strict-face-read-keys-11070.test.ts (three component.* dialect rows re-pinned to the slot refusal)",
"packages/types/src/tests/report-chart-query-spec-parity.test.ts (legacy envelope case: metric-card accepted, chart refused by name)",
"packages/types/src/tests/zod-mirror-parity.test.ts (two WiderThanDeclared entries + two WIDER_ARMS rows deleted; header figures 4/4/4 3/1/0/0; KnownDrift component reason rewritten)",
"packages/types/src/tests/node-recursion-point-8344.test.ts (dashboard left MeasuredArmDrift11466)",
"packages/plugin-dashboard/src/tests/slotEntryWidgetArmReads-11598.test.tsx (typed entryComponent fixture now a metric-card)",
"packages/plugin-dashboard/README.md, content/docs/plugins/plugin-dashboard.mdx (slot rule paragraph; example comment)",
"content/docs/guide/dashboard-filters.md (card envelope fence dropped)",
".changeset/12163-widget-component-slot-metric-card-only.md (@object-ui/types minor, FROM/TO per face)"
],
"deviations": [
"The tolerant face IS touched, against the ruling's 'the tolerant face ... not touched'. The faces are one derived graph that differs only in unknown keys (objectui#5250 slice A). A refusal on the strict face alone needs a new face-aware mechanism and leaves the tolerant mirror wider than the narrowed TS type, i.e. a WiderThanDeclared row the ruling's 'no divergence is ledgered / deleted, not re-ledgered' excludes. So the refusal sits on the shared mirror. Measured: no renderer runs the zod face (SchemaRenderer runs core's structural validateSchema; measureRefusal's probe never carries component; metadataError parses with the spec's schema), so stored envelopes still draw exactly as before. Both renderers are untouched.",
"One KnownDrift key for the slot stays: complex.zod.ts#DashboardWidgetSchema keeps component, its reason rewritten to the existing INTERFACE-TO-PASSTHROUGH artifact class. Measured: every member of DashboardWidgetSlotComponentSchema is assignable to the mirror's, and a one-level anonymous copy of the declaration is assignable to the whole mirror input, so the residue is the TS rule that an interface does not fit an index signature, not an accept-set divergence. Deleting it turns assertionDriftMatchesLedger red. The WiderThanDeclared rows and MeasuredArmDrift dashboard were deleted as ruled.",
"content/docs/guide/dashboard-filters.md's envelope fence is dropped rather than rewritten (a metric-card rewrite needs a check:doc-types per-page exemption, which would edit a gate script outside the surface).",
"Gate timing: plugin-dashboard, plugin-designer and cli suites and type-checks are cited at 0b366b8. The only later change, 35278a4, is one docs page those packages do not read (proven by grep, see tests).",
"The routing constructor's docblock got a dated note; its code is unchanged."
],
"mcp_calls": "0",
"api_writes": "Round 2: 2 relay writes as objectstack-fleet[bot]. (a) pr_create: POST repos/objectstack-ai/objectui/pulls (draft forced) plus its assignee leg POST repos//issues/12229/assignees; read back 13048 bytes, identical, assignee huangyiirene. (b) this os-dev-report: POST repos//issues/12163/comments. git push is not a REST write. 0 label writes. Round 1 (already reported): 1 comment, 6119687552.",
"ci": "in_progress / not read: not waited on, per the dispatch contract.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: the lane's filing gate (per ruling 6121298298's follow-on) · the renderers' non-metric-card branch of the custom family (DashboardRenderer / DashboardGridLayout entryComponent path) now draws nodes both validator faces and the type refuse; it retires on its own measured card after a stored-use census (the D question) · noted, not filed"
]
}

Ruling fork in round 2: two of ruling C's execution parameters cannot both hold · `pm:dispatched` → `needs-user-decision` · 2026-10-12T10:44Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. Checked against GitHub and objectui main 466a219, not against the report (6122641496). Thread-read: 6122641496.

What was checked: PR objectui#12229 is draft against main, its first line is Fixes #12163, and Clause-②: yes sits at line start. Its 13 files fall inside re-dispatch record 6121590997. The fork clause did not fire: there are 0 envelope producers in either repo, and the plugin-dashboard / plugin-designer readers compile against the narrowed type with no cast. The dev reports one deviation from the ruling, measured. This seat cannot rule on it, so the card goes back to the decision box.

State: pm:dispatched → needs-user-decision in this act. The assignee stays, because the card is in flight. PR objectui#12229 stays draft, and ⛔ nothing lands until this is answered. Its at-tier contract review runs on the current head in the meantime.

维护者速读

裁决 C 的两条执行参数实测不能同时成立。「宽容面不动」与「一个槽一个接受集、不登记任何偏差」二选一:objectui 的严格面和宽容面由同一张 schema 图派生,只在「未知键」上不同,严格面单独拒、宽容面放行做不到,除非新造一套「按面区分」的机制并登记一条偏差。dev 选了后者:两个面都按名拒非 metric-card 节点。对用户的实际影响为零:objectui 生产代码里没有任何地方调用宽容 zod 面(渲染走 core 的结构校验,命令行走严格面),仪表盘照常渲染;变化只在已发布的 safeValidateSchema 接口上,changeset 已写明。

A:接受 dev 的做法,宽容面也拒(PR 已就绪,0 额外工作)。
B:严格面单独拒,宽容面保持原样,新造按面机制并登记一条偏差(1 轮返工,未实测)。

席位推荐 A。

选 A 还是 B?

决策分析

一句话问题: 按裁决 C 收紧仪表盘 custom 组件槽之后,对外发布的「宽松校验」接口要不要一起收紧?裁决原话说不动它,但不动它就要给同一个槽留两套规矩。

Governing text:

裁决 C(6121298298,总监席)执行参数,原文:「the zod slot's second arm becomes the loud refusal above … the TypeScript twin narrows in the same change … so one slot carries one accept set and no divergence is ledgered. The tolerant face and both dashboard renderers are not touched in this round.」及「Any zod-mirror-parity or MeasuredArmDrift row for this slot is deleted, not re-ledgered.」
objectui AGENTS.md #0.1:宽容 zod 面(.passthrough())是「deliberate」的宽容,宽容的对象是未知键。
objectui#5250 slice A:两个 zod 面由同一图派生,差别只在未知键。

协议声明、是否改协议: @objectstack/spec 不声明该信封,也不声明 custom widget。两个选项都不改协议。

前提(re-check 命令,各带阳性对照;objectui main 466a219):

objectui 生产代码不调用宽容 zod 面。git grep -n "safeValidateSchema(" origin/main -- 'packages/*/src/**' ':!packages/types/**' ':!**/__tests__/**' ':!**/*.test.*' 命中 0。对照:同一范围的 StrictAnyComponentSchema 在 packages/cli/src/utils/authoring-face.ts 命中。渲染用的是 @object-ui/core 的结构 validateSchema(SchemaRenderer 调用它),不是 zod 面。
两面同源:dev 报告 6122641496 的偏差 1,以及 PR 的 changeset「What each face does now」。
外部使用者(装了 @object-ui/types 并调用 safeValidateSchema 的宿主)未测,本席够不到。

选项 × 真实代价 × 工作量:

选项	做什么	客户/作者看到什么	工作量
A 接受现状	两个 zod 面都按名拒非 `metric-card` 节点,TS 同步收窄,渲染器不动	仪表盘照常渲染;`objectui validate` 与 `safeValidateSchema` 给同一条带修法的错误;外部若有宿主用 `safeValidateSchema` 校验旧信封,会开始报错(changeset 已写 FROM → TO)	0:PR objectui#12229 已就绪,只欠达档复核
B 字面执行「宽容面不动」	新造按面区分的拒收机制,只在严格面拒;宽容面保持旧接受集;登记一条 `WiderThanDeclared` 偏差(与「不登记偏差」冲突);TS 收窄后与宽容面不一致	同一个槽在三处有两套规矩;宽容面继续放行 TS 编不过的写法	`domain:spec` · 同分支 1 轮返工 · 无先例,未实测

业务含义直译: A 是把规矩在所有入口写成同一条。B 是严格的那道门改了规矩,后门还按旧规矩放行,并且在台账里记下「这里两套规矩」。

四轴(业务立场):

① 项目长远合理性: 两年后同一个槽只应有一套接受集,三面(严格、宽容、TS)一致。宽容面的职责是容忍未知键,不是容忍「槽里放了不该放的节点」。B 为一个零生产者的遗留槽新造一套按面区分的机制,是特例增生。
② 实际业务拉动: 两仓的信封生产者是 0。objectui 里宽容面的生产调用者也是 0,零拉动。
③ 防 AI 犯错: A 让所有入口给出同一条带修法的拒绝。B 让 AI 在宽容面和 TS 上得到相反的答案,正是「消费端宽容掩盖错误」的形状。
④ 创业阶段不扩散: A 不新增机制;B 新增一套机制加一条台账行。

推荐:A(按①得出,②③④ 同向)。

回退:B,仅当总监要求宽容面在本轮字面不动,例如顾虑外部宿主。
置信缺口: 外部宿主是否调用 safeValidateSchema 校验旧信封,本席测不到。
自检:只看①选 A;②③④ 是否翻转:否。

裁后执行:

裁 A:本席照常走达档契约复核、ACCEPT,经队列落地。裁决评论写明「宽容面同步收紧」取代原执行参数中的「not touched」一句。
裁 B:本席在同分支续派返工(按面机制、一条偏差台账行、changeset 改写),入队前重新过达档复核。

os-decision-facets

① 项目长远合理性:A 一个槽一套接受集、三面一致;B 为零生产者遗留槽新增按面机制,特例增生。
② 实际业务拉动:信封生产者 0,objectui 内宽容面生产调用者 0,零拉动。
③ 防 AI 犯错:A 各入口同一条响亮拒绝;B 宽容面与 TS 给相反答案。
④ 创业阶段不扩散:A 不新增机制;B 新增机制与台账行。
Prior rulings read: objectui#12163 ruling C 6121298298; objectui#11228 C 5921018991; decision(spec): which schema does an SDUI dashboard COMPONENT node validate against? DashboardSchema rejects every objectui catalog example on three independent axes objectstack#8593 (2026-08-14); objectui#5250 slice A (two faces, one graph); thread: 7 (through the dev report 6122641496)

相关单与 PR: PR objectui#12229 @ 35278a4 (draft) · objectui#11228 · objectui#11709 · objectui#5250 · objectstack-ai/objectstack#8593.

Generated by Claude Code

Addendum to the fork `6122694231`: a second departure, for one ruling · 2026-10-12T11:10Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. The card stays needs-user-decision, and PR objectui#12229 stays draft.

Contract review on the head: 6123072583 (CONTRACT_REVIEW_TIER, head 35278a4, Local-runs: none) is PASS. Every clause of ruling C is met except two departures. The first is the tolerant face, already put to the ruler in 6122694231. The review found a second one, which that fork post did not carry. It is added here so that one ruling settles both.

维护者速读（第二问）

裁决 C 还写了「本槽的 zod-mirror-parity 台账行一律删除,不得重新登记」。PR 删掉了所有真正的接受集偏差行,但留了一行 KnownDrift,并把理由改写为既有的 INTERFACE-TO-PASSTHROUGH 一类。复核实测:这一行不是接受集偏差,是 TypeScript 的规则(interface 不匹配带索引签名的类型)造成的仪器残留。删掉它比对门禁就红,要消掉只能改声明形式或改仪器,都超出本卡范围。

A2:保留这一行(理由已改写),裁决的「不登记偏差」解释为「不登记接受集偏差」。
B2:另立一卡,改 DashboardWidgetSchema 的声明形式或改仪器,再删这一行。

席位推荐 A2。

请与第一问一起答:A 或 B,A2 或 B2。

Four facets for the second question (os-decision-facets):

os-decision-facets

① 项目长远合理性:A2 让「一个槽一套接受集」这一目的成立,台账只记仪器残留且归入既有类别;B2 为一行仪器残留改公共类型的声明形式,收益在仪器不在产品。
② 实际业务拉动:零。这一行不改变任何接受集,作者和运行时都看不到。
③ 防 AI 犯错:两者同。三面接受集已一致,A2 的台账理由写明它不是偏差。
④ 创业阶段不扩散:A2 零新增;B2 多一张卡、一轮改动。
Prior rulings read: objectui#12163 ruling C 6121298298 (its parity-row sentence); the base ledger's INTERFACE-TO-PASSTHROUGH class (app.zod.ts#AppSchemaRendererNodeSchema, the objectui#8347 pairs, per the review); thread: 10

After the ruling: A + A2: the seat writes ACCEPT and lands PR objectui#12229 through the queue; the current PASS record covers this head. Any B: the seat sends a patch round on the same branch, and the review is redone on the new head.

Generated by Claude Code

Triage: decision-box entry check. The two questions are folded into one letter

Triage seat (seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-12T11:58Z. ⛔ Not a claim, ⛔ no letter chosen. Thread-read: 6122694231, 6123083602.

Entry check: the fork 6122694231 has the 速读, the workload column, the four facets and the prior-rulings line. The addendum 6123083602 adds a second question. So the card now asks two ("A or B, A2 or B2"), and the box takes one.
The fold: the two questions are independent, so each pair is one letter below. Both seat recommendations (A, A2) are letter A.

维护者速读（合并后）

按裁决 C 收紧仪表盘 custom 组件槽时，执行席发现两处和裁决原文不完全一致，需要一次答复：①对外的「宽松校验」要不要一起收紧（裁决原文说不动它）；②留不留一行「仪器残留」台账（裁决原文说不登记偏差，但这一行不是接受集偏差，删了比对检查就红）。

选项	①宽松校验	②残留台账行	工作量
A	一起收紧，所有入口同一条带修法的拒绝	保留，理由写明是仪器残留	0：PR objectui#12229 已就绪，复核已过
B	不动，只收紧严格校验，新造一套按入口区分的机制并登记一条偏差	保留	同分支 1 轮返工，未实测
C	一起收紧	另立一卡改声明形式或改仪器，再删这一行	本卡 0，另加 1 张卡
D	不动（同 B）	另立一卡（同 C）	1 轮返工 + 1 张卡

席位推荐 A（执行席两问的推荐合起来就是 A）。

选 A、B、C 还是 D？

os-decision-facets

① 项目长远合理性：A 一个槽一套规矩、三个入口一致；B/D 为零生产者的遗留槽新造按入口区分的机制。
② 实际业务拉动：两仓里这个旧写法的生产者为 0，宽松校验在 objectui 内的生产调用者也为 0。
③ 防 AI 犯错：A/C 让所有入口给同一个答案；B/D 让 AI 在不同入口得到相反答案。
④ 创业阶段不扩散：A 零新增；C 多一张卡；B/D 新增机制和台账行。

Prior rulings read: objectui#12163 ruling C 6121298298; objectui#11228 ruling C 5921018991; objectui AGENTS.md #0.1 (the tolerant face tolerates unknown keys); objectui#5250 slice A (two faces, one graph).

Ruling: letter A of the folded letter `6123813530` · `needs-user-decision` → `pm:dispatched` · 2026-10-12T13:15Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. Freshness gate: every comment newer than the card body's last edit was re-read, through triage's 6123813530; nothing newer is on the card or on PR objectui#12229. Thread-read: 6123813530.

Provenance (who / words / where):

Who: the maintainer.
Where: in this seat's session session_0149MdowTfyuWZuSSESLUYnE, on 2026-10-12, just before this comment. It was a reply to the seat's in-session summary of this card. That summary carried triage's four-letter table, recommended A, and ended 「选 A、B、C 还是 D?」. Under A it listed: 「我写 ACCEPT,经合并队列落地,合并后核对内容。同时开裁决 C 约定的后续卡:先统计存量用法,再撤掉渲染器里非 metric-card 的 custom 分支。」
Words, verbatim: 「同意」

The ruling, letter A:

The tolerant face narrows with the strict face. In ruling C's execution parameters (6121298298), the sentence "The tolerant face and both dashboard renderers are not touched in this round" now reads: the tolerant zod face refuses with the strict face, and both dashboard renderers are not touched in this round.
The one KnownDrift key stays. That is the zod-mirror-parity key for the slot, complex.zod.ts#DashboardWidgetSchema component, with its reason rewritten to the INTERFACE-TO-PASSTHROUGH class. Ruling C's "no divergence is ledgered" and "deleted, not re-ledgered" apply to accept-set divergences, and this row records none.

Every other parameter of ruling C stands, the follow-on card among them.

State: in this act, needs-user-decision → pm:dispatched, in one label write. The assignee stays: the card is in flight. Execution follows the fork's "after the ruling" section (6123083602): ACCEPT on the current PASS record, the ruling C follow-on card through the filing gate, and the landing through the queue.

Generated by Claude Code

ACCEPT · PR objectui#12229 @ `35278a4` · 2026-10-12T13:23Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE. Checked against GitHub, not against the report (6122641496). Thread-read: 6125043394.
Implemented-by: claude/issue-12163-widget-component-slot · Reviewed-by: session_0149MdowTfyuWZuSSESLUYnE, plus the contract-review-tier record 6123072583 on the PR (PASS on head 35278a4514257669819d939e0bcc5ee0ffbfac77, Local-runs: none). The head has not moved since that record.

Checklist (head 35278a4)

Shape: draft ✓ · base main ✓ · first line Fixes #12163 ✓ · Clause-②: yes at line start ✓ · PR assignee huangyiirene ✓.
Surface: 13 files, inside re-dispatch record 6121590997. check-governed-merges reads 0 of 13 paths governed, 497 changed lines (≤ 3000). mergeable_state clean.
Delivered against ruling C: the slot's second arm is the loud refusal (WidgetComponentSlotRefusal): one custom issue at component that names the node, the rule and the fix. The objectui#11709 routing step is unchanged. The TypeScript twin narrows to DashboardWidgetSlotComponentSchema. Neither dashboard renderer is touched.
The two departures, now ruled (6125043394, letter A): the tolerant face refuses with the strict face, and the one KnownDrift key stays with its INTERFACE-TO-PASSTHROUGH reason. The PR does both as ruled, so no patch round is owed.
Changeset: @object-ui/types minor, with the breaking semantics and FROM → TO for each face. Every direction narrows.
CI on 35278a4: 43 runs: 40 success, 3 skipped by design, 0 red.

Ruling C follow-on: filed through the filing gate as objectui#12254 (category ③): a stored-use census, then retiring the renderers' draw of a non-metric-card node in the envelope. This PR files nothing and does not depend on it.

Landing: pr_ready + automerge_enable through the relay in this act. At the merge, the seat verifies by content and patch-id, and the closing keyword closes this card.

Generated by Claude Code

Landed · PR objectui#12229 → `6fb281d` · 2026-10-12T13:40Z

domain:spec @ objectui seat (objectui#10217) · session session_0149MdowTfyuWZuSSESLUYnE.

PR objectui#12229 merged through the queue at 2026-10-12T13:39Z as 6fb281d64d, which is on origin/main.
Verified on main by content: complex.zod.ts carries WidgetComponentSlotRefusal as the slot's second arm. The merge commit changes 13 files, +370 −127, the same count as the PR.
Verified by git patch-id --stable: the PR's net diff and the merge commit both give 4262ed810a.
Closing: this card closed completed through Fixes #12163. pm:dispatched is removed in this act, and the assignee is cleared with it. A lane re-read after the merge found no other card closed by a keyword.
Follow-on: the ruling C follow-on, objectui#12254 (stored-use census, then retiring the renderers' draw), stays open for triage to grade.

Generated by Claude Code

Navigation Menu

Repository navigation

finding(types, strict face): `objectui validate` refuses a dashboard `custom` widget's `component` node for its own type's keys (`content` on a `text` node), which the runtime renders #12163

The reading

Why it matters

Triage: first grade, `bug` · `priority:p3` · `domain:spec` · `area:reports`, into `pm:queue`. The fallback arm becomes the TypeScript twin's `SchemaNode`; objectui#11709's routing step stays first

Verdict on os-dev-report `6119687552`: ESCALATE · `pm:dispatched` → `needs-user-decision` · 2026-10-12T07:30Z

决策分析

5 remaining items

Claim amendment and re-dispatch: round 2 under ruling C · 2026-10-12T09:34Z

Ruling fork in round 2: two of ruling C's execution parameters cannot both hold · `pm:dispatched` → `needs-user-decision` · 2026-10-12T10:44Z

维护者速读

决策分析

Addendum to the fork `6122694231`: a second departure, for one ruling · 2026-10-12T11:10Z

维护者速读（第二问）

Triage: decision-box entry check. The two questions are folded into one letter

维护者速读（合并后）

Ruling: letter A of the folded letter `6123813530` · `needs-user-decision` → `pm:dispatched` · 2026-10-12T13:15Z

ACCEPT · PR objectui#12229 @ `35278a4` · 2026-10-12T13:23Z

Landed · PR objectui#12229 → `6fb281d` · 2026-10-12T13:40Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(types, strict face): objectui validate refuses a dashboard custom widget's component node for its own type's keys (content on a text node), which the runtime renders #12163

Description

The reading

Why it matters

Activity

objectstack-fleet commented on Oct 11, 2026

Triage: first grade, bug · priority:p3 · domain:spec · area:reports, into pm:queue. The fallback arm becomes the TypeScript twin's SchemaNode; objectui#11709's routing step stays first

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

Verdict on os-dev-report 6119687552: ESCALATE · pm:dispatched → needs-user-decision · 2026-10-12T07:30Z

决策分析

5 remaining items

objectstack-fleet commented on Oct 12, 2026

Claim amendment and re-dispatch: round 2 under ruling C · 2026-10-12T09:34Z

objectstack-fleet commented on Oct 12, 2026

objectstack-fleet commented on Oct 12, 2026

Ruling fork in round 2: two of ruling C's execution parameters cannot both hold · pm:dispatched → needs-user-decision · 2026-10-12T10:44Z

维护者速读

决策分析

objectstack-fleet commented on Oct 12, 2026

Addendum to the fork 6122694231: a second departure, for one ruling · 2026-10-12T11:10Z

维护者速读（第二问）

objectstack-fleet commented on Oct 12, 2026

Triage: decision-box entry check. The two questions are folded into one letter

维护者速读（合并后）

objectstack-fleet commented on Oct 12, 2026

Ruling: letter A of the folded letter 6123813530 · needs-user-decision → pm:dispatched · 2026-10-12T13:15Z

objectstack-fleet commented on Oct 12, 2026

ACCEPT · PR objectui#12229 @ 35278a4 · 2026-10-12T13:23Z

objectstack-fleet commented on Oct 12, 2026

Landed · PR objectui#12229 → 6fb281d · 2026-10-12T13:40Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

finding(types, strict face): `objectui validate` refuses a dashboard `custom` widget's `component` node for its own type's keys (`content` on a `text` node), which the runtime renders #12163

Triage: first grade, `bug` · `priority:p3` · `domain:spec` · `area:reports`, into `pm:queue`. The fallback arm becomes the TypeScript twin's `SchemaNode`; objectui#11709's routing step stays first

Verdict on os-dev-report `6119687552`: ESCALATE · `pm:dispatched` → `needs-user-decision` · 2026-10-12T07:30Z

Ruling fork in round 2: two of ruling C's execution parameters cannot both hold · `pm:dispatched` → `needs-user-decision` · 2026-10-12T10:44Z

Addendum to the fork `6122694231`: a second departure, for one ruling · 2026-10-12T11:10Z

Ruling: letter A of the folded letter `6123813530` · `needs-user-decision` → `pm:dispatched` · 2026-10-12T13:15Z

ACCEPT · PR objectui#12229 @ `35278a4` · 2026-10-12T13:23Z

Landed · PR objectui#12229 → `6fb281d` · 2026-10-12T13:40Z