chore(repo): migrate from bun to pnpm

[haydenshively]

Part 1 of 2 for CRTR-2822. pnpm takes over installs, workspace resolution, the version catalog, and
script running. bun stays as the runtime and test runner, so this PR touches no test file and
bun test is unchanged. Part 2 removes bun (vitest, esbuild bundles, Node runtime).

Splitting it this way lands the entire security motivation now, without waiting on a 136-file vitest
port.

Why

A npm supply-chain attack prompted a team-wide decision (Slack #curators, 2026-07-17) to
standardize on pnpm. The deciding property is pnpm's default-deny on dependency lifecycle scripts: a
compromised transitive dependency cannot run arbitrary code at install time. bun has no equivalent.

The decision was already written up in docs/decisions/TIB-2026-07-20-migrate-to-pnpm.md, which
lived only on the unmerged claude/migrate-repo-pnpm-e5f4c1 (3 commits, @cashd, 2026-07-20, no PR).
That branch is 190 commits behind main and predates four workspaces, so this re-derives from it
rather than rebasing. The TIB is carried over here with Addendum A recording what changed.

Three settings the original branch omitted

Setting	Why it matters
strictDepBuilds: true	Without it an un-opted-in build script is a warning, not a failure — the deciding security property of the TIB would have been advisory only.
enablePrePostScripts: true	pnpm does not run npm-style pre/post scripts by default. prestart builds @repo/contracts' gitignored dist/; without this the bots cannot resolve their own workspace dependency.
allowBuilds: {}	Starts empty, not {esbuild: true} — nothing in the current tree declares preinstall/install/postinstall, and esbuild is absent entirely. It becomes the first entry in Part 2.

No dependency upgrades ride along

Regenerating the lockfile re-resolves every caret range, which would contradict the TIB's non-goal.
Catalog entries that drifted are pinned to what bun.lock had resolved:

• solc 0.8.35 → pinned. This one is not just parity: solc fixes the compiled bytecode of the
  soltag sol\``` lens templates and the Executor, so a silent bump would invalidate the recorded
  explorer-verification settings (0.8.35, optimizer runs=200).
• @internationalized/date 3.12.1, date-fns 4.1.0, @types/bun 1.3.13 — pinned.
• Remaining drift is dev-tooling transitives inside their declared ranges. The only runtime-reachable
  one is valibot 1.4.1 → 1.4.2 (patch, via @morpho-org/viem-dlc).
• Package set is otherwise identical; pnpm correctly skips one Windows-only optional binary.

Docker

Keeping FROM oven/bun was not viable: pnpm is activated through corepack, which those images do not
provide, and bun install --frozen-lockfile is no fallback once bun.lock is deleted. All three
images move to node:24.14.1-slim with the bun binary copied in. Both runtimes must stay on PATH
in the final image for this PR, because CMD fires prestart, which shells out to pnpm. Part 2
drops the bun binary and switches CMD to node dist/src/index.js.

Evidence

• Default-deny actually blocks CI — not a vacuous check. An esbuild probe on a clean
  node_modules exits 1 with ERR_PNPM_IGNORED_BUILDS; probe reverted, lockfile byte-identical
  after.
• prestart still runs — wiped packages/contracts/dist/, ran
  pnpm --filter @morpho-org/blue-liquidation run start, watched pnpm fire
  pnpm -r --parallel --if-present run build and rebuild it before reaching the bot's own config check.
• Tests byte-identical to main — 1412 pass, 3 skip, 3 fail, 1 error, 7732 expect() calls, 1418 tests across 136 files on both main (in a baseline worktree) and this branch. Same failing
  test names. The 3 failures are a pre-existing missing RPC_URL_8453 for the fork suites; CI
  supplies it as a secret.
• pnpm install --frozen-lockfile on a clean checkout: clean.
• pnpm -r run typecheck 12/12 Done · pnpm lint 0 warnings 0 errors · pnpm knip clean · pnpm format clean.
• pnpm --filter @repo/contracts run generate re-run; the only diff in the tracked generated sources
  is the command string in the header.
• pnpm -- forwarding verified against the market-making CLI (--json is honored), before rewriting
  ~22 README examples.
• Pre-commit hook exercised on the real commit: lint-staged + knip both ran under pnpm.

Containers run unprivileged

oven/bun ends with USER bun; the official node images define a node user (uid 1000) but do
not switch to it, so the base swap would have promoted a process holding a funded liquidator key to
root. Each Dockerfile now runs corepack enable as root (its shim lands in /usr/local/bin),
chowns /repo, then drops to USER node — every layer after that, the install, and CMD are
unprivileged.

Docker is verified

All three images build, docker run … id reports uid=1000(node) gid=1000(node), and the
blue-liquidation container runs prestart — writing @repo/contracts' gitignored dist/ as
non-root — before reaching its fail-loud Missing required env var: CHAIN_ID. Both pnpm 11.1.1 and
bun 1.3.12 are on PATH in the final image, as this intermediate state requires.

Not verified

Nothing outstanding.

Follow-ups

• Part 2: remove bun.
• The six open PRs (test(market-making): add MKT-1491 workflow e2e coverage #112, fix(bot-kit): stamp pending txs with the broadcast-time head #116, feat: add market maker parameter playground #122, feat(market-making): add docker image, compose, and docker hub publish #123, feat(market-making): support router ratifiers #124, fix(market-making): batch invalidation with Midnight multicall #125) add new bun:test files and Bun.* calls and
  will need a mechanical fix on rebase. feat(market-making): add docker image, compose, and docker hub publish #123 is the sharpest — it adds a bun-based
  bots/market-making/Dockerfile plus a Docker Hub publish workflow needing a node-slim port.
• Bump oxlint together with oxlint-tsgolint >= 0.24 (pin comment left in the catalog).
• Have an org admin allowlist pnpm/setup@*, then switch the setup action to it. Upstream scopes
  pnpm/action-setup to pnpm v10 and older and points v11+ at pnpm/setup, but morpho-org's
  Actions allowlist permits only the former — switching fails every job at the Setup step. Beyond the
  deprecation, pnpm/setup v2 verifies pnpm's release binary against GitHub's published SHA-256
  digest instead of bootstrapping through an npm ci of @pnpm/exe, which is the same threat model
  this PR is about. action-setup installs pnpm 11.1.1 correctly meanwhile.

🤖 Generated with Claude Code

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 88ae719a35

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[linear-code]

CRTR-2971