[harshabala]

Summary

• Coverage: the measured core (background handlers, storage, LLM, events, recommendations, message router, content scanner; 18 files, ~2,950 statements) goes from 49% to 100% statements, branches, functions and lines. vitest.config.ts now sets 100% thresholds, and CI plus npm run ci run test:coverage, so any drop fails the build. There are 941 tests, up from 674.
• Lint: all 103 ESLint warnings are fixed. lint:eslint runs with --max-warnings 0 in npm run ci and as a CI step.
• Drive setup:
  • store/WHAT_YOU_STILL_DO.md §3 now has click-by-click Google Auth Platform steps. The app's two scopes (drive.appdata, userinfo.email) are non-sensitive, so publishing needs no Google review. The steps also cover registering the store item's redirect URI between upload and submit.
  • Settings shows readers a plain message when Drive sign-in fails because of setup; the technical detail goes to Diagnostics.

Bugs found and fixed while writing tests

1. Dropped poster scans (src/content/scanner.ts): each DOM mutation batch restarted the poster-scan debounce with only its own nodes, so posters from earlier batches in the same 500 ms window were never scanned. Image roots now accumulate until the scan runs.
2. Inflated "titles added" (mergeSeedCatalog): every refreshed catalogue title counted as added, so "Merge highlight catalogue" always reported ~150 new titles and RESTORE_DEMO_LIBRARY always said it seeded. Only new titles count now. Two existing test expectations are updated with the reason.
3. Duplicate bridges (grouped recommendations): the same cross-medium bridge could be listed twice under one seed.
4. Wasted startup work (App.tsx): the whole people list was fetched at startup and on every filmmaker update to fill counters that were never shown. Those fetches are removed.

Other changes

• Removed about 20 conditions that could never be taken instead of writing tests for them. Each one has a comment or commit note explaining why it was dead (e.g. a length check the regex already enforces, an oldVersion < 4 inside an upgrade that only runs below v4).
• Replaced any with real types: TMDb person/credit rows, logger args, scanner responses, settings validator, UI message payloads. Rethrown errors now carry cause.

Scope note

The 100% applies to the existing coverage.include set. The Preact UI (src/ui/**) and the content-script renderers (hoverCard.tsx, posterBadge.tsx) stay outside it, as before.

Verification

• npm run release-check passes: typecheck, lint (0 warnings), 941 tests with 100% core coverage, build, package check.
• The coverage gate fails as intended when a suite is removed (checked by excluding the scanner suite).
• Loaded the unzipped store subsume.zip in headless Chromium:
  • popup renders;
  • Settings Drive connect/disconnect works;
  • the content script mounts on a movie page;
  • no page errors.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FHFhkzNyPBLTv6hU2PeX3e

---

Generated by Claude Code