DaiChaoXiong 1d1f50d1b1 fix(providers): keep the API's real tool-call ids across turns ... Multi-turn tool calls collided on replay: the reducer regenerated call_0, call_1, ... every turn while ignoring the API's real call ids, so replayed history had duplicate function_call/function_call_output ids that the API cannot pair (visible once a conversation has two tool-using turns). - ProviderEventReducer::tool_call_start_with_id(index, name, id) keeps the API's id; tool_call_start delegates with an auto-generated fallback - Responses API: use item.call_id; Chat Completions: use tool_calls[].id - regressions: real-log test asserts the captured ids, agent replay test asserts ids stay unique across three turns; reducer id-override test		2026-08-09 22:07:18 +08:00
..
agent_loop.rs	feat(core): agent message setters, thinking support, reducer arg-slot fix	2026-08-09 20:59:39 +08:00
batch_tests.rs	feat(core): agent message setters, thinking support, reducer arg-slot fix	2026-08-09 20:59:39 +08:00
json_tests.rs	feat(core): agent message setters, thinking support, reducer arg-slot fix	2026-08-09 20:59:39 +08:00
model_tests.rs	feat(core): agent message setters, thinking support, reducer arg-slot fix	2026-08-09 20:59:39 +08:00
provider_tests.rs	fix(providers): keep the API's real tool-call ids across turns	2026-08-09 22:07:18 +08:00
tool_tests.rs	feat(core): agent message setters, thinking support, reducer arg-slot fix	2026-08-09 20:59:39 +08:00