fix(deps): better-sqlite3 11 → 12 (Node 26 install fix)

better-sqlite3@11 has no prebuilt binary for Node 26, so npm install fell
back to a node-gyp compile that fails against Node 26's V8 (GetPrototype /
GetIsolate / PropertyCallbackInfo::This removed). Users on current Node
could not install the project at all.

@12.11.1 ships prebuilt binaries for Node 20.x–26.x, so install just
downloads the matching binary — no compiler, no failure. Verified: fresh
clone + @12 passes the full 38-test suite on both Node 22 and Node 26.

- package.json: better-sqlite3 ^11 → ^12
- ci.yml: add Node 24 to the matrix (now 20/22/24)
- README: Node-version troubleshooting note
- .nvmrc: pin recommended Node 22 LTS

Author: Sage Hart

.github/workflows/ci.yml

@@ -31,7 +31,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node-version: [20, 22]
+        node-version: [20, 22, 24]
     steps:
       - uses: actions/checkout@v7
       - name: Use Node.js ${{ matrix.node-version }}

.nvmrc

@@ -0,0 +1 @@
+22

README.md

@@ -67,6 +67,11 @@ npm run dev        # boot the server + dashboard on $PORT or 3000
 
 Open `http://localhost:3000/`. With no key set, agents run in **simulation** — click **▶ Run demo** to watch a curated 5-agent scenario auto-play through real approval gates.
 
+> **Node version:** requires Node 20+ (verified through Node 26). If `npm install`
+> fails while compiling `better-sqlite3` (a V8-API error from node-gyp), you're on
+> an unsupported Node — use Node 22 LTS. On supported versions the install uses a
+> prebuilt binary, so no compiler is needed.
+
 ### Live demo (one-click deploy)
 
 No clone required — run the control plane in the cloud in simulation mode, then

package-lock.json

@@ -42,7 +42,7 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "better-sqlite3": "^11.3.0",
+    "better-sqlite3": "^12.11.1",
     "express": "^5.2.1",
     "nanoid": "^5.0.7",
     "ws": "^8.18.0",