[MumuTW]

Problem

check:mutation-test-coverage fails on release/v3.8.49 at its own HEAD (7a8f9156d) — no PR content involved:

open-sse/services/accountFallback.ts
  + tests/unit/8396-cooldown-429-cap.test.ts

open-sse/services/combo/comboPredicates.ts
  + tests/unit/8376-econnrefused-breaker.test.ts

✗ 2 covering unit test(s) across 2 module(s) are missing from stryker.conf.json tap.testFiles.

It is a step in the Fast Quality Gates job, so the job is red for every PR→release/**. It sits behind check:file-size and check:db-rules in the step order, so it only becomes visible once those pass (#8524 and #8534 respectively).

Both tests genuinely exercise a mutated module but were never registered, so their mutant kills do not count toward the mutation score — the gate exists precisely to catch that drift.

Test	Mutated module	Imports
tests/unit/8396-cooldown-429-cap.test.ts	open-sse/services/accountFallback.ts	checkFallbackError
tests/unit/8376-econnrefused-breaker.test.ts	open-sse/services/combo/comboPredicates.ts	shouldRecordProviderBreakerFailure

Change

Two strings added to tap.testFiles, in the array's existing sorted position. No other key in stryker.conf.json is touched — the diff is exactly +2 lines.

Note: the file does not currently satisfy prettier --check on the base either (it has expanded plugins/reporters arrays that Prettier would collapse). I deliberately left that alone rather than reformatting, to keep this diff to the two lines that matter.

Verification

	Before	After
npm run check:mutation-test-coverage	✗ 2 missing across 2 modules	✓ No drift — every covering unit test is listed (3312 test files scanned against 31 mutated modules)
node --import tsx/esm --test on both files	—	10/10 pass
JSON.parse of the config	—	valid

Related

Part of clearing the base-red surface on this tip, alongside #8524 (check:file-size) and #8534 (check:db-rules). A follow-up will handle the three stale backoff tests, which trace to the same #8396 landing as the first entry here.

[diegosouzapw]

Thanks for tracking this down — the root cause analysis is correct and the two registrations you added (tests/unit/8396-cooldown-429-cap.test.ts, tests/unit/8376-econnrefused-breaker.test.ts) are exactly right: both tests exist, pass 10/10 locally, and were genuinely missing from tap.testFiles as of the commit you branched from (7a8f915).

One thing surfaced during review: release/v3.8.49 has moved since you opened this (now at 3070925, via merged PR #8504), and that merge introduced tests/unit/repro-7503-no-choices.test.ts covering open-sse/utils/error.ts, which is also not yet in tap.testFiles. I confirmed this by cherry-picking your commit onto the current tip and re-running npm run check:mutation-test-coverage — it still reports 1 missing entry instead of 0.

Could you add that third line (same sorted-array pattern, right before tests/unit/repro-antigravity-404-family-cooldown-hijack.test.ts) so the gate actually goes green once merged, rather than trading one drift item for another? Everything else here (scope, the two entries you did add, leaving the pre-existing prettier formatting issue alone) looks good to me. What happens next with sequencing against #8524/#8534 is the maintainer's call.