inillucent 1.0.31 → 1.0.32

package/bin/inillucent-mcp.mjs

@@ -1,33 +1,33 @@
-#!/usr/bin/env node
-// The `inillucent-mcp` shim: resolve the platform binary and become it.
-//
-// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
-// execve and this has to work on Windows. The child's exit code and its signal
-// are both passed back up: a wrapper that always exited 0 would break every
-// script that branches on the exit code, and inillucent's exit codes carry
-// meaning - 3 is "the engine has not built that".
-import { spawn } from 'node:child_process';
-import { resolveBinary } from '../resolve.mjs';
-
-let binary;
-try {
-  binary = resolveBinary('inillucent-mcp');
-} catch (why) {
-  process.stderr.write(String(why.message ?? why) + '\n');
-  process.exit(1);
-}
-
-const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
-child.on('error', (why) => {
-  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
-  process.exit(1);
-});
-child.on('exit', (code, signal) => {
-  if (signal) {
-    // Re-raise it on ourselves so a shell sees the same thing it would have
-    // seen from the real program, rather than a plain exit.
-    process.kill(process.pid, signal);
-    return;
-  }
-  process.exit(code ?? 0);
-});
+#!/usr/bin/env node
+// The `inillucent-mcp` shim: resolve the platform binary and become it.
+//
+// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
+// execve and this has to work on Windows. The child's exit code and its signal
+// are both passed back up: a wrapper that always exited 0 would break every
+// script that branches on the exit code, and inillucent's exit codes carry
+// meaning - 3 is "the engine has not built that".
+import { spawn } from 'node:child_process';
+import { resolveBinary } from '../resolve.mjs';
+
+let binary;
+try {
+  binary = resolveBinary('inillucent-mcp');
+} catch (why) {
+  process.stderr.write(String(why.message ?? why) + '\n');
+  process.exit(1);
+}
+
+const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
+child.on('error', (why) => {
+  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
+  process.exit(1);
+});
+child.on('exit', (code, signal) => {
+  if (signal) {
+    // Re-raise it on ourselves so a shell sees the same thing it would have
+    // seen from the real program, rather than a plain exit.
+    process.kill(process.pid, signal);
+    return;
+  }
+  process.exit(code ?? 0);
+});

package/bin/inillucent-migrate.mjs

@@ -1,33 +1,33 @@
-#!/usr/bin/env node
-// The `inillucent-migrate` shim: resolve the platform binary and become it.
-//
-// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
-// execve and this has to work on Windows. The child's exit code and its signal
-// are both passed back up: a wrapper that always exited 0 would break every
-// script that branches on the exit code, and inillucent's exit codes carry
-// meaning - 3 is "the engine has not built that".
-import { spawn } from 'node:child_process';
-import { resolveBinary } from '../resolve.mjs';
-
-let binary;
-try {
-  binary = resolveBinary('inillucent-migrate');
-} catch (why) {
-  process.stderr.write(String(why.message ?? why) + '\n');
-  process.exit(1);
-}
-
-const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
-child.on('error', (why) => {
-  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
-  process.exit(1);
-});
-child.on('exit', (code, signal) => {
-  if (signal) {
-    // Re-raise it on ourselves so a shell sees the same thing it would have
-    // seen from the real program, rather than a plain exit.
-    process.kill(process.pid, signal);
-    return;
-  }
-  process.exit(code ?? 0);
-});
+#!/usr/bin/env node
+// The `inillucent-migrate` shim: resolve the platform binary and become it.
+//
+// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
+// execve and this has to work on Windows. The child's exit code and its signal
+// are both passed back up: a wrapper that always exited 0 would break every
+// script that branches on the exit code, and inillucent's exit codes carry
+// meaning - 3 is "the engine has not built that".
+import { spawn } from 'node:child_process';
+import { resolveBinary } from '../resolve.mjs';
+
+let binary;
+try {
+  binary = resolveBinary('inillucent-migrate');
+} catch (why) {
+  process.stderr.write(String(why.message ?? why) + '\n');
+  process.exit(1);
+}
+
+const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
+child.on('error', (why) => {
+  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
+  process.exit(1);
+});
+child.on('exit', (code, signal) => {
+  if (signal) {
+    // Re-raise it on ourselves so a shell sees the same thing it would have
+    // seen from the real program, rather than a plain exit.
+    process.kill(process.pid, signal);
+    return;
+  }
+  process.exit(code ?? 0);
+});

package/bin/inillucent-shell.mjs

