test: run CLI entry tests in-process so V8 coverage attributes them

[altaywtf]

Summary

Fixes #63. Mirrors the design from the sibling issue, landed in putdotio/taizn#62 (one design, two applications): subprocess-spawned CLI tests execute real code V8 coverage never attributes, understating the floor set in #61.

Design decision (shared): no released vitest can attribute subprocess coverage — vitest 4.1.10/4.1.11 has zero NODE_V8_COVERAGE handling; coverage.autoAttachSubprocess exists only in unreleased Vitest 5.0. Manual NODE_V8_COVERAGE plumbing + sourcemapped bundle remapping through a custom coverage provider is disproportionate machinery. So spawn-based tests were restructured to run the same entry in-process where the subprocess boundary isn't the thing under test.

Changed

• --completions and the package usage-error tests now run mainEffect(argv) in-process with console spies (rokit's entry was already importable and argv-parameterized, so no source changes were needed).
• The boot test still spawns dist/rokit.mjs — the process boundary is the thing under test there. That blind spot (the src/rokit.ts shim, already excluded from coverage) is now documented in vite.config.ts and AGENTS.md with the vitest 5 pointer.
• Coverage floors raised to the new measured baseline minus ~3-point headroom.

Risks

Low: test-only change plus threshold/doc updates. The in-process harness restores process.exitCode and console spies in a finally.

Verification

vp run verify green (check, skillcheck lint, typecheck, pack, smoke, coverage thresholds, npm pack).

Coverage delta (vp test run --coverage, same denominators):

Metric	Before	After	Old floor	New floor
Statements	65.91%	68.96%	63	66
Branches	53.42%	55.88%	51	53
Functions	57.86%	60.73%	55	58
Lines	65.83%	68.73%	63	66

Follow-Ups

When vite-plus ships vitest 5, enable coverage.autoAttachSubprocess and re-measure to close the boot-test blind spot (same follow-up as taizn).

[Copilot]

Pull request overview

This PR restructures CLI entrypoint tests to run in-process (instead of spawning the built CLI) so V8 coverage correctly attributes executed code, addressing the subprocess coverage blind spot described in #63 and aligning with the sibling design referenced in the PR description.

Changes:

• Updated CLI tests to call mainEffect(argv) in-process with console spies for cases where the subprocess boundary is not under test.
• Documented the remaining subprocess coverage blind spot (boot test still spawns dist/rokit.mjs) in vite.config.ts and AGENTS.md, with a pointer to Vitest 5’s coverage.autoAttachSubprocess.
• Raised V8 coverage thresholds to match the new measured baseline (with headroom).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
vite.config.ts	Documents the subprocess coverage limitation and raises coverage thresholds to the new baseline.
test/cli.test.ts	Introduces an in-process CLI runner for coverage-attributed tests while keeping a spawn-based boot test.
AGENTS.md	Captures the testing/coverage approach as a repo “Sharp Edges” guidance note for contributors.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[putio-releaser]

🎉 This PR is included in version 2.4.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