From fc8b283e2fdea9ecdbd3196faa5ede863290da03 Mon Sep 17 00:00:00 2001
From: RubenGlez <ruben.daren@gmail.com>
Date: Sat, 4 Jul 2026 01:00:30 +0200
Subject: [PATCH] docs: fix contradictory Node version in Install (>=24 ->
 >=22)

The Install section claimed Node >= 24, but package.json engines and the Design Choices section both say >= 22. >= 22 is the real floor (native type-stripping is stable on 22.18+). Align the Install line.

Claude-Session: https://claude.ai/code/session_01Be9Fxdq5NroabmT83VZuxs
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 24a0810..8c1f84d 100644
--- a/README.md
+++ b/README.md
@@ -74,7 +74,7 @@ Failure modes include `no_tool_call`, `wrong_tool`, `wrong_argument`, `missing_a
 npm install -g langdrift
 ```
 
-Requires Node >= 24. The published package ships compiled JavaScript, so no build step or type-stripping flags are needed to run the installed CLI.
+Requires Node >= 22. The published package ships compiled JavaScript, so no build step or type-stripping flags are needed to run the installed CLI.
 
 Working from a clone instead runs the TypeScript source directly via Node's native type stripping (`node ./src/cli.ts`), which is how the "30 seconds" demo above works without a build.