## Problem

The release pipeline fails on `npm ci` with errors like:

```
npm error Missing: [email protected] from lock file
npm error Missing: @esbuild/[email protected] from lock file
...
```

## Root cause

The pipeline's `NodeTool@0` task uses `versionSpec: '24.x'`, which
provisions Node 24 + **npm 11**. However:

- This repo pins `"packageManager": "[email protected]"` in `package.json`.
- npm 10 only records platform-specific optional dependencies for the
**current** platform when generating `package-lock.json` (so a lockfile
generated on macOS only contains Mac binaries for `@esbuild/*` and
`turbo-*`).
- npm 11 requires **all** platform binaries to be present in the
lockfile and treats missing ones as out-of-sync, failing `npm ci`.

Lockfile is valid under npm 10 — `npm ci` succeeds locally. The mismatch
is purely between the pipeline's npm and the project's pinned npm.

## Fix

Pin the pipeline to Node 22 (LTS), which ships with npm 10, matching the
`packageManager` field and every developer's local environment.

## Alternative considered

Bumping the project to npm 11 (update `packageManager`, regenerate
lockfile under npm 11, force every dev to upgrade). Rejected as larger
blast radius for an unblock-the-release fix.

## Follow-up

This same change needs to be cherry-picked to `release` to unblock the
2.0.10 publish.