Goal command input projection
Goal 命令输入投影
Human commands execute outside the model turn and persist as `command/run` plus `command/done`. The Web transcript rendered only their result row. On a fresh session, `/goal` therefore cleared the composer and completed successfully while the page stayed on the empty hero; its result became visible only after later conversation content activated Chat. Appending an ordinary `user/message` from the handler would change
English
Problem
Human commands execute outside the model turn and persist as command/run plus command/done. The Web transcript rendered only their result row. On a fresh session, /goal therefore cleared the composer and completed successfully while the page stayed on the empty hero; its result became visible only after later conversation content activated Chat. Appending an ordinary user/message from the handler would change model-visible history and command semantics.
Decision
The command registry and durable command lifecycle remain unchanged. command/run records the parser-owned name, optional verbatim arguments, source, and invocation id; command/done records settlement. Neither event carries browser presentation intent.
The ui-goal client plugin registers a Goal-owned Conversation Definition beside the generic command Definition. Both match the same /goal command/run: the generic Definition retains the durable result row, while the Goal Definition builds a separate command-input Chat Node at an earlier fractional anchor. The Goal plugin also registers the keyed React renderer for that Node. Its local component copies only the user bubble's right-aligned geometry and semantic tokens, uses 14px/22px monospace text, and mounts no timestamp, copy, or branch actions.
Session.composerPhase treats visible non-command Chat Nodes as conversation content, so command-input activates the current conversation while a generic command row alone does not. The Host summary.blank bit remains turn-based, so list hiding and blank-session reuse do not change.
The Goal Definition derives /<name><args.trimEnd()> from the structured run: separator and internal multiline input survive, while the claimed bare form whose arguments contain one space displays /goal. A history window containing only command/done has no matching Goal Context, so it keeps the generic result row without inventing an input bubble; loading the older run restores both Nodes.
The model boundary is unchanged. The Goal projection creates no user/message, turn/start, step/start, or request/header. Accepted goal mutations reach the model only through the goal domain's existing <goal_state> snapshot or clear tombstone, independently of the command-input Node.
Verification
Goal client tests pin the dual Definition output, ordering, other-command exclusion, bare and multiline text, done-only cuts, renderer semantics, disposal, and fresh-session phase selection. The keyless assembled Web scenario submits bare /goal in a fresh session with no model adapter, verifies both rows and the absence of model-surface events, then reloads and verifies the persisted transcript.
Alternatives considered
Append user/message in the /goal handler. Rejected because the command would become model input and could trigger or alter a later request.
Add presentation intent to the command registry and durable event. Rejected because one Goal view would widen the generic command interface and make Session, Chat, and every command fixture carry browser presentation state. The existing command/run name and arguments already let the composed Goal client reconstruct its own view.
Teach the generic command renderer about /goal. Rejected because command-specific view construction belongs to the Goal client plugin. Composing that plugin out must remove the bubble without changing command execution or the generic result row.
Render every command input as a user bubble. Rejected because existing control commands deliberately leave a fresh session on the hero; changing them would broaden interaction semantics without a feature-owned Conversation Definition.
Consequences
One durable /goal run feeds two independently owned view Contexts without changing the command capability. Composing ui-goal out leaves ordinary command execution and its result row intact. Live tabs and cold reloads agree because both views derive from the same run. A page cut that retains only command/done temporarily shows only the result row; if that command is the session's only content, the hero hides the row until an older page restores the run. The session remains list-hidden and reusable until a model turn starts because Host blank semantics remain turn-based.
中文
问题
面向用户的命令在模型轮次之外执行，并持久化为 command/run 与 command/done。Web transcript（文本记录）此前只渲染结果行。因此，在新会话中，/goal 会清空编辑器并成功完成，但页面仍停留在空白 Hero；只有后续对话内容激活 Chat 后，结果才会显示。若处理器追加普通 user/message，将改变模型可见历史与命令语义。
决策
命令注册表与持久命令生命周期保持不变。command/run 记录由解析器提供的名称、可选的原样参数、来源和调用 id；command/done 记录结算。两条事件都不携带浏览器呈现意图。
ui-goal 客户端插件会在通用命令 Definition 之外注册一个归 Goal 所有的 Conversation Definition。两者都匹配同一条 /goal command/run：通用 Definition 保留持久结果行，Goal Definition 则在更早的分数锚点构建独立的 command-input Chat Node。Goal 插件还为该 Node 注册 keyed React renderer。它的本地组件只复用用户气泡的右对齐几何形态和语义 token，使用 14px/22px 等宽字体文本，并且不挂载时间戳、复制或分支操作。
Session.composerPhase 把可见的非命令 Chat Node 视为对话内容，因此 command-input 会激活当前对话，而仅有通用命令行时不会。Host 的 summary.blank 位仍以轮次为基础，因此列表隐藏和空白会话复用保持不变。
Goal Definition 根据结构化 run 派生 /<name><args.trimEnd()>：分隔符与内部多行输入保持不变；在已认领的裸命令形式中，参数只有一个空格时显示 /goal。仅包含 command/done 的历史窗口没有匹配的 Goal Context，因此会保留通用结果行，而不会虚构输入气泡；加载包含更早 run 的页面后，两个 Node 都会恢复。
模型边界保持不变。Goal 投影不会创建 user/message、turn/start、step/start 或 request/header。已接受的 goal 变更只会通过 goal 领域现有的 <goal_state> 快照或 clear tombstone 到达模型，与 command-input Node 无关。
验证
Goal 客户端测试固定双 Definition 输出、顺序、排除其他命令、裸命令与多行文本、仅含 done 的切分窗口、renderer 语义、资源释放和新会话 phase 选择。无密钥的完整组装 Web 场景在不含模型适配器的新会话中提交裸 /goal，验证两行都显示且不存在面向模型的事件，然后重新加载并验证持久化后的 transcript。
备选方案
**在 /goal 处理器中追加 user/message。**不予采纳，因为该命令会变成模型输入，并可能触发或改变后续请求。
**向命令注册表与持久事件添加呈现意图。**不予采纳，因为一个 Goal 视图会扩大通用命令接口，并要求 Session、Chat 和每个命令 fixture（测试前置数据）都携带浏览器呈现状态。现有 command/run 的名称和参数已足以让组合后的 Goal 客户端重建自有视图。
**让通用命令 renderer 识别 /goal。**不予采纳，因为命令专用视图的构建归 Goal 客户端插件所有。在组合中移除该插件后，气泡必须随之消失，且命令执行和通用结果行不能改变。
**把每条命令输入都渲染为用户气泡。**不予采纳，因为现有控制命令会有意让新会话停留在 Hero；这样修改会在没有功能自有 Conversation Definition 的情况下扩大交互语义。
后果
一条持久 /goal run 会向两个各自独立归属的视图 Context 提供数据，而不改变命令能力。在组合中移除 ui-goal 后，普通命令执行及其结果行保持不变。实时标签页与冷重载会得到一致结果，因为两个视图都派生自同一条 run。页面切分只保留 command/done 时，会暂时只显示结果行；如果该命令是会话中的唯一内容，Hero 会隐藏该行，直到加载更早页面恢复 run。由于 Host 的 blank 语义仍以轮次为基础，会话在模型轮次开始前仍从列表中隐藏，并且可以复用。