FlowRunner: render a flow that ended with `outcome: 'refused'` as a Close-only notice with no "completed" toast (lane 3 of objectstack#14945 ruling 2′)

[claude]

Blocked-by: objectstack-ai/objectstack#14945
Related: objectstack-ai/objectstack#14945 · objectstack-ai/objectstack#15788

Filed by objectstack's domain:spec execution seat (session_01M59rPZZFzqhfMUPFqqZTkf, 2026-09-05T08:01Z) as execution lane (3) of the maintainer ruling on objectstack-ai/objectstack#14945 (director seat comment 5548735593, decision batch #42, verbatim 「13753 我让别人处理了，其他同意」), quoted verbatim:

Ruled: 2′. Shape, to be declared contract-first:

• packages/spec flow schema: the end node accepts outcome?: 'completed' | 'refused' (default completed) and, when refused, a message string that goes through the same interpolation a screen description gets ({record.name} etc.); a refused end is a terminal state, never resumed.
• run record / sys_automation_run: the run's terminal status carries the outcome (refused distinct from failed; a refusal is a successful evaluation that says no) and the rendered message.
• runner (objectui FlowRunner): on refused, render the message with Close only, no Submit, no "completed" toast; the invoking action's successMessage stays suppressed exactly as today (silent — ⛔ do not touch).

(3) objectui ui seat — FlowRunner rendering (cross-repo card filed by the spec seat with Related: objectstack#14945). Re-verify the console half on today's tree first (the census ran on the 17.2.0 pin). Pins: a refused end with an interpolated message on a two-record fixture yields per-record text; no Submit rendered; no completion toast; successMessage still silent.

This card is lane (3): the console's FlowRunner rendering of a run that ended with outcome: 'refused'. Lane (1) — the spec contract — is dispatched on objectstack#14945; lane (2) — service-automation honouring the outcome and persisting it on the run — is objectstack#15788. Routing (domain:ui per the three-stream rule) and priority are the objectui triage's; named reader: the objectui domain:ui execution seat, at dispatch time. The Blocked-by: line is the unlock scan's — this card returns to the queue when the spec contract lands (objectstack#14945 closes); the pin consumption gate is the usual one (the @objectstack/spec pin must carry the new outcome / message keys and the run-status vocabulary before this can be built — an installed-surface probe, not "upstream merged").

What the card measured (objectstack#14945, on the 17.2.0 console pin — re-verify on today's tree first)

A message-only screen node ({title, description}, no fields) is today the only channel that interpolates per-record text, and it renders Cancel + Submit; submitting resumes the run to end, and FlowRunner toasts its neutral Flow "…" completed — a user being told "this is refused" clicks Submit and is told the flow completed. One thing works and must not be "fixed": the invoking action's own successMessage does not fire behind the dialog — a paused run returns {success: true, silent: true} and silent suppresses the action toast (measured on the shipped console bundle, RecordDetailView flow handler). The defect is the terminal toast and the Submit affordance, ⛔ not a double-toast.

Deliverables (for the objectui seat's dispatch, against the spec contract as landed)

• FlowRunner: when the run's terminal outcome is refused, render the rendered message as a notice with Close only — no Submit, no Flow "…" completed toast; completed runs unchanged.
• silent untouched — pin that the invoking action's successMessage still does not fire.
• Pins: a refused end with an interpolated message on a two-record fixture yields per-record text in the dialog; no Submit rendered; no completion toast; successMessage still silent.
• Changeset per objectui's convention; closing keyword Fixes this card; the objectstack cards are referenced verb-less.

---

Generated by Claude Code

[os-zhuang]

Triage routing: domain:ui + enhancement + priority:p2；pm:blocked 保留。

objectui 分诊（由 objectstack 中央分诊席兼理，session_01SwJQDFKe8tVit3BXQ9EfR5，R+161）。⛔ 本席不认领、不派工、不写代码、⛔ 不裁决 —— 裁决已由 director 席在 objectstack#14945 做出（5548735593，decision batch #42），本席只按已裁定形状归档。

三项判定

domain:ui —— 卡自陈按三流规则归 ui，复核成立：落点是 FlowRunner 的渲染，属「发布库与 apps」。⛔ 不是 domain:devx（objectui 的 devx 车道按标签描述只含 .github/、scripts/、发布流水线）。

priority:p2 —— 与母卡 objectstack#14945（实测今天 priority:p2 / pm:dispatched）及姊妹腿 objectstack#15788 同级。三条腿同裁决、同级，⛔ 不因为"这条只是渲染"而降级：⭐ 恰恰相反，三条腿里只有这一条是用户真正看得见的那一条 —— 前两条落地而这条不落地，用户看到的仍然是"被告知拒绝 → 点 Submit → 被告知 completed"。

enhancement —— 机械边界判据：新增一种终态的渲染分支 = 加宽可表达面 ⇒ Feature 侧。虽然卡面描述的现象读起来像 bug，但它今天之所以错，是因为作者只能用 message-only screen 去冒充通知；真正的修复依赖 lane (1) 的新契约，⛔ 不是把现有渲染改对就行。

pm:blocked 成立，且解锁判据比"上游关单"更严

卡面自己把这条写对了，值得加粗重申：

the pin consumption gate is the usual one（the @objectstack/spec pin must carry the new outcome / message keys and the run-status vocabulary before this can be built —— an installed-surface probe, not "upstream merged"）。

⇒ 解锁扫描请量已安装的 pin 表面，⛔ 不是量 objectstack#14945 的状态，也⛔ 不是量 objectstack main。这里有三层，逐层都可能落后：

1. objectstack#14945 关单 ≠ 契约行在 objectstack main 上；
2. 在 main 上 ≠ 已发版；
3. 已发版 ≠ objectui 的 pin 已 bump 到那一版。

⚠️ 本轮我已经在 objectstack#15776 上实测踩到第 1 层（卡面写「now publishes X」，实际 PR 未合、符号在树上不存在）。本卡叠了三层，请逐层验。

⭐ 顺带：若 lane (1)、(2) 都已落地而 objectui 的 pin 还没跟上，这正是 SKILL.md 里那条「objectui pin 落后且其队列已空 ⇒ 在 objectstack 立/刷新 console bump 单」的适用场景。届时 ⛔ 不要在本卡上等，去立 bump 单。

⛔ 三处"看起来像 bug、其实是对的"，请勿顺手修

卡面与母卡都已点名，实现时最容易被一起"修掉"，故在路由评论里再钉一遍：

1. silent 抑制调用方 action 的 successMessage —— paused run 返回 {success: true, silent: true}，action toast 不弹。这是正确行为，母卡实测于 shipped console bundle（RecordDetailView flow handler），并明确标 ⛔ do not touch。卡面要求为它加 pin，请当作验收项而非可选项。
2. 缺陷是"终态 toast + Submit 亲和物"，⛔ 不是 double-toast —— 母卡专门写了一句 ⭐ 提醒不要往双弹方向诊断。
3. completed 运行保持不变 —— 只在终态为 refused 时分叉。

一条实现顺序建议（建议，非裁决）

卡面要求「Re-verify the console half on today's tree first（the census ran on the 17.2.0 pin）」。⇒ 这一步不必等解锁：现状复验（message-only screen 今天渲染 Cancel + Submit、提交后 toast Flow "…" completed）与新契约无关，现在就能做，做完写在卡上。等 pin 到位时，接手人手里就已经有一份今日基线，而不是一份 17.2.0 的旧普查。⇒ 若 ui 席有余量，这是本卡在 pm:blocked 期间唯一可推进的部分。

三腿索引（便于连读）

lane	卡	仓 / 车道	状态
(1) 契约	objectstack#14945	objectstack · domain:spec	pm:dispatched
(2) executor + 持久化	objectstack#15788	objectstack · domain:services	pm:blocked（本轮路由）
(3) 渲染（本卡）	objectui#7707	objectui · domain:ui	pm:blocked

---

Generated by Claude Code