fix(build): pin pnpm to 10.32.1 (Railway was hitting bleeding-edge)

Previous fixes (move overrides to pnpm-workspace.yaml + add
onlyBuiltDependencies for esbuild/msw/sharp) work locally on pnpm
10.32.1 — install --frozen-lockfile finishes clean, no
ignored-builds warning. But Railway still failed:

  [ERR_PNPM_IGNORED_BUILDS] Ignored build scripts: esbuild@0.27.2, msw@2.11.3, sharp@0.34.4

Root cause: the Dockerfile runs `corepack prepare pnpm@latest --activate`
which pulls whatever's *currently* on the npm registry. The latest
pnpm tightened its build-script policy to a hard error even when
onlyBuiltDependencies is set — or maybe the YAML key changed names in
a newer release. Either way, "@latest" gave us a moving target.

Two-part pin so local + CI stay aligned:

- Dockerfile: corepack prepare pnpm@10.32.1 (no longer @latest).
- package.json: packageManager: pnpm@10.32.1 — corepack will use
  this for anyone running scripts locally too.

Bump intentionally when we validate a newer pnpm.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ralyodio

Dockerfile

@@ -63,7 +63,11 @@ ENV VITE_LOG_LEVEL=$VITE_LOG_LEVEL
 WORKDIR /app
 # Copy lockfiles first for better caching
 COPY pnpm-lock.yaml* package.json pnpm-workspace.yaml ./
-RUN corepack enable && corepack prepare pnpm@latest --activate
+# Pin pnpm to a known-good version. `pnpm@latest` pulls whatever's on
+# the npm registry RIGHT NOW, so Railway can suddenly start failing
+# when pnpm ships a stricter minor (e.g. ERR_PNPM_IGNORED_BUILDS hard-
+# fail vs warn). Bump intentionally when we test a new version.
+RUN corepack enable && corepack prepare pnpm@10.32.1 --activate
 RUN pnpm install --frozen-lockfile
 
 # Copy the rest and build

package.json

@@ -9,6 +9,7 @@
   "engines": {
     "node": ">=20.0.0"
   },
+  "packageManager": "pnpm@10.32.1",
   "scripts": {
     "cli": "node bin/qryptchat-cli.js",
     "dev": "vite dev",