context-mode 1.0.119 → 1.0.121

package/skills/.ignore

@@ -0,0 +1,7 @@
+# Files in this directory that are NOT skills.
+# Pi's skill loader (@mariozechner/pi-coding-agent) reads `.ignore`, `.gitignore`,
+# and `.fdignore` while scanning skill directories with includeRootFiles=true,
+# and skips matching entries. Keeping this list in-package guarantees Pi will not
+# attempt to parse non-skill markdown as a skill — even if a stale copy of the
+# file ever slips into a published tarball (see issue #496 / v1.0.120 regression).
+UPSTREAM-CREDITS.md

package/skills/ctx-purge/SKILL.md

@@ -9,23 +9,37 @@ user-invocable: true
 
 # Context Mode Purge
 
-Permanently deletes ALL session data for this project: knowledge base, session events, analytics, and stats.
+Permanently deletes session data for this project. Two scopes are supported (issue #520):
+
+- **Project scope** (`scope: "project"`): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats.
+- **Session scope** (`sessionId: "<id>"` or `scope: "session"`): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved.
 
 ## Instructions
 
-1. **Warn the user**: This is irreversible. Everything will be deleted:
+1. **Decide the scope first** with the user:
+   - "Wipe just one session?" → ask for the `sessionId`.
+   - "Wipe the whole project?" → confirm scope:'project' (this is the destructive, irreversible default).
+2. **Warn the user about scope:'project'**. Everything will be deleted:
    - FTS5 knowledge base (all indexed content from `ctx_index`, `ctx_fetch_and_index`, `ctx_batch_execute`)
-   - Session events DB (analytics, metadata, resume snapshots)
+   - Session events DB (analytics, metadata, resume snapshots) for ALL sessions in the project
    - Session events markdown file
-   - In-memory session stats
-2. Call the `mcp__context-mode__ctx_purge` MCP tool with `confirm: true`.
-3. Report the result to the user — the response lists exactly what was deleted.
+   - In-memory session stats + persisted stats file
+3. Call the `mcp__context-mode__ctx_purge` MCP tool with the chosen parameters:
+   - Scoped: `{ confirm: true, sessionId: "<id>" }` — implies scope:'session'.
+   - Project: `{ confirm: true, scope: "project" }` — explicit destructive form.
+   - Bare `{ confirm: true }` still works but emits a deprecation warning. Prefer the explicit forms.
+4. Report the result to the user — the response lists exactly what was deleted and (for scoped purges) confirms that other sessions and project stats were preserved.
+
+## Schema rules
+
+- `confirm: true` is always required.
+- `sessionId` and `scope: "project"` together is REJECTED as ambiguous (the sessionId implies session scope; combining with project scope contradicts intent).
+- `scope: "session"` without `sessionId` throws — sessionId is required.
 
 ## When to Use
 
-- When the KB contains stale or incorrect content polluting search results.
-- When switching between unrelated projects in the same session.
-- When you want a completely fresh start for this project.
+- **Scoped (per-session)**: scratch acceptance scenarios, drill replays, isolating a polluted session without losing the main working session's stats.
+- **Project**: KB contains stale or incorrect content polluting search results, switching between unrelated projects in the same session, completely fresh start.
 
 ## Important