feature/q2-review-handoff-groupchat-wp3
main
Q2 验收二:review 拓扑须与今天的 backend runReview 等价(并行找问题、逐条验证、丢掉未验证);handoff 与 group_chat 点亮后 12 内置拓扑达 11/12(task_board 属 WP4)。
[
]
GOWORK=off go test ./... -count=1
-race
Why: Q2 acceptance 2 requires the squad review topology to be equivalent to today's backend runReview flow (parallel finders, per-finding verification, drop unverified); handoff and group_chat complete 11 of 12 builtin topologies. Evidence: wp3_conformance_test.go mirrors backend review_test.go assertions (true finder concurrency via release gate, verify calls = 5 unique after dedupe, only PASS kept, dropped-count line, severity order); handoff records ownership transfer, target receives filtered history, finalize takes chain-tail output, unknown target role fails closed; group-chat rotate / close-marker / moderator conformance with budget stop and fail-closed unknown nominee. Full suite green with -race. Impact: review/group_chat drivers lit in the topology registry (task_board remains fail-closed until WP4); RunState gains Handoffs (persisted); RunOptions gains GroupChat*/Review* knobs; runOneStep validates handoff targets and injects handoff context; finalize prefers chain-tail deliverable. Parse/dedupe/verdict/severity/report formats ported verbatim from backend internal/runtime/review.go for byte-level report equivalence. Refs: Q2 plan WP3 (2026-10-07-agent-stack-q2q3-plans.md); task card .task/feature-agent-stack-q2.md
No dependencies set.
The note is not visible to the blocked user.
Why
Q2 验收二:review 拓扑须与今天的 backend runReview 等价(并行找问题、逐条验证、丢掉未验证);handoff 与 group_chat 点亮后 12 内置拓扑达 11/12(task_board 属 WP4)。
What
[末],丢空 issue)→ (location,issue) 去重上限 10 → 每条独立 verifier(直接 Execute,落盘 reviews/verify_NN 留痕;尾行 VERDICT: PASS/FAIL/PARTIAL)→ 只留 PASS(fail-closed)→ severity 稳定排序 → 报告恒带「已丢弃 N 条未验证」。解析/去重/判定/排序/文案与 backend review.go 同格式串逐段移植(计划 §一.5:以报告字节形态为等价判据)。verify 角色先行解析 fail-fast;finder 非关键失败宽容(backend spawn-err 同款)收口降级。Evidence
GOWORK=off go test ./... -count=1+-race绿(SELF);CI 为权威(GATE)Refs