From a32aed7383c0f321ce1e4d4139c7e2e79e381ec6 Mon Sep 17 00:00:00 2001 From: Will Gordon Date: Fri, 7 Aug 2026 16:14:18 -0400 Subject: [PATCH] fix(sse): update stale ALL_ACCOUNTS_INACTIVE test assertion (T24) Pre-existing upstream test-drift, same as fix/basered-changelog-integrity-fabricated-docs@58ab721fe: t23-t24-fallback-resilience.test.ts's T24 case asserts the pre-dispatch-skip scenario returns ALL_ACCOUNTS_INACTIVE, but production code returns the more precise ALL_TARGETS_SKIPPED when recordedAttempts === 0. --- tests/unit/t23-t24-fallback-resilience.test.ts | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tests/unit/t23-t24-fallback-resilience.test.ts b/tests/unit/t23-t24-fallback-resilience.test.ts index 6682581e69..22f9c5d7da 100644 --- a/tests/unit/t23-t24-fallback-resilience.test.ts +++ b/tests/unit/t23-t24-fallback-resilience.test.ts @@ -148,7 +148,11 @@ test("T24: all inactive accounts return 503 service_unavailable (not 406)", asyn assert.equal(result.status, 503); const body = (await result.json()) as any; - assert.equal(body.error?.code, "ALL_ACCOUNTS_INACTIVE"); + // isModelAvailable always false means every target is skipped by the + // pre-dispatch filter with zero dispatch attempts — the more precise + // ALL_TARGETS_SKIPPED classification, not ALL_ACCOUNTS_INACTIVE (which + // implies targets were attempted and their accounts found inactive). + assert.equal(body.error?.code, "ALL_TARGETS_SKIPPED"); }); test("combo falls through 400s and reaches the next model", async () => {