@xenosystem/agent-interface-electron-host 0.1.35 → 0.1.36

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 (1) hide show
  1. package/package.json +4 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xenosystem/agent-interface-electron-host",
3
- "version": "0.1.35",
3
+ "version": "0.1.36",
4
4
  "license": "UNLICENSED",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -29,11 +29,11 @@
29
29
  "dependencies": {
30
30
  "@xenosystem/agent-sdk": "0.9.27",
31
31
  "@xenosystem/web-context-client": "0.1.1",
32
- "@xenosystem/agent-interface-host": "0.1.35"
32
+ "@xenosystem/agent-interface-host": "0.1.36"
33
33
  },
34
34
  "peerDependencies": {
35
- "electron": ">=28"
35
+ "electron": ">=35"
36
36
  },
37
- "//electron-peer": "The floor is what THIS package needs, not what the standalone app happens to run. It imports only `ipcMain` and `app`, present since Electron 1; the real constraint is ESM support in the main process, which landed in Electron 28. The previous \">=44\" mirrored apps/desktop and made the whole agent-host chain uninstallable for any XENO product on an older Electron — xeno-canvas is on 34, and npm refused it with ERESOLVE.",
37
+ "//electron-peer": "MEASURED, not reasoned. `@xenosystem/agent-sdk` imports `node:sqlite`, a Node 22.5+ builtin, at module load. Electron 34.5.8 is Node 20.19.1 and does NOT have it — verified by launching xeno-canvas against it, which died with ERR_UNKNOWN_BUILTIN_MODULE at load. Electron 35 is the first line on Node 22, so that is the floor. Only Electron 44 (apps/desktop) is actually exercised; 35-43 satisfy the builtin requirement but are untested here. History worth keeping: this was \">=44\" (over-declared, mirroring apps/desktop), briefly \">=28\" (reasoned from ESM-in-main support and WRONG in the dangerous direction — an under-declared peer installs cleanly and dies at launch, while an over-declared one refuses at install with a clear message).",
38
38
  "scripts": {}
39
39
  }