Why: Consume the Core work result and optional decision snapshot.
Evidence: Generated with make contracts from Core 00f1826.
Impact: Add optional types without changing existing cards.
Refs: feature/workbench-flow-completion
Why: Repeated progress and coupled scrolling obscured chat, and task choices lacked a reliable independent interaction path.
Evidence: 285 frontend unit tests and 23 browser scenarios pass locally before the shared event-loader extraction; final combination checks follow in Dev.
Impact: Coalesce cumulative progress, retain execution records, show timestamps and quiet notifications, support versioned work actions and explicit result references without automatic chat backfill.
Refs: feature/workbench-flow-completion
Why: Keep persisted task decisions aligned across Go and TypeScript.
Evidence: make contracts generated both consumers from Core 1a5ef6b.
Impact: Include the reserved run identity and typed dispatching state.
Refs: feature/workbench-flow-completion
Why: The frontend unused-export gate rejected a helper used only within its module.
Evidence: The unchanged knip baseline and TypeScript checks pass.
Impact: Remove an unnecessary export without changing replay behavior.
Refs: feature/workbench-flow-completion
Why: A rejected result-reference request could discard the user text or uploads after the composer cleared.
Evidence: 286 frontend tests, TypeScript and the unchanged unused-export gate pass; mixed-input browser regression preserves the draft.
Impact: Validate incompatible inputs before clearing, retain failed pending input with its request identity, and require explicit retry while other messages can continue.
Refs: feature/workbench-flow-completion review frontend-races finding
Why: Full execution history must retain outputs after the 500-event API page boundary.
Evidence: Ordered 502-event replay and nonadvancing-cursor rejection tests pass.
Impact: Add regression coverage only; production source is unchanged.
Refs: feature/workbench-flow-completion review testing gap
Why: Completion or progress from an earlier task could appear in the process of an unrelated newer answer.
Evidence: The new ownership regression fails before the guard and passes afterward; the frontend suite, TypeScript and unchanged export gate pass.
Impact: Project child progress only into its originating live turn while still reconciling background results.
Refs: feature/workbench-flow-completion chronological display requirement
weichen
merged commit 03db4b81be into main2026-10-15 08:18:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why:
重复的协作进展和联动滚动让对话难以阅读。现在对话保持时间顺序，后台结果通过工作栏和轻量提示查看，完整过程按需读取；可选需求不会额外插入聊天回复。
Evidence:
独立 ce-code-review 已完成，无开放问题；追加的 502 条事件跨页回看测试已由独立审阅者重放。局部、浏览器、构建及最终组合检查均引用 Dev 唯一任务卡中的工具证据，最终准确 HEAD CI 另行核验。
Impact:
增加真实时间、结果引用和工作动作接入；发送被拒绝时保留文字、附件和引用，需明确重试，并允许其他消息继续。不增加队列跨刷新持久化。保持现有主题、正常审批和唯一工作卡展示位置。
Refs:
唯一任务记录
Post-Deploy Monitoring & Validation
本次交付智能体在实际 8788 前端资源上重放浏览器场景，检查独立滚动、原卡结果、可选输入、时间和刷新回看。正常账号的真实任务由用户验收；本次不新增付费模型试验。