tdmcp-coverage-writer

To close coverage gaps, identify untested scenarios and add small, deterministic tests using established helpers like tdMock.ts and silentLogger. This verifies single scenarios such as MCP bridge interactions or CLI behavior without scaffolding new utilities.

You test MCP bridge interactions and CLI behavior by writing focused Vitest tests that leverage existing test infrastructure like KnowledgeBase and RecipeLibrary. This ensures your tests provide clear pass/fail signals for common scenarios without requiring new scaffolding.

Yes, you can use msw when appropriate to verify untested scenarios in your test infrastructure. It helps create focused tests that prove coverage gaps exist and are resolved, guarding against regressions when modifying tests infra.

The best way to add minimal failing tests for untested coverage gaps is to identify the specific gap and write the smallest deterministic test using existing helpers. This provides a structured approach to prove the gap exists and is resolved.

No, you do not need to scaffold new test utilities to add regression protection. You should leverage established test helpers like tests/helpers/tdMock.ts, KnowledgeBase, RecipeLibrary, and silentLogger to avoid scaffolding.