Ask-question Web presentation
Ask-question Web 呈现
The Web GUI could already collect answers through the `QuestionComposer` composer takeover, but the transcript around it was wrong on three counts. A pending question rendered twice: once as the composer takeover and once as the read-only `PendingCard` placeholder that predates the takeover. A settled `ask_user_question` call rendered as the generic "Tool call" row dumping raw args JSON, so the two composer verdicts
English
Problem
The Web GUI could already collect answers through the QuestionComposer composer takeover, but the transcript around it was wrong on three counts. A pending question rendered twice: once as the composer takeover and once as the read-only PendingCard placeholder that predates the takeover. A settled ask_user_question call rendered as the generic "Tool call" row dumping raw args JSON, so the two composer verdicts — the user dismissing the whole set (ASK_CANCELLED) and a turn interrupt landing while the question was pending (ASK_ABORTED) — both read as anonymous red-dot failures. And the composer's own chrome copy (pager, buttons, placeholders, validation feedback) was hardcoded Chinese while the surrounding client is bilingual through dsh-client-locale.
Separately, the composer visuals had drifted from the current design: an expand-to-open custom answer entry, no multi-select affordance beyond a trailing check, header-mounted paging, and a （可多选） title-suffix convention parsed out of model text.
Decision
A pending question owns exactly two surfaces: the composer takeover collects the answers, and a dedicated ask_user_question toolview row in the transcript names the interaction outcome. The row registers into the keyed tool.call.toolview hole exactly like todo_write and composes the shared ToolRow (chrome, running sweep, leading expansion). Its summary is the interaction verdict rather than args: waiting while running, N/M answered from the result JSON once settled (a skipped answer — empty selected, no custom — stays out of the count), cancelled for ASK_CANCELLED, and interrupted with the shared amber stopped semantics for ASK_ABORTED. Malformed or truncated results fall back to the generic summary. PendingCard narrowed to PendingWait<'approval'> and ChatView filtered the pending list to approval waits, leaving the placeholder card to approvals alone; the approval composer takeover (web permission and approval) has since removed it entirely.
A successful row keeps the collapsed transcript to its one-line verdict and replaces generic JSON in the expanded body with a read-only question transcript. The presenter validates questions from call args and answers from result content, pairs them by the echoed stable id, preserves call order, and renders each model-authored question in a muted label followed by its selected and custom answer lines in primary text. A skipped question shows the localized Not answered verdict. The card caps its height and scrolls internally. Invalid JSON, duplicate ids, missing ids, count mismatches, unknown answer ids, and invalid visible fields all retain the generic input/output card instead of presenting a partial or incorrectly paired transcript.
A cancelled or interrupted row has no answer payload to pair. Its expanded card shows a localized set-level verdict that no answers were submitted followed by the original model-authored questions; it does not label cancellation as a per-question skip or fabricate answer records. Invalid call args retain the generic diagnostic card. Cancellation uses the neutral settled state because the user chose it deliberately; interruption keeps the amber stopped state.
The composer redesign moves paging into the footer next to the actions, renders multi-select options with explicit checkboxes, keeps single-select numbered rows, and replaces the expand-to-open custom entry with an always-visible custom input row (textarea for optionless questions). The parseQuestionTitle multi-select suffix convention is deleted; multi_select is already structured metadata, so the title renders verbatim.
Composer chrome copy becomes bilingual: the plugin registers zh/en dictionaries under the question namespace of dsh-client-locale and hands the entry a namespace-bound translator plus the locale snapshot as a hooks-compartment source through the slot inject face, so a locale flip re-renders a mounted composer. Validation feedback is stored as a dictionary key and re-translated on flip; carrier failure messages and all model-authored question/option text render verbatim.
Two adjacent fixes ride along. All generic toolview leading icons (and the hover chevron) now inherit the single tertiary label color — the others-variant secondary override and the separate chevron color rule are deleted, leaving only the intentional cordis business-primary accent. And the client dev-watch bundler registers each CSS module with addWatchFile, because the virtual-module indirection previously hid css-only edits from the watcher.
Alternatives considered
Keep rendering questions through PendingCard. Rejected: the card was a read-only placeholder from before the takeover existed, so a pending question showed the same content twice with one copy not answerable. The toolview row plus takeover covers both the transcript record and the collection surface.
Show the questions or answers in the collapsed transcript row. Rejected: the composer takeover owns answer collection, and the row convention (todo_write) keeps the collapsed line scannable. The row therefore reports only the outcome until expanded; its expanded body owns the read-only question transcript.
Keep raw input and output JSON in the expanded body. Rejected: the payload preserves all information but makes the user's own answers or the cancelled questions difficult to scan. The structured view presents the same authored text while retaining raw JSON as the fail-closed fallback when question parsing or answer pairing is not trustworthy.
Render ASK_CANCELLED/ASK_ABORTED through the generic error shape. Rejected: dismissal is the user's own deliberate action and an interrupt is the shared stop gesture; both are expected outcomes, not tool failures. Naming the verdict (and keeping amber stopped semantics for the abort) matches how interrupted tool calls read elsewhere.
Keep the row verdicts in English. Initially deferred, then superseded when Client UI copy became locale-owned: the current conversation dictionaries localize the row verdicts and the expanded card's skipped-answer label, while model-authored questions and answers remain verbatim.
Keep the title-suffix multi-select convention. Rejected: multi_select is structured request metadata and the checkbox affordance now carries the signal, so parsing （可多选） out of model text was a fragile duplicate channel.
Consequences
ask_user_question and todo_write now demonstrate the intended toolview pattern: compose ToolRow, summarize from call args or result JSON with shape-checked fallbacks, and register through the keyed slot. The bespoke todo-row.module.css is gone.
The expanded transcript adds a typed, plain-data question-card model to the shared ToolRow; other tool views retain their existing generic or specialized cards. The question row reads only persisted call and result fields and does not add a Host presentation field. The approval composer takeover shipped (web permission and approval, height-capped per the approval-panel note), and PendingCard no longer exists.
ui-user-questions gains a dsh-client-locale dependency and an inject face where it previously had none; its contract (QuestionComposerInjected) lives with the consumer in contract/slots.ts.
Verification
ui-tool tests pin the row's waiting/answered/skipped/cancelled/interrupted matrix, readable id-based pairing, selected and custom answer lines, no-answer verdicts, and fail-closed fallback. Keyless assembled-Web snapshots expand successful and cancelled question rows and record their readable transcripts. ui-user-questions tests pin the redesigned composer (checkbox multi-select, always-visible custom row, footer pager, dictionary-key feedback re-translation, IME-safe Enter) and the plugin's dictionary registration plus inject face; ui-primitives tests pin the icon set. The assembled Web GUI was exercised against a live session covering answer, cancel, and turn-interrupt paths.
中文
问题
Web GUI 已经可以通过 QuestionComposer 的输入区接管收集回答，但其周边的会话记录呈现在三个方面是错的。待回答的问题会渲染两次：一次是输入区接管，一次是早于接管存在的只读 PendingCard 占位卡片。已结算的 ask_user_question 调用渲染为通用 "Tool call" 行并直接倾倒原始 args JSON，因此两种输入区裁决 —— 用户放弃整组问题（ASK_CANCELLED）与问题待回答期间轮次被打断（ASK_ABORTED）—— 都显示为无名的红点失败。而且输入区自身的界面文案（分页、按钮、占位符、校验反馈）是硬编码中文，而周边客户端已通过 dsh-client-locale 实现双语。
另外，输入区视觉也偏离了当前设计：自定义回答需展开才能输入、多选除尾部对勾外没有可见标识、分页挂在头部、还有从模型文本里解析 （可多选） 标题后缀的约定。
决定
一个待回答的问题恰好拥有两个界面：输入区接管收集回答，会话记录中一个专门的 ask_user_question toolview 行陈述交互结果。该行与 todo_write 完全一样注册进带 key 的 tool.call.toolview 槽位，并复用共享的 ToolRow（外观、运行扫光、前导展开）。其摘要是交互裁决而非参数：运行中显示 waiting，结算后从结果 JSON 得出 N/M answered（被跳过的回答 —— selected 为空且无 custom —— 不计入），ASK_CANCELLED 显示 cancelled，ASK_ABORTED 显示 interrupted 并沿用共享的琥珀色 stopped 语义。畸形或截断的结果回退到通用摘要。PendingCard 曾收窄为 PendingWait<'approval'>，ChatView 曾将待处理列表过滤为仅审批等待，使占位卡片只服务于审批；其后审批输入区接管（Web 权限与审批）已将它彻底移除。
成功的问题行仍让折叠后的会话记录只显示单行裁决，并在展开内容中用只读问答记录取代通用 JSON。presenter 校验调用参数中的问题与结果内容中的回答，按回显的稳定 id 配对、保持调用顺序，并将每段模型撰写的问题显示为弱化标签，下方用主要文字显示已选项和自定义回答。被跳过的问题显示本地化的 未回答 裁决。卡片限制最大高度并在内部滚动。无效 JSON、重复 id、缺少 id、数量不符、未知回答 id 与无效可见字段都保留通用输入／输出卡片，不呈现不完整或错误配对的记录。
已取消或已中断的问题行没有可供配对的回答载荷。其展开卡片先显示本地化的整组裁决，说明未提交回答，再列出模型撰写的原始问题；它不会把取消标成逐题跳过，也不会虚构回答记录。无效调用参数保留通用诊断卡片。取消是用户主动选择，使用中性 settled 状态；中断保留琥珀色 stopped 状态。
输入区重设计将分页移到底部操作区旁，多选选项渲染显式复选框，单选保留编号行，并用始终可见的自定义输入行取代展开式自定义入口（无选项问题用多行文本框）。删除 parseQuestionTitle 的多选后缀约定；multi_select 已是结构化元数据，标题原样渲染。
输入区界面文案实现双语：插件在 dsh-client-locale 的 question 命名空间下注册中英词典，并通过 slot inject face 向条目提供绑定命名空间的翻译器和作为 hooks compartment 来源的 locale 快照，语言切换时已挂载的输入区会重新渲染。校验反馈以词典 key 存储、切换时重新翻译；载体失败消息与所有模型撰写的问题/选项文本原样渲染。
两个相邻修复随行。所有通用 toolview 前导图标（含悬停箭头）现在统一继承三级标签色 —— 删除了 others 变体的二级色覆盖和独立的箭头颜色规则，只保留有意为之的 cordis 业务主色强调。客户端 dev-watch 打包器用 addWatchFile 注册每个 CSS 模块，因为虚拟模块间接层此前使仅改 CSS 的编辑对 watcher 不可见。
曾考虑的替代方案
继续通过 PendingCard 渲染问题。 否决：该卡片是接管存在之前的只读占位，导致同一内容显示两份且其中一份不可作答。toolview 行加接管同时覆盖了记录与收集两个面。
在折叠的会话记录行显示问题或回答。 否决：输入区接管拥有回答收集，而行的约定（todo_write）让折叠单行保持易扫描。因此该行在展开前只报告结果，展开内容拥有只读问答记录。
在展开内容中保留原始输入与输出 JSON。 否决：载荷保留了全部信息，却让用户自己的回答或已取消的问题难以浏览。结构化视图展示相同的作者文本；问题解析或回答配对不可信时仍以原始 JSON 作为 fail-closed 回退。
用通用错误形态渲染 ASK_CANCELLED/ASK_ABORTED。 否决：放弃是用户自己的主动操作，打断是共享的停止手势；两者都是预期结果而非工具失败。命名裁决（且中止保持琥珀色 stopped 语义）与其他被打断的工具调用的呈现一致。
让行内裁决保持英文。 最初延期，随后在 Client UI 文案改由 locale 管理时被取代：当前 conversation 词典本地化行内裁决与展开卡片的未回答标签，而模型撰写的问题和回答保持原样。
保留标题后缀的多选约定。 否决：multi_select 是结构化请求元数据且复选框标识已承载该信号，从模型文本解析 （可多选） 是脆弱的重复通道。
后果
ask_user_question 与 todo_write 现在共同示范预期的 toolview 模式：复用 ToolRow、从调用参数或结果 JSON 做带形状校验回退的摘要、通过带 key 的 slot 注册。专用的 todo-row.module.css 已删除。
展开问答记录为共享 ToolRow 增加类型化的纯数据问题卡片模型；其他工具视图保留原有的通用或专用卡片。问题行只读取已持久化的调用与结果字段，不增加 Host 呈现字段。审批输入区接管已交付（Web 权限与审批，并按审批面板 Agent Note施加高度上限），PendingCard 已不复存在。
ui-user-questions 新增 dsh-client-locale 依赖和此前没有的 inject face；其约定（QuestionComposerInjected）与消费方一起放在 contract/slots.ts。
验证
ui-tool 测试钉住行的 waiting/answered/skipped/cancelled/interrupted 矩阵、可读的 id 配对、已选项与自定义回答行、无回答裁决和 fail-closed 回退。无密钥的组装 Web 快照分别展开成功与取消的问题行并记录其可读内容。ui-user-questions 测试钉住重设计的输入区（复选框多选、始终可见的自定义行、底部分页、词典 key 反馈重翻译、IME 安全的 Enter）以及插件的词典注册与 inject face；ui-primitives 测试钉住图标集。组装后的 Web GUI 在真实会话中演练了回答、取消与轮次打断路径。