@ai-ecoverse/slicc 1.19.0 → 1.20.0

package/README.md

@@ -274,9 +274,9 @@ HELLO from `attach`: `{ "v": 1, "role": "node", "name", "host", "version", "mode
 
 **List changes.** The node checks every listed browser's debugging port every 2 s. One that fails twice in a row is removed: its open streams get `RESET ECONNRESET: browser quit`, and a later OPEN for it gets `ENOENT`. Once its port answers again it is listed again under the same id. A browser removed through the API (`Registry.Remove`, for the TUI) has its streams reset with `ECONNRESET: browser removed`.
 
-**`browsers` updates** (§5.8.1 of the link spec, a node → page stream that tells the page about list changes) are not sent yet: a link sees the list in its HELLO, and a browser removed later answers `ENOENT`.
+**`browsers` updates** (page cap `browsers`), node → page. When the list changes while a link is up and the page's HELLO has `browsers` in `caps`, the node opens `OPEN { "kind": "browsers", "browsers": [ … ] }` on the control channel with the full current list in HELLO's shape. It replaces the previous list; there are no deltas. The page answers OPENED `{}` and END, and the node sends END. Updates are sent one at a time per link, a change that comes while one is in flight is sent after it, with the list as it is then, and an update the page doesn't finish within 10 s is reset with `ETIMEDOUT`. A change between the HELLO and the link coming up is sent as an update right away.
 
-`test/integration/testdata/link/link.js` is a page-side implementation of the link (framing, credit, both channel layouts, the violation rules, and `resolve` and raw-fetch helpers) that the integration tests run in Chrome against `slicc attach`. `cdp.js` next to it is a CDP client over `cdp` streams. Loaded with `?kernel`, the test page lists `kernel-in` and answers `kernel` OPENs with `kernel.js`, a small HTTP and WebSocket echo server in the page.
+`test/integration/testdata/link/link.js` is a page-side implementation of the link (framing, credit, both channel layouts, the violation rules, and `resolve` and raw-fetch helpers) that the integration tests run in Chrome against `slicc attach`. `cdp.js` next to it is a CDP client over `cdp` streams, and `page.js` answers `browsers` updates. Loaded with `?kernel`, the test page lists `kernel-in` and answers `kernel` OPENs with `kernel.js`, a small HTTP and WebSocket echo server in the page.
 
 ### Kernel services
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc",
-  "version": "1.19.0",
+  "version": "1.20.0",
   "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,11 +18,11 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@ai-ecoverse/slicc-darwin-arm64": "1.19.0",
-    "@ai-ecoverse/slicc-darwin-amd64": "1.19.0",
-    "@ai-ecoverse/slicc-linux-arm64": "1.19.0",
-    "@ai-ecoverse/slicc-linux-amd64": "1.19.0",
-    "@ai-ecoverse/slicc-windows-arm64": "1.19.0",
-    "@ai-ecoverse/slicc-windows-amd64": "1.19.0"
+    "@ai-ecoverse/slicc-darwin-arm64": "1.20.0",
+    "@ai-ecoverse/slicc-darwin-amd64": "1.20.0",
+    "@ai-ecoverse/slicc-linux-arm64": "1.20.0",
+    "@ai-ecoverse/slicc-linux-amd64": "1.20.0",
+    "@ai-ecoverse/slicc-windows-arm64": "1.20.0",
+    "@ai-ecoverse/slicc-windows-amd64": "1.20.0"
   }
 }