@groeponline/pi-missions 0.3.9 → 0.3.10
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.
- package/CHANGELOG.md +4 -0
- package/README.md +16 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -20,6 +20,18 @@ Pi Missions gives a job a durable identity with a plan, ordered features, accept
|
|
|
20
20
|
|
|
21
21
|
Use it when a task is too large for one prompt, one context window or one uninterrupted coding session.
|
|
22
22
|
|
|
23
|
+
## Where it fits
|
|
24
|
+
|
|
25
|
+
Pi Missions owns **durable work state**: plans, features, evidence, history, recovery, and handoff context that must survive session boundaries. It does not replace Wishcraft's lightweight idea inbox and it does not execute multi-agent swarms itself.
|
|
26
|
+
|
|
27
|
+
`pi-wishcraft idea -> pi-missions mission -> pi-agent-orchestrator run` is the intended promotion path when a thought becomes durable work and then needs parallel or isolated execution.
|
|
28
|
+
|
|
29
|
+
- [`pi-wishcraft`](https://github.com/GroepOnline/pi-wishcraft): operator cockpit and fast idea capture.
|
|
30
|
+
- **pi-missions**: durable plan/task/evidence state.
|
|
31
|
+
- [`pi-agent-orchestrator`](https://github.com/GroepOnline/pi-agent-orchestrator): execution fabric for agents, worktrees, swarms, schedules, and handoffs.
|
|
32
|
+
|
|
33
|
+
GitHub, Slack and webhook integration classes remain lightweight scaffolding; production-readiness is tracked in [#13](https://github.com/GroepOnline/pi-missions/issues/13).
|
|
34
|
+
|
|
23
35
|
## 30-second start
|
|
24
36
|
|
|
25
37
|
```bash
|
|
@@ -181,6 +193,10 @@ Run the built extension locally:
|
|
|
181
193
|
pi -e ./dist/index.js
|
|
182
194
|
```
|
|
183
195
|
|
|
196
|
+
### Recovery behavior
|
|
197
|
+
|
|
198
|
+
Safe mission saves keep the previous valid `plan.json` as `plan.json.bak`. When the primary plan is unreadable or invalid, loading automatically tries the backup before giving up. Schema migrations create a separate timestamped `plan.json.pre-migration-*.bak` before rewriting state. Recovery is automatic for a corrupt primary plan; operators can inspect the backup files directly when diagnosing a failed migration or filesystem problem.
|
|
199
|
+
|
|
184
200
|
CLI diagnostics:
|
|
185
201
|
|
|
186
202
|
```bash
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@groeponline/pi-missions",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.10",
|
|
4
4
|
"description": "Persistent mission orchestration for Pi: durable plans, task queues, evidence trails, SQLite state, resumable execution, and handoffs across agent sessions.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"private": false,
|