pi-herdsman 0.6.2 → 0.7.1
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/SKILL.md +9 -1
- package/dist/index.js +88 -70
- package/docs/concepts/agents.md +4 -3
- package/docs/concepts/lifecycle.md +8 -0
- package/docs/guides/recovery.md +13 -1
- package/docs/reference/agent-states.md +32 -8
- package/docs/reference/agent.md +18 -9
- package/docs/reference/commands.md +2 -1
- package/docs/reference/configuration.md +10 -0
- package/docs/reference/status-widget.md +11 -6
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -54,6 +54,12 @@ Use steer only to change active work. Use reply only to answer a valid
|
|
|
54
54
|
outstanding ask_owner question. Use close only for intentional teardown or
|
|
55
55
|
abandonment.
|
|
56
56
|
|
|
57
|
+
A lost agent is a managed assignment whose exact physical execution is proven
|
|
58
|
+
gone before a durable terminal result resolved it. Loss is not completion or
|
|
59
|
+
task failure. Treat the assignment as unresolved. Use close to abandon the
|
|
60
|
+
lost generation before replacing it or continuing its saved session. Unknown
|
|
61
|
+
evidence remains fail-closed and is not proof of loss.
|
|
62
|
+
|
|
57
63
|
Never guess identities, paths, sessions, or control state. Treat unknown or
|
|
58
64
|
conflicting evidence as unresolved. Keep one writer per worktree or file-
|
|
59
65
|
ownership boundary. Use a capable definition or report blocked when a required
|
|
@@ -64,7 +70,9 @@ file inspection, large logs or command output, and dataset analysis. Keep small,
|
|
|
64
70
|
tightly coupled work local.
|
|
65
71
|
If several tightly coupled phases are already known, put them in one bounded
|
|
66
72
|
assignment when practical. If genuinely new follow-up work emerges after
|
|
67
|
-
completion and previous context is valuable, continue the exact returned session
|
|
73
|
+
completion and previous context is valuable, continue the exact returned session
|
|
74
|
+
only when the completion is not marked retired. A retired session requires a
|
|
75
|
+
fresh delegation; pass its resultRef/handoff and relevant files instead.
|
|
68
76
|
Never continue work that depends on an active agent. Continue useful
|
|
69
77
|
independent work when available; otherwise end the turn normally. Agent
|
|
70
78
|
completion or attention resumes the owning controller automatically. Do not
|