No test files exist for any background handler or service module #105

@

Summary

Zero .test.ts or .spec.ts files were found in src/, making the 69 handlers and push engines untested in isolation.

Detail

find src -name *.test.ts -o -name *.spec.ts returned no results. Combined with the monolithic structure and inline service instantiation, this means no handler can be unit tested without mocking chrome.runtime.sendMessage, chrome.storage.local, chrome.tabs.query, and the entire MessageBus. The push orchestration logic (batch scheduling, concurrency control, abort handling, checkpoint consistency) is particularly high-risk without tests.

Location

src/background/index.ts:1

Reproduction

find src -name *.test.ts -o -name *.spec.ts returns empty output.

Suggested Fix

After extracting handlers and push engines into injectable modules, add unit tests for each domain. Start with executeRestPush and executeBulkPush using mock ApiClient and StorageService. Add integration tests for the MessageBus dispatch path with a test harness.

Verification

REFUTED(high): The finding conflates two separate claims. The first (no tests for background handlers) is confirmed | REAL(high): Background handlers and push engines operate autonomously and are hard to debug in production; zero | REAL(high): The finding is factually correct that no test files target src/background/index.ts directly, but it

🤖 Found by automated codebase audit (Claude Fable 5.1)
@