@ai-ecoverse/slicc-bios 1.47.0 → 1.47.2

package/README.md

@@ -25,6 +25,14 @@ Seven's documents are never kept in the back/forward cache. The service worker s
 
 Every other OPFS file is served sandboxed: `Content-Security-Policy: sandbox allow-scripts allow-forms allow-popups allow-modals; frame-ancestors 'self'` (without `allow-same-origin`), `X-Content-Type-Options: nosniff`, `Cross-Origin-Resource-Policy: same-origin`, and no COOP or COEP. An HTML page there still renders and runs its scripts, but in an opaque origin, with no access to seven's IndexedDB, `localStorage`, OPFS or keys. JavaScript and TypeScript files there are served as `text/plain` and wasm as `application/octet-stream`, and a request for a script, a worker or a worklet there gets a 403, so none of seven's pages can import, run or instantiate them. Bare imports are resolved only in the live paths. Kernel symlinks live in the kernel's metadata, not in OPFS, so the service worker never follows one. The kernel itself reads binaries from OPFS directly, not through the service worker.
 
+**Requests the service worker never answers skip it (#728).** When it installs, `sw.js` adds static routes (`InstallEvent.addRoutes`, in Chromium):
+- **Straight to the network:** an `https:` request to any host other than seven's own, `localhost` or a `.localhost` name (with or without a trailing dot). The worker isn't started for it.
+- **To the fetch handler, as before:** everything else. That covers seven's host on any scheme or port, every `localhost` and kernel-port form, and every `http:` request.
+
+The handler passes the routed requests through untouched anyway, so the only change is that they don't wake the worker. Before this, the update check's release-notes fetches to npm and GitHub kept an old worker busy, or restarted it while it was stopping for an update. Chromium skips the activation check when a stopping worker restarts, so the update stayed `installed`.
+
+Every rule's `URLPattern` has all its parts explicit, with no base URL. Where `addRoutes` or `URLPattern` is missing, or Chromium refuses the rules, there are no routes and every request reaches the handler.
+
 ### Next to SLICC 6 (`www.sliccy.ai/7`)
 
 Seven can share its origin with another app: on `www.sliccy.ai` the BIOS is `/7/` and SLICC 6 keeps the rest of the origin, the first step of the in-place upgrade from six (#648; the routes are sliccy-ai#51).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-bios",
-  "version": "1.47.0",
+  "version": "1.47.2",
   "description": "Slim loader that boots SLICC into OPFS and serves the UI from there",
   "type": "module",
   "license": "Apache-2.0",
@@ -48,11 +48,11 @@
     "format": "biome check --write ."
   },
   "devDependencies": {
-    "@ai-ecoverse/slicc": "1.49.23",
+    "@ai-ecoverse/slicc": "1.49.25",
     "@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.13.0",
+    "@ai-ecoverse/slicc-shared-web": "2.13.2",
     "@ai-ecoverse/slicc-spectrum": "1.104.1",
     "@ai-ecoverse/slicc-vault": "1.17.0",
     "@biomejs/biome": "2.5.15",

package/src/packages/package-lock.json

@@ -30,7 +30,7 @@
         "@ai-ecoverse/wasm-mount": "1.0.0-5",
         "@ai-ecoverse/wasm-ncurses-utils": "6.5.0-6",
         "@ai-ecoverse/wasm-patch": "2.8.0-5",
-        "@ai-ecoverse/wasm-procps": "4.0.7-5",
+        "@ai-ecoverse/wasm-procps": "4.0.7-6",
         "@ai-ecoverse/wasm-sed": "4.10.0-6",
         "@ai-ecoverse/wasm-tar": "1.35.0-9",
         "@ai-ecoverse/wasm-tls-engine": "4.2.0-12",
@@ -333,10 +333,10 @@
       "license": "GPL-3.0-or-later"
     },
     "node_modules/@ai-ecoverse/wasm-procps": {
-      "version": "4.0.7-5",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/wasm-procps/-/wasm-procps-4.0.7-5.tgz",
-      "integrity": "sha512-N69rs2QAstDMKWSGbCYV3RcEfhifH4xQagpFOM70Ia9oDHkBJO9jyf66rsVqAbHl3gUdKVgq7G9MeJW1pc3/Xg==",
-      "license": "GPL-2.0-or-later",
+      "version": "4.0.7-6",
+      "resolved": "https://registry.npmjs.org/@ai-ecoverse/wasm-procps/-/wasm-procps-4.0.7-6.tgz",
+      "integrity": "sha512-pFRV/plLnZ9bYVIHl2TIDl6bhiqJ32HJn0/UDnsik28JiCWy4sZ1fZjZvsP1l1MaxLscelovaaRzOiQf1QnFkQ==",
+      "license": "GPL-2.0-or-later AND LGPL-2.1-or-later",
       "engines": {
         "slicc-kernel": ">=1.44.0"
       }

package/src/packages/package.json

@@ -27,7 +27,7 @@
     "@ai-ecoverse/wasm-mount": "1.0.0-5",
     "@ai-ecoverse/wasm-ncurses-utils": "6.5.0-6",
     "@ai-ecoverse/wasm-patch": "2.8.0-5",
-    "@ai-ecoverse/wasm-procps": "4.0.7-5",
+    "@ai-ecoverse/wasm-procps": "4.0.7-6",
     "@ai-ecoverse/wasm-sed": "4.10.0-6",
     "@ai-ecoverse/wasm-tar": "1.35.0-9",
     "@ai-ecoverse/wasm-tls-engine": "4.2.0-12",

package/src/packages/pnpm-lock.yaml

@@ -81,8 +81,8 @@ importers:
         specifier: 2.8.0-5
         version: 2.8.0-5
       '@ai-ecoverse/wasm-procps':
-        specifier: 4.0.7-5
-        version: 4.0.7-5
+        specifier: 4.0.7-6
+        version: 4.0.7-6
       '@ai-ecoverse/wasm-sed':
         specifier: 4.10.0-6
         version: 4.10.0-6
@@ -243,8 +243,8 @@ packages:
   '@ai-ecoverse/wasm-patch@2.8.0-5':
     resolution: {integrity: sha512-xoMrYGOwbD43O46JQaQsIQkv7hcP/oVMsDH1F3kgaAFMko0KZXUURm0xtnZVEQMy9JLPlN+dwalKZf93gx17sg==}
 
-  '@ai-ecoverse/wasm-procps@4.0.7-5':
-    resolution: {integrity: sha512-N69rs2QAstDMKWSGbCYV3RcEfhifH4xQagpFOM70Ia9oDHkBJO9jyf66rsVqAbHl3gUdKVgq7G9MeJW1pc3/Xg==}
+  '@ai-ecoverse/wasm-procps@4.0.7-6':
+    resolution: {integrity: sha512-pFRV/plLnZ9bYVIHl2TIDl6bhiqJ32HJn0/UDnsik28JiCWy4sZ1fZjZvsP1l1MaxLscelovaaRzOiQf1QnFkQ==}
     engines: {slicc-kernel: '>=1.44.0'}
 
   '@ai-ecoverse/wasm-sed@4.10.0-6':
@@ -451,7 +451,7 @@ snapshots:
 
   '@ai-ecoverse/wasm-patch@2.8.0-5': {}
 
-  '@ai-ecoverse/wasm-procps@4.0.7-5': {}
+  '@ai-ecoverse/wasm-procps@4.0.7-6': {}
 
   '@ai-ecoverse/wasm-sed@4.10.0-6': {}