@ai-ecoverse/slicc 1.49.21 → 1.49.22

package/README.md

@@ -1704,6 +1704,7 @@ On a [§1.3](#13-local-setup-without-cdp-loopback-signalling) loopback link, `un
   - **In targets the stream touched** (attached to or created): the node fails every protected document load with `net::ERR_BLOCKED_BY_CLIENT`, so instrumentation installed before a navigation can never run in a protected document. That covers redirects, service-worker-served navigations and the page's own Fetch interception.
   - **Redirects into protected URLs:** a protected URL that reaches the page inside any string it gets, such as a redirect's `Location`, `Link` or `Refresh` header or a `headersText` line, plain or percent-encoded once (doubly encoded nesting isn't decoded), is cut to its origin, and its `urlFragment` is blanked; unprotected URLs stay intact. A stylesheet or script whose URL, or any hop of whose redirect chain (as the node's own guard session saw it on that target, compared in WHATWG form without the fragment), is protected can't be read: `Page.getResourceContent` and `Page.searchInResource` for such a URL (or one that doesn't parse), and any command naming such a `styleSheetId` or `scriptId` (`CSS.getStyleSheetText`, `Debugger.getScriptSource`, `searchInContent` and the rest), are refused with `slicc: refused: the response came from seven's origin`, and the CSS rules and styles from such a stylesheet reach the page with only their `styleSheetId` and `origin`. `Network.loadNetworkResource` (Chrome follows its redirects with the user's cookies) and `Page.captureSnapshot` (it serialises every frame) are refused on every session. [`cdp` (browser control)](#cdp-browser-control) has the details.
   - **Workers:** a touched dedicated, shared or service worker gets a guard session too (Network only, to see its imports' redirect chains), and its commands wait for it the same way, except `Runtime.runIfWaitingForDebugger` on a shared or service worker, which goes ahead so the worker can't stall on its own guard; its imports from before the guard was ready then count as unseen and can't be read. A worker script other than the worker's own whose chain that guard didn't see, or which touched a protected URL, can't be read. In pages, scripts and stylesheets loaded before the node attached are a known residual.
+  - **CDP command ids:** ids at or above `0x70000000` (1879048192) belong to the CLI and are refused from clients. `0x40000000` (2^30) through `0x6FFFFFFF` is reserved for seven's (bios) guard; other clients use ids below 2^30.
   - **Waiting for that guard:** page commands on a touched target's session wait while the node sets its guard up there. The wait fails closed after 30 s without progress (an answer or event on that target's own guard session, or the answer to the node's attach to it; answers and events elsewhere on the stream don't count) or 5 min in all, whichever comes first, and the refusal names the bound. At most 4096 commands or 64 MiB wait on a stream; more is `RESET ENOBUFS`.
   - **Sessions the node doesn't know:** a page command whose `sessionId` the node hasn't seen on this stream (in a `Target.attachedToTarget`, in the answer to the page's `Target.attachToTarget` or `Target.attachToBrowserTarget`, or its own) is held, not forwarded, until the session appears, and is then decided as usual. Only messages on that session id count as progress. The same bounds and caps apply, and the refusal is `slicc: refused: slicc doesn't know which target this session belongs to: …`, naming the bound. A session that detached is refused at once, without the suffix. Commands without a `sessionId` are unaffected.
   - **Auto-attached targets with no URL yet** (OOPIFs, popups) are held until the URL is known, then detached if protected. After 10 s with no URL they are treated as protected. The node's own setup connection ([§1.1](#11-local-setup-over-cdp)) isn't a `cdp` stream and is the one exception. [`cdp` (browser control)](#cdp-browser-control) has the details.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc",
-  "version": "1.49.21",
+  "version": "1.49.22",
   "description": "SLICC's command line for seven: links a machine's network, compute and browsers to seven over WebRTC",
   "license": "Apache-2.0",
   "repository": {
@@ -18,12 +18,12 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@ai-ecoverse/slicc-darwin-arm64": "1.49.21",
-    "@ai-ecoverse/slicc-darwin-amd64": "1.49.21",
-    "@ai-ecoverse/slicc-linux-arm64": "1.49.21",
-    "@ai-ecoverse/slicc-linux-amd64": "1.49.21",
-    "@ai-ecoverse/slicc-windows-arm64": "1.49.21",
-    "@ai-ecoverse/slicc-windows-amd64": "1.49.21",
+    "@ai-ecoverse/slicc-darwin-arm64": "1.49.22",
+    "@ai-ecoverse/slicc-darwin-amd64": "1.49.22",
+    "@ai-ecoverse/slicc-linux-arm64": "1.49.22",
+    "@ai-ecoverse/slicc-linux-amd64": "1.49.22",
+    "@ai-ecoverse/slicc-windows-arm64": "1.49.22",
+    "@ai-ecoverse/slicc-windows-amd64": "1.49.22",
     "@ai-ecoverse/slicc-jerk": "^1.3.0"
   }
 }