kern-sandbox 0.1.41 → 0.1.43

package/README.md

@@ -242,6 +242,11 @@ so a `runCode` claims one instead of paying for a box start plus an interpreter
 `python:3.12-slim`, six calls each: **14.2 ms p50 by default against 0.8 ms with `prewarm: 4`**, and
 30.9 ms against 0.9 for the first call.
 
+**The pool also fills on that worker thread, so the first call is fast only once it HAS filled.**
+Measured: constructing with `prewarm: 4` and calling immediately gives 13.7 ms five times over,
+while half a second later the same burst reads 0.8, 0.6, 0.5, 0.6 for the first four and then
+32.7 for the fifth, the pool empty. The table is the steady state, not the first moment.
+
 The refill runs while your agent thinks, so it is off the caller's clock. That also says when it buys
 nothing: if calls arrive faster than the pool refills, the pool empties and you are back to the
 default cost. N is the burst you want covered, not a throughput knob.

package/index.js

@@ -36,7 +36,7 @@ const crypto = require("crypto");
 const zlib = require("zlib");
 const { spawn, spawnSync } = require("child_process");
 
-const VERSION = "0.1.41";
+const VERSION = "0.1.43";
 
 const DEFAULT_IMAGE = "python:3.12-slim";
 const WORKSPACE = "/workspace"; // where the persistent workspace is mounted inside every box
@@ -594,12 +594,21 @@ function findKern() {
     throw new SandboxError(
       "the `kern` binary was not found on PATH, and this is macOS: kern is Linux-only " +
         "(no namespaces, no cgroups on a Mac), so there is no macOS build to find. " +
-        "Run inside a Linux VM (colima, Lima, OrbStack, UTM), where kern installs normally, " +
-        "or set $KERN_BIN to a kern reachable from here. https://github.com/getkern/kern",
+        "Run inside a Linux VM (colima, Lima, OrbStack, UTM) and install it there with:\n" +
+        "    curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh\n" +
+        "or set $KERN_BIN to a kern reachable from here.",
     );
+  // THE COMMAND, NOT A LINK. `npm install kern-sandbox` does NOT bring the binary: this package is a
+  // wrapper around a process it does not ship, and the moment a user meets that fact is this error.
+  // It used to answer with a repository URL, which asks someone one paste away from working to go
+  // and read a page first. The same sentence the Python binding gives, deliberately: two wrappers
+  // around one runtime must not disagree about how to get it, and the installer line is the one the
+  // project's README leads with.
   throw new SandboxError(
-    "the `kern` binary was not found on PATH - install it " +
-      "(https://github.com/getkern/kern) or set $KERN_BIN",
+    "the `kern` binary was not found on PATH. `npm install kern-sandbox` installs this wrapper, " +
+      "not the runtime it drives - install kern with:\n" +
+      "    curl -fsSL https://raw.githubusercontent.com/getkern/kern/main/install.sh | sh\n" +
+      "or point $KERN_BIN at a kern you already have.",
   );
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kern-sandbox",
-  "version": "0.1.41",
+  "version": "0.1.43",
   "description": "kern is a fast, rootless sandbox and virtual resource runtime for any workload, including untrusted and AI-generated code; kern-sandbox is its Node/TypeScript binding. Run untrusted or agent-generated code (Python/JS/Bash) in a real, kernel-enforced box in single-digit milliseconds, with no cloud, no account and no VM.",
   "keywords": [
     "sandbox",