[bluetomlee]

Fixes #4930

Summary

src/everything/tsconfig.json had no exclude, so tsc emitted __tests__/** and vitest.config.js into dist/, and "files": ["dist"] published them. This adds the same exclude list src/filesystem/tsconfig.json already uses, so the tarball ships only the server and its docs/, matching the other three TS servers.

Changes

• src/everything/tsconfig.json — add exclude: **/__tests__/**, **/*.test.ts, **/*.spec.ts, vitest.config.ts (list taken verbatim from src/filesystem/tsconfig.json).

Verification (before / after)

Clean rebuild of src/everything (npm install → npm run build), original config vs. this branch:

	dist files	test artifacts in dist
before	50	6 (__tests__/{prompts,registrations,resources,server,tools}.test.js + vitest.config.js)
after	44	0

npm pack --dry-run after the change lists only README.md, the compiled server files under dist/, and dist/docs/* — no tests, no test config.

Tests are unaffected (Vitest compiles from source, not dist/): npx vitest run → 109 passed (5 test files), identical before and after.

Checklist

• Linked issue everything: compiled tests and vitest.config ship in the published tarball #4930; implements the fix suggested there (align with src/filesystem's exclude)
• Single concern: 1 file changed, +7/−1
• Package tests pass locally; tarball contents verified via npm pack --dry-run

[changeset-bot]

⚠️ No Changeset found

Latest commit: da3b379

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cliffhall]

Thanks, @bluetomlee but this was meant to be against v2/main with changesets.