fix(sandbox): upgrade Node runtime to 24.18.0 (#83)

## Summary
- upgrades the single repository, CI, local-container, web, sandbox, and
generated-app Node baseline to 24.18.0
- pins both Docker images to the verified multi-architecture Node
24.18.0 image digest
- makes protected Daytona snapshot publication fail unless the candidate
actually runs Node 24.18.0
- regenerates only the affected npm lock metadata

## Context
Production upload QA proved that files persist under the project
`uploads` directory, remain available through the slash picker in later
chats, and are readable by the agent. Recovery of one pre-existing
mobile workspace still failed because Node 22.22.2/libuv treats
timestamp preservation on the Daytona-mounted workspace as fatal,
causing pnpm to exit with `EPERM: operation not permitted, futime`.

Node 24.18.0 contains the upstream mounted-filesystem copy fix and is
compatible with the pinned npm 12.0.1 and pnpm 11.15.0 toolchain. This
changes the runtime baseline directly; it does not add a package-manager
workaround or legacy path.

## Decisions
| Decision | Choice | Reasoning |
|---|---|---|
| Runtime | Node 24.18.0 LTS everywhere | One version across local, CI,
Vercel, Daytona, and generated apps |
| Image integrity | Exact version plus immutable OCI digest |
Reproducible image input across architectures |
| Publication guard | Assert the exact Node version in snapshot smoke
tests | Prevents a mislabeled or stale runtime from being promoted |
| Migration scope | No database change | The repository remains at
exactly one SQL migration |

## Verification
- [x] full workspace typecheck under Node 24.18.0 — 46/46 tasks passed
- [x] full workspace and repository lint under Node 24.18.0 — no
warnings
- [x] production build under Node 24.18.0 — 26/26 tasks passed
- [x] operational script typecheck, architecture boundaries, and
dead-code scan passed
- [x] GitHub Actions workflow and embedded shell passed
actionlint/shellcheck
- [x] five npm locks and both pnpm template locks validated under Node
24.18.0
- [x] official Node image digest independently resolved before pinning
- [ ] protected AMD64 sandbox build, vulnerability/secret scan, runtime
smoke test, and Daytona snapshot publication after merge
- [ ] direct production recovery QA after the new snapshot is promoted

No database migration or data mutation is included. No Linear issue or
plan document is associated with this production QA fix.

Author: iamjr15

.github/actions/setup-repository/action.yml

@@ -19,7 +19,7 @@ runs:
     - uses: pnpm/action-setup@0ebf47130e4866e96fce0953f49152a61190b271 # v6.0.9
     - uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
       with:
-        node-version: 22.22.2
+        node-version: 24.18.0
         cache: pnpm
     - name: Install workspace dependencies
       shell: bash

.github/workflows/build-snapshot.yml

@@ -113,7 +113,7 @@ jobs:
           docker run --rm --platform=linux/amd64 --entrypoint /bin/sh "$IMAGE_TAG" -lc '
             test "$(id -un)" = node
             test "$PWD" = /workspace
-            node --version
+            test "$(node --version)" = v24.18.0
             npm --version
             pnpm --version
             python3 --version

.nvmrc

@@ -1 +1 @@
-22.22.2
+24.18.0

README.md

@@ -46,8 +46,8 @@ docker compose version
 docker info
 ```
 
-The expected Node and pnpm versions are `v22.22.2` and `11.15.0`. Do not ignore
-an engine warning: select or install Node 22.22.2 before installing packages or
+The expected Node and pnpm versions are `v24.18.0` and `11.15.0`. Do not ignore
+an engine warning: select or install Node 24.18.0 before installing packages or
 running repository commands. Docker must be running before `pnpm dev`.
 
 ### Configure local credentials
@@ -104,7 +104,7 @@ From the repository root:
 pnpm dev
 ```
 
-The first run builds the pinned Node 22.22.2/pnpm 11.15.0 image, installs the
+The first run builds the pinned Node 24.18.0/pnpm 11.15.0 image, installs the
 locked workspace dependencies inside it, builds shared packages, validates
 `.env.local`, generates permission-restricted local Wrangler configs, and then
 starts the watchers. Subsequent source edits are synchronized into the
@@ -152,7 +152,7 @@ workflow can remove remote resources correctly.
 
 ### Troubleshooting
 
-- **Node engine mismatch:** run `nvm install 22.22.2 && nvm use 22.22.2`, then
+- **Node engine mismatch:** run `nvm install 24.18.0 && nvm use 24.18.0`, then
   confirm `node --version` before retrying.
 - **Docker cannot connect:** start Docker Desktop or the Docker daemon and
   confirm `docker info` succeeds.

apps/web/package.json

@@ -5,7 +5,7 @@
   "type": "module",
   "packageManager": "pnpm@11.15.0",
   "engines": {
-    "node": "22.22.2"
+    "node": "24.18.0"
   },
   "scripts": {
     "build": "next build",

infra/containers/dev/Dockerfile

@@ -1,4 +1,4 @@
-FROM node:22.22.2-bookworm-slim@sha256:9f6d5975c7dca860947d3915877f85607946403fc55349f39b4bc3688448bb6e
+FROM node:24.18.0-bookworm-slim@sha256:6f7b03f7c2c8e2e784dcf9295400527b9b1270fd37b7e9a7285cf83b6951452d
 
 ENV PNPM_HOME=/pnpm
 ENV PATH=$PNPM_HOME:$PATH

infra/containers/sandbox/Dockerfile

@@ -1,4 +1,4 @@
-FROM node:22.22.2-bookworm-slim@sha256:9f6d5975c7dca860947d3915877f85607946403fc55349f39b4bc3688448bb6e
+FROM node:24.18.0-bookworm-slim@sha256:6f7b03f7c2c8e2e784dcf9295400527b9b1270fd37b7e9a7285cf83b6951452d
 
 ARG CODE_SERVER_VERSION=4.128.0
 ARG CODE_SERVER_SHA256=79ba26bf186e5268a22b7c17b30a5f288a16c37791f0b86c27859e8fef103188

infra/containers/sandbox/app-generators/package-lock.json

@@ -3,7 +3,7 @@
   "private": true,
   "version": "0.0.0",
   "engines": {
-    "node": "22.22.2"
+    "node": "24.18.0"
   },
   "dependencies": {
     "create-next-app": "16.2.11"

infra/containers/sandbox/app-generators/package.json

@@ -5,7 +5,7 @@
   "private": true,
   "packageManager": "pnpm@11.15.0",
   "engines": {
-    "node": "22.22.2"
+    "node": "24.18.0"
   },
   "scripts": {
     "start": "expo start",