@pify/plan-mode 0.4.1 → 0.4.2

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pify/plan-mode",
3
- "version": "0.4.1",
3
+ "version": "0.4.2",
4
4
  "description": "Read-only planning mode for pi with an explicit approve-then-execute gate: enforced tool policy, plan files, approach options, fresh-session handoff",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -56,7 +56,7 @@
56
56
  }
57
57
  },
58
58
  "devDependencies": {
59
- "@earendil-works/pi-coding-agent": "^0.84.4",
59
+ "@earendil-works/pi-coding-agent": "^0.85.1",
60
60
  "@types/node": "^22.10.2",
61
61
  "typebox": "^1.1.38",
62
62
  "typescript": "^5.7.2"
@@ -30,6 +30,9 @@ Do not enter plan mode for trivial single-file edits.
30
30
  1-3 alternative approaches, marking one "(Recommended)". The user approves
31
31
  (here or in a fresh session), requests revisions, or discards.
32
32
  6. After approval, implement the plan exactly; report any deviation.
33
+ An approved plan is frozen: do not quietly rewrite the plan file so it
34
+ matches what you ended up doing. Track progress with `plan_step_done`,
35
+ and if the plan turns out to be wrong, say so and re-plan in the open.
33
36
 
34
37
  ## While plan mode is active
35
38