[ENHANCEMENT] Add dist-scoped Vitest config and Turbo task for bundle-coupled tests

[edelauna]

Problem (one or two sentences)

The 13 root-level integration tests in src/__tests__/ (including dist_assets.spec.ts, extension wiring specs, and delegation flow specs) all require dist/ to be present and cannot be safely grouped with area-unit tests that have no bundle dependency.

Context (who is affected and when)

dist_assets.spec.ts directly validates dist/ file presence (WASM files, tree-sitter grammars, marketplace assets). The other specs in src/__tests__/ exercise extension and delegation behaviors that also depend on built artifacts. Grouping them with pure unit tests would either silently skip bundle-dependent assertions or force every area slice to depend on bundle. This is part of the coverage-slicing work tracked in #47 and depends on #114.

Desired behavior (conceptual, not technical)

A dedicated vitest.dist.config.ts covers src/__tests__/**. A corresponding test:coverage:dist Turbo task with dependsOn: ["bundle"] ensures the bundle is present before these tests run. Coverage output goes to coverage/dist/.

Constraints / preferences (optional)

• dependsOn in src/turbo.json for this task should only list bundle — @roo-code/types#build is inherited from root turbo.json.
• src/__tests__/ should remain the home for integration/dist tests only; pure unit tests belong in area subdirectories.

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Acceptance criteria (optional)

• vitest run --config vitest.dist.config.ts --coverage passes with dist/ present and fails cleanly without it.
• turbo run test:coverage:dist --filter=zoo-code --dry-run shows bundle in the dependency graph.
• Coverage output appears at coverage/dist/lcov.info.

Proposed approach (optional)

1. Create src/vitest.dist.config.ts scoping include to src/__tests__/** and coverage.reportsDirectory to coverage/dist/.
2. Add test:coverage:dist to src/turbo.json with dependsOn: ["bundle"] and outputs: ["coverage/dist/**"].

Trade-offs / risks (optional)

If future tests are added to src/__tests__/ that are not dist-coupled, they will unnecessarily depend on bundle. Keep src/__tests__/ for integration/dist tests only.

---

Parent issue: #47
Depends on: #114

[zoomote]

Draft PR #1614 implements a corrected version of this boundary. Current src/__tests__/ contains many ordinary source-level integration tests; repository inspection found only dist_assets.spec.ts reading real built output. The PR therefore creates a focused dist lane for that file instead of making the entire directory bundle-dependent, and creates a source-unit lane with equivalent LCOV line coverage.

Measured locally: the dist smoke is 40/40 assertions in ~435ms, while its forced bundle prerequisite is ~40s. Turbo dry-run confirms the dist lane depends on zoo-code#bundle; the source-unit lane depends on @roo-code/types#build and excludes only the dist test input. CI wiring remains intentionally deferred to #117/#118.

[zoomote]

Profiling for #1614 invalidated this issue's original scope and coverage assumptions:

• Only src/__tests__/dist_assets.spec.ts directly reads emitted dist/ assets; the other root-level tests do not require the bundle.
• The focused smoke test contains 40 artifact-presence assertions and contributes no source coverage.
• The unit lane retains complete source coverage: 467 files and 22,823/30,227 covered lines, matching the prior full-coverage command.
• Requiring --coverage and coverage/dist/ for the smoke lane would create an empty/redundant report and extra overhead without improving coverage integrity.

The validated replacement acceptance criteria are therefore: a dist-scoped Vitest config includes only __tests__/dist_assets.spec.ts; test:dist passes with the bundle and fails cleanly when required artifacts are absent; and its Turbo task depends on bundle. PR #1614 implements that narrower measured boundary.

I cannot edit the issue body with the task's available source-control permissions, so this comment records the corrected criteria. The PR will reference rather than close #116 until the stale issue body is updated or superseded.