pi-soly 1.13.3 → 1.13.4

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 +20 -0
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -39,6 +39,26 @@ Restart pi (`/reload`), and you have:
39
39
 
40
40
  The LLM drives execution; `plan`/`execute` delegate to a `worker` subagent when one is available (via pi-subagents), with first-party delegation on the roadmap. You focus on the work.
41
41
 
42
+ ### Known install issue (upstream `pi install`)
43
+
44
+ `pi install` currently does **not** install transitive `peerDependencies` (it skips them the way `--omit=optional` would). pi-soly's MCP stack depends on `@modelcontextprotocol/ext-apps`, which in turn peer-requires `@modelcontextprotocol/sdk` (declared non-optional upstream). After `pi install npm:pi-soly` you may see:
45
+
46
+ ```
47
+ Error: Cannot find module '@modelcontextprotocol/sdk/types.js'
48
+ Require stack:
49
+ - ~/.pi/agent/npm/node_modules/@modelcontextprotocol/ext-apps/dist/src/app-bridge.js
50
+ ```
51
+
52
+ **Workaround** (one-time, after each `pi install` of pi-soly or any pi-soly-related upgrade):
53
+
54
+ ```bash
55
+ cd ~/.pi/agent/npm && npm install
56
+ ```
57
+
58
+ This makes plain npm resolve the transitive peer deps that `pi install` skipped. After this, restart pi (`/reload`) and the MCP features work.
59
+
60
+ Tracked upstream — fix is expected on the pi side, not here.
61
+
42
62
  ---
43
63
 
44
64
  ## 🎯 Why pi-soly?
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-soly",
3
- "version": "1.13.3",
3
+ "version": "1.13.4",
4
4
  "description": "Project management + workflow framework for pi-coding-agent. Plans, state, MANDATORY rules, self-review, multi-question picker, native footer + welcome chrome — one npm install, zero config. The LLM drives execution and delegates to a worker subagent when available.",
5
5
  "type": "module",
6
6
  "main": "index.ts",