@ai-ecoverse/slicc 1.58.2 → 1.58.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -5
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -486,7 +486,7 @@ Lists running CDP endpoints and installed browsers, best match first. The browse
486
486
 
487
487
  **A token in the path.** Some browsers answer `/json/version`, `/json/list` and their socket only under a secret path, as `http://127.0.0.1:9227/<token>/json/version`, and refuse the port's root. slicc keeps the path of an `http(s)` URL, ignoring a trailing `/` and a trailing `/json/version`, `/json/list` or `/json`, and asks for each route under it. The path works like a password, so it is shown only where a program needs it to connect: `cdp` and `webSocketDebuggerUrl` in `--json`, and the same fields of `--json` events. The table, status lines, errors, `SLICC_DEBUG=1` diagnostics and what a `cdp` stream's RESET tells the page show `http://127.0.0.1:9227/…`. Such an endpoint is never found by the port probe, since its token can't be guessed: name it with `--cdp`.
488
488
 
489
- Endpoints are merged by host and port. A `DevToolsActivePort` file wins over `--cdp`, which wins over the process list, which wins over the port probe. For each endpoint, `/json/version` gives the name, version and `webSocketDebuggerUrl`, and `/json/list` gives the seven tabs: `page` targets whose origin is `https://<label>.sliccy.ai`, other than `www` (`:443` is the same origin, any other port isn't). An endpoint's `cdp` has its host in lower case, with `localhost` and `::1` written as `127.0.0.1`. A `DevToolsActivePort` whose port is open but serves no `/json/version` (Chrome's opt-in remote debugging of a running browser) is listed as `wsOnly`, with the websocket URL from the file and no tab check.
489
+ Endpoints are merged by host and port. A `DevToolsActivePort` file wins over `--cdp`, which wins over the process list, which wins over the port probe. For each endpoint, `/json/version` gives the name, version and `webSocketDebuggerUrl`, and `/json/list` gives the seven tabs: `page` targets whose origin is `https://<label>.sliccy.ai`, other than the service hosts in slicc-browsers' `seven.excludedLabels` (`:443` is the same origin, any other port isn't). An endpoint's `cdp` has its host in lower case, with `localhost` and `::1` written as `127.0.0.1`. A `DevToolsActivePort` whose port is open but serves no `/json/version` (Chrome's opt-in remote debugging of a running browser) is listed as `wsOnly`, with the websocket URL from the file and no tab check.
490
490
 
