From d862372efe7e52fe989088ec9c0e6e1d0e63cf4b Mon Sep 17 00:00:00 2001 From: weichen Date: Wed, 14 Oct 2026 08:40:28 +0000 Subject: [PATCH] Hold first checkpoint in browser timing fixture Why: The safe acknowledgement must be observed before fake findings arrive. Evidence: Dev evidence receipt for ten browser scenarios and isolated PostgreSQL/Redis tests. Impact: Changes only the task-owned zero-paid fixture delay. Refs: U3 r0.5 implementation plan Task 4 --- internal/server/work_checkpoint_eval_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/server/work_checkpoint_eval_test.go b/internal/server/work_checkpoint_eval_test.go index 897c8ec..67ef5d6 100644 --- a/internal/server/work_checkpoint_eval_test.go +++ b/internal/server/work_checkpoint_eval_test.go @@ -139,7 +139,7 @@ func evalMechanismStream(ctx context.Context, model string, msgs []agentllm.Mess } else { content = "整理结束，日期与验收条件需要核对；完整范围以原件为准。" } - if strings.Contains(sourceText, "[fixture:slow-stages]") { + if strings.Contains(sourceText, "[fixture:slow-stages]") || strings.Contains(sourceText, "[fixture:fast-ack]") { time.Sleep(1500 * time.Millisecond) } else { time.Sleep(200 * time.Millisecond)