build(mcp-server): avoid tsup DTS worker OOM by delegating to tsc --allowJs --emitDeclarationOnly

The 47-entry-point mcp-server bundle causes tsup's rollup-dts worker to
hit ERR_WORKER_OUT_OF_MEMORY on Node 22 / Windows (pre-existing; reproducible
on commits before 0.8.43).  Split the build so tsup handles the ESM bundle
and a post-step `tsc --allowJs --emitDeclarationOnly` generates the .d.ts
files.  This unblocks the full extension build pipeline.

Generated with [Devin](https://cli.devin.ai/docs)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>

Author: A.R.

packages/mcp-server/package.json

@@ -126,7 +126,7 @@
     "CHANGELOG.md"
   ],
   "scripts": {
-    "build": "tsup && node scripts/post-build-shebang.mjs",
+    "build": "tsup --no-dts && tsc --allowJs --emitDeclarationOnly && node scripts/post-build-shebang.mjs",
     "typecheck": "tsc -p tsconfig.json --noEmit",
     "test": "cd ../.. && npx vitest run packages/mcp-server/test",
     "test:coverage": "cd ../.. && npx vitest run --coverage packages/mcp-server/test"

packages/mcp-server/tsup.config.ts

@@ -51,7 +51,11 @@ export default defineConfig({
   target: "node20",
   outDir: "dist",
   clean: true,
-  dts: true,
+  // tsup's rollup-dts worker thread OOMs on this package's 47 entry points
+  // under Node 22 / Windows (pre-existing; fails even on commits before 0.8.43).
+  // Declarations are generated separately with tsc --allowJs --emitDeclarationOnly
+  // in the package.json build script, which is faster and avoids the worker heap.
+  dts: false,
   // got-scraping and its transitive data-bearing deps must resolve at runtime
   // from node_modules (they load JSON data files via fs.readFileSync that tsup
   // can't inline). Same story for patchright (native Chromium).