491
491
  **Discovery only reads.** Every source, the port probe included, sends each endpoint `GET /json/version` and `GET /json/list` and nothing else: no WebSocket, no navigation, no new tab. Its HTTP client never follows a redirect (a `3xx` counts as no answer) and never uses a proxy from the environment. The same client does every other read of a CDP endpoint: `/json/version` and the WebSocket handshake when `slicc` and `attach` connect, and the [`cdp`](#cdp-browser-control) capability's `/json/version` and WebSocket for each stream. A `DevToolsActivePort` or `ws://` `--cdp` URL whose port serves no `/json/version` gets a TCP connect, closed at once, to tell `wsOnly` from stale. The targets in `/json/list` that aren't seven tabs are dropped as soon as the list is parsed: their URLs, titles and ids are never logged (`SLICC_DEBUG=1` included), cached, written to disk, printed (`--json`, the picker, plain mode), sent over the link, or put in telemetry or error messages. Only the seven tabs' `id`, `url` and `title` are kept. Attaching to a browser, and anything else that talks to it over CDP, happens only once a browser has been chosen to host seven (see [The default](#the-default-slicc)).
492
492
 
@@ -598,7 +598,7 @@ slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal
598
598
  **Flags.**
599
599
  - `--cdp`: the browser's endpoint, in any form `slicc browsers --cdp` takes, here and on `prompt`, `watch`, `wait` and `abort`. `http://host:port`, with [a token path](#browsers) if the browser wants one, is looked up through `GET /json/version`, and `ws://…` is used as is. `host:port` is `http://host:port`, and a bare port is `http://127.0.0.1:<port>`. As in `slicc browsers`, a trailing `/` and a trailing `/json/version`, `/json/list` or `/json` are ignored. slicc talks to the browser WebSocket only and attaches to the tab with `Target.attachToTarget { flatten: true }`. It names one browser; a second `--cdp` is an error. This browser is also listed for the [`cdp`](#cdp-browser-control) capability, with `seven: true`.
600
600
  - `--cdp-extra`: another browser seven may drive over the link (repeatable), in any form `slicc browsers --cdp` takes. Each must answer when `attach` starts.
601
- - `--origin`: also accept seven on this origin (`scheme://host[:port]`), repeatable. `https://<label>.sliccy.ai` is always accepted, except `www`.
601
+ - `--origin`: also accept seven on this origin (`scheme://host[:port]`), repeatable. `https://<label>.sliccy.ai` is always accepted, except the service hosts in slicc-browsers' `seven.excludedLabels` such as `vault`. `www` is seven's, since seven runs on `www.sliccy.ai/os/` for six's in-place upgrade.
602
602
  - `--signal`: `cdp` (default) or `stdio`.
603
603
  - `--name`: the link's `name` and `host` in HELLO. The default name is `slicc on <host>`, with this machine's short host name, lower-cased.
604
604
  - `--allow`, `--deny`: policy rules on top of the local default (see [Network policy](#network-policy)). The `--cdp` and `--cdp-extra` ports and endpoint addresses are denied, and so are this machine's other [debugging ports](#network-policy), whatever `--allow` says.
@@ -1540,7 +1540,7 @@ The wire protocol between seven (the page) and `slicc` (the node), v1. seven's s
1540
1540
 
1541
1541
  Used when the node already holds a CDP connection to the browser that runs seven. No key in a URL, and nothing listening on loopback.
1542
1542
 
1543
- 1. The node finds the seven target. That's a page target whose main-frame origin is allowed, using the same origin rule as slicc-node's gate: `https://<label>.sliccy.ai` other than `www`, plus any `--origin`.
1543
+ 1. The node finds the seven target. That's a page target whose main-frame origin is allowed, using the same origin rule as slicc-node's gate: `https://<label>.sliccy.ai` other than the service hosts in slicc-browsers' `seven.excludedLabels`, plus any `--origin`.
1544
1544
  2. It attaches (`flatten: true`), calls `Runtime.enable` and `Runtime.addBinding { name: "sliccLinkSend" }`.
1545
1545
  3. It sends `{ "t": "hello", "v": 1, "nonce": "<base64url 16 bytes>", "node": "<random per-process id>" }` (see [§5.11](#511-agent-page-cap-agent-node--page-remote-control) for how the page uses `node`) by calling `Runtime.evaluate` on `globalThis.sliccLinkReceive?.(<json>)`.
1546
1546
  4. The page answers through the binding, `sliccLinkSend(<json>)`, with:
@@ -1611,7 +1611,7 @@ The scenario: seven is open in the user's **everyday browser** (Chrome, Edge or
1611
1611
  - **Gate, on every request:**
1612
1612
  - `Host` must be `127.0.0.1:<port>`, `[::1]:<port>` or `localhost:<port>` (against DNS rebinding);
1613
1613
  - the method and the two paths are exact;
1614
- - `Origin` must pass exactly the same rule as CDP setup ([§1.1](#11-local-setup-over-cdp)): slicc-cli's `IsSevenOrigin` with slicc-browsers' catalog `ExcludedLabels` (so `www`, `vault`, `mcpcat`, `get` and every other service label never pair or signal), plus `--origin`;
1614
+ - `Origin` must pass exactly the same rule as CDP setup ([§1.1](#11-local-setup-over-cdp)): slicc-cli's `IsSevenOrigin` with slicc-browsers' catalog `ExcludedLabels` (so `vault`, `mcpcat`, `get` and every other service label never pair or signal; `www` does, since seven runs there for six's in-place upgrade), plus `--origin`;
1615
1615
  - the body is JSON, at most 64 KiB;
1616
1616
  - **preflight:** `OPTIONS` answers only for allowed origins, with `Access-Control-Allow-Private-Network: true`, `Access-Control-Allow-Origin: <that origin>` (never `*`), no credentials, and `Vary: Origin`.
1617
1617
  - Everything else gets `403` with no body. The listener isn't a proxy and serves nothing else. `Origin` can be forged by non-browser processes, but the gate only filters browsers; trust is the token or the pinned fingerprint.
@@ -2168,7 +2168,7 @@ HELLO adds `"jerk": { "version": "1.0.0" }` next to `caps`.
2168
2168
  **Host revoke and `seal-off` (node → page):** the host can revoke a lease seven holds and stop new ones, through the node's control socket ([`jerk`](#jerk-slicc-jerk-over-the-link)). Preventing future issuance and revoking what was issued are separate ops.
2169
2169
  - **The lease list:** a node that offers `jerk-seal` remembers, in memory and for as long as the process runs, each lease it sent: provider, `lease_id` and `expires_at`, never the credentials.
2170
2170
  - **Revoke:** the host's `unseal` runs `FNOX_LEASE_ID=<lease_id> jerk <provider> drop --lease --via-link` on the node, with no link request. Once jerk exits 0, the node tells seven.
2171
- - **The notice:** to a page that lists the page cap `jerk-revoke`, the node sends `OPEN { "kind": "jerk-revoked", "provider": "github", "lease_id": "jerk-github-…", "by": "host" }` on the control channel. It carries no credential, scope or rule text. The page answers OPENED `{}`, then END, and the node sends END.
2171
+ - **The notice:** only after the node has sent its HELLO on that link, and to a page whose HELLO lists the page cap `jerk-revoke`, the node sends `OPEN { "kind": "jerk-revoked", "provider": "github", "lease_id": "jerk-github-…", "by": "host" }` on the control channel. It carries no credential, scope or rule text. The page answers OPENED `{}`, then END, and the node sends END.
2172
2172
  - **Delivery:** the node sends each notice once on every link that is up and on each later link of this process whose page lists the cap, until the lease's `expires_at`. A RESET, or no answer within 10 s, is logged (`jerk: revoke notice <provider>: …`) and the notice waits for the next link. Repeats are harmless.
2173
2173
  - **No notice** after seven's own `unseal`, since seven asked.
2174
2174
  - **The page's obligation:** the page acts only on a notice from the node that created that lease. Otherwise any linked device with the cap could make seven forget another host's credential. When it seals a lease, the page keeps the per-process `node` id from the HELLO of the link the `lease` event came in on. It forgets the lease only when the HELLO `node` of the link the notice comes in on is that same id, and the `provider` and `lease_id` match. A notice from any other node, or for a `lease_id` it doesn't know, is answered OPENED `{}` and changes nothing.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc",
3
- "version": "1.58.2",
3
+ "version": "1.58.4",
4
4
  "description": "SLICC's command line for seven: links a machine's network, compute and browsers to seven over WebRTC",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -18,12 +18,12 @@
18
18
  "node": ">=18"
19
19
  },
20
20
  "optionalDependencies": {
21
- "@ai-ecoverse/slicc-darwin-arm64": "1.58.2",
22
- "@ai-ecoverse/slicc-darwin-amd64": "1.58.2",
23
- "@ai-ecoverse/slicc-linux-arm64": "1.58.2",
24
- "@ai-ecoverse/slicc-linux-amd64": "1.58.2",
25
- "@ai-ecoverse/slicc-windows-arm64": "1.58.2",
26
- "@ai-ecoverse/slicc-windows-amd64": "1.58.2",
21
+ "@ai-ecoverse/slicc-darwin-arm64": "1.58.4",
22
+ "@ai-ecoverse/slicc-darwin-amd64": "1.58.4",
23
+ "@ai-ecoverse/slicc-linux-arm64": "1.58.4",
24
+ "@ai-ecoverse/slicc-linux-amd64": "1.58.4",
25
+ "@ai-ecoverse/slicc-windows-arm64": "1.58.4",
26
+ "@ai-ecoverse/slicc-windows-amd64": "1.58.4",
27
27
  "@ai-ecoverse/slicc-jerk": "^1.4.0"
28
28
  }
29
29
  }