From 07998c32ed4418237cf6552c371e0157a29aa06b Mon Sep 17 00:00:00 2001 From: 404oops Date: Thu, 27 Aug 2026 22:18:42 +0200 Subject: [PATCH] test(ai): point the provider-level replay test at the real driver fallback test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment claimed the fallback loop cannot be driven from a test — false since ChatCompletionDriver.test.ts gained a two-attempt fallback test that drives the actual loop. Say where that test lives instead. Co-Authored-By: Claude Fable 5 (1M context) --- .../ai-chat/providers/claude/ClaudeProvider.test.ts | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/backend/drivers/ai-chat/providers/claude/ClaudeProvider.test.ts b/src/backend/drivers/ai-chat/providers/claude/ClaudeProvider.test.ts index e85115e22..cf0f8351d 100644 --- a/src/backend/drivers/ai-chat/providers/claude/ClaudeProvider.test.ts +++ b/src/backend/drivers/ai-chat/providers/claude/ClaudeProvider.test.ts @@ -471,9 +471,10 @@ describe('ClaudeProvider.complete request shape', () => { // reuses one messages array across attempts, so if attempt 1 strips // `reasoning_details` in place, attempt 2 sends a message with no // thinking blocks and Anthropic rejects the continuation. Two - // sequential calls over one shared array reproduce that directly — the - // harness wires only one provider per model, so the real fallback loop - // cannot be driven from here. + // sequential calls over one shared array reproduce that at the + // provider level; the real fallback loop is driven end-to-end by + // "hands every fallback attempt the same messages array" in + // ChatCompletionDriver.test.ts. const { provider } = makeProvider(); messagesCreateMock .mockResolvedValueOnce(baseResponse)