@ai-ecoverse/slicc-bios 1.32.1 → 1.33.0

package/README.md

@@ -182,6 +182,21 @@ The Files panel lists `/opt/grammars/node_modules` but doesn't scan it.
 
 `os/updates.js` is spectrum's `UpdatesPort` (`model.updates`, spectrum ≥ 1.27.0), with one row per component: **Agent** (`/opt/agent`), **Kernel** (`slicc-kernel`), **UI** (`slicc-spectrum`), **BIOS packages** (the other root packages) and **Syntax grammars**. Each row shows its version, when it was last checked, pnpm's download or link count while it installs, and pnpm's output under *Install log*. A component that isn't installed yet is *Waiting* (`queued`, spectrum ≥ 1.29.0) until its install starts. A failed row leads with one sentence on what failed and what to do, and keeps pnpm's output in the log. `ready()` is false at every boot until the agent's model is in place, or until the check finds no agent to start. While it is false, spectrum opens the Install / Update panel, so it shows while the agent installs or loads; while an installed agent starts, its row reads *Starting* (`starting`, spectrum ≥ 1.37.0). It closes once the agent is up without failures, and a new failure opens it again. An installed agent that doesn't start fails its row with **Retry**. Background updates show in the header. Each row's actions go back to the installers: **Retry** runs that installer again, **Restart agent** restarts the agent worker and **Reload** reloads through the BIOS.
 
