Why: Background notice runs blocked chat, truncated results, and duplicated deliverable execution.
Evidence: Focused run manager, card, server, recovery and race regressions pass locally; final combination checks are tracked in Dev.
Impact: Persist full results and optional choices, fence dispatch by run identity, retain public child process, and repair legacy projections without a schema change. No paid model trial was run.
Refs: feature/workbench-flow-completion
Why: A fresh question referencing an earlier result could be mistaken for a duplicate background request.
Evidence: The new English-summary reference regression failed with the old receipt branch and passes with the explicit-reference distinction.
Impact: Deduplicate inferred pending choices while allowing explicit new requests to use the saved result.
Refs: feature/workbench-flow-completion review P1
Why: A failed completion-card write could strand durable results, and routed messages could discard a selected result reference.
Evidence: Regressions cover missing projection recovery without execution, unavailable saved runs, pre-child dispatch failures and existing work/authorization paths.
Impact: Reconcile terminal saved results on authorized reads, keep known failures visible, and route explicit references through the conversation context.
Refs: feature/workbench-flow-completion review reliability and API findings
Why: Card registration or transcript persistence failures must not orphan paid work or discard a generated result, and ordinary questions must not match summary requests.
Evidence: Registration/promote and message-insert fault regressions, implicit-question checks and scoped race tests pass; legacy projection caching preserves historical times.
Impact: Fail before execution when tracking is unavailable, preserve full public final text with an explicit failure state, cache legacy projections once, and repair the concurrent material test fixture.
Refs: feature/workbench-flow-completion independent review closure
weichen
merged commit c7b4ad7ed5 into main2026-10-15 08:18:44 +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 及故障重放完成，无开放问题。验证命令、对象和原始输出见 Dev 唯一任务卡；覆盖权限和版本校验、按钮与消息竞争、重启、卡片登记失败时零执行、记录保存失败保留完整公开结果。新的付费模型试验 NOT_RUN。
Impact:
真正的审批继续走原 HITL。旧结果从保存记录补全并缓存，保留历史时间；不新增 schema。参考结果在发送与上下文组装时重新校验；拒绝不支持的命令组合。
Refs:
唯一任务记录
Post-Deploy Monitoring & Validation
本次交付智能体在 8788 更新后核对任务卡完整结果、普通追问可继续、后台完成无额外前台 run，以及最终回复后的完整过程回看。出现结果丢失、重复执行或错误阻塞即停止交付并前向修复；不自动重试模型或恢复已放开写入前的旧快照。