kern-sandbox 0.2.43 → 0.2.44

package/index.d.ts

@@ -101,8 +101,8 @@ export interface SandboxOptions {
   name?: string | null;
   /** Keep ONE resident box and run every call in it with `kern exec`, 2 ms against 6 ms for a fresh
    * box. Requires `name` and `workspace`. Survives close(); destroy() stops it. A resident box is not
-   * a fresh one: /tmp accumulates, the PID namespace is shared, and an OOM comes back `killed` rather
-   * than `oom`. A box built under another posture with the same name is refused. Default false. */
+   * a fresh one: /tmp accumulates and the PID namespace is shared. A box built under another posture
+   * with the same name is refused. Default false. */
   persist?: boolean;
   /** How long the resident box lives, in seconds. It is kern's own `--timeout` on that box, so it ends
    * by itself if the owning process dies. Default 3600. */

package/index.js

@@ -42,7 +42,7 @@ const crypto = require("crypto");
 const zlib = require("zlib");
 const { spawn, spawnSync } = require("child_process");
 
-const VERSION = "0.2.43";
+const VERSION = "0.2.44";
 
 const DEFAULT_IMAGE = "python:3.12-slim";
 // WHAT THE DEFAULT IMAGE CONTAINS, as a fact ABOUT THE IMAGE and not about its name. It drives the
@@ -2192,11 +2192,12 @@ class Sandbox {
     // left running - `kern exec` reaps its descendants when it returns, including one detached with
     // setsid, which is why the resident box runs `--init`.
     //
-    // ⛔ AND THE VERDICT IS COARSER. `oom` is read from the teardown bytes kern writes for the box IT
-    // started; `kern exec` does not carry them and the registry keeps only exitCode 137, which an
-    // external kill produces too. So an OOM comes back `killed` on this path where the one-shot path
-    // says `oom`. Not papered over: claiming `oom` from "137 and a cap was set" would be an inference
-    // presented as a measurement.
+    // ⛔ THE VERDICT NEEDS kern 0.30.1 OR NEWER. `oom` is read from the bytes kern writes where the
+    // workload cannot reach them, and `kern exec` writes them since 0.30.1: the command ran, whether
+    // the OOM killer took it with its box, and the signal that ended it. Measured with 0.30.1: an OOM
+    // comes back `oom` and the cell's own `exit(137)` an exit with no fault. Against an older kern on
+    // PATH only the 137 arrives and both read `killed`, never guessed into `oom`. The npm package
+    // carries 0.30.1.
     //
     // 📌 WHAT ADOPTION KEYS ON, AND THE TWO THINGS IT DELIBERATELY DOES NOT. A box is adopted when
     // its fingerprint matches: the argv, the `KERN_*` environment kern builds the box from, and what

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kern-sandbox",
-  "version": "0.2.43",
+  "version": "0.2.44",
   "description": "Your model writes the code. This runs it where it can't touch your machine: a rootless Linux container, no daemon, no VM, no cloud, no account. A kernel boundary, not a microVM: for deliberately hostile code, use one.",
   "keywords": [
     "sandbox",