Greptile Summary

Cherry-picks the one-line npm fix from #28519 onto patch/1.86.0 to unblock the v1.86.0-stable Dockerfile.non_root build. Without npm on PATH, prisma-python fell back to a nodeenv-bootstrapped Node binary that cannot load libatomic.so.1 on Wolfi, causing prisma generate to exit with code 127.

• Adds npm alongside nodejs in the builder stage's apk add block so prisma generate (line 93) finds a system npm and skips the broken nodeenv fallback.
• The runtime stage (apk add at line 107) still installs only nodejs without npm; the runtime prisma generate (line 141) relies on PRISMA_OFFLINE_MODE=true and pre-copied engine binaries to avoid the same fallback path.

Confidence Score: 4/5

The builder-stage fix is correct and minimal. The only open question is whether the runtime-stage prisma generate (which does not install npm) is fully covered by PRISMA_OFFLINE_MODE=true and the pre-copied engine binaries.

The change is a targeted one-liner cherry-pick that directly addresses a documented build failure. The runtime stage's prisma generate run without npm is a plausible second exposure of the same issue, though environment variables and pre-built binaries are likely enough to prevent it. The test plan checkbox is still unchecked, so end-to-end confirmation is pending.

The runtime-stage apk add block in docker/Dockerfile.non_root (lines 103–108) is worth a second look to confirm that the missing npm there is intentional and covered by the offline-mode flags.

_{Reviews (1): Last reviewed commit: "fix(docker): restore npm to non_root bui..." | Re-trigger Greptile}