Statements / Lines	Branches	Functions
		79.42%	75.15%	67.94%
		68.16%	63.55%	64.06%
		56.95%	66.05%	57.80%

.
• is part of the product and must remain in scope.
• .

• , , , and

	Target
	60% statements / lines
	65% statements / lines
	70% statements / lines
	75% statements / lines	translators and helpers
	80% statements / lines	handlers and executor branches
	85% statements / lines
	90% statements / lines

at 7.57%
4. at 20.66%
   • at 34.46%
   • at 36.25%
   • at 46.40%
   • at 33.33%
5. at 21.12%
   • at 9.56%
   • at 30.00%
6. at 41.16%

Fix coverage metric so it reflects source code instead of test files
• Keep a legacy coverage script for comparison
• Record the baseline and hotspots in-repo
• Add focused tests for low-risk utilities:
• Add route tests for:

Add DB-backed tests for:
• Cover branch behavior in:

Add usage analytics tests for:
• Expand route coverage for proxy management and settings branches

Cover translator helpers and central translation paths:

Add handler-level tests for:
• Add executor branch coverage for provider-specific auth, retries, and endpoint overrides

Merge more edge-case suites into the main coverage path
• Increase function coverage for DB modules with weak constructor/helper coverage
• Close branch gaps in , , , and translator helpers

Treat the remaining low-coverage files as blockers
• Add regression tests for every uncovered production bug fixed during the push to 90%
• Raise the coverage gate in CI only after the local baseline is stable for at least two consecutive runs

thresholds only after the project actually exceeds the next milestone with a comfortable buffer.

.

. It does not yet merge Vitest coverage into a single unified report. That merge is worth doing later, but it is not a blocker for starting the 60% -> 80% climb.