pi-herdsman 0.6.1 → 0.6.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/SKILL.md +4 -0
- package/dist/index.js +52 -47
- package/docs/guides/recovery.md +3 -1
- package/docs/reference/agent-states.md +5 -1
- package/docs/reference/agent.md +5 -2
- package/docs/reference/status-widget.md +10 -7
- package/package.json +1 -1
package/docs/guides/recovery.md
CHANGED
|
@@ -50,7 +50,9 @@ recovery error is present, inspect its exact details.
|
|
|
50
50
|
## Inactivity advisory
|
|
51
51
|
|
|
52
52
|
A `working` agent with an exact active assignment can become advisory `stale`
|
|
53
|
-
after ten minutes without
|
|
53
|
+
after ten minutes without qualifying execution progress. Model streaming,
|
|
54
|
+
turn/message boundaries, and tool execution start/end boundaries count;
|
|
55
|
+
streaming tool updates alone do not reset progress.
|
|
54
56
|
|
|
55
57
|
Possible list fields:
|
|
56
58
|
|
|
@@ -48,7 +48,11 @@ model metadata, missing activity, a guessed session, or an old agent identity.
|
|
|
48
48
|
## Inactivity fields
|
|
49
49
|
|
|
50
50
|
A qualifying `working` agent may also report `stale`, `inactive_ms`, and
|
|
51
|
-
`last_activity_at`.
|
|
51
|
+
`last_activity_at`. Qualifying progress includes model streaming and tool
|
|
52
|
+
execution boundaries (`tool_execution_start` and `tool_execution_end`), along
|
|
53
|
+
with the surrounding turn and message boundaries. Streaming tool updates alone
|
|
54
|
+
do not advance `last_activity_at`. This advisory does not change the state or
|
|
55
|
+
prove a hang.
|
|
52
56
|
|
|
53
57
|
## See also
|
|
54
58
|
|
package/docs/reference/agent.md
CHANGED
|
@@ -150,8 +150,11 @@ when the exact message limit permits. Otherwise they remain canonical references
|
|
|
150
150
|
|
|
151
151
|
`timeoutMs` is valid on `delegate` and `continue` and must be an integer
|
|
152
152
|
from `5001` through `300000`. The startup budget reserves one bounded diagnostic
|
|
153
|
-
window
|
|
154
|
-
|
|
153
|
+
window; it is unrelated to managed-agent Pi shell execution. Direct calls from
|
|
154
|
+
a managed agent to the Pi built-in `bash` or `powershell` tool receive a default
|
|
155
|
+
600-second timeout when the call omits `timeout`; an explicit timeout is kept
|
|
156
|
+
unchanged. Current message limits are governed by the Herdsman config file and
|
|
157
|
+
its defaults, plus the fixed mailbox protocol ceiling. Managed mailbox records use
|
|
155
158
|
protocol V4 in the `mailboxes-v4` namespace, and control requests use the marker prefix
|
|
156
159
|
`__PI_HERDSMAN_AGENT_V4__:`.
|
|
157
160
|
|
|
@@ -75,9 +75,9 @@ Example:
|
|
|
75
75
|
|
|
76
76
|
The header reports exact non-zero lifecycle states in the order `working`,
|
|
77
77
|
`blocked`, `settling`, `starting`, and `unknown`. `starting` is a
|
|
78
|
-
presentation-only count for assignments
|
|
79
|
-
|
|
80
|
-
|
|
78
|
+
presentation-only count for controller-local assignments that have begun
|
|
79
|
+
startup but have not yet become active or terminal. It is not mailbox state,
|
|
80
|
+
control authority, or Running inventory.
|
|
81
81
|
|
|
82
82
|
Before the first successful refresh, the header says `unavailable`.
|
|
83
83
|
|
|
@@ -103,10 +103,13 @@ useful room before it is truncated.
|
|
|
103
103
|
|
|
104
104
|
Working rows use `● working`, blocked rows use `◐ blocked`, settling rows use
|
|
105
105
|
`◌ settling`, starting rows use `◌ starting`, and unknown rows use `? unknown`.
|
|
106
|
-
Working, settling, and starting animate; blocked and unknown rows are static.
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
106
|
+
Working, settling, and starting animate; blocked and unknown rows are static.
|
|
107
|
+
While a controller-local start remains pending, an authoritative `settling`
|
|
108
|
+
row is presented as `starting` so launch and request handoff remain visually
|
|
109
|
+
continuous. `working`, `blocked`, and `unknown` authoritative states are never
|
|
110
|
+
overridden. A starting row is removed when its exact request becomes active or
|
|
111
|
+
terminal, its local runtime is removed, startup fails or rolls back, the
|
|
112
|
+
controller session restarts, or shutdown clears transient state.
|
|
110
113
|
|
|
111
114
|
`Running` inspection shows every authoritative agent row and excludes
|
|
112
115
|
presentation-only starting rows. A terminal result is followed by cleanup; the
|
package/package.json
CHANGED