showcase 的 component-gallery 在 `element:button` 上授权 `actionName`,renderer 只读 `action` —— "Create Task" 按钮点了没反应

[qq9340100]

在 #5776(tab key → value)的闸门实跑里顺手量到,与本单同一形状,另开记录。

实测

examples/app-showcase/src/ui/pages/index.ts:82(page showcase_component_gallery):

{ type: 'element:button', properties: { label: 'Create Task', actionName: 'showcase_new_task' } },

• schema 侧:ElementButtonPropsSchema(packages/spec/src/ui/component.zod.ts:598)声明的是 label / variant / size / icon / iconPosition / disabled / action(InlineActionSchema)—— 没有 actionName。schema 是 strip 模式,parse 把它剥掉。

• renderer 侧:objectui 的按钮渲染器(packages/components/src/renderers/basic/elements.tsx:220)只读 props.action,全文件不读 actionName;handleClick 的第一行就是

  if (!action || running) return;
  

  所以按钮正常渲染、正常可点,点击是空转 —— 不报错、不导航、不执行动作。

os validate 对 showcase 语料实跑,这一条稳定出现:

⚠ page "showcase_component_gallery" · element:button: `actionName` is not a prop `element:button` declares
  (ComponentPropsMap, @objectstack/spec/ui), so nothing verifies it …

为什么单独开

这是 #5068 component-props-unknown-key warning 期清单里剩下的两条之一(另一条 element:button 的 action.params 形状之争已由 #5777 跟踪),此前没有对应的单。#5068 距离 error 升级正卡在这类清空上。

修法(待分诊裁定)

倾向改语料:把 actionName: 'showcase_new_task' 改写成 action: { name: 'showcase_new_task', … },与页面上其它按钮以及 element-button-action 的渲染路径一致 —— 即声明侧与 renderer 早已一致(action),错的是这一处语料。

需要先确认的一点:showcase_new_task 是否是一个已注册的对象动作、以及它期望的 type/target,这决定 action 里要补哪几个键;改完应当在浏览器里点一次确认真的执行(本条只是静态量出来的,没有实跑过点击)。

另一条路是给 element:button 声明 actionName 作为「按名引用已注册动作」的简写 —— 但那是给同一件事加第二种拼法,与 Prime Directive #12 相悖,除非有真实业务拉力,否则不建议。

[os-zhuang]

Triage: pm:queue + domain:devx.

