Statements / Lines	Branches	Functions
		79.42%	75.15%	67.94%
		68.16%	63.55%	64.06%
		82.58%	75.22%	84.23%

.
• 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

on 2026-05-13:

		Lines %
		7.87%
		9.67%
		9.80%
		10.00%
		10.63%
		10.96%
		11.28%
		12.19%
		12.77%
		12.98%
		13.26%
		13.43%
		13.51%
		13.52%
		14.46%
		14.94%
		15.07%
		15.54%
		16.66%
		16.66%

is the densest cluster of low coverage and dominates the remaining gap.
• , ) need handler-level tests.
• , ) and need scenario tests.
• are lower priority but cheap branch wins.

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.

Current gate (as of 2026-05-13): enforces 75 statements / 75 lines / 75 functions / 70 branches. This is the conservative ratchet against the measured baseline (82.58% / 82.58% / 84.23% / 75.22%) and preserves headroom for transient flakiness.

node scripts/check/test-report-summary.mjs --threshold 75

):

once branch coverage holds above 78% for two consecutive runs.

. 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.