From d0049a7f8eaa650d51283b2c8f70c14800e09e86 Mon Sep 17 00:00:00 2001 From: Will Gordon Date: Fri, 7 Aug 2026 16:11:08 -0400 Subject: [PATCH] fix(sse): update second stale ALL_ACCOUNTS_INACTIVE assertion (T24) Same pre-existing upstream test-drift as 038035f93: 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. Caught by this PR's own fresh CI run after the dirty-mergeable-state fix. --- tests/unit/t23-t24-fallback-resilience.test.ts | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/unit/t23-t24-fallback-resilience.test.ts b/tests/unit/t23-t24-fallback-resilience.test.ts index f0f51d30a2..22f9c5d7da 100644 --- a/tests/unit/t23-t24-fallback-resilience.test.ts +++ b/tests/unit/t23-t24-fallback-resilience.test.ts @@ -148,6 +148,10 @@ test("T24: all inactive accounts return 503 service_unavailable (not 406)", asyn assert.equal(result.status, 503); const body = (await result.json()) as any; + // 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"); });