pi-herdsman 0.7.4 → 0.8.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.
@@ -71,10 +71,11 @@ A lead Pi session owns its direct agents.
71
71
  A delegating agent may own direct agents when its effective definition has
72
72
  allowed `agents`.
73
73
 
74
- Public list visibility follows this ownership boundary. Durable descendants
74
+ Public list visibility follows this ownership boundary. A lead sees only
75
+ generations whose durable owner chain resolves to that lead. Durable descendants
75
76
  remain attached to their recorded parent even when that parent is lost or
76
- physically unresolved; missing durable ancestry is shown as non-actionable
77
- recovery evidence.
77
+ physically unresolved. Missing, ambiguous, or cyclic durable ancestry is not
78
+ attributed to a herd.
78
79
 
79
80
  ## Authority boundaries
80
81
 
@@ -66,8 +66,8 @@ failed inventory never proves `lost`; relocated or conflicting evidence is
66
66
  | `lost` | `close` only. |
67
67
  | `unknown` | None. |
68
68
 
69
- Descendants remain visible through durable ancestry but do not gain direct
70
- control from that visibility.
69
+ Owned descendants remain visible through proven durable ancestry but do not gain
70
+ direct control from that visibility.
71
71
 
72
72
  ## Inactivity fields
73
73
 
@@ -89,8 +89,9 @@ Request:
89
89
  No selectors or other fields are accepted. A successful result includes the
90
90
  effective `agent_definitions` roster and visible agent records.
91
91
 
92
- Each valid durable generation remains visible, including unresolved `unknown`
93
- and proven `lost` records. Each actionable live agent record includes:
92
+ Each valid durable generation in the controller's proven ownership projection
93
+ remains visible, including physically unresolved `unknown` and proven `lost`
94
+ records. Each actionable live agent record includes:
94
95
 
95
96
  | Field | Meaning |
96
97
  | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
@@ -122,10 +123,11 @@ projection returned by `list` for that controller. It is a startup snapshot;
122
123
  use `list` for live agent state, ownership, or a refreshed definition roster
123
124
  after configuration changes. Leaf agents do not receive a definition roster.
124
125
 
125
- Lead controllers see the complete effective definition roster and agents visible
126
- through their ownership boundary. Delegating agents see only allowed enabled
127
- leaf definitions and their visible agents. Unknown mailbox diagnostics remain
128
- non-actionable.
126
+ Lead controllers see the complete effective definition roster and agents whose
127
+ durable ownership chain resolves to that lead. Delegating agents see only allowed
128
+ enabled leaf definitions and their direct agents. Unrooted, ambiguous, or cyclic
129
+ durable ancestry is not attributed to the current controller. Unknown mailbox
130
+ diagnostics remain non-actionable.
129
131
 
130
132
  ## `inspect`
131
133
 
@@ -71,8 +71,10 @@ A `rollback_failure` can preserve:
71
71
 
72
72
  Inspect these fields before another destructive attempt.
73
73
 
74
- Model-facing error text surfaces available identity, stage, primary cause,
75
- cleanup cause, and next action without discarding the structured details.
74
+ Model-facing error text surfaces operation, rollback and retry state, available
75
+ identity, stage, primary cause, cleanup cause, and next action. Complete
76
+ structured error details remain available in tool-result details for UI and
77
+ logging.
76
78
 
77
79
  ## Model-visible truncation
78
80
 
@@ -13,9 +13,10 @@ overview, peek, and focus behavior is documented in the
13
13
  [supervision reference](supervision.md). The two widgets are never combined.
14
14
 
15
15
  The ambient supervision rows use `├─` for non-final visible leads and `└─` for the
16
- final visible lead. Lead state glyphs remain separate (`◐` needs you, `●`
17
- working, and `○` ordinary/idle). Workspace labels are presentation text inside
18
- each lead row, not additional hierarchy nodes. The widget always retains
16
+ final visible lead. Lead state glyphs remain separate (`◐` needs you, `●` lead
17
+ working, `◉` idle/done with working descendants, and `○` otherwise). Workspace
18
+ labels are presentation text inside each lead row, not additional hierarchy
19
+ nodes. The widget always retains
19
20
  attention leads, caps ordinary leads, and shows omitted leads in a final
20
21
  `└─ … N more · /chief` row.
21
22
 
@@ -91,8 +92,9 @@ Header refresh staleness is not agent inactivity.
91
92
  Every visible agent is rendered in a stable tree. Siblings are sorted by
92
93
  logical label and use Pi's `├─`, `└─`, and `│` connectors.
93
94
  The row shows the agent definition and its exact logical agent label
94
- separately. Recovery-only ancestry evidence is retained by structured status
95
- paths but is not included in this human projection.
95
+ separately. The tree contains only agents in the controller's proven ownership
96
+ projection; unrooted, ambiguous, or cyclic durable ancestry is not attributed to
97
+ the herd.
96
98
 
97
99
  Rows share globally aligned columns for state, elapsed time, compact model,
98
100
  thinking, context percentage, and optional inactivity. Context is shown as a
@@ -112,9 +114,9 @@ overridden. A starting row is removed when its exact request becomes active or
112
114
  terminal, its local runtime is removed, startup fails or rolls back, the
113
115
  controller session restarts, or shutdown clears transient state.
114
116
 
115
- The normal widget retains `lost` and fail-closed `unknown` rows because they
116
- represent durable unresolved generations whose physical state is either proven
117
- gone or not safely provable. `Running` inspection excludes `lost` and
117
+ The normal widget retains owned `lost` and fail-closed `unknown` rows because
118
+ they represent durable unresolved generations whose physical state is either
119
+ proven gone or not safely provable. `Running` inspection excludes `lost` and
118
120
  fail-closed `unknown` rows because they are not safely focusable targets; it
119
121
  otherwise shows authoritative live agent rows and excludes presentation-only
120
122
  starting rows. A terminal result is followed by cleanup; the widget does not
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-herdsman",
3
- "version": "0.7.4",
3
+ "version": "0.8.1",
4
4
  "type": "module",
5
5
  "description": "Asynchronous Pi subagents and agent fleet orchestration with nested delegation, parallel execution, and supervision in herdr.",
6
6
  "license": "Apache-2.0",