build: drop ambient host types from the published build

[b2m9]

Adds "types": [] to tsconfig.build.json.

Why

src/ imports no Node built-ins — the fold is pure ECMAScript. But the build config inherits types: ["node"] from the root tsconfig.json, so a stray import { randomUUID } from "node:crypto" in src/ would compile cleanly, pass lint, and break only for consumers who bundle the package for a browser.

tsconfig.build.json already scopes to include: ["src"], so emptying the types list lands exactly on the published surface. The test program is untouched and keeps the Node globals that vitest and vite pull in through their own type declarations.

Verification

• npm run check passes end to end.
• The guard fires. With import { randomUUID } from "node:crypto" added to src/objects.ts, npm run build fails:

  src/objects.ts(42,28): error TS2591: Cannot find name 'node:crypto'.
  

• Note that npm run typecheck still passes on that same code, since the root config supplies node types to src. That is why the guard belongs in the build config. Both steps run under npm run check, so CI catches it either way.
• The emitted .d.ts references nothing node-related, before or after.

Scope

Independent of #6 — that one pins the @types/node version, this one bounds where those types apply. Branched off main, so the two can merge in either order.

🤖 Generated with Claude Code

---

Summary by cubic

Remove ambient Node types from the published build to keep the library browser-safe. Set "types": [] in tsconfig.build.json so any Node built-in import in src fails at build time, while tests keep Node types from the root config.

^{Written for commit 49a0cad. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}