@ai-ecoverse/slicc-kernel 1.134.0 → 1.134.1

package/README.md

@@ -1251,7 +1251,7 @@ The tools in `tools/cert-review/`:
   - **FAIL:** a regression, or a failing test (by the counts, even without its rows) is **not certified**, and the group is red;
   - **INCOMPLETE** blocks too: no result, a result from another bios than the pinned one, a missing shard, a shard that exited without a failing test, a refused candidate, 0 tests run, or no test passed;
   - **not judged:** every failing test fails on `main`'s own pins too (`both`), so the canary is broken on `main`, not by this group. That passes with a note, as do `both` rows next to a pass. Either way, `pr notice` opens one issue, `downstream: bios canary failing on main (<bios sha>)`, or comments on the open one, and the next group that passes closes it. Flaky rows are advisory.
-- **`downstream-override`**, next to `cert-review-approved`: a coordinator-only label that waives a downstream FAIL. It is head-bound by the same self-guard (`cert-self-guard` with `approval-label: downstream-override` and every path, dot paths included), so a push drops it. It applies only when **every** pull request in the group carries it on the head being merged: the group reads the guard's receipt and waives only when each member was checked and approved, so a pull request whose paths the guard's globs miss gets no waiver. The group's line then reads `downstream: overridden (downstream-override on the head, by the coordinator) …`, with the failure it waived. It never covers INCOMPLETE. A pull request's own certification line ends `downstream: merge group`, since its downstream verdict comes in the group.
+- **No downstream waiver.** A downstream FAIL or INCOMPLETE in the merge group is not certified; fix the regression or bios's side first (the coordinator-only `downstream-override` label was removed with the 2026-10-19 cert model). A pull request's own certification line ends `downstream: merge group`, since its downstream verdict comes in the group.
 
 Not part of the run yet: the rest of bios's setup (the `rest` shard, the upgrade boot, the sudo rows under `enforce`). More shards plug in through the canary call's `shards`.
 

package/dist/kernel-worker.js

@@ -2570,15 +2570,21 @@ var OpfsFs = class {
     let writable2;
     let handle;
     try {
-      const [made2, existed, at] = await this.fileFor(destination);
-      handle = made2;
-      target = at;
-      if (!existed && !created4) {
-        created4 = true;
-        await this.stampNew(target, options.owner, false);
+      const kept = created4 ? this.files.get(destination) : void 0;
+      if (kept) {
+        if (options.owner?.fifo || options.owner?.socket) throw fsError("ENXIO", to);
+        handle = kept;
+      } else {
+        const [made2, existed, at] = await this.fileFor(destination);
+        handle = made2;
+        target = at;
+        if (!existed && !created4) {
+          created4 = true;
+          await this.stampNew(target, options.owner, false);
+        }
+        const [entry] = await this.meta.get([target]);
+        if (entry?.fifo || entry?.socket) throw fsError("ENXIO", to);
       }
-      const [entry] = await this.meta.get([target]);
-      if (entry?.fifo || entry?.socket) throw fsError("ENXIO", to);
       this.wrote(handle);
       writable2 = await handle.createWritable();
       await writable2.write(file);
@@ -7095,7 +7101,7 @@ function satisfies(version, range2) {
 }
 
 // src/version.ts
-var KERNEL_VERSION = true ? "1.134.0" : "0.0.0-dev";
+var KERNEL_VERSION = true ? "1.134.1" : "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