@ai-ecoverse/slicc-kernel 1.99.1 → 1.99.2

package/README.md

@@ -885,6 +885,35 @@ The Biome, TypeScript, lefthook, Renovate and CI configuration comes from [slicc
 
 Releases are cut by semantic-release on every push to `main`, in two jobs, and only on `main`. The first job runs on the bench pool, so it starts within a minute of the push, before `main` has moved on. It computes the version, tags the commit and creates the GitHub release, with `npmPublish: false`. A run that starts after `main` has moved skips; the run for the newer commit releases it. The second job runs on a GitHub-hosted runner, because npm's trusted publishing and provenance accept no self-hosted runner. It publishes the tagged commit with `tools/release-recover.mjs`. However long it waits for a runner, it publishes exactly the commit the run started on, so the provenance, the tag and the package's `gitHead` agree. For any version tagged at HEAD, `tools/release-recover.mjs` pushes the tag if origin lacks it, publishes the version if npm lacks it (with retries), and creates its GitHub release if that is missing too. So a failure after the version is tagged (a rejected push, a failed `npm publish`) doesn't strand it, and re-running the Release workflow completes it the same way.
 
+### Certification (`cert-review`)
+
+`.github/workflows/cert-review.yml` certifies every release from CI. It runs when the Release workflow succeeds on `main`. The version is the tag on the released commit. The delta is read from the newest earlier release whose `cert-review` status is `success` or `pending`, skipping failed and unreviewed ones (or `base.json`'s release, or the tag before), so a release whose review was cancelled or failed is covered by the next one, and the line says `covers <first>–<last>`. It also runs on `workflow_dispatch` with a `version`, optionally with `prev` and `base`, or with `planted` (a branch) and `pr` for proofs. A dispatch off `main`, or a planted one, is a dry run. Each release (its commit) has its own concurrency group, so no pending review is cancelled by a newer one. The tools are in `tools/cert-review/`:
+
+- **plan:** works out the version, the previous tag, the commit and the base (`base.mjs`). The base is the newest earlier release whose `cert-review` commit status is `success`, or, until there is one, the release `base.json` names (the cert lane's last line). CI never reads the npm `certified` dist-tag.
+- **delta** (`delta.mjs`): lists the pull requests merged between the two tags (their merge commits, plus `pr` for a planted branch). Each gets its conventional-commit kind (`fix`, `feat`, `perf` and `revert` are behaviour changes) and the integration test files and titles it adds or changes. The titles are read from the pull request's patch: the added `test(…)` lines and the hunk headers git puts above changed lines. Escapes are decoded as JavaScript does, and a title git cut short, or a template literal, matches as a prefix.
+- **suite** (`suite.mjs`, `reporter.mjs`) runs on the bench pool, without secrets. It takes the tag's tree with its own dependencies and Chromium, and replaces `dist/` with the **published npm tarball** (for a planted branch, its own `npm pack`).
+  - The release job runs the release's whole `test/integration/` suite, then the delta's test files again on the **previous release's dist** (the NEGATIVE).
+  - The base job runs the base release's own suite on its own published dist.
+  - Each run uses the tree's own `npm test` command, with a reporter that records every test and subtest with its status and error.
+- **kernel-compat** (`compat.mjs`) supplies the base-set and catalog evidence: homescoop's kernel-compat run for the release.
+  - Release runs share one group and intermediate ones are cancelled. When there is no finished run for the release commit, it dispatches `kernel-compat.yml` for that version (whose run is named `Kernel compat v<version>`) and waits up to 150 minutes.
+  - It reads the run's report artifact, and **re-runs every regressing package once** (a dispatch with that `set`).
+  - A regression that doesn't reproduce is a `compat-flake`; one that does is a `compat-regression`. A crash that reproduces and doesn't happen on the reference kernel is a `compat-crash`, which record FAILs in code.
+- **review:** `findings.mjs` decides in code, per pull request:
+  - `negative` (a fix's test fails on the previous dist and passes on the release) or `passes` (a feature's test passes);
+  - otherwise a finding: `no-test`, `no-negative`, `fails-on-release`, `not-run`, `prev-not-run` or `no-titles`.
+
+  It also diffs the two suites test by test (`regressed`, `newFailing`, `fixed`, `stillFailing`, `removed`), flags a suite run that didn't finish (`suite-incomplete`), and adds the kernel-compat findings. Claude, on Bedrock with the key only in that step, then reads those artifacts and `instructions.txt` (which has the roll-forward FAIL list verbatim) and writes `verdict.json` and `comment.md`. Its tools are reading files, `gh pr view`, and `gh issue list`/`view`. `gh issue create` is allowed only for a release on `main`; otherwise, and for an issue in another repository, it lists the issue under `elsewhere` for the cert lane to file.
+- **record** (`record.mjs`), in code, with read-only permissions:
+  - It re-downloads the tarball and checks `dist.integrity` (sha512) and the sha256, the SLSA v1 provenance (the tarball is its subject; `release.yml`, `refs/heads/main`, a GitHub-hosted builder; commit = `gitHead` = the tag), `npm audit signatures`, and that the commit is on `main`. A problem there, a `compat-crash`, or a planted build is a FAIL whatever the review says.
+  - It adds the **known issues as of the release**: every issue labelled `known-issue` (open or closed) and every one in `known.json`, unless it was fixed before the release. That holds when `known.json`'s `fixedIn` names an earlier or equal version, or the merged pull request that closed it is an ancestor of the tag, or it was closed (with no closing pull request) before the release commit. An issue closed as not planned or as a duplicate is dropped.
+  - The line is `certified @ai-ecoverse/slicc-kernel@<v> sha256=<…> (ci: <run>; known: …)`. Any test gaps from the findings (`no-test`, `no-negative`, `prev-not-run`, `no-titles`, `not-run`) are appended in code as `test gaps: #<pr> <kind>`, so a fix without a NEGATIVE is never certified silently.
+- **publish** runs only for a release on `main`, never for a dry run. It puts the line into a `cert-review` commit status on the tag's commit and into the GitHub release's notes, between `<!-- cert-review -->` markers.
+
+Moving the `certified` dist-tag stays manual. Automating it needs an npm token that may change dist-tags, in a step that re-hashes the tarball and tags only on a `certified` line.
+
+Not part of the run yet: bios's real setup (the base-set sweep in bios, the upgrade boot, the sudo rows under `enforce`). It would plug in as one more job before review that runs slicc-bios's `npm run test:cert` with `CERT_COMMANDS` and the release's tarball, and leaves its results next to the others.
+
 ## Test fixtures
 
 The WASIX fixtures of `test/integration/epoll.test.mjs` (#674), under `test/integration/fixtures/`, are committed with their sources, build scripts and built wasm.

package/dist/kernel-worker.js

@@ -9305,12 +9305,18 @@ var DriverConnection = class _DriverConnection {
   timeoutMs;
   nextId = 0;
   onFail;
-  constructor(port, capabilities, waiting, timeoutMs, onFail) {
+  idle;
+  constructor(port, capabilities, waiting, timeoutMs, options) {
     this.port = port;
     this.capabilities = capabilities;
     this.waiting = waiting;
     this.timeoutMs = timeoutMs;
-    this.onFail = onFail;
+    this.onFail = options.onFail;
+    this.idle = options.idle === true;
+    if (this.idle) port.unref?.();
+  }
+  settled() {
+    if (this.idle && this.waiting.size === 0) this.port.unref?.();
   }
   static async open(port, mount, options = {}) {
     const timeoutMs = options.timeoutMs ?? DRIVER_TIMEOUT_MS;
@@ -9326,6 +9332,7 @@ var DriverConnection = class _DriverConnection {
       clearTimeout(call.timer);
       if (data.errno) call.reject(errnoError(data.errno, data.message ?? data.errno));
       else call.resolve(data.result);
+      if (options.idle && waiting.size === 0) port.unref?.();
     });
     port.start?.();
     port.postMessage({ hello: { protocol: DRIVER_PROTOCOL, mount } });
@@ -9344,7 +9351,7 @@ var DriverConnection = class _DriverConnection {
     const refused2 = driverVersionError(hello.protocol);
     if (refused2) throw errnoError("EPROTO", refused2);
     if (hello.error) throw errnoError(hello.errno ?? "EIO", hello.error);
-    return new _DriverConnection(port, hello.capabilities ?? {}, waiting, timeoutMs, options.onFail);
+    return new _DriverConnection(port, hello.capabilities ?? {}, waiting, timeoutMs, options);
   }
   call(call, transfer = []) {
     if (this.failure) return Promise.reject(this.failure);
@@ -9353,6 +9360,7 @@ var DriverConnection = class _DriverConnection {
       const timer = unref(
         setTimeout(() => {
           this.waiting.delete(id2);
+          this.settled();
           const error = errnoError(
             "EIO",
             `the driver did not answer ${call.op} within ${this.timeoutMs} ms`
@@ -9362,6 +9370,7 @@ var DriverConnection = class _DriverConnection {
           this.onFail?.(error);
         }, this.timeoutMs)
       );
+      if (this.idle && this.waiting.size === 0) this.port.ref?.();
       this.waiting.set(id2, { resolve: resolve2, reject, timer });
       this.port.postMessage({ ...call, id: id2 }, transfer);
     });
@@ -9374,6 +9383,7 @@ var DriverConnection = class _DriverConnection {
       call.reject(error);
     }
     this.waiting.clear();
+    this.settled();
   }
   close() {
     this.fail(errnoError("EIO", "the file system is unmounted"));
@@ -9728,6 +9738,7 @@ var MountTable = class {
           { source: spec.source, options },
           {
             ...this.deps.timeoutMs ? { timeoutMs: this.deps.timeoutMs } : {},
+            ...opened2.idle ? { idle: true } : {},
             onInvalidate: (paths) => this.invalidated(target, paths),
             onFail: (error) => {
               if (mounted) this.crashed(mounted, error);
@@ -12096,7 +12107,7 @@ var PATH_OPS = new Set(SYNC_FS_OPS);
 var EARLY_WHOLE_FILE = 64 * 1024;
 
 // src/version.ts
-var KERNEL_VERSION = true ? "1.99.1" : "0.0.0-dev";
+var KERNEL_VERSION = true ? "1.99.2" : "0.0.0-dev";
 var OS_RELEASE = "6.0.0-slicc";
 function procVersion() {
   return `Linux version ${OS_RELEASE} (slicc-kernel ${KERNEL_VERSION}) #1 SMP PREEMPT_DYNAMIC
@@ -20558,9 +20569,6 @@ var NOT_EXECUTABLE = 126;
 var DECIDE_MS = 100;
 var INIT_PID = 1;
 var SHARED_DIRS = ["/tmp", "/home"];
-function unref2(port) {
-  port.unref?.();
-}
 var LAYOUT = [
   ["/", 493],
   ["/root", 448],
@@ -20771,7 +20779,6 @@ var Launcher = class {
   pnpmMade;
   pnpmEpoch = 0;
   mounts;
-  shmPorts = [];
   createDriverWorker;
   media;
   onMountPending;
@@ -22036,9 +22043,10 @@ var Launcher = class {
         },
         { owned: true }
       );
-      if (spec.target === SHM) this.shmPorts = [port1, port2];
+      if (spec.target === SHM) port2.unref?.();
       return {
         port: port1,
+        ...spec.target === SHM ? { idle: true } : {},
         dispose: () => {
           port1.close();
           port2.close();
@@ -22142,7 +22150,6 @@ var Launcher = class {
   async mountShm() {
     await this.base.mkdir(SHM, { recursive: true });
     await this.mounts.mountSystem({ type: "tmpfs", source: "shm", target: SHM }, this.fs);
-    for (const port of this.shmPorts) unref2(port);
     await this.fs.chmod(SHM, 1023);
   }
   async ownTmp() {