pi-task-tracker 0.1.7 → 0.1.8
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 +1 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -85,6 +85,7 @@ Optional `taskTracker` key in `~/.pi/agent/settings.json` (all default to `true`
|
|
|
85
85
|
|
|
86
86
|
- Rollback granularity is per **task** (agent turn-set), not per message. If you need message-level time travel including your own manual edits, a snapshot-based extension is a better fit — at the cost of full-worktree scans every turn.
|
|
87
87
|
- Files created by shell commands inside a nested repo that was never touched via write/edit during the session are not captured.
|
|
88
|
+
- **Out-of-scope by design** — files outside the session directory (and outside its owning repo) are neither recorded nor rolled back: no new commits in *their* repos, no worktree changes. `/rollback` only ever touches the session's own repo scope, so sibling projects are safe even when the agent writes there via absolute paths — but such changes have no checkpoint.
|
|
88
89
|
- An embedded (unregistered) sub-repo shows as `?? dir/` in the outer `git status` — that's standard git behavior; this extension never stages it.
|
|
89
90
|
|
|
90
91
|
## 本简介（中文）
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-task-tracker",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"description": "Task workflow tracking for the pi coding agent: TODO/README maintenance, per-task git auto-commits as checkpoints, and an interactive /rollback. Hashline-aware, nested-repo aware, subagent-artifact-safe.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|