src/tools/* coverage sitting at 10-15%, failing the global 90% threshold on every PR/main run

[albatrossflyon-coder]

Summary

The `coverage` CI check has been failing on `main` for at least the last several runs (confirmed 2026-07-13 and 2026-07-14), and fails identically on every PR opened against it — not something any individual PR is causing.

What's failing

The global thresholds (90% lines / 94% functions / 89% statements / 76% branches) aren't met because `src/tools/` — the MCP-server-mode tool handlers — are almost entirely untested:

```
src/tools | 10.47 | 0 | 0 | 11.04
check-server.ts | 14.28 | 0 | 0 | 15.78
ci-report.ts | 13.04 | 0 | 0 | 14.28
diff-runs.ts | 15.78 | 0 | 0 | 15.78
get-history.ts | 11.53 | 0 | 0 | 13.63
get-last-run.ts | 13.04 | 0 | 0 | 13.04
helpers.ts | 4.76 | 0 | 0 | 5
lock-verify.ts | 10.34 | 0 | 0 | 11.11
record.ts | 16.66 | 0 | 0 | 16.66
replay.ts | 10.71 | 100 | 0 | 10.71
scan.ts | 11.53 | 0 | 0 | 13.04
score-server.ts | 11.53 | 0 | 0 | 11.53
test-servers.ts | 4.28 | 0 | 0 | 4.68
verify-tool.ts | 13.04 | 0 | 0 | 13.04
watch.ts | 10.34 | 0 | 0 | 10.34
```

`src/types` and `src/integrations/index.ts` are also at 0%.

Impact

Every PR's `coverage` check is red regardless of what the PR actually touches, which makes it useless as a real signal — it's already failing before any diff-specific coverage is even considered.

Not included here

Not attempting a fix in this issue — writing meaningful tests for 14 largely-untested tool handlers is a real body of work, not a quick fix, and deserves its own scoped effort (or a decision to adjust the threshold/scope it to changed files only) rather than a rushed pass bundled into an unrelated PR.

[albatrossflyon-coder]

Hey William,

Following up after digging into a few issues on mcp-observatory (just shipped #280 and #281) — found this one worth flagging separately, hence its own issue. Root cause is src/tools/* sitting at 10-15% coverage against a 90% global threshold. Didn't attempt a fix here since it's real scope, not a quick pass.

Also wanted to say — appreciate the follow. Been enjoying working in this codebase.

One other thing, no pressure either way: I'm doing OSS contributions right now partly to build up a portfolio, and I'm also open to freelance work if you ever know of anyone looking. Totally fine if not, just figured I'd mention it.

— Chris

[albatrossflyon-coder]

Hey William,

Following up after digging into a few issues on mcp-observatory (just shipped #280 and #281) — found something worth flagging separately: your coverage CI check has been failing on main for a few days now, not tied to any specific PR. Root cause is src/tools/* sitting at 10-15% coverage against a 90% global threshold. Didn't attempt a fix since it's real scope, not a quick pass.

Also wanted to say — appreciate the follow. Been enjoying working in this codebase.

One other thing, no pressure either way: I'm doing OSS contributions right now partly to build up a portfolio, and I'm also open to freelance work if you ever know of anyone looking. Totally fine if not, just figured I'd mention it.

— Chris

[KryptosAI]

Good catch on the coverage gap — the src/tools/* files are MCP server implementations that act as real endpoints, so they do hit the 10-15% range naturally since they're integration-tested via the CLI surface, not unit-tested directly. This is on the backlog to address properly (either by adding targeted unit tests or lowering the threshold for that subdirectory). Appreciate you flagging it.