@ai-ecoverse/slicc-agent 6.0.3 → 6.0.5

package/README.md

@@ -753,7 +753,7 @@ Every same-repo pull request gets one `cert-review` status from `.github/workflo
   - **Plan:** packs the base and the pull request merged onto it with `npm pack --dry-run --ignore-scripts`. A change touches behaviour when it changes a file either side ships (`dist`, `bin`, `packages/vfs-root` and whatever `files` lists, so a shipped prompt or agent definition counts), a build input (`src/`, `bin/`, `build.mjs`, `tsconfig*.json`, `patches/`, `package.json` and its lock, `.releaserc*`, `scripts/publish.mjs`), `release.yml` or `ci.yml`, or the reviewer itself.
   - **Not behaviour:** anything else, such as `evals/`, `test/`, `README.md`, `AGENTS.md`, `renovate.json`, `lefthook.yml`, `scripts/check-*.mjs` and `review.yml`. It gets a green `not behaviour: <files>`.
   - **Same dist:** a behaviour change is packed for real on both sides. If the tarballs carry the same files, entry types, modes and bytes once each side's exact version and `gitHead` are normalised (source maps without their `mappings`), and `package.json` differs only in `devDependencies`, `version` and `gitHead`, the status is `not behaviour (identical dist)` with both sha256. A change to the reviewer, `release.yml`, `ci.yml`, `.releaserc*` or `scripts/publish.mjs` always gets the full review.
-- **When it runs:** on `merge-ok`, and again on every push while the label is on. Before that a behaviour change is red with `waits for merge-ok`.
+- **When it runs:** on `merge-ok`, and again on every push while the label is on. Before that a behaviour change is red with `waits for merge-ok`. A same-repo pull request by `renovate[bot]` is reviewed without the label, on every push, so a devDependency bump settles as `not behaviour (identical dist)` without anyone labelling it, and a bump that changes what ships gets the full review.
 - **The full review:**
   - The integration suite runs on the merged tree and on main's tree, on `vars.CERT_RUNNER`, with no secrets in those steps. The agent's tests bundle `src/`, so they run on the tree the tarball was packed from.
   - **The NEGATIVE:** the pull request's `test/` diff is applied to main's tree, and its integration tests must fail there for a fix (a test file that fails to load is never a NEGATIVE). Unit tests stay out of git and out of it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ai-ecoverse/slicc-agent",
-  "version": "6.0.3",
+  "version": "6.0.5",
   "description": "SLICC's agent core on pi durable: an agent worker, session storage, remoting and pi extensions",
   "type": "module",
   "license": "Apache-2.0",
@@ -55,15 +55,15 @@
     "typecheck": "tsc",
     "eval:judge": "node evals/judge.mjs",
     "lint": "slicc-lint && npm run lint:patches && npm run lint:chord",
-    "lint:chord": "node scripts/check-chord.mjs",
-    "lint:patches": "node scripts/check-patches.mjs",
+    "lint:chord": "node scripts/verdict.mjs check-chord scripts/check-chord.mjs",
+    "lint:patches": "node scripts/verdict.mjs check-patches scripts/check-patches.mjs",
     "format": "biome check --write .",
     "trust": "npx fledgling sync -y --skip-publish",
     "trust:dry": "npx fledgling sync --dry-run -y --skip-publish",
     "release": "semantic-release"
   },
   "devDependencies": {
-    "@ai-ecoverse/slicc-kernel": "1.120.2",
+    "@ai-ecoverse/slicc-kernel": "1.122.1",
     "@ai-ecoverse/slicc-scrub": "1.0.0",
     "@ai-ecoverse/slicc-shared-web": "1.23.1",
     "@ai-ecoverse/slicc-spectrum": "1.85.0",
@@ -82,7 +82,7 @@
     "typescript": "7.0.2"
   },
   "dependencies": {
-    "@ai-ecoverse/slicc-browsers": "1.7.8",
+    "@ai-ecoverse/slicc-browsers": "1.7.9",
     "@ai-ecoverse/slicc-vault": "1.9.1",
     "@aws-sdk/middleware-websocket": "^3.972.54",
     "@earendil-works/chord": "1.3.0",