From 82cb85f163de46e858dd0a3d30bf930163116a77 Mon Sep 17 00:00:00 2001
From: Mike Schwarz <171890339+mvschwarz@users.noreply.github.com>
Date: Wed, 21 Oct 2026 16:59:07 -0700
Subject: [PATCH] docs(contributing): use the npm that comes with Node; a
 distro npm 9 fails a fresh npm ci (#1731)

Someone setting up a clone with a separately packaged npm 9, such as Debian's `npm` package (9.2.0), hits a failed `npm ci`: `ENOENT` on `chmod` of `node_modules/@openrig/tui/dist/main.js`.

CONTRIBUTING's setup paragraph now says to use the npm that comes with your Node, which is npm 10 or newer for Node 22 and 24, and shows how to check (`npm --version`). `engines.npm` is unchanged.

Text only: `CONTRIBUTING.md` +3/-1.
---
 CONTRIBUTING.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fab0776c2..b8630fd32 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -42,7 +42,9 @@ repository, and we're happy to link to it.
 
 Node `^22 || ^24`, a working `tmux` and `rsync` are required. macOS includes `rsync`; many Linux
 installs don't (`sudo apt-get install rsync` on Debian or Ubuntu). `npm test` and `npm run mirror-skills`
-use it. Then:
+use it. Use the npm that comes with your Node, which is npm 10 or newer (`npm --version` shows which you
+have). A separately packaged npm 9, such as Debian or Ubuntu's `npm` package, fails a fresh `npm ci` with
+`ENOENT` on `chmod` of `node_modules/@openrig/tui/dist/main.js`. Then:
 
 ```bash
 git clone https://github.com/mvschwarz/openrig.git