@ai-ecoverse/slicc-agent 5.0.2 → 5.0.3

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 +1 -1
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -631,7 +631,7 @@ The agent never holds a secret's value. Values live in the vault (`vault.sliccy.
631
631
 
632
632
  ## The kernel
633
633
 
634
- `@ai-ecoverse/slicc-kernel` is a peer dependency (`>=1.81.0 <2`; until 3.31.0 the floor was 1.26.3, then 1.47.1): the agent only calls `attachKernel`, the client end of the page kernel's port, so it must match the kernel the page runs. Seven chooses that version: slicc-bios pins the certified kernel next to the agent in `src/packages/agent/package.json`, and pnpm fills the peer from that pin. The floor is the kernel slicc-bios ships (1.81.0 today), and slicc-bios's own CI tests the agent on it; when slicc-bios moves its pin, the floor follows. The kernel and the `wasm-*` commands are devDependencies pinned to certified versions (kernel 1.94.0 today), and CI runs the unit and integration tests on them in one leg. If the port protocol ever breaks within 1.x, a patch release narrows the upper bound. Renovate opens PRs for the kernel, `wasi-pnpm`, the `wasm-*` packages and `slicc-cdp` but never merges them, because they move only after the homescoop coordinator certifies them; such a PR is merged once the cert lane has certified its version.
634
+ `@ai-ecoverse/slicc-kernel` is a peer dependency (`>=1.90.0 <2`; until 3.31.0 the floor was 1.26.3, then 1.47.1, then 1.81.0): the agent only calls `attachKernel`, the client end of the page kernel's port, so it must match the kernel the page runs. Seven chooses that version: slicc-bios pins the certified kernel next to the agent in `src/packages/agent/package.json`, and pnpm fills the peer from that pin. The floor is the kernel slicc-bios ships (1.90.0 today), and slicc-bios's own CI tests the agent on it; when slicc-bios moves its pin, the floor follows. The kernel and the `wasm-*` commands are devDependencies pinned to certified versions (kernel 1.94.0 today), and CI runs the unit and integration tests on them in one leg. If the port protocol ever breaks within 1.x, a patch release narrows the upper bound. Renovate opens PRs for the kernel, `wasi-pnpm`, the `wasm-*` packages and `slicc-cdp` but never merges them, because they move only after the homescoop coordinator certifies them; such a PR is merged once the cert lane has certified its version.
635
635
 
636
636
  ## Patched dependencies
637
637
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc-agent",
3
- "version": "5.0.2",
3
+ "version": "5.0.3",
4
4
  "description": "SLICC's agent core on pi durable: an agent worker, session storage, remoting and pi extensions",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
@@ -64,7 +64,7 @@
64
64
  "@ai-ecoverse/slicc-kernel": "1.94.0",
65
65
  "@ai-ecoverse/slicc-scrub": "1.0.0",
66
66
  "@ai-ecoverse/slicc-shared-web": "1.20.0",
67
- "@ai-ecoverse/slicc-spectrum": "1.77.0",
67
+ "@ai-ecoverse/slicc-spectrum": "1.77.1",
68
68
  "@ai-ecoverse/wasm-bash": "5.3.0-18",
69
69
  "@ai-ecoverse/wasm-coreutils": "9.12.0-6",
70
70
  "@ai-ecoverse/wasm-git": "2.55.0-15",
@@ -91,7 +91,7 @@
91
91
  "typebox": "1.3.36"
92
92
  },
93
93
  "peerDependencies": {
94
- "@ai-ecoverse/slicc-kernel": ">=1.81.0 <2",
94
+ "@ai-ecoverse/slicc-kernel": ">=1.90.0 <2",
95
95
  "@ai-ecoverse/slicc-spectrum": "^1.75.0"
96
96
  },
97
97
  "peerDependenciesMeta": {