@groeponline/pi-missions 0.3.9 → 0.3.11

package/CHANGELOG.md

@@ -7,6 +7,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.11] - 2026-09-05
+
+### Fixed
+- persist history onto fresh mission state (#18)
+
+### Documentation
+- disambiguate schema_version from SCHEMA_VERSION (#12)
+## [0.3.10] - 2026-08-30
+
+### Maintenance
+- prove durable mission fallback path (#17)
 ## [0.3.9] - 2026-08-30
 
 ### Documentation

package/README.md

@@ -20,6 +20,18 @@ Pi Missions gives a job a durable identity with a plan, ordered features, accept
 
 Use it when a task is too large for one prompt, one context window or one uninterrupted coding session.
 
+## Where it fits
+
+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.
+
+`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.
+
+- [`pi-wishcraft`](https://github.com/GroepOnline/pi-wishcraft): operator cockpit and fast idea capture.
+- **pi-missions**: durable plan/task/evidence state.
+- [`pi-agent-orchestrator`](https://github.com/GroepOnline/pi-agent-orchestrator): execution fabric for agents, worktrees, swarms, schedules, and handoffs.
+
+GitHub, Slack and webhook integration classes remain lightweight scaffolding; production-readiness is tracked in [#13](https://github.com/GroepOnline/pi-missions/issues/13).
+
 ## 30-second start
 
 ```bash
@@ -181,6 +193,10 @@ Run the built extension locally:
 pi -e ./dist/index.js
 ```
 
+### Recovery behavior
+
+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.
+
 CLI diagnostics:
 
 ```bash

package/dist/index.js

@@ -2158,24 +2158,25 @@ function spawnWorker(mission, config) {
       }
       try {
         const missionId = mission.id;
-        appendHistory(mission, {
-          event: "worker_finished",
-          featureId: config.featureId,
-          note: `Exit ${code}${signal ? ` (${signal})` : ""} in ${Math.round(durationMs / 1e3)}s`,
-          details: {
-            exitCode: code,
-            signal: signal ?? void 0,
-            durationMs,
-            killed,
-            missionId,
-            stdoutLen: stdout.length,
-            stderrLen: stderr.length,
-            model,
-            orchestraCorrelation: config.orchestraCorrelation
-          }
-        });
-        saveMissionSafe(mission).catch(() => {
-        });
+        const freshMission = loadMissionFromDisk(missionId);
+        if (freshMission?.id === missionId) {
+          appendHistory(freshMission, {
+            event: "worker_finished",
+            featureId: config.featureId,
+            note: `Exit ${code}${signal ? ` (${signal})` : ""} in ${Math.round(durationMs / 1e3)}s`,
+            details: {
+              exitCode: code,
+              signal: signal ?? void 0,
+              durationMs,
+              killed,
+              missionId,
+              stdoutLen: stdout.length,
+              stderrLen: stderr.length,
+              model,
+              orchestraCorrelation: config.orchestraCorrelation
+            }
+          });
+        }
       } catch {
       }
       resolve3(result);