@ai-ecoverse/slicc-bios 1.30.1 → 1.30.2

package/README.md

@@ -564,6 +564,16 @@ No test calls a real model. Every test serves an empty `packages/agent/` project
 
 `ci.yml` runs on pull requests, the merge queue and pushes to `main`. A `ci / plan` job ([`scripts/ci/plan.mjs`](scripts/ci/plan.mjs)) splits the integration tests into 14 shards: each `guard-set-*.test.mjs` becomes one item per detach variant of the pinned guard vectors (run with `GUARD_VARIANTS`), every other test file is one item, and the items go in a random order, seeded with the run id, to the least-loaded shard by the times in [`scripts/ci/durations.json`](scripts/ci/durations.json), the longest items first. Each shard (`ci / integration (s01)` …) runs its items with [`scripts/ci/shard.mjs`](scripts/ci/shard.mjs), one `node --test` per guard-set file with its variants (the other files join the first), counting a test the guard-set helper reports for that run's guard-set file, keeps the harness's artifacts and coverage from every run, and writes its verdict line. `ci / test`, the required check, fails without a passing verdict from every shard the plan named.
 
+On a pull request, the plan first reads the files the pull request changes (`git diff HEAD^1 HEAD` on its merge commit) and picks a mode ([`scripts/ci/scope.mjs`](scripts/ci/scope.mjs)):
+
+- **docs**: only Markdown or `docs/` changed. Lint runs, and neither the shards nor `ci / vendors` run.
+- **tests**: only `test/integration/*.test.mjs` files changed, and perhaps `durations.json`. Only those files run, in shards; `ci / vendors` runs when a vendors test changed.
+- **catalog**: only `src/packages/optional/**` or `certs.json` changed. The pins, optional, packages, unshadow and renovate rows run, plus the rows of each changed package.
+- **bump**: only pins and lockfiles changed (the base set, `/opt/agent`, grammars, Tailscale, the optional packages, root devDependencies) and `certs.json`. Pins, the boot smoke and renovate run, plus the rows of each changed package, and the catalog rows when an optional package changed.
+- **full**: everything else, and every merge queue run, push to `main` and dispatch. A `package.json` that changed beyond its dependencies, a lockfile without a pin change, a changed helper or fixture, and a package without rows all run the full suite.
+
+[`scripts/ci/scopes.json`](scripts/ci/scopes.json) maps each package name or pattern to its rows (`full` for the harness, Playwright and the installer's tar, `vendors` for the slicc CLI). The plan prints its mode and why in the job summary, and `ci / test` passes only when the jobs that mode skips were skipped and every other job passed: `ci: PASS docs plan, 0 shards, skipped integration and vendors`. The merge queue always runs everything, so `main` is never less tested.
+
 Every shard runs the files with a failing test once more and passes when they pass (`retry`, skipped when it wouldn't fit the shard's 62 minutes). From 2026-10-17 to 2026-10-18 a two-by-two experiment compared that with control: 0 of 28 merge queue runs with retry failed, against 15 of 42 without it, so the arms without retry were retired. The pull request's number mod 2 still picks whether a failing shard also cancels the others (`fail-fast+retry` for odd numbers, `retry` for even ones and pushes to `main`), for its runs and its merge queue runs alike, to measure what fail-fast does to the time a pull request waits on CI and its time to merge. The plan, with the arm, the seed and each shard's items, is in the job summary and the `experiment-plan` artifact; each shard's record (`artifacts/experiment/<shard>.json`: its groups, the first run and any retry with their exit codes, counts and failed files) is in its `integration-<shard>` artifact, with each item's time and every test that failed and then passed on the retry. `ci / test` joins them into `summary.json` (the `experiment-summary` artifact), and for each test that flipped it files an issue labeled `flaky-test`, or comments on the open one for that test, with the run, the arm, the shard and the first run's error ([`scripts/ci/summary.mjs`](scripts/ci/summary.mjs)); this step never fails the check, and a fork's read-only token files nothing. `node scripts/ci/durations.mjs` refreshes `durations.json` with the median times of the last 40 runs' summaries.
 
 ## Hosting

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-bios",
-  "version": "1.30.1",
+  "version": "1.30.2",
   "description": "Slim loader that boots SLICC into OPFS and serves the UI from there",
   "type": "module",
   "license": "Apache-2.0",
@@ -43,7 +43,7 @@
   },
   "devDependencies": {
     "@ai-ecoverse/slicc": "1.44.8",
-    "@ai-ecoverse/slicc-browsers": "1.8.5",
+    "@ai-ecoverse/slicc-browsers": "1.9.0",
     "@ai-ecoverse/slicc-node": "2.5.1",
     "@ai-ecoverse/slicc-shared-web": "1.24.2",
     "@ai-ecoverse/slicc-spectrum": "1.96.1",

package/src/packages/package-lock.json

@@ -6,7 +6,7 @@
     "": {
       "name": "slicc-bios-packages",
       "dependencies": {
-        "@ai-ecoverse/slicc-browsers": "1.8.5",
+        "@ai-ecoverse/slicc-browsers": "1.9.0",
         "@ai-ecoverse/slicc-cdp": "1.30.11",
         "@ai-ecoverse/slicc-clipboard": "1.0.2",
         "@ai-ecoverse/slicc-kernel": "1.129.0",
@@ -37,9 +37,9 @@
       }
     },
     "node_modules/@ai-ecoverse/slicc-browsers": {
-      "version": "1.8.5",
-      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-browsers/-/slicc-browsers-1.8.5.tgz",
-      "integrity": "sha512-Ec91bcUjUORvGzC1YQ9BJ+0N17T8pJMITcAkVSVFayO0cq5OP8T1kXrMC/LoXVqLcOjo8kmxEVsu/qkzylyNFw==",
+      "version": "1.9.0",
+      "resolved": "https://registry.npmjs.org/@ai-ecoverse/slicc-browsers/-/slicc-browsers-1.9.0.tgz",
+      "integrity": "sha512-e20UO/bon0lXGDMq/UEaNwHedvX8Qyun7wneRVhlJUiFPrnOpjRx6xBopglLQIv1Iw/14ap5Xcc/GoNQwSeX8w==",
       "license": "Apache-2.0",
       "engines": {
         "node": ">=24"

package/src/packages/package.json

@@ -3,7 +3,7 @@
   "private": true,
   "description": "Packages the BIOS installs from npm into OPFS, pinned by package-lock.json and pnpm-lock.yaml",
   "dependencies": {
-    "@ai-ecoverse/slicc-browsers": "1.8.5",
+    "@ai-ecoverse/slicc-browsers": "1.9.0",
     "@ai-ecoverse/slicc-cdp": "1.30.11",
     "@ai-ecoverse/slicc-clipboard": "1.0.2",
     "@ai-ecoverse/slicc-kernel": "1.129.0",

package/src/packages/pnpm-lock.yaml

@@ -9,8 +9,8 @@ importers:
   .:
     dependencies:
       '@ai-ecoverse/slicc-browsers':
-        specifier: 1.8.5
-        version: 1.8.5
+        specifier: 1.9.0
+        version: 1.9.0
       '@ai-ecoverse/slicc-cdp':
         specifier: 1.30.11
         version: 1.30.11
@@ -95,8 +95,8 @@ importers:
 
 packages:
 
-  '@ai-ecoverse/slicc-browsers@1.8.5':
-    resolution: {integrity: sha512-Ec91bcUjUORvGzC1YQ9BJ+0N17T8pJMITcAkVSVFayO0cq5OP8T1kXrMC/LoXVqLcOjo8kmxEVsu/qkzylyNFw==}
+  '@ai-ecoverse/slicc-browsers@1.9.0':
+    resolution: {integrity: sha512-e20UO/bon0lXGDMq/UEaNwHedvX8Qyun7wneRVhlJUiFPrnOpjRx6xBopglLQIv1Iw/14ap5Xcc/GoNQwSeX8w==}
     engines: {node: '>=24'}
 
   '@ai-ecoverse/slicc-cdp@1.30.11':
@@ -200,7 +200,7 @@ packages:
 
 snapshots:
 
-  '@ai-ecoverse/slicc-browsers@1.8.5': {}
+  '@ai-ecoverse/slicc-browsers@1.9.0': {}
 
   '@ai-ecoverse/slicc-cdp@1.30.11': {}