@ai-ecoverse/slicc-bios 1.46.0 → 1.46.2

package/README.md

@@ -584,6 +584,12 @@ Limits:
 - Emscripten programs see only the directories at `/`, so `ls /` and `cat /pnpm-lock.yaml` don't find the two files; WASI programs such as `pnpm` (`cd / && pnpm install`) do.
 - An update of the seed (`os/`) or `sw.js` alone has no lockfile change, so it arrives with the next boot through the BIOS.
 
+**A new `sw.js` that waits.** A new service worker calls `skipWaiting()` when it installs, but Chromium can leave it `installed` after that. If the old worker was stopped or starting when the request came (for example, it had idled out between the update check's fallback fetches), Chromium doesn't ask it to stop early, and it lives on its 30 s idle timer, which every fetch event resets. Both places that wait for a new worker nudge it once through `os/activate.js`, 2 s after it is `installed`:
+- **The BIOS's `intercept` step**, before it goes on to `/os/`.
+- **Every tab's `watchWaiting`**, once for each waiting worker. Only the first `skipWaiting()` after `installed` re-triggers activation in Chromium, so a tab that nudges after another does nothing.
+
+A nudge first sends the old worker `{ streams: 'mine' }` and waits for its answer (2 s at most), which makes sure it is running. It then sends the waiting worker `{ activate: 'now' }`. `sw.js` takes that message only from a window client and only with nothing else in it, and does nothing but call `self.skipWaiting()` again. Activation still waits until the old worker has no work, so a half-read download keeps holding it, and *Seven updated* still shows after 10 s.
+
 ## Certified packages
 
 Seven certifies a gated package (slicc-kernel, slicc-cdp, slicc-capture, slicc-clipboard, slicc-jsh, mcpcat, and the `wasi-*`, `wasix-*`, `wasm-*` and `py-*` packages) by its integrity: a version is certified when [`src/packages/certs.json`](src/packages/certs.json) (the historic list, with its recorded `exception`s) or one of the lockfiles seven ships (the base set, `/opt/agent`, Tailscale and the catalog's projects) carries it with that integrity. `src/seed/layer.js`'s `certifiedSet()` reads that union in the page, and a user's or a project's install that needs anything else is refused, except an optional catalog package that passes [the gate](#optional-packages), with the dependencies it pins exactly, so a user's own add of a catalog package passes or fails as the panel's Install does. homescoop's certification exceptions apply to every version there, a `certs.json` or lockfile match included, and when they can't be read the version is refused. A pin on main is certified because it reached main through the merge queue, where every integration test ran on it, and because `pins.test.mjs` checks every gated pin is its own repository's release from main. `test/integration/pins.test.mjs` checks the union covers every gated pin with its integrity (Tailscale's project included), and fails when a pinned package's `engines.slicc-kernel` or kernel peer range isn't met by the pinned kernel.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-bios",
-  "version": "1.46.0",
+  "version": "1.46.2",
   "description": "Slim loader that boots SLICC into OPFS and serves the UI from there",
   "type": "module",
   "license": "Apache-2.0",
@@ -32,6 +32,12 @@
   "engines": {
     "node": ">=26"
   },
+  "slicc": {
+    "unitSources": [
+      "src",
+      "edge"
+    ]
+  },
   "scripts": {
     "prepare": "slicc-install-hooks",
     "start": "node test/integration/chrome.mjs",
@@ -42,11 +48,11 @@
     "format": "biome check --write ."
   },
   "devDependencies": {
-    "@ai-ecoverse/slicc": "1.49.3",
+    "@ai-ecoverse/slicc": "1.49.23",
     "@ai-ecoverse/slicc-browsers": "1.18.14",
     "@ai-ecoverse/slicc-cdp": "1.41.20",
     "@ai-ecoverse/slicc-node": "2.5.1",
-    "@ai-ecoverse/slicc-shared-web": "2.12.4",
+    "@ai-ecoverse/slicc-shared-web": "2.13.0",
     "@ai-ecoverse/slicc-spectrum": "1.104.1",
     "@ai-ecoverse/slicc-vault": "1.17.0",
     "@biomejs/biome": "2.5.15",