[timeleft--]

Answers Q5 of iaser-ai#335.

What was wrong

The MCP tests run the built artifacts: dist/server/index.js, dist/view.html and the Workers bundle. pnpm mcp test ran them without building, so after a source change they passed against the old build.

Shown on this branch before the change: I built, then made src/node/index.ts throw on import. The old pnpm test passed all 154 tests. The new one rebuilds and fails on the thrown error.

Change

• test runs build and build:worker before the tests.

• verify no longer runs its own build steps, so it builds each target once.

• In apps/mcp/turbo.json:

  • test drops its build and build:worker dependencies, and declares dist/** and dist-worker/** as its outputs.
  • test:browser now depends on test instead of build.

  Together these keep a single Turbo run from building in two tasks at once, and let a cache hit on test restore the build that test:browser reads.

• The README says test builds first and that test:browser reads the build without making one.

No version bump: this changes only test wiring and docs.

Verification

• pnpm mcp verify passed: 154 tests and 78 browser checks. Each target was built once.
• turbo run test test:browser --filter ansari-mcp --force ran test, then test:browser, and both passed.
• Then I deleted dist/ and dist-worker/ and ran turbo run test:browser. test was a cache hit that restored the build, and the 78 browser checks passed.

pnpm mcp test:browser run on its own still reads whatever is in dist/. That is unchanged and documented.

🤖 Generated with Claude Code

[yia-mw-agent]

Reviewed the full merge-base-to-head diff (base develop 396b091 = merge-base, 3 files) at 69dba4e. No material defects.

Helmet-Review-Request: #10 (comment)

What I checked:

• apps/mcp/package.json: test now runs build and build:worker before the tests, and verify drops its own build steps, so each target is built once. The root test script excludes ansari-mcp, so no other job is affected.
• apps/mcp/turbo.json: test drops its build dependencies and declares dist/** and dist-worker/** as outputs; test:browser depends on test. This avoids two Turbo tasks building at once and lets a cache hit restore the build.
• apps/mcp/README.md matches the new behaviour.

Validation at this exact head (apps/mcp): lint and typecheck pass; pnpm test rebuilt both targets and passed 154/154; test:browser passed 78 checks with no errors. Under Turbo (turbo run test test:browser --filter ansari-mcp --env-mode=loose): test ran, then test:browser passed. After moving dist/ and dist-worker/ aside, turbo run test:browser showed test as a cache hit that restored both directories, and the 78 checks passed. This matches the PR description. CI checks (MCP application, api, auth, frontend, gitleaks) are green. Live head matched 69dba4e at start and before submission.

Non-blocking: under Turbo's default strict env mode, test:browser does not see PLAYWRIGHT_BROWSERS_PATH. That only mattered in my sandbox (a non-default browser cache) and is unchanged by this PR.