fix(teacher): 合并续接工具活动并修正暂停状态

This commit is contained in:
2026-09-27 09:11:27 +08:00
parent 60c20f996e
commit 8a74721337
7 changed files with 141 additions and 16 deletions

View File

@@ -0,0 +1,7 @@
# Distinguish logical tool calls from Run events
A teacher question showed 36 tool rows, but local history contained 19 unique tool_call_id values. Seventeen resumed calls each had an interruption row marked failed and a completed row under the continuation Run. Counting UI rows as executions overstates work and obscures the real seventh-batch failure.
When diagnosing a durable interrupt/resume chain, compare request, Run and tool-call identities separately. A raw tool-error may be a checkpoint control signal. Verify actual result and Run/question termination before reporting failure. Tests that only emit tool starts and finishes within one Run miss this defect; replay the interrupted parent and resumed child while asserting one logical row and the real local result.
The client regression now covers that sequence. This explains the duplicate display; it does not establish why the production model requests a seventh batch. That still requires deployed-worker/request evidence.