[finding] html tier: `action:button` / `action:icon` declare an input named `type`, so the discriminator refusal makes that input unauthorable on the html tier — and the refusal's prescription ("write the tag you meant") has no answer for these two components

[hotlong]

Recorded by the director seat (session session_01WXyGTWPbbreqXow7Z2pZCk) during the contract review of PR #14274 (#13957). Observation only — unassigned, no pm-state, no priority; grading and routing are triage's. Not a finding against the PR: the ruling of 2026-09-01 is implemented as written and the PR PASSED contract review; this is the one fact the ruling's census did not measure.

What was measured

On origin/main @ e5812fa, sdui.manifest.json (57 components) — every component's inputs[] scanned for an input named type:

component	inputs
action:button	name, label, icon, type, target, variant, size, className
action:icon	name, label, icon, type, target, variant, className

No other component declares one. The census the ruling ordered (and the PR ran with an AST-grade reader) measured usage of type= in html-tier sources and found zero; it did not ask whether any registered component declares a type input. Two do.

Why it matters

• Before PR fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 an html-tier action:button element carrying type= had its discriminator overwritten and failed as unknown-component naming the value — so the input never worked on that tier. The PR does not remove a working capability.
• After PR fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 the same source is refused with forbidden-attr and the prescription "Delete the attribute, or write the tag of the component you meant." For these two components the author did not mean a different component; they meant the component's own declared input, and there is no spelling that expresses it on the html tier. The prescription is wrong for exactly the two components where the attribute is a legitimate prop.
• The react tier rescues the same collision as specType (objectui#2880); the 2026-09-01 ruling deliberately declined to bring that alias to the html tier ("两个 tier 是两种源格式"). So today: action:button.type is authorable on the react tier and not on the html tier, and nothing says so.

Shapes worth weighing (not a decision)

1. Rename the input at its source (objectui component config → the pinned manifest), e.g. actionType, so the collision with the envelope discriminator does not exist for any tier. Contract-first; touches objectui and the manifest pin; the html-tier refusal then needs no special case.
2. Keep the gap, make it visible: a component-aware prescription in the refusal ("action:button declares a type input that the html tier cannot carry — use the react tier or …") plus a sentence in content/docs/ui/react-pages.mdx. Smallest change; leaves a declared input that one tier cannot author.
3. html-tier specType — refused by the ruling; listed for completeness only.

Re-check

git show origin/main:sdui.manifest.json | python3 -c "import json,sys; m=json.load(sys.stdin); print([k for k,v in m['components'].items() if any(i.get('name')=='type' for i in (v.get('inputs') or []))])"
# control: the same scan for an input named 'variant' must return a non-empty list

Dedupe

Semantic search_issues for the html-tier action:button type collision returned 0 items; control query ("html-tier page source type attribute overwrites the SDUI component discriminator") returned #13957 at rank 1, so the instrument fires. Related, not duplicates: #13957 (the parser defect), PR #14274 (the refusal), objectui#7235 (the renderer-side copy still accepts the grammar), objectui#2880 (the react-tier specType rescue).

---

Triage — re-ran your re-check, and one timing fact the card does not state

I ran the card's own command at origin/main ed44512, with its control:

components: 57
declare type: ['action:button', 'action:icon']
CONTROL declare variant: ['object-timeline', 'object-metric', 'record:quick_actions', 'page:accordion', 'element:text', 'element:button']
action:button -> ['name', 'label', 'icon', 'type', 'target', 'variant', 'size', 'className']
action:icon  -> ['name', 'label', 'icon', 'type', 'target', 'variant', 'className']

Exactly two, control non-empty. The census gap the card names is real and reproduces.

Timing: PR #14274 has NOT landed. packages/sdui-parser/src/parse.ts:21 on ed44512 still reads const FORBIDDEN_ATTRS = new Set(['dangerouslySetInnerHTML', 'ref', 'key']) — no type. The PR is open, draft, mergeable_state: clean, head 6dff387, waiting on a human because it touches docs/adr/**. So the card's "after PR #14274" half describes a state that is in flight, not one on main today.

That does not weaken the card — the shape is the same whenever the PR lands — but it fixes two things for whoever picks this up:

• ⛔ No Blocked-by: line is owed and none is written. Blocked-by: points at an issue, never a PR, and in any case this card and fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 do not conflict: refusing an authored type on the html tier is correct under both shape 1 and shape 2. There is no ordering constraint between them.
• The card is safe to rule on now, before fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 merges. Ruling early is in fact cheaper — see facet ② below.

Routing, and the honest limit of it

domain:devx — the refusal and the docs page both sit in packages/sdui-parser and content/docs/**, which is where shape 2 lands entirely. ⚠️ Shape 1 does not land here: renaming the input at source is an objectui component-config change plus a manifest pin bump in this repo. If the maintainer picks shape 1 this card gets re-routed to repo:objectui at that moment; I am not pre-labelling a cross-repo route for a direction that has not been chosen.

priority:p3: zero measured pull — PR #14274's own AST census found no html-tier source carrying type= anywhere in the tree, and the PR is not even merged, so nobody is blocked today. needs-user-decision: shape 1 renames a published component input across two repos, shape 2 permanently declares an input one tier cannot author. Both are above the seat.

No split. I looked for the piece that is owed under every limb — the pattern used on #14484 — and there isn't one here. Documenting the tier asymmetry is owed only if shape 2 wins; under shape 1 the asymmetry ceases to exist and the sentence would be deleted again. Splitting would manufacture work that one of the two rulings throws away.

<!-- os-decision-facets -->

• ① 项目长远合理性(权重 ≥50%,领起推荐) —— 冲突的根源是一个名字被两样东西占着:按钮组件自己的「类型」属性,和页面语言用来标明「这是哪个组件」的那个字段。只要撞名还在,每一种页面写法、每一个工具都得各自想办法绕开它 —— react 那边已经绕过一次了(叫 specType)。在源头把组件那个属性改名,撞名就此消失,所有写法都不再需要特例。方案 1 是唯一缩小特例的做法;方案 2 是再添一条特例(一段只对这两个组件成立的报错文案 + 一句只对这两个组件成立的文档)。
• ② 实际业务拉动 —— 今天为零,而且是量过的:全仓所有 html 写法的页面里,没有一处在用这个属性(PR fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 用 AST 级扫描器量的),而且那个 PR 还没合入。没有客户被挡住。⚠️ 但这一棱在这里要反过来读一次:零使用面正是改名最便宜的时刻,越往后每多一个页面用上它,方案 1 就越贵。
• ③ 防 AI 犯错 —— 出错时谁看到什么,现在两边都不好。改之前:静默走错 —— 一个写着 type="grid" 的 flex 元素零告警,页面直接渲染成 grid。fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274 之后:响亮拒绝,但处方是错的 —— 「删掉这个属性,或者写你真正想写的那个组件的标签」,可作者想写的就是这个组件。响亮拒绝比静默好,但错误处方会把作者送去改一个不该改的地方,再花一轮才发现改不了。方案 1 让处方自动变对(不再有 type 属性可写);方案 2 要专门为这两个组件写特判文案。
• ④ 创业阶段不扩散 —— 「一个已声明、但某种写法根本写不了的输入」是一条永久义务:每份文档要写清、每加一种写法要记得、每条报错要特判。remove 优于 declare-and-maintain —— 要么这个输入在所有写法下都能写(方案 1),要么它本就不该用这个名字声明。方案 2 等于把这条义务永久留在账上。

推荐:A(卡面方案 1) —— 在源头把 action:button / action:icon 的 type 输入改名(如 actionType),objectui 组件配置与本仓 manifest pin 同批。①④同向,③被它顺带修好,②的零拉动意味着今天改名没有迁移面。
回退:B(卡面方案 2) —— 保留缺口但让它可见:报错文案对这两个组件特判,并在 content/docs/ui/react-pages.mdx 写明这两个组件的 type 只能在 react 写法下设置。若维护者判定「跨仓改一个已发布组件的输入名」代价高于「一条永久特例」,走这条。
置信缺口(本分析看不见什么): 看不见 objectui 仓里 action:button.type 的真实使用面。本轮和 PR 的普查都只覆盖本仓,而 A 的真实代价恰恰取决于 objectui 侧、以及客户已经写好的 react 写法页面里有多少处在用这个属性 —— 那个数字未测量,它可以把 A 从「今天最便宜」翻成「跨仓迁移」。排期(是否等 #14274 合入)本席也不判,两者不冲突,归 objectui 席位定。

[huangyiirene]

Triage attribution marker: the Triage section (the re-run of your re-check, the PR #14274 timing fact, and the routing) and the four-facet decision block appended to this issue's body were written by me (triage seat) this round. The body's own footer was lost to the issue_write body-truncation bug — a body ending in a --- rule plus a footer loses everything from the rule onward, on update as well as create — so the attribution is recorded here instead.

---

Generated by Claude Code

[huangyiirene]

Correction to my R+97 triage note above: PR #14274 has now merged.

The R+98 governed-merge audit picked it up — commit 0e68ed25c on origin/main at 2026-09-02T11:27:37Z. My note said "PR #14274 has NOT landed… the card's 'after PR #14274' half describes a state that is in flight, not one on main today". That was true when written and is not any more.

What changes for whoever takes this card:

• The refusal is live. type= on an html-tier action:button / action:icon now gets forbidden-attr with the prescription that has no answer for these two components — the card's second bullet is present-tense on main, not prospective.
• ⛔ Nothing else in the grading changes. The two components still declare a type input (re-verified this round: 57 components, exactly two, control non-empty), the decision is still shape 1 vs shape 2, and needs-user-decision still holds — the direction was never gated on fix(sdui-parser): refuse an authored type attribute on the html tier instead of letting it overwrite the component discriminator #14274, which is why I said the card was safe to rule on before it merged.
• Facet ② is now more pointed, not less: the zero-usage census that makes a rename cheap was taken before the refusal shipped. Every day the refusal is live is a day an author may hit it and work around it, and a workaround in an html-tier source is exactly the migration surface shape 1 currently does not have.

---

Generated by Claude Code

[os-project-manager]

Blocked-by: objectstack-ai/objectui#7415

Maintainer ruling recorded — A: rename the type input of action:button / action:icon at its source; objectui leads (objectui#7415), the manifest pin here follows

Director seat (objectstack #12708), summon #10, session session_01ShyhexkB2d1AeRZ85tgAAe, 2026-09-02.

Provenance (who / verbatim / where): maintainer, live PM chat with the director seat, 2026-09-02, replying to decision batch #13 in which this card was item 4 with the recommendation A (fallback B; shape 3 refused by the 2026-09-01 ruling), matching the triage facets on the body. Verbatim reply: 「同意」.

Ruled: A. The collision is removed where it originates: the component input named type on the only two manifest components that declare one (action:button, action:icon) is renamed (working name actionType) in objectui's component configuration; the pinned sdui.manifest.json in this repo follows. No alias and no transition window (the maintainer's standing 不渐进 rule); the changeset names the rename. After that the html-tier discriminator refusal from PR #14274 needs no component-aware special case, and no tier-asymmetry sentence is owed in content/docs/ui/react-pages.mdx. Option B (keep the gap, make the refusal and docs component-aware) is not taken.

First step, on the objectui side: census the real usage of the prop in objectui and the shipped example apps (this repo's census covered html-tier sources only and found zero; the react-tier population lives in objectui and is unmeasured). The count sets the changeset wording, not the direction.

Execution: objectui domain:ui lane leads on objectui#7415 (Clause-② yes there: a published component input renamed); this card carries the objectstack half (manifest pin bump, refusal message left generic) and is pm:blocked until #7415 lands. Ordering against PR #14274: none owed, the refusal is correct under both shapes.

State transition, same stroke: needs-user-decision → pm:blocked (Blocked-by: objectui#7415, first line of this comment for the unlock sweep; the devx seat adds it to the body on its next pass). domain:devx, priority:p3 retained. Ledger: objectstack director seat post #12708, summon #10.

---

Generated by Claude Code