+#### Developer mode and agent betas
+
+**Developer mode** (`os/beta.js`, #641) lets the owner try a newer slicc-agent from npm before it's certified. It's off by default, and with it off nothing changes: the deployment's lockfiles are the only source. Only the agent (`/opt/agent`) gets betas for now.
+
+- **The switch:** `model.updates.developer()` and `setDeveloper(on)`, rendered in Settings by spectrum. Only the owner tab's own port has them. Other tabs' mirrored ports, remote followers and guests don't, and the owner tab refuses `install-beta` and `back-to-certified` from other tabs. The setting is `slicc-os.developer` in the owner page's `localStorage`, which no kernel process and no agent worker can reach (and the guard keeps the agent's CDP off seven's tabs). No file, URL, hash or environment variable turns it on.
+- **The check:** at every update check with developer mode on, bios reads `https://registry.npmjs.org/@ai-ecoverse/slicc-agent/latest`. When that version is newer than both the certified pin and what's installed, it's offered only if:
+  - it has npm's `dist.integrity` and an SLSA v1 provenance attestation whose subject is this release with that sha512, built from `github.com/ai-ecoverse/slicc-agent` (otherwise the row says *not offered: no provenance*) by its `.github/workflows/release.yml` on `refs/heads/main` or `refs/tags/v<version>` (otherwise *not offered: built outside the release workflow*). bios trusts the attestation npm stores: npm verified its Sigstore signature when the version was published, and bios checks the statement's subject, repository, workflow and ref but not the signature again, so it trusts the registry as much as pnpm already does for the tarball;
+  - its peer ranges and `engines.slicc-kernel` accept seven's kernel and spectrum;
+  - `pnpm install --lockfile-only` in `/opt/slicc/beta/agent`, started from the deployment's lock with only the agent's pin changed, resolves the agent with npm's integrity, and every gated package that changes (see [Certified packages](#certified-packages)) is in `certs.json`.
+
+  The row's `npm` field says what it found (`offered` with how many packages change and which gated ones, `not-offered` with the reason, `current`, `failed`).
+- **Install beta** asks first, naming the version, the certified version and what changes in `/opt/agent`'s lockfile. Then it keeps the resolved lockfile and manifest in `slicc-os.beta` in `localStorage`, and the agent installs from them with `--frozen-lockfile` as usual. Afterwards bios checks that the installed lock is exactly the approved one and that `/opt/agent` has that version; otherwise it goes back to the certified pin and says why. Later checks install the same beta, so it isn't "repaired" back.
+- **Always marked:** the row's `beta` field (`{ version, certified }`) and a warning notice in the chat panels, *The agent runs a beta*, with **Back to certified**. Dismissing the notice hides it for the session, and it comes back at the next boot.
+- **Back to certified** drops the record, installs the certified lock again and restarts a running agent (once it's idle), so the uncertified worker doesn't keep running unmarked. When the deployment's agent lock changes, the beta goes too, with a notice. If seven now ships the beta's version or a newer one, the notice says the beta is no longer needed; otherwise it says to install the beta again. Turning developer mode off asks whether to return a beta to certified (**Keep beta** keeps it marked) and stops the offers.
+
 #### Optional packages
 
 Below the system rows, Install / Update offers **Optional packages** (spectrum ≥ 1.42.0): tools that seven doesn't preinstall, each at the version the homescoop coordinator certified. The catalog is [`src/packages/optional/`](src/packages/optional/): `package.json` pins each package exactly, `package-lock.json` (made with `npm install --package-lock-only --ignore-scripts`, never installed) holds its integrity, and `catalog.json` gives its id, label, description, commands, tarball size and `requires`. A test keeps the three in step. 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, dig, 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 catalog entries provide the same command, so an install never shadows another entry's.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-bios",
-  "version": "1.32.1",
+  "version": "1.33.0",
   "description": "Slim loader that boots SLICC into OPFS and serves the UI from there",
   "type": "module",
   "license": "Apache-2.0",
@@ -46,7 +46,7 @@
     "@ai-ecoverse/slicc-browsers": "1.10.3",
     "@ai-ecoverse/slicc-node": "2.5.1",
     "@ai-ecoverse/slicc-shared-web": "1.24.2",
-    "@ai-ecoverse/slicc-spectrum": "1.100.0",
+    "@ai-ecoverse/slicc-spectrum": "1.101.0",
     "@ai-ecoverse/slicc-vault": "1.15.1",
     "@biomejs/biome": "2.5.15",
     "es-module-lexer": "3.0.3",

package/src/packages/package-lock.json

@@ -10,7 +10,7 @@
         "@ai-ecoverse/slicc-cdp": "1.30.14",
         "@ai-ecoverse/slicc-clipboard": "1.0.2",
         "@ai-ecoverse/slicc-kernel": "1.136.1",
-        "@ai-ecoverse/slicc-spectrum": "1.100.0",
+        "@ai-ecoverse/slicc-spectrum": "1.101.0",
         "@ai-ecoverse/wasi-fnox": "1.39.0-5",
         "@ai-ecoverse/wasi-pnpm": "12.9.1-17",
         "@ai-ecoverse/wasi-ripgrep": "15.2.0-5",
@@ -81,9 +81,9 @@
       }
     },
     "node_modules/@ai-ecoverse/slicc-spectrum": {
-      "version": "1.100.0",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-spectrum/-/slicc-spectrum-1.100.0.tgz",
-      "integrity": "sha512-AT96NjcXRpjK2snrdgwFZoKWz3ndCAKI3D3Ce3tU9tI8gv8jOjonFK5rlvcsutlm+cJdFURhMottViGlB+ErPQ==",
+      "version": "1.101.0",
+      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-spectrum/-/slicc-spectrum-1.101.0.tgz",
+      "integrity": "sha512-m2+lFTgPvaY2zl0ITxxPOZJOSBmGThZneeNj5GbiJvGuM0rhil1xF61Htetz6nob6xRXm9titmXXfi3DuQ0WUQ==",
       "license": "Apache-2.0",
       "engines": {
         "node": ">=24"

package/src/packages/package.json

@@ -7,7 +7,7 @@
     "@ai-ecoverse/slicc-cdp": "1.30.14",
     "@ai-ecoverse/slicc-clipboard": "1.0.2",
     "@ai-ecoverse/slicc-kernel": "1.136.1",
-    "@ai-ecoverse/slicc-spectrum": "1.100.0",
+    "@ai-ecoverse/slicc-spectrum": "1.101.0",
     "@ai-ecoverse/wasi-fnox": "1.39.0-5",
     "@ai-ecoverse/wasi-pnpm": "12.9.1-17",
     "@ai-ecoverse/wasi-ripgrep": "15.2.0-5",

package/src/packages/pnpm-lock.yaml

@@ -21,8 +21,8 @@ importers:
         specifier: 1.136.1
         version: 1.136.1
       '@ai-ecoverse/slicc-spectrum':
-        specifier: 1.100.0
-        version: 1.100.0
+        specifier: 1.101.0
+        version: 1.101.0
       '@ai-ecoverse/wasi-fnox':
         specifier: 1.39.0-5
         version: 1.39.0-5
@@ -115,8 +115,8 @@ packages:
     resolution: {integrity: sha512-OIrL7sWfPIM+uyUQxqpwfYKiMX+lc58kcR8gx1zYi9R0I8UTcsMCKXJsW+VrFHcCqXY/7G3YE/9LB9I0VTJtXQ==}
     engines: {node: '>=24'}
 
-  '@ai-ecoverse/slicc-spectrum@1.100.0':
-    resolution: {integrity: sha512-AT96NjcXRpjK2snrdgwFZoKWz3ndCAKI3D3Ce3tU9tI8gv8jOjonFK5rlvcsutlm+cJdFURhMottViGlB+ErPQ==}
+  '@ai-ecoverse/slicc-spectrum@1.101.0':
+    resolution: {integrity: sha512-m2+lFTgPvaY2zl0ITxxPOZJOSBmGThZneeNj5GbiJvGuM0rhil1xF61Htetz6nob6xRXm9titmXXfi3DuQ0WUQ==}
     engines: {node: '>=24'}
     peerDependencies:
       '@shikijs/langs': 4.5.0
@@ -215,7 +215,7 @@ snapshots:
 
   '@ai-ecoverse/slicc-kernel@1.136.1': {}
 
-  '@ai-ecoverse/slicc-spectrum@1.100.0': {}
+  '@ai-ecoverse/slicc-spectrum@1.101.0': {}
 
   '@ai-ecoverse/wasi-fnox@1.39.0-5': {}