@ngockhoale/ukit 2.2.5 → 2.2.6

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 All notable changes to UKit are documented here.
 
+## 2.2.6 - 2026-08-27
+
+Follow-up to a real-world report: a user on a Bun-hosted/self-compiled omp build kept getting
+every Edit/Write blocked with `UKit OMP hook runner failed before producing a valid result
+(killed=true, ..., runtime=/Users/.../bin/omp)`. The diagnostic added in 2.2.4 was already
+honest about the failure, but it did not say *why* — `runtime=` pointed straight at omp's own
+binary (proof that `process.execPath` inside that omp build resolves to omp itself, not a real
+Node.js binary), yet the message never told the user the fix was to set `UKIT_NODE_PATH`.
+
+### Fixed
+
+- **The omp bridge's transport-failure message named the wrong-runtime symptom but never the
+  fix.** [`ukit-bridge.js`](.omp/hooks/pre/ukit-bridge.js) already resolved
+  `process.env.UKIT_NODE_PATH || process.execPath` and reported the resolved `runtime` on failure
+  (2.2.4), but a user seeing `runtime=/Users/lenk/.local/bin/omp` had no way to know that string
+  meant "wrong binary" or what to do about it. When `UKIT_NODE_PATH` is unset, the failure
+  message now appends: the reported runtime may not be a real Node.js binary, and the exact fix —
+  `export UKIT_NODE_PATH="$(command -v node)"`. No behavior change when `UKIT_NODE_PATH` is
+  already set.
+
+### Added
+
+- **2 regression tests** in `tests/hooks/ompHookBridge.test.js` (case 13) — the wrong-runtime
+  hint appears when `UKIT_NODE_PATH` is unset, and is omitted when it is already set.
+
 ## 2.2.5 - 2026-08-27
 
 Follow-up to the user's report that UKit had become too heavy-handed: too many hook scripts firing per tool call, too much blocking, and a concrete false-positive in the destructive-command gate itself. This wave trims default hook wiring and fixes the false positive, while explicitly preserving `rm`/destructive-command protection as instructed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngockhoale/ukit",
-  "version": "2.2.5",
+  "version": "2.2.6",
   "description": "Install/update an index-first AI workspace for Claude Code, OpenAI Codex, OpenCode, and omp (Oh My Pi).",
   "license": "MIT",
   "type": "module",

package/templates/.omp/hooks/pre/ukit-bridge.js

@@ -241,10 +241,15 @@ export async function runScriptChain(
       wrapperError: chainResult?.wrapperError || null,
     };
     recordHookErrorDiagnostic(projectRoot, payload.session_id, diagnostic);
+    const nodePathHint = process.env.UKIT_NODE_PATH
+      ? ''
+      : ` "${diagnostic.nodeExecutable}" may not be a real Node.js binary (e.g. a Bun-hosted or `
+        + `self-compiled omp reports its own path as process.execPath). If so, set UKIT_NODE_PATH `
+        + `to one, e.g.: export UKIT_NODE_PATH="$(command -v node)".`;
     const reason = `UKit OMP hook runner failed before producing a valid result `
       + `(killed=${diagnostic.killed}, code=${diagnostic.code}, elapsedMs=${diagnostic.elapsedMs}, `
       + `runtime=${diagnostic.nodeExecutable}). No safety-gate verdict was available for [${scripts.join(', ')}]. `
-      + `See .ukit/storage/cache/hook-errors/.`;
+      + `See .ukit/storage/cache/hook-errors/.${nodePathHint}`;
     if (failClosedOnTransportError) {
       return { block: true, reason, context, invoked };
     }