feat: migrate to pnpm v11.0.0-rc.0

[John-David Dalton (jdalton)]

Summary

• Migrate .npmrc pnpm settings → pnpm-workspace.yaml (ignoreScripts, linkWorkspacePackages, loglevel)
• Migrate package.json pnpm.overrides (49 entries) → pnpm-workspace.yaml overrides:
• Migrate package.json pnpm.patchedDependencies (7 patches) → pnpm-workspace.yaml
• Remove unused patches: @npmcli/run-script@10.0.3, node-gyp@12.1.0 (older versions no longer resolved)
• Add allowBuilds for esbuild, postject
• Update packageManager to pnpm@11.0.0-rc.0
• Regenerate lockfile (v9.0 format)

Breaking changes handled

• .npmrc → pnpm-workspace.yaml config split (pnpm v11 only reads auth/registry from .npmrc)
• pnpm field in package.json no longer read by v11
• strictDepBuilds default requires explicit allowBuilds
• Lockfile v9.0 format (incompatible with v10)

Dependencies

• Requires socket-registry PR Bump eslint from 9.14.0 to 9.15.0 #253 (CI setup action updated for v11 tarballs)

Test plan

• pnpm install succeeds
• pnpm run build:cli succeeds
• Tests pass (pre-commit hook verified)
• CI workflows pass

---

Note

Medium Risk
Upgrades core package manager and relocates dependency override/patch configuration, which can change resolution and install/build behavior across the monorepo. Risk is mainly CI/dev-environment breakage rather than runtime code changes.

Overview
Migrates the repo to pnpm v11.0.0-rc.0, updating package.json packageManager and engine requirements.

Moves pnpm-specific configuration out of .npmrc and package.json into pnpm-workspace.yaml, including install policies, overrides, patchedDependencies, and explicit allowBuilds entries required by pnpm v11’s stricter build-script defaults.

^{Reviewed by Cursor Bugbot for commit 0c4f355. Configure here.}