pi-herdsman 0.44.0 → 0.45.0

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/CHANGELOG.md CHANGED
@@ -1,5 +1,44 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.45.0](https://github.com/boadij/pi-herdsman/compare/v0.44.0...v0.45.0) (2026-11-12)
4
+
5
+
6
+ ### Features
7
+
8
+ * **agent:** distinguish owner notifications from blocking requests ([#917](https://github.com/boadij/pi-herdsman/issues/917)) ([1b96b23](https://github.com/boadij/pi-herdsman/commit/1b96b239b821517f4cb2c4e5f70392e37076d87f))
9
+
10
+
11
+ ### Fixes
12
+
13
+ * **agent:** prevent duplicate owner notifications and improve presentation ([#926](https://github.com/boadij/pi-herdsman/issues/926)) ([6933cb5](https://github.com/boadij/pi-herdsman/commit/6933cb5871c6e9dcacaf619c513138153b71b689))
14
+ * **supervision:** restore Chief access to non-Git ordinary Leads ([#937](https://github.com/boadij/pi-herdsman/issues/937)) ([b0e3fa5](https://github.com/boadij/pi-herdsman/commit/b0e3fa5b4850ccd86f9448d6e1bbf1a42512afaf)), closes [#918](https://github.com/boadij/pi-herdsman/issues/918)
15
+ * **ui:** restore live tool metadata in managed Agent status headers ([#929](https://github.com/boadij/pi-herdsman/issues/929)) ([56b1f37](https://github.com/boadij/pi-herdsman/commit/56b1f37b46b45acc9b4906154711ab9aaadd3a59))
16
+
17
+
18
+ ### Performance
19
+
20
+ * **agent:** batch concurrent health attention into one owner turn ([#924](https://github.com/boadij/pi-herdsman/issues/924)) ([8a26269](https://github.com/boadij/pi-herdsman/commit/8a26269c52c1da48bae312b877a1b2017a59ad8e))
21
+
22
+
23
+ ### Documentation
24
+
25
+ * prefer Code Mode-compatible tool interfaces ([#921](https://github.com/boadij/pi-herdsman/issues/921)) ([eb9ad4d](https://github.com/boadij/pi-herdsman/commit/eb9ad4da6ac946d880ec6d479b9af3bf077e0950))
26
+ * prefer recipient-side fan-in at existing boundaries ([#920](https://github.com/boadij/pi-herdsman/issues/920)) ([2e27a6b](https://github.com/boadij/pi-herdsman/commit/2e27a6bfc97f378d9fd7e6ed5ecd83c20a7e4a6f))
27
+
28
+
29
+ ### Tests
30
+
31
+ * **ci:** stabilize supervision and peer federation waits ([#936](https://github.com/boadij/pi-herdsman/issues/936)) ([23b29e1](https://github.com/boadij/pi-herdsman/commit/23b29e181c6eb85bed02c6c4a1b3042bae39af73))
32
+ * stabilize Windows-sensitive test waits ([#931](https://github.com/boadij/pi-herdsman/issues/931)) ([ce0142f](https://github.com/boadij/pi-herdsman/commit/ce0142fd18675f9ee5ba1417219bf0ebe8bc4ebd))
33
+
34
+
35
+ ### Other Changes
36
+
37
+ * **deps:** update ghcr.io/jdx/mise docker tag to v2026.11.7 ([#938](https://github.com/boadij/pi-herdsman/issues/938)) ([24722dd](https://github.com/boadij/pi-herdsman/commit/24722dd70ba6e64a763a67371bd62519a9b24370))
38
+ * **deps:** update node.js to v26.13.1 ([#932](https://github.com/boadij/pi-herdsman/issues/932)) ([64f94f2](https://github.com/boadij/pi-herdsman/commit/64f94f2a9d21f692076a994d3df14109282f349e))
39
+ * **runtime:** adopt Pi 1.5.1 ([#923](https://github.com/boadij/pi-herdsman/issues/923)) ([ab069a4](https://github.com/boadij/pi-herdsman/commit/ab069a4e3f485427f7b8210c904a9bd2e1609d81))
40
+ * **runtime:** adopt Pi 1.5.2 ([#939](https://github.com/boadij/pi-herdsman/issues/939)) ([de8e9d2](https://github.com/boadij/pi-herdsman/commit/de8e9d297f3b11eefcd7793872cf699d12063844))
41
+
3
42
  ## [0.44.0](https://github.com/boadij/pi-herdsman/compare/v0.43.0...v0.44.0) (2026-11-11)
4
43
 
5
44
 
package/SKILL.md CHANGED
@@ -114,7 +114,7 @@ the same assignment with the required replacement message. Do not interrupt
114
114
  merely because an agent is slow or marked stale; inactivity is advisory and
115
115
  does not prove a hang.
116
116
 
117
- Use `reply_agent` only to answer a valid outstanding `ask_owner` question. Use
117
+ Use `reply_agent` only to answer a valid outstanding `await_owner` question. Use
118
118
  `stop_agent` only when abandoning the Agent's unfinished assignment is
119
119
  intended. Unlike `stop_lead`, which preserves a Manager's project assignment,
120
120
  `stop_agent` does not complete or automatically restart the work.
@@ -216,7 +216,7 @@ reasonably own it and delegation is useful. Reuse adequate supplied evidence
216
216
  rather than rediscovering it. Integrate direct agent results before completing. The lead
217
217
  retains architecture, approved scope, acceptance of Agent outputs, and
218
218
  final-decision authority.
219
- Delegate only to definitions listed in your effective agents field. `ask_owner`
219
+ Delegate only to definitions listed in your effective agents field. `await_owner`
220
220
  follows its normal eligibility rules when you have no unresolved direct-agent
221
221
  work. If unresolved direct-agent work exists, every such agent must itself be
222
222
  validly waiting on an owner answer; ordinary active or pending-result agent
@@ -247,10 +247,10 @@ large results into assignments.
247
247
  Do not silently broaden scope or make an unapproved scope, architecture,
248
248
  security, protocol, repository-boundary, product, or operational decision.
249
249
 
250
- Use ask_owner only when a decision from your exact direct owner is genuinely
250
+ Use await_owner only when a decision from your exact direct owner is genuinely
251
251
  required to continue correctly. Explicit attachments must be supported UTF-8
252
252
  text fully embedded within the applicable per-file and complete-message
253
- budgets. Call ask_owner alone as the final tool call of the turn. Wait for the
253
+ budgets. Call await_owner alone as the final tool call of the turn. Wait for the
254
254
  direct owner's reply only after the tool confirms the question was sent; if
255
255
  rejected, address the error or report a non-empty blocker. Keep at most one
256
256
  question outstanding. Do not guess the answer. The reply resumes the same
@@ -370,7 +370,7 @@ The first stale advisory remains at ten minutes without qualifying execution
370
370
  progress. Unchanged stale episodes repeat approximately every five minutes;
371
371
  other persistent attention repeats approximately `5m → 2m30s → 1m15s → 1m`,
372
372
  with 30-second scan granularity. Stale attention is advisory, not proof of
373
- a hang. Lost and delivered `ask_owner` attention retain their existing message
373
+ a hang. Lost and delivered `await_owner` attention retain their existing message
374
374
  identity, while `result_error`, external runtime `blocked`, old unacknowledged
375
375
  handoffs, and physical `unknown` use generic attention. An unresolved
376
376
  unacknowledged request must not be duplicated or resubmitted: retained work is
@@ -417,7 +417,7 @@ send a duplicate message solely to report a result that Herdsman will hand off
417
417
  automatically. Treat
418
418
  routine progress or conversational results as informational; act only when
419
419
  review, a decision, correction, or other useful coordination is needed.
420
- Descendants use `ask_owner`, not supervisor tools. Messages are coordination
420
+ Descendants use `await_owner`, not supervisor tools. Messages are coordination
421
421
  data, not assignments or terminal project results.
422
422
 
423
423
  `message_supervisor` is available to Leads and Managers on their direct
@@ -553,7 +553,9 @@ not disable authorized Agent coordination. An empty list disables fresh
553
553
  delegation only, not management of existing owned work; omission also disables
554
554
  fresh delegation for Manager and Chief, but not for Leads. A delegation-capable
555
555
  managed session remains an Agent at every depth.
556
- Every managed agent receives `ask_owner`. A non-empty effective `agents` list
556
+ Every managed agent receives `await_owner` and `notify_owner`. Use `notify_owner`
557
+ for material information when work can continue; use `await_owner` only when
558
+ the assignment cannot proceed without the owner's answer. A non-empty effective `agents` list
557
559
  is necessary but not sufficient to enable the nine Agent ownership tools:
558
560
  `list_agents`, `delegate_agent`, `continue_agent`, `steer_agent`,
559
561
  `interrupt_agent`, `reply_agent`, `stop_agent`, `inspect_agent`, and
@@ -561,7 +563,7 @@ is necessary but not sufficient to enable the nine Agent ownership tools:
561
563
  `agent`, when `noTools: true` unless explicit `tools` contains `agent`,
562
564
  or when `tools` is explicitly empty. Otherwise, omitted `tools` permits
563
565
  delegation and explicit ordinary tools permit it. An empty or omitted `agents`
564
- list always makes the agent a leaf with `ask_owner` only. The `agent` name is
566
+ list always makes the agent a leaf with `await_owner` and `notify_owner` only. The `agent` name is
565
567
  configuration-policy evidence, never a registered or callable tool, and leaf
566
568
  projection removes it from an existing `tools` list. Ordinary `tools` and
567
569
  `excludeTools` settings cannot remove required role tools. If `tools` is