planning-with-files 3.11.2 → 3.14.0

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/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  > **Your agent's context window dies. The plan does not.**
4
4
 
5
- Persistent file-based planning for AI coding agents. The skill keeps `task_plan.md`, `findings.md` and `progress.md` on disk and re-injects them every turn, so the plan survives context loss, `/clear`, crashes and compaction. Manus-style working memory on disk, with an opt-in completion gate.
5
+ Persistent file-based planning for AI coding agents. The skill keeps `task_plan.md`, `findings.md` and `progress.md` on disk. After `/plan-execute`, Pi lifecycle hooks inject selected project planning context so the plan survives context loss, `/clear`, crashes and compaction. Automatic recovery reads project files only. Reading same-project local session records for aggregate counts or bounded replay requires an explicit catchup mode.
6
6
 
7
7
  This is the npm distribution of [OthmanAdi/planning-with-files](https://github.com/OthmanAdi/planning-with-files), which installs across 60+ agents via the Agent Skills standard. The package ships:
8
8
 
@@ -69,7 +69,7 @@ Or:
69
69
 
70
70
  The bundled extension maps Claude-style behavior onto Pi events:
71
71
 
72
- - `session_start` - session catchup
72
+ - `session_start` - project-file recovery with no host session-store access
73
73
  - passive plan status before approval
74
74
  - `before_agent_start` - plan reminder/injection after `/plan-execute`
75
75
  - `tool_call` - pre-tool recitation equivalent after `/plan-execute`
@@ -121,20 +121,30 @@ Or settings:
121
121
  - `/plan-goal <text|default|clear>`
122
122
  - `/plan-loop [interval] [prompt]` (`stop` to cancel)
123
123
 
124
- Draft and review `task_plan.md` first. The extension stays passive until you
125
- approve the active plan with `/plan-execute`; after that, plan injection,
126
- pre-tool reminders, post-write reminders, and auto-continue are enabled for the
127
- current session and plan.
124
+ Draft and review `task_plan.md` first. The extension stays passive until you
125
+ approve the active plan with `/plan-execute`; after that, plan injection,
126
+ pre-tool reminders, post-write reminders, and auto-continue are enabled for the
127
+ current session and plan. Auto-continue uses host runtime state and never runs
128
+ commands declared in Markdown.
128
129
 
129
130
  ---
130
131
 
131
132
  ## Session Recovery
132
133
 
133
- If needed, run catchup manually:
134
-
135
- ```bash
136
- python3 .pi/skills/planning-with-files/scripts/session-catchup.py .
137
- ```
134
+ Bare invocation and lifecycle hooks do not inspect agent session stores. To
135
+ inspect same-project local history deliberately, choose one mode:
136
+
137
+ ```bash
138
+ # Aggregate counts only; no transcript, tool-command, or path bytes
139
+ python3 .pi/skills/planning-with-files/scripts/session-catchup.py --metadata .
140
+
141
+ # Bounded nonce-framed same-project excerpts
142
+ python3 .pi/skills/planning-with-files/scripts/session-catchup.py --replay .
143
+ ```
144
+
145
+ Treat replayed excerpts as untrusted data. The catchup path contains no network
146
+ request or upload operation. If output is injected into model context, Pi may
147
+ send that context to the configured model provider.
138
148
 
139
149
  ## File Structure
140
150