@@ -1,33 +1,33 @@
-#!/usr/bin/env node
-// The `inillucent-shell` shim: resolve the platform binary and become it.
-//
-// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
-// execve and this has to work on Windows. The child's exit code and its signal
-// are both passed back up: a wrapper that always exited 0 would break every
-// script that branches on the exit code, and inillucent's exit codes carry
-// meaning - 3 is "the engine has not built that".
-import { spawn } from 'node:child_process';
-import { resolveBinary } from '../resolve.mjs';
-
-let binary;
-try {
-  binary = resolveBinary('inillucent-shell');
-} catch (why) {
-  process.stderr.write(String(why.message ?? why) + '\n');
-  process.exit(1);
-}
-
-const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
-child.on('error', (why) => {
-  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
-  process.exit(1);
-});
-child.on('exit', (code, signal) => {
-  if (signal) {
-    // Re-raise it on ourselves so a shell sees the same thing it would have
-    // seen from the real program, rather than a plain exit.
-    process.kill(process.pid, signal);
-    return;
-  }
-  process.exit(code ?? 0);
-});
+#!/usr/bin/env node
+// The `inillucent-shell` shim: resolve the platform binary and become it.
+//
+// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
+// execve and this has to work on Windows. The child's exit code and its signal
+// are both passed back up: a wrapper that always exited 0 would break every
+// script that branches on the exit code, and inillucent's exit codes carry
+// meaning - 3 is "the engine has not built that".
+import { spawn } from 'node:child_process';
+import { resolveBinary } from '../resolve.mjs';
+
+let binary;
+try {
+  binary = resolveBinary('inillucent-shell');
+} catch (why) {
+  process.stderr.write(String(why.message ?? why) + '\n');
+  process.exit(1);
+}
+
+const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
+child.on('error', (why) => {
+  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
+  process.exit(1);
+});
+child.on('exit', (code, signal) => {
+  if (signal) {
+    // Re-raise it on ourselves so a shell sees the same thing it would have
+    // seen from the real program, rather than a plain exit.
+    process.kill(process.pid, signal);
+    return;
+  }
+  process.exit(code ?? 0);
+});

package/bin/inillucent.mjs

@@ -1,33 +1,33 @@
-#!/usr/bin/env node
-// The `inillucent` shim: resolve the platform binary and become it.
-//
-// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
-// execve and this has to work on Windows. The child's exit code and its signal
-// are both passed back up: a wrapper that always exited 0 would break every
-// script that branches on the exit code, and inillucent's exit codes carry
-// meaning - 3 is "the engine has not built that".
-import { spawn } from 'node:child_process';
-import { resolveBinary } from '../resolve.mjs';
-
-let binary;
-try {
-  binary = resolveBinary('inillucent');
-} catch (why) {
-  process.stderr.write(String(why.message ?? why) + '\n');
-  process.exit(1);
-}
-
-const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
-child.on('error', (why) => {
-  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
-  process.exit(1);
-});
-child.on('exit', (code, signal) => {
-  if (signal) {
-    // Re-raise it on ourselves so a shell sees the same thing it would have
-    // seen from the real program, rather than a plain exit.
-    process.kill(process.pid, signal);
-    return;
-  }
-  process.exit(code ?? 0);
-});
+#!/usr/bin/env node
+// The `inillucent` shim: resolve the platform binary and become it.
+//
+// `spawn` with `stdio: 'inherit'` rather than an exec, because Node has no
+// execve and this has to work on Windows. The child's exit code and its signal
+// are both passed back up: a wrapper that always exited 0 would break every
+// script that branches on the exit code, and inillucent's exit codes carry
+// meaning - 3 is "the engine has not built that".
+import { spawn } from 'node:child_process';
+import { resolveBinary } from '../resolve.mjs';
+
+let binary;
+try {
+  binary = resolveBinary('inillucent');
+} catch (why) {
+  process.stderr.write(String(why.message ?? why) + '\n');
+  process.exit(1);
+}
+
+const child = spawn(binary, process.argv.slice(2), { stdio: 'inherit' });
+child.on('error', (why) => {
+  process.stderr.write(`inillucent: could not run ${binary}: ${why.message}\n`);
+  process.exit(1);
+});
+child.on('exit', (code, signal) => {
+  if (signal) {
+    // Re-raise it on ourselves so a shell sees the same thing it would have
+    // seen from the real program, rather than a plain exit.
+    process.kill(process.pid, signal);
+    return;
+  }
+  process.exit(code ?? 0);
+});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "inillucent",
-  "version": "1.0.31",
+  "version": "1.0.32",
   "description": "Embedded SQL database with full-text and vector search, an MCP server, and a sqlite3-shaped shell. No native build step: the binaries ship as platform packages.",
   "keywords": [
     "database",
@@ -43,10 +43,10 @@
     "README.md"
   ],
   "optionalDependencies": {
-    "@blackrainbowlabs/cli-win32-x64": "1.0.31",
-    "@blackrainbowlabs/cli-darwin-arm64": "1.0.31",
-    "@blackrainbowlabs/cli-darwin-x64": "1.0.31",
-    "@blackrainbowlabs/cli-linux-x64": "1.0.31",
-    "@blackrainbowlabs/cli-linux-arm64": "1.0.31"
+    "@blackrainbowlabs/cli-win32-x64": "1.0.32",
+    "@blackrainbowlabs/cli-darwin-arm64": "1.0.32",
+    "@blackrainbowlabs/cli-darwin-x64": "1.0.32",
+    "@blackrainbowlabs/cli-linux-x64": "1.0.32",
+    "@blackrainbowlabs/cli-linux-arm64": "1.0.32"
   }
 }