Why: SR-B10 (RDM requirements/01 V2.1, ruling J-03) defines the task-level
dual-speed pattern: a fast lane gives immediate feedback while deep work runs
in background with queryable progress and results posted back to the inbox.
The base system had the background spawn/notice machinery but nothing the
user could see while it ran or collect afterwards, so heavy tasks just made
the user wait on a synchronous turn.
Evidence: go test ./... -count=1 green (32 pkgs); new runmgr tests cover the
card lifecycle on success (progress card -> done/ok with result summary and
artifact line, card.created/updated/status events) and on failure
(done/danger with the error), plus the cards==nil no-op path.
Impact: spawnBackground now registers an inbox progress card linked to the
child run and rewrites it with the result on completion; the delegate_task
description and base-method working prompt teach the fast-feedback-first
pattern; a #background mock demo exercises the whole path end to end.
Refs: RDM docs/requirements/01 UR-27/SR-B10; .tmp 03-V2 §任务快慢双速通用模式;
Dev task feature/dual-speed-tasks.
weichen
merged commit d2bb936784 into main2026-10-10 06:52:50 +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: SR-B10（RDM requirements/01 V2.1，裁定 J-03）定义任务级快慢双速：快通道即时反馈，慢通道后台深度执行、进度可查、结果回投收件箱。基座已有后台派发/通知机制，但运行中与完成后用户侧均不可见，重任务只能同步干等。
改动：
Evidence: go test ./... -count=1 全绿（32 包）；新增 runmgr 测试覆盖成功/失败/未启用收件箱三条路径与 card.created/updated/status 事件。真实模型前后对照见 Dev 任务卡（feature/dual-speed-tasks）。
Refs: RDM docs/requirements/01 UR-27/SR-B10；.tmp 03-V2 §任务快慢双速通用模式；Dev 任务 feature/dual-speed-tasks。