• Landing anchor (re-verified on origin/main @ 04476e7): examples/app-showcase/src/ui/pages/index.ts:82 still carries actionName: 'showcase_new_task'; schema declares action (ElementButtonPropsSchema) and the objectui renderer reads only props.action — the corpus is the wrong side, as the card concludes. Fix = one corpus edit + a browser click-through (the card notes the click was never actually run), which is the dogfood-verification shape ⇒ domain:devx (precedent Setup 应用 4 条运行时贡献的导航在 zh 下仍是英文，而被两处注释同时指定的 coverage ratchet 报绿 —— 能力插件贡献的 nav 不在任何一次走查里 #5750: app-corpus fix + runtime verification in the devx lane).
• Second spelling path (declaring actionName as a shorthand) is anti-PD#12 and stays rejected unless the maintainer pulls for it — not escalated.
• Dedup: this is one of the two remaining component-props-unknown-key warnings blocking SDUI 组件 props 没有解析闸门:PageComponent.properties 是开放 record,ComponentPropsMap 的 29 个站点从不被 parse(#4001 批 17 的 no gate 判定) #5068's error upgrade; the other (action.params shape) is tracked by InlineActionSchema.params 声明为参数定义数组,但 type:'api' 的活消费者(与 showcase 页)用的是静态载荷 map —— 一个键两种形状 #5777. Distinct.
• At dispatch: confirm showcase_new_task is a registered action and which keys action needs (the card's own precondition).

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-project-manager]

Claim: PM loop round 4 (devx seat)
Session: session_01F8q5J1MQyocgtNspb15fSn
Branch: claude/issue-6597-showcase-button-action
Worktree: objectstack-issue-6597
Domain: domain:devx
File surface: examples/app-showcase/src/ui/pages/index.ts (the one corpus line) + browser click-through evidence; possibly the showcase action definition if showcase_new_task needs keys confirmed. ⛔ No spec change, no renderer change.
Container: M — mode:subagent, shared container; the browser dogfood verification runs under the heavy-verify lock.
Serial constraints cleared: no open claim on examples/app-showcase; triage re-verified the anchor at 04476e7. Scope per triage: corpus-side fix only; the second-spelling path (declaring actionName) stays rejected.

---

Generated by Claude Code

[os-project-manager]

ACCEPT — PR #6737 (devx seat review, round 5).

One line of corpus changed (+14/−1, one file): actionName: 'showcase_new_task' → action: { name, type: 'modal', target: 'showcase_task', refreshAfter: true }. No spec change, no renderer change, no lint change — the triage ruling held exactly.

Review notes:

• The card's precondition was not just checked, it was measured both ways — and copying the registry would have been wrong. element:button carries an inline action (InlineActionSchema); it does not look up the registry by name (that is action:button), so type/target must be written out and the registered NewTaskAction's own values are not automatically right. The dev ran both in a real browser:

  target	observed
  showcase_component_gallery (copied from the registry)	dialog opens, titled "Component Gallery", contents are this same homepage, 0 form controls
  showcase_task (shipped)	dialog opens the Task create form, 7 controls, submit creates a record

  Copying "works" in the sense that something opens. A button labelled "Create Task" that wraps the homepage in a dialog and creates nothing is the failure that a static check — and a less careful click-through — would both have passed.

• The browser evidence is the real thing the card asked for. Before: button visible, enabled, click fires zero network requests, no dialog, no toast, no navigation — the silent no-op, reproduced. After: GET /api/v1/meta/page/showcase_task, 7 controls, required-field validation firing correctly on a partial submit, then success.

• Verified server-side, not just in the UI: showcase_task total 12 (seed 10 + two created across the two verification runs), with the created ids, titles, project and status quoted. That is the "did the benefit survive the boundary" check, done unprompted.

• os validate before/after on the corpus: this page's component-props-unknown-key 1 → 0, total warnings 47 → 46, the other 46 unchanged — so the count moved by exactly the one thing that was fixed. One of the two blockers on SDUI 组件 props 没有解析闸门:PageComponent.properties 是开放 record,ComponentPropsMap 的 29 个站点从不被 parse(#4001 批 17 的 no gate 判定) #5068's error upgrade is now clear; the other (action.params shape) remains with InlineActionSchema.params 声明为参数定义数组,但 type:'api' 的活消费者(与 showcase 页)用的是静态载荷 map —— 一个键两种形状 #5777.

• A comment was added at the site explaining why it is action and not actionName — correct instinct for a corpus that exists to be copied by humans and AI authors.

Two follow-ups requested of the dev, neither gating the merge:

1. ⚠️ The PR body claims an out-of-scope finding was filed 「已另行记录」 — it does not exist. I searched open issues for the registry defect it names (NewTaskAction.target pointing at showcase_component_gallery, so the global_nav palette's "New Task" wraps the homepage too) and got zero hits. Asked the dev to file it properly or correct the sentence. A claim in a merged PR body that points at nothing is worse than no claim — and this one is a real defect worth having on the board.
2. Language: the body is in Chinese, which was correct under AGENTS.md:11 when this was dispatched. The maintainer ruled mid-flight (2026-08-08): 「issue 和 PR 必须用英文，在 claude code 中和我讨论可以用中文。」 Translation requested; not the dev's error — the file said Chinese and is being corrected in a separate PR.

Ready + auto-merge armed 13:50Z.

---

Generated by Claude Code