@ai-ecoverse/slicc-bios 1.39.16 → 1.40.0

package/README.md

@@ -200,17 +200,23 @@ The Files panel lists `/opt/grammars/node_modules` but doesn't scan it.
 
 **Release notes (slicc-spectrum#458):** each update check also gives the Kernel, UI, Agent and Tailscale rows a `releases` list from their GitHub repositories (`slicc-kernel`, `slicc-spectrum`, `slicc-agent`, `wasm-tailscale`), and each optional package one from the repository its npm version document names, when that is on GitHub ([`os/releases.js`](src/seed/releases.js)). A row gets the release it has installed and every newer one up to the version it offers, newest first, at most 30. Each release has its `version` (the tag without the `v`, or without the package's name in a shared repository such as homescoop), its `url` and its `notes`, the release body unchanged (the `<!-- cert-verify -->` block included, which spectrum turns into a Certified badge) up to 64 KB. Spectrum renders the notes; bios only fetches them. bios asks GitHub's unauthenticated API (`/repos/<repo>/releases?per_page=100`, page by page down to the installed version, at most 5 pages), without credentials, a referrer or any header but `Accept` and `If-None-Match`. It keeps each list in IndexedDB (`slicc-releases`) for a day and revalidates it with its ETag at every check, and GitHub doesn't count a 304 against its 60 requests an hour. A 403 or 429 backs off until `Retry-After`, the rate limit's reset or 15 minutes, and leaves `releases` out, so the row looks as it does without notes, with no error. The page sets no `connect-src`, so these requests need no change to its CSP.
 
-Below the system rows, Install / Update offers **Optional packages** (spectrum ≥ 1.42.0): tools that seven doesn't preinstall. homescoop's packages (`wasm-*`, `wasi-*`, `wasix-*`) come at npm's `latest`, which under cert-review v2 is certified, since homescoop publishes only from a reviewed main through its ladder. The four that other repos publish, slicc-jsh, mcpcat, wasi-slicc (slicc-cli's) and sliccy-browser (slicc-cdp's), stay bios pins in [`src/packages/optional/package.json`](src/packages/optional/package.json) and its `package-lock.json`, so Renovate bumps them and CI tests each bump (`pins.test.mjs` checks each is its own repository's release from main); the page can't check those repos' CI runs itself (GitHub's API allows 60 unauthenticated requests an hour), so a main-built release alone doesn't reach seven. The catalog, [`src/packages/optional/catalog.json`](src/packages/optional/catalog.json), lists each package by its npm name, with only what npm can't tell: its `id` and `label`, and optionally `requires` (other ids), `notes` (bios's own caveats, one line each, shown next to npm's description), `helpers` (commands to leave out of the list until homescoop marks them `helper: true`), `range` and `abi` (Python's, below) and `kind: "project"`. A project keeps its `description`, `commands` and `size`, since npm doesn't know it.
+Below the system rows, Install / Update offers **Optional packages** (spectrum ≥ 1.42.0): tools that seven doesn't preinstall. Seven pins only what UI boot and the agent install need (Lars, 2026-10-21), so every catalog package comes at npm's `latest`, behind [the gate](#optional-packages). A release passes when npm's provenance shows its publisher's release workflow built it on `main`. homescoop publishes its packages (`wasm-*`, `wasi-*`, `wasix-*`) through its ladder. The other publishers are slicc-jsh, mcpcat, slicc-cli (wasi-slicc) and slicc-cdp (sliccy-browser), and the catalog names each one's repository and workflow in its `source`. The catalog, [`src/packages/optional/catalog.json`](src/packages/optional/catalog.json), lists each package by its npm name, with only what npm can't tell: its `id` and `label`, and optionally `requires` (other ids), `notes` (bios's own caveats, one line each, shown next to npm's description), `helpers` (commands to leave out of the list until homescoop marks them `helper: true`), `range` and `abi` (Python's, below), `source` (a publisher other than homescoop: its `repo` and release `workflow`, and optionally `since`, the first version it certifies, and `deny`, versions it never certifies, each with a reason) and `kind: "project"`. A project keeps its `description`, `commands` and `size`, since npm doesn't know it.
 
-- **What npm tells (`os/packages.js`):** at boot, and at an update check at most every ten minutes, bios fetches each entry's version doc from the registry from the page (`https://registry.npmjs.org/<name>/latest`, which sends CORS `*`; the kernel's network path isn't needed), all in parallel and each with a 15-second timeout. A pinned entry's doc is its pin's (`/<name>/<pin>`), so only its description, commands and size come from npm. It takes `version` (the row's `offered`), `description` (npm's text, verbatim), the commands (the keys of `slicc.commands`, without one marked `helper: true` or listed in `helpers`, and only names a shell can run), `dist.unpackedSize` (the row's `size`, now what the package unpacks to on disk, its own files only, so git reads 56 MB where the old tarball-based size read 19 MB; the row says `unpacked: true`) and `dist.integrity`. An entry with a `range` (Python's is `3.15.0`) takes the highest version in range from the abbreviated packument instead, where the range is matched against the upstream X.Y.Z with homescoop's `-N` build ignored, so `3.15.0` offers 3.15.0-3 but never a 3.15.1 or 3.16 (pydata's builds are for one Python ABI: homescoop keeps the ABI within one X.Y.Z, and its py-* ranges stop at the next patch). With `abi`, a version whose `slicc.python.abi` differs isn't offered.
+- **What npm tells (`os/packages.js`):** at boot, and at an update check at most every ten minutes, bios fetches each entry's version doc from the registry from the page (`https://registry.npmjs.org/<name>/latest`, which sends CORS `*`; the kernel's network path isn't needed), all in parallel and each with a 15-second timeout. It takes `version` (the row's `offered`), `description` (npm's text, verbatim), the commands (the keys of `slicc.commands`, without one marked `helper: true` or listed in `helpers`, and only names a shell can run), `dist.unpackedSize` (the row's `size`, now what the package unpacks to on disk, its own files only, so git reads 56 MB where the old tarball-based size read 19 MB; the row says `unpacked: true`) and `dist.integrity`. An entry with a `range` (Python's is `3.15.0`) takes the highest version in range from the abbreviated packument instead, where the range is matched against the upstream X.Y.Z with homescoop's `-N` build ignored, so `3.15.0` offers 3.15.0-3 but never a 3.15.1 or 3.16 (pydata's builds are for one Python ABI: homescoop keeps the ABI within one X.Y.Z, and its py-* ranges stop at the next patch). With `abi`, a version whose `slicc.python.abi` differs isn't offered.
 - **Cache:** the last good answer for each entry is kept in `var/lib/slicc/optional/npm.json`, so the panel works offline and shows at once at boot; a later fetch replaces it, an entry that fails keeps its cached answer, and holds only what the rows show. A passing provenance verdict is remembered only in the tab's memory, for the listing (never a refusal, never in OPFS, which kernel processes can write, and never for an install, which always asks npm again).
 - **No answer and no cache:** boot never waits for npm. Such a row has `registry: 'checking'` while the fetch runs, then `registry: 'unreachable'`, with `offered: null`, an empty description, no commands, no size and no Install (spectrum shows *Couldn't reach npm.*); a row that isn't installed gets **Retry**, which, like the panel's `refreshPackages()`, fetches npm again. An installed row keeps **Remove**.
 - **The gate** (one function, `gate()` in `os/packages.js`, for the panel's Install and Update, a user's Update and [Your packages](#your-packages)) checks every package in the lock pnpm made. Each must be one of:
-  - an exact `name@version` with that integrity in the base set's lockfile (`src/packages/package-lock.json`), the catalog's pins (`src/packages/optional/package-lock.json`) or `src/packages/certs.json`, which is the only way a pinned entry passes; or
-  - an `@ai-ecoverse/*` package whose locked integrity equals the registry's `dist.integrity` for that exact version, and that npm's stored SLSA v1 provenance (`dist.attestations`, which bios trusts as npm stores it) binds to that integrity (its subject's sha512) and to its publisher's repository and release workflow at `refs/heads/main`. The publisher is bios's own, never read from npm: homescoop's `ladder-build.yml` or `publish.yml` for the `wasm-*`, `wasi-*`, `wasix-*` and `py-*` packages, and [`sources.json`](src/packages/optional/sources.json) for slicc-cdp, whose rule is `certified: "tag"`, its npm dist-tag `certified` (from the abbreviated packument), since its main released versions its cert-review didn't pass. A package with no publisher there (slicc-jsh, mcpcat, sliccy-browser at another version than its pin, or wasi-slicc, whose provenance is slicc-cli's, not homescoop's) is refused.
+  - an exact `name@version` with that integrity in the base set's lockfile (`src/packages/package-lock.json`) or `src/packages/certs.json`; or
+  - an `@ai-ecoverse/*` package whose locked integrity equals the registry's `dist.integrity` for that exact version, and that npm's stored SLSA v1 provenance (`dist.attestations`, which bios trusts as npm stores it) binds to that integrity (its subject's sha512) and to its publisher's repository and release workflow at `refs/heads/main`. The publisher is bios's own, never read from npm:
+    - a catalog entry's `source`: slicc-jsh's, mcpcat's and slicc-cli's (for wasi-slicc) own `release.yml`, or their `ci.yml` since they moved onto slicc-shared-web's pipeline, and slicc-cdp's `publish-sliccy-browser.yml` for sliccy-browser;
+    - otherwise homescoop's `ladder-build.yml` or `publish.yml` for the `wasm-*`, `wasi-*`, `wasix-*` and `py-*` packages;
+    - and [`sources.json`](src/packages/optional/sources.json) for a dependency-only publisher: slicc-cdp, under sliccy-browser, whose rule is `certified: "tag"`, its npm dist-tag `certified` (from the abbreviated packument), since its main released versions its cert-review didn't pass.
+    
+    A release from another repository, another workflow or another ref (a maintenance branch, a tag) is refused, and so is a package with no publisher there.
+  - A source's `deny` and `since` refuse those versions, exact matches included: wasi-slicc 1.44.4 and everything before 1.44.1.
   - Whatever matched, homescoop's certification exceptions then apply, exact matches included: a `fail` verdict refuses that version, and a `requires` verdict refuses it unless every pin of what it requires, in the lock and the base set's lockfile (never `certs.json`'s history), is in range. bios bundles `certification-exceptions.json` at the homescoop commit `pins.test.mjs` pins ([`exceptions.json`](src/packages/optional/exceptions.json); `pins.test` keeps it byte for byte that file) and unions it with homescoop main's (`raw.githubusercontent.com`, CORS `*`), which can only deny or constrain, never grant: a tampered or missing live file is at worst a denial, and the bundled copy decides alone when it can't be fetched. Finally a package whose `engines['slicc-kernel']` or kernel peer range the base set's kernel doesn't meet is refused.
   - Anything that isn't `@ai-ecoverse/*` and isn't in the base set is refused; homescoop packages have no third-party dependencies.
-- **Listing:** each entry's latest goes through the same rules (with its exact `dependencies`) when it's fetched. If latest fails, bios walks back through older versions (in range, not deprecated, at most five; a version whose doc is broken is skipped) and offers the newest that passes, with `newer: { version, reason }` naming latest's blocker. A pinned entry is never walked back. If none passes, the row is `withheld` with that reason, offers no Install or Update, and an installed copy keeps Remove.
+- **Listing:** each entry's latest goes through the same rules (with its exact `dependencies`) when it's fetched. If latest fails, bios walks back through older versions (in range, not deprecated, at most five; a version whose doc is broken is skipped) and offers the newest that passes, with `newer: { version, reason }` naming latest's blocker. If none passes, the row is `withheld` with that reason, offers no Install or Update, and an installed copy keeps Remove.
 
 Today it offers git, the GitHub CLI, OpenSSH, `slicc` (see [Sevens this kernel follows](#network)), Python, the Python data tools (numpy, pandas and matplotlib), Node.js (slicc-jsh's `node` and `jsh`), `sliccy:browser` for `.jsh` scripts, Ruby, Perl, Biome, the PDF tools (poppler), qpdf, rsync, screen, SQLite, the BIND tools (`dig`, `host` and `nslookup`), websocat, ntfy, GnuPG, fnox, mcpcat (an MCP client), zip (Info-ZIP's `zip`, `unzip` and `zipinfo`), xxd (vim's hex dump, with `xxd -r`) and ImageMagick. zip's `unzip` refuses an entry whose name isn't UTF-8 (an old Latin-1 or CP437 archive without a Unicode path): it says `cannot create <name>` / `Illegal byte sequence`, extracts the other entries and exits 50, and `unzip -l` still lists the entry. It never extracts it under a changed name, and `unzip -p` still streams its bytes ([homescoop#1174](https://github.com/ai-ecoverse/homescoop/issues/1174)). ImageMagick is homescoop's HEIF build (`wasm-imagemagick-heif`, a superset of the plain build, which isn't offered), with `magick`, `convert`, `mogrify`, `identify` and `magick-open`, and it reads HEIC and AVIF. A failed write leaves an existing target as it was. Its known issues: writing over another user's 0666 file in a sticky directory such as `/tmp` fails with `Operation not permitted`, though writing your own files works ([homescoop#1258](https://github.com/ai-ecoverse/homescoop/issues/1258)); `.mpc` writes fail with `cache resources exhausted` ([homescoop#1208](https://github.com/ai-ecoverse/homescoop/issues/1208)); and the cert's coverage gaps, among them the no-encoder fallback and MPC's two-file write ([homescoop#1209](https://github.com/ai-ecoverse/homescoop/issues/1209)). sudo for `magick`, `convert` or `mogrify` is offered once, never always, since they write files. No two entries' npm `latest` provide the same command, so an install never shadows another entry's; `packages.test` checks that against npm's current `latest`.
 
@@ -535,15 +541,15 @@ Limits:
 
 ## Certified packages
 
-Seven certifies a gated package (slicc-kernel, slicc-cdp, 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`, the optional catalog's pins, 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.
+Seven certifies a gated package (slicc-kernel, slicc-cdp, 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.
 
 **Provenance** (`pins.test.mjs`, an ordinary integration test): every gated pin in a lockfile seven ships has npm's SLSA provenance for that exact tarball (its subject's sha512 is the lockfile's integrity), built on `refs/heads/main` of its own repository: slicc-kernel, slicc-jsh, slicc-cdp, slicc-clipboard, mcpcat, wasm-tailscale, slicc-cli for wasi-slicc, and homescoop for the other `wasm-*`, `wasi-*`, `wasix-*` and `py-*`. A homescoop pin that the bundled `certification-exceptions.json` withdraws, or whose `requires` the pins don't meet, fails it too. The test names each pin that fails and why.
 
 ### Renovate keeps the pins current
 
-[`renovate.json`](renovate.json) bumps every `@ai-ecoverse/*` pin in the base set (`src/packages/package.json`), the optional catalog's four non-homescoop pins (`src/packages/optional/package.json`) and `/opt/agent` (`src/packages/agent/package.json`), with their npm and pnpm lockfiles. The catalog's homescoop entries aren't pinned, so they need no bumps; the Python data tools' project (`src/packages/optional/projects/pydata`) is pinned by hand, from the dependency dashboard.
+[`renovate.json`](renovate.json) bumps every `@ai-ecoverse/*` pin in the base set (`src/packages/package.json`) and `/opt/agent` (`src/packages/agent/package.json`), with their npm and pnpm lockfiles. The optional catalog pins nothing, so it needs no bumps; the Python data tools' project (`src/packages/optional/projects/pydata`) is pinned by hand, from the dependency dashboard.
 
-- **PRs:** homescoop's packages (`wasi-*`, `wasix-*`, `wasm-*`, `py-*`, `wasi-pnpm` included) come as one PR a day, between 00:00 and 06:00 UTC. The kernel (its base-set and `/opt/agent` pins together), slicc-cdp, slicc-agent, slicc-spectrum and slicc-jsh each get their own PR, and so does every other package. The grammars and Tailscale projects stay on the dependency dashboard.
+- **PRs:** homescoop's packages (`wasi-*`, `wasix-*`, `wasm-*`, `py-*`, `wasi-pnpm` included) come as one PR a day, between 00:00 and 06:00 UTC. The kernel (its base-set and `/opt/agent` pins together), slicc-cdp, slicc-agent and slicc-spectrum each get their own PR, and so does every other package. The grammars and Tailscale projects stay on the dependency dashboard.
 - **Automerge once CI is green:** Renovate turns on auto-merge, so a PR goes through the merge queue once its required checks, `ci / integration` and `ci / review`, are green (see [CI](#ci)). No bot writes to a Renovate branch: the shipped lockfiles are part of what seven certifies, so a certified pin needs no `certs.json` line.
 - **Known breaks** are `packageRules` with `allowedVersions`, each with its reason and issue in `description`. Today the only one is wasi-pnpm skipping the deprecated 12.9.1-11 and 12.9.1-12 (homescoop#1128). wasm-bash's hold below 5.3.0-20 went with the pin of kernel 1.135.2, which has slicc-kernel#1146. bash 5.3.0-20 and later count as certified only with kernel 1.130.2 or later (homescoop#1230), and -21 declares `engines.slicc-kernel >=1.130.2`. `test/integration/renovate.test.mjs` checks the config, the gate and the queue in plain node.
 
@@ -551,7 +557,7 @@ Seven certifies a gated package (slicc-kernel, slicc-cdp, slicc-clipboard, slicc
 
 ### The npm package
 
-`@ai-ecoverse/slicc-bios` on npm carries only the manifests a consumer needs to test against what seven ships: `src/packages/package.json`, `package-lock.json`, `pnpm-lock.yaml` and `certs.json`, `src/packages/agent/package.json` and `pnpm-lock.yaml`, and `src/packages/optional/package.json`, `package-lock.json` (the four non-homescoop pins), `catalog.json`, `sources.json` and `exceptions.json`. It has no runtime code and no dependencies, and those paths stay where they are. `ci.yml` releases it from `main` only, after lint, through slicc-shared-web's pipeline: semantic-release reads the conventional commits, tags `v<version>`, writes the GitHub release and publishes to npm with provenance through npm's trusted publishing (`fledgling.workflow` is `ci.yml`). The deploy to seven (`deploy.yml`) is separate and doesn't wait for it.
+`@ai-ecoverse/slicc-bios` on npm carries only the manifests a consumer needs to test against what seven ships: `src/packages/package.json`, `package-lock.json`, `pnpm-lock.yaml` and `certs.json`, `src/packages/agent/package.json` and `pnpm-lock.yaml`, and `src/packages/optional/catalog.json`, `sources.json` and `exceptions.json`. It has no runtime code and no dependencies, and those paths stay where they are. `ci.yml` releases it from `main` only, after lint, through slicc-shared-web's pipeline: semantic-release reads the conventional commits, tags `v<version>`, writes the GitHub release and publishes to npm with provenance through npm's trusted publishing (`fledgling.workflow` is `ci.yml`). The deploy to seven (`deploy.yml`) is separate and doesn't wait for it.
 
 ## Develop
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-bios",
-  "version": "1.39.16",
+  "version": "1.40.0",
   "description": "Slim loader that boots SLICC into OPFS and serves the UI from there",
   "type": "module",
   "license": "Apache-2.0",
@@ -25,8 +25,6 @@
     "src/packages/certs.json",
     "src/packages/agent/package.json",
     "src/packages/agent/pnpm-lock.yaml",
-    "src/packages/optional/package.json",
-    "src/packages/optional/package-lock.json",
     "src/packages/optional/catalog.json",
     "src/packages/optional/sources.json",
     "src/packages/optional/exceptions.json"
@@ -44,7 +42,7 @@
     "format": "biome check --write ."
   },
   "devDependencies": {
-    "@ai-ecoverse/slicc": "1.49.2",
+    "@ai-ecoverse/slicc": "1.49.3",
     "@ai-ecoverse/slicc-browsers": "1.18.7",
     "@ai-ecoverse/slicc-cdp": "1.30.25",
     "@ai-ecoverse/slicc-node": "2.5.1",

package/src/packages/agent/package.json

@@ -4,6 +4,6 @@
   "description": "SLICC's agent, which the UI installs with pnpm in the background into /opt/agent in OPFS",
   "dependencies": {
     "@ai-ecoverse/slicc-agent": "6.18.3",
-    "@ai-ecoverse/slicc-kernel": "1.147.0"
+    "@ai-ecoverse/slicc-kernel": "1.148.0"
   }
 }

package/src/packages/agent/pnpm-lock.yaml

@@ -15,10 +15,10 @@ importers:
     dependencies:
       '@ai-ecoverse/slicc-agent':
         specifier: 6.18.3
-        version: 6.18.3(@ai-ecoverse/slicc-kernel@1.147.0)(@aws-sdk/credential-provider-node@3.972.84)(@smithy/signature-v4@5.7.4)(ws@8.22.0)
+        version: 6.18.3(@ai-ecoverse/slicc-kernel@1.148.0)(@aws-sdk/credential-provider-node@3.972.84)(@smithy/signature-v4@5.7.4)(ws@8.22.0)
       '@ai-ecoverse/slicc-kernel':
-        specifier: 1.147.0
-        version: 1.147.0
+        specifier: 1.148.0
+        version: 1.148.0
 
 packages:
 
@@ -36,8 +36,8 @@ packages:
     resolution: {integrity: sha512-WVaDUiZbd5nwG03+2WoQ8YA8ATC2mkx1DRCWpLuMFBNnyN0cd5IRoGF6KYNjMkXvBQCvZZxP+gwffrpmHYJ/cQ==}
     engines: {node: '>=24'}
 
-  '@ai-ecoverse/slicc-kernel@1.147.0':
-    resolution: {integrity: sha512-L/gWZ9LvehYkdDYjRUSGEKtKBhtTBPMjA6EFUcjXJa+0zIQX9JaI46a2Cdz1Q36+G3Mnqw1OFzhQPob/jo2NGw==}
+  '@ai-ecoverse/slicc-kernel@1.148.0':
+    resolution: {integrity: sha512-LLYvZ7AKqi6kJwQzKoNcgSj9bCLRvu+abziXfMao29HXTwYGmBO3hj1izWRAQcPkbdFgW0mTHnwhsmwJdNCqcw==}
     engines: {node: '>=26'}
 
   '@ai-ecoverse/slicc-vault@1.15.1':
@@ -346,10 +346,10 @@ packages:
 
 snapshots:
 
-  '@ai-ecoverse/slicc-agent@6.18.3(@ai-ecoverse/slicc-kernel@1.147.0)(@aws-sdk/credential-provider-node@3.972.84)(@smithy/signature-v4@5.7.4)(ws@8.22.0)':
+  '@ai-ecoverse/slicc-agent@6.18.3(@ai-ecoverse/slicc-kernel@1.148.0)(@aws-sdk/credential-provider-node@3.972.84)(@smithy/signature-v4@5.7.4)(ws@8.22.0)':
     dependencies:
       '@ai-ecoverse/slicc-browsers': 1.9.2
-      '@ai-ecoverse/slicc-kernel': 1.147.0
+      '@ai-ecoverse/slicc-kernel': 1.148.0
       '@ai-ecoverse/slicc-vault': 1.15.1
       '@aws-sdk/middleware-websocket': 3.972.54
       '@earendil-works/chord': 1.3.0
@@ -372,7 +372,7 @@ snapshots:
 
   '@ai-ecoverse/slicc-browsers@1.9.2': {}
 
-  '@ai-ecoverse/slicc-kernel@1.147.0': {}
+  '@ai-ecoverse/slicc-kernel@1.148.0': {}
 
   '@ai-ecoverse/slicc-vault@1.15.1': {}
 

package/src/packages/optional/catalog.json

@@ -26,6 +26,14 @@
   "@ai-ecoverse/wasi-slicc": {
     "id": "slicc",
     "label": "slicc",
+    "source": {
+      "repo": "ai-ecoverse/slicc-cli",
+      "workflow": [".github/workflows/release.yml", ".github/workflows/ci.yml"],
+      "since": "1.44.1",
+      "deny": {
+        "1.44.4": "its release run failed, so it was never certified (slicc-cli coordinator, 10-19)"
+      }
+    },
     "notes": [
       "For root and cones. The other seven must allow remote control from this one in its Linked devices."
     ]
@@ -49,6 +57,10 @@
   "@ai-ecoverse/slicc-jsh": {
     "id": "node",
     "label": "Node.js (jsh)",
+    "source": {
+      "repo": "ai-ecoverse/slicc-jsh",
+      "workflow": [".github/workflows/release.yml", ".github/workflows/ci.yml"]
+    },
     "notes": [
       "No fork, worker or asymmetric crypto yet.",
       "fetch() reaches servers inside seven (localhost, <port>.kernel.localhost)."
@@ -58,6 +70,10 @@
     "id": "jsh-browser",
     "label": "Browser for jsh scripts",
     "requires": ["node"],
+    "source": {
+      "repo": "ai-ecoverse/slicc-cdp",
+      "workflow": ".github/workflows/publish-sliccy-browser.yml"
+    },
     "notes": ["Seven's own tab and the vault stay out of reach."]
   },
   "@ai-ecoverse/wasix-ruby": {
@@ -126,6 +142,10 @@
   "@ai-ecoverse/mcpcat": {
     "id": "mcpcat",
     "label": "mcpcat (MCP client)",
+    "source": {
+      "repo": "ai-ecoverse/mcpcat",
+      "workflow": [".github/workflows/release.yml", ".github/workflows/ci.yml"]
+    },
     "notes": [
       "-H 'Authorization: Bearer ${NAME}' (single quotes) sends the vault's placeholder, which the vault fills in where a secret rule allows that host; mcpcat never prints the value."
     ]

package/src/packages/package-lock.json

@@ -9,7 +9,7 @@
         "@ai-ecoverse/slicc-browsers": "1.18.1",
         "@ai-ecoverse/slicc-cdp": "1.30.25",
         "@ai-ecoverse/slicc-clipboard": "1.0.2",
-        "@ai-ecoverse/slicc-kernel": "1.147.0",
+        "@ai-ecoverse/slicc-kernel": "1.148.0",
         "@ai-ecoverse/slicc-spectrum": "1.104.1",
         "@ai-ecoverse/wasi-fnox": "1.39.0-6",
         "@ai-ecoverse/wasi-pnpm": "12.9.1-21",
@@ -72,9 +72,9 @@
       }
     },
     "node_modules/@ai-ecoverse/slicc-kernel": {
-      "version": "1.147.0",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-kernel/-/slicc-kernel-1.147.0.tgz",
-      "integrity": "sha512-L/gWZ9LvehYkdDYjRUSGEKtKBhtTBPMjA6EFUcjXJa+0zIQX9JaI46a2Cdz1Q36+G3Mnqw1OFzhQPob/jo2NGw==",
+      "version": "1.148.0",
+      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-kernel/-/slicc-kernel-1.148.0.tgz",
+      "integrity": "sha512-LLYvZ7AKqi6kJwQzKoNcgSj9bCLRvu+abziXfMao29HXTwYGmBO3hj1izWRAQcPkbdFgW0mTHnwhsmwJdNCqcw==",
       "license": "Apache-2.0",
       "engines": {
         "node": ">=26"

package/src/packages/package.json

@@ -6,7 +6,7 @@
     "@ai-ecoverse/slicc-browsers": "1.18.1",
     "@ai-ecoverse/slicc-cdp": "1.30.25",
     "@ai-ecoverse/slicc-clipboard": "1.0.2",
-    "@ai-ecoverse/slicc-kernel": "1.147.0",
+    "@ai-ecoverse/slicc-kernel": "1.148.0",
     "@ai-ecoverse/slicc-spectrum": "1.104.1",
     "@ai-ecoverse/wasi-fnox": "1.39.0-6",
     "@ai-ecoverse/wasi-pnpm": "12.9.1-21",

package/src/packages/pnpm-lock.yaml

@@ -18,8 +18,8 @@ importers:
         specifier: 1.0.2
         version: 1.0.2
       '@ai-ecoverse/slicc-kernel':
-        specifier: 1.147.0
-        version: 1.147.0
+        specifier: 1.148.0
+        version: 1.148.0
       '@ai-ecoverse/slicc-spectrum':
         specifier: 1.104.1
         version: 1.104.1
@@ -111,8 +111,8 @@ packages:
     resolution: {integrity: sha512-p7b1h85qkiU0LKjNLCLiU7GVXjGigkyR2+VUCInM1cZo2yjLFxr7tGAOO09e6OG9nB7XKiQn3W88wb3s0gxy+g==}
     engines: {node: '>=24', slicc-kernel: '>=1.75.0'}
 
-  '@ai-ecoverse/slicc-kernel@1.147.0':
-    resolution: {integrity: sha512-L/gWZ9LvehYkdDYjRUSGEKtKBhtTBPMjA6EFUcjXJa+0zIQX9JaI46a2Cdz1Q36+G3Mnqw1OFzhQPob/jo2NGw==}
+  '@ai-ecoverse/slicc-kernel@1.148.0':
+    resolution: {integrity: sha512-LLYvZ7AKqi6kJwQzKoNcgSj9bCLRvu+abziXfMao29HXTwYGmBO3hj1izWRAQcPkbdFgW0mTHnwhsmwJdNCqcw==}
     engines: {node: '>=26'}
 
   '@ai-ecoverse/slicc-spectrum@1.104.1':
@@ -213,7 +213,7 @@ snapshots:
 
   '@ai-ecoverse/slicc-clipboard@1.0.2': {}
 
-  '@ai-ecoverse/slicc-kernel@1.147.0': {}
+  '@ai-ecoverse/slicc-kernel@1.148.0': {}
 
   '@ai-ecoverse/slicc-spectrum@1.104.1': {}
 

package/src/packages/optional/package-lock.json

@@ -1,78 +0,0 @@
-{
-  "name": "slicc-bios-optional",
-  "lockfileVersion": 3,
-  "requires": true,
-  "packages": {
-    "": {
-      "name": "slicc-bios-optional",
-      "dependencies": {
-        "@ai-ecoverse/mcpcat": "0.20.4",
-        "@ai-ecoverse/slicc-jsh": "0.54.9",
-        "@ai-ecoverse/sliccy-browser": "0.1.34",
-        "@ai-ecoverse/wasi-slicc": "1.47.2"
-      }
-    },
-    "node_modules/@ai-ecoverse/mcpcat": {
-      "version": "0.20.4",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/mcpcat/-/mcpcat-0.20.4.tgz",
-      "integrity": "sha512-GaK4LeMjpRT40nnOm/ZtTUKNzvtg0A4+AC/T62Fclivq5oTIBirrZG2USkthAGpFlS3BJDIT5NXaq3OdCSNt4Q==",
-      "license": "Apache-2.0",
-      "bin": {
-        "mcpcat": "dist/host/mcpcat.mjs"
-      },
-      "engines": {
-        "node": ">=26",
-        "slicc-kernel": ">=1.65.2"
-      }
-    },
-    "node_modules/@ai-ecoverse/slicc-cdp": {
-      "version": "1.30.18",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-cdp/-/slicc-cdp-1.30.18.tgz",
-      "integrity": "sha512-8aty5CgO3hPiZ0H8ikx60j1QzTWJmr6MGRKAFy9DMDrU/nwqPnifx1UXLX6AW6GdvDsZdRR9NpAV2A4hWfj4ZA==",
-      "license": "Apache-2.0",
-      "workspaces": [
-        "packages/sliccy-browser"
-      ],
-      "bin": {
-        "slicc-cdp": "src/cli.js"
-      },
-      "engines": {
-        "node": ">=24"
-      }
-    },
-    "node_modules/@ai-ecoverse/slicc-jsh": {
-      "version": "0.54.9",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-jsh/-/slicc-jsh-0.54.9.tgz",
-      "integrity": "sha512-bl8jBQs+sMWNkxKjsK16P6eFEpgCE/Z9aEeomK1qcu7+bhkH44Y1Ios/DaSJAxPyod+TmzcuT9iyaXYFEzhrxA==",
-      "license": "Apache-2.0",
-      "bin": {
-        "jsh": "dist/host/jsh.mjs"
-      },
-      "engines": {
-        "node": ">=22",
-        "slicc-kernel": ">=1.53.2"
-      }
-    },
-    "node_modules/@ai-ecoverse/sliccy-browser": {
-      "version": "0.1.34",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/sliccy-browser/-/sliccy-browser-0.1.34.tgz",
-      "integrity": "sha512-epSMU6SkUwuhCA6Ods927VtpxbrmsaajJj5o/UZhc6MG0dxj84GpNfExHDGsNvFh+jsM8gwLFFnqsgM4IRCX9w==",
-      "license": "Apache-2.0",
-      "dependencies": {
-        "@ai-ecoverse/slicc-cdp": "1.30.18"
-      },
-      "engines": {
-        "node": ">=24"
-      }
-    },
-    "node_modules/@ai-ecoverse/wasi-slicc": {
-      "version": "1.47.2",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/wasi-slicc/-/wasi-slicc-1.47.2.tgz",
-      "integrity": "sha512-ehIKArcaerL0Ak29YeTUAD+xf1o2K0zuvk+KyRDOqvcp7AF1DBjQ8J7xiO0TRskbfWqK/dY6OQMO8HCsAUQVOQ==",
-      "license": "Apache-2.0",
-      "engines": {
-        "slicc-kernel": ">=1.92.0"
-      }
-    }
-  }
-}

package/src/packages/optional/package.json

@@ -1,11 +0,0 @@
-{
-  "name": "slicc-bios-optional",
-  "private": true,
-  "description": "The optional packages that seven pins because their publisher isn't homescoop's ladder: slicc-jsh, mcpcat, wasi-slicc (slicc-cli) and sliccy-browser (slicc-cdp). Release-state and cert review certify these pins; every other catalog entry is npm's latest behind the runtime gate. Never installed as a project: the panel runs pnpm add -g for each one.",
-  "dependencies": {
-    "@ai-ecoverse/mcpcat": "0.20.4",
-    "@ai-ecoverse/slicc-jsh": "0.54.9",
-    "@ai-ecoverse/sliccy-browser": "0.1.34",
-    "@ai-ecoverse/wasi-slicc": "1.47.2"
-  }
-}