docs(ci): fix stale vitest.config.ts comment claiming lib/cli-error.js has no in-process test

[JSONbored]

Context

vitest.config.ts's coverage.include section carries a comment above the
"packages/loopover-mcp/lib/**/*.js" entry stating: "4 of the 5 files (format-table/local-branch/
redact-local-path/telemetry) are already imported in-process by test/unit/.test.ts; lib/cli-error.js
currently has no in-process test at all, so it will need one before a PR touching it can pass
codecov/patch -- that's intended enforcement, not a bug."* This was true when written (2026-07-19,
commit 80b59c64). One day later, PR #7409 (2026-07-20, commit 0d896ce62, "Phase 1 of #7291") added
test/unit/mcp-cli-error.test.ts, which does exactly the missing thing: it imports cli-error.js
in-process and exercises all 3 of its exports across 5 test cases (reportCliFailure with/without
--json, default exit code, argsWantJson, describeCliError). The comment was never updated, so it
now tells a future contributor something false about the current state of test coverage in this
package — exactly the kind of stale-comment-vs-code drift this audit was asked to look for.

Requirements

• Update the comment above the "packages/loopover-mcp/lib/**/*.js" entry in vitest.config.ts to
  remove or correct the now-false "cli-error.js currently has no in-process test at all" sentence,
  reflecting that all 5 of the package's lib/ files (format-table, local-branch,
  redact-local-path, telemetry, cli-error) now have in-process tests under test/unit/.
• Purely a comment change — do not alter any coverage.include/coverage.exclude glob or any other
  behavior in this file.

Deliverables

• The stale sentence in vitest.config.ts's comment block is corrected to match current test-coverage reality

Test Coverage Requirements

Not applicable — comment-only change, no executable code path affected, nothing to regression-test.

Expected Outcome

vitest.config.ts's own inline documentation about packages/loopover-mcp/lib/** coverage accurately
reflects, as of the change, which files have in-process tests — a future contributor reading this
comment before touching cli-error.js (or any sibling file) is no longer told something false.

Links & Resources

• vitest.config.ts (comment above the "packages/loopover-mcp/lib/**/*.js" line in coverage.include)
• test/unit/mcp-cli-error.test.ts (the test that made the comment stale)
• Commit 80b59c64 (introduced the claim), commit 0d896ce62 / PR chore(mcp): add tsc build pipeline + convert small lib utilities to TypeScript (Phase 1 of #7291) #7409 (made it stale)

[linear-code]

JSO-5296