pi-herdsman 0.38.1 → 0.39.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 +36 -0
- package/README.md +12 -5
- package/SKILL.md +10 -4
- package/dist/index.js +486 -111
- package/dist/index.js.map +3 -3
- package/dist/peer-bridge.js.map +2 -2
- package/docs/adr/0015-use-reserved-definition-for-managed-project-leads.md +4 -0
- package/docs/adr/0037-prioritize-project-definition-overlays.md +29 -0
- package/docs/concepts/coordination.md +6 -2
- package/docs/coordination-api.md +5 -0
- package/docs/guides/agent-definitions.md +10 -5
- package/docs/guides/customizing-agents.md +10 -2
- package/docs/guides/project-orchestration.md +23 -9
- package/docs/guides/recovery.md +5 -2
- package/docs/reference/agent-definition-schema.md +5 -1
- package/docs/reference/staff.md +32 -10
- package/docs/reference/status-widget.md +14 -4
- package/package.json +1 -1
- package/skills/agent-definitions/SKILL.md +4 -2
package/CHANGELOG.md
CHANGED
|
@@ -4,11 +4,47 @@
|
|
|
4
4
|
|
|
5
5
|
### Breaking changes
|
|
6
6
|
|
|
7
|
+
* **config:** Trusted project Agent and role-profile definitions now override global definitions (`bundled < global < trusted project`). Projects may override global `enabled`, `tools`, `agents`, and `permission` values; review trusted project files accordingly.
|
|
7
8
|
* **config:** Role profiles now use `pi-herdsman/roles/` under the Pi
|
|
8
9
|
agent directory and trusted project `.pi/`, separate from Agent definitions.
|
|
9
10
|
Move existing role overrides from `agents/` to `pi-herdsman/roles/` in the
|
|
10
11
|
same scope. Reserved role names in `agents/` are rejected.
|
|
11
12
|
|
|
13
|
+
## [0.39.0](https://github.com/boadij/pi-herdsman/compare/v0.38.1...v0.39.0) (2026-11-04)
|
|
14
|
+
|
|
15
|
+
|
|
16
|
+
### ⚠ BREAKING CHANGES
|
|
17
|
+
|
|
18
|
+
* **config:** prioritize trusted project definition overlays ([#813](https://github.com/boadij/pi-herdsman/issues/813))
|
|
19
|
+
* **manager:** require instructions when resuming work ([#804](https://github.com/boadij/pi-herdsman/issues/804))
|
|
20
|
+
|
|
21
|
+
### Features
|
|
22
|
+
|
|
23
|
+
* **manager:** require instructions when resuming work ([#804](https://github.com/boadij/pi-herdsman/issues/804)) ([bda3c3f](https://github.com/boadij/pi-herdsman/commit/bda3c3f1910f68bcad8a828ee4979688c208fd2e))
|
|
24
|
+
* **manager:** support evidence handoffs in resume_work ([#810](https://github.com/boadij/pi-herdsman/issues/810)) ([0ba2d9c](https://github.com/boadij/pi-herdsman/commit/0ba2d9c7d0435ee529c1944f95a72459578888a4))
|
|
25
|
+
* **ui:** place paused Manager work last ([#808](https://github.com/boadij/pi-herdsman/issues/808)) ([9d152ba](https://github.com/boadij/pi-herdsman/commit/9d152ba1aeac063b1f4ebece4ce8a814f13ef3eb))
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
### Fixes
|
|
29
|
+
|
|
30
|
+
* **ci:** use native Herdr startup in peer federation smoke ([#796](https://github.com/boadij/pi-herdsman/issues/796)) ([62628eb](https://github.com/boadij/pi-herdsman/commit/62628eb95d7d0427cdb1c97b734aa102ed1d524f))
|
|
31
|
+
* **ui:** prioritize Manager Git diffs on narrow screens ([#800](https://github.com/boadij/pi-herdsman/issues/800)) ([75be9c5](https://github.com/boadij/pi-herdsman/commit/75be9c5cf6c8e82a7ce0cce31fb4a68735d3fd08))
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
### Refactoring
|
|
35
|
+
|
|
36
|
+
* **config:** prioritize trusted project definition overlays ([#813](https://github.com/boadij/pi-herdsman/issues/813)) ([4c14646](https://github.com/boadij/pi-herdsman/commit/4c1464602551ea709c2f13fb123b81d97a829815))
|
|
37
|
+
|
|
38
|
+
|
|
39
|
+
### Documentation
|
|
40
|
+
|
|
41
|
+
* **readme:** clarify federated peer communication status ([#799](https://github.com/boadij/pi-herdsman/issues/799)) ([c57e147](https://github.com/boadij/pi-herdsman/commit/c57e14749a297e666c4ecf34b277200ca95aad88))
|
|
42
|
+
|
|
43
|
+
|
|
44
|
+
### Other Changes
|
|
45
|
+
|
|
46
|
+
* **deps:** update ghcr.io/jdx/mise docker tag to v2026.11.0 ([#809](https://github.com/boadij/pi-herdsman/issues/809)) ([fc7ba70](https://github.com/boadij/pi-herdsman/commit/fc7ba7040bdfc229d792d5fe25b11eb23ed21d4c))
|
|
47
|
+
|
|
12
48
|
## [0.38.1](https://github.com/boadij/pi-herdsman/compare/v0.38.0...v0.38.1) (2026-11-03)
|
|
13
49
|
|
|
14
50
|
|
package/README.md
CHANGED
|
@@ -127,11 +127,18 @@ workflow.
|
|
|
127
127
|
Pi Herdsman is actively evolving. Core orchestration workflows are available today,
|
|
128
128
|
while other areas are being refined or expanded.
|
|
129
129
|
|
|
130
|
-
| Area
|
|
131
|
-
|
|
|
132
|
-
| **Lead & Agent orchestration**
|
|
133
|
-
| **Manager orchestration**
|
|
134
|
-
| **Chief coordination**
|
|
130
|
+
| Area | Status | What to expect |
|
|
131
|
+
| -------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------- |
|
|
132
|
+
| **Lead & Agent orchestration** | ✅ **Core complete** | Background and nested delegation, result handoffs, and local peer communication. Ongoing reliability fixes. |
|
|
133
|
+
| **Manager orchestration** | ✨ **Polishing** | Branch-based delegation, supervision, and integration are implemented. Refining recovery and usability. |
|
|
134
|
+
| **Chief coordination** | 🚧 **In progress** | Supervision is available. Repository provisioning and Manager lifecycle orchestration are being developed. |
|
|
135
|
+
| **Federated peer communication** | 🚧 **In progress** | Cross-machine Manager/ordinary Lead messaging and durable replies work. Reverse initiation is planned. |
|
|
136
|
+
|
|
137
|
+
**Federation limitations:** Independent discovery and initiation currently require
|
|
138
|
+
an SSH route from the initiating machine. Replies work over an existing
|
|
139
|
+
correspondence without reverse SSH. See [#790](https://github.com/boadij/pi-herdsman/issues/790)
|
|
140
|
+
for bidirectional initiation and [#688](https://github.com/boadij/pi-herdsman/issues/688)
|
|
141
|
+
for cross-build messaging interoperability.
|
|
135
142
|
|
|
136
143
|
**On the roadmap:** [Coordination profiles](https://github.com/boadij/pi-herdsman/issues/734)
|
|
137
144
|
(replacing the current role-definition terminology),
|
package/SKILL.md
CHANGED
|
@@ -42,8 +42,8 @@ Use these high-salience rules for the model-facing agent boundary:
|
|
|
42
42
|
evidence is also supplied to eligible descendants automatically. Use `files` for relevant evidence
|
|
43
43
|
not registered as retained or specific to one recipient. When forwarding
|
|
44
44
|
evidence that must remain available downstream, set `retain: true` on
|
|
45
|
-
`message_staff` (Manager, retaining its message text and
|
|
46
|
-
target project assignment) or `delegate_agent` (retaining its files for
|
|
45
|
+
`message_staff` or `resume_work` (Manager, retaining its message text and
|
|
46
|
+
files for the target project assignment) or `delegate_agent` (retaining its files for
|
|
47
47
|
eligible managed Agents' own descendants).
|
|
48
48
|
Retained evidence is available to eligible descendants; inspect relevant
|
|
49
49
|
references as needed, not every entry.
|
|
@@ -481,8 +481,14 @@ Pi Herdsman uses one durable vocabulary:
|
|
|
481
481
|
managed Lead, keyed by repository identity and semantic branch, not by Manager
|
|
482
482
|
session. Its branch is the work handle. A
|
|
483
483
|
Manager uses `delegate_work` with a task and optional branch to start new
|
|
484
|
-
project work, and `resume_work` with its branch
|
|
485
|
-
|
|
484
|
+
project work, and `resume_work` with its branch and required fresh instruction
|
|
485
|
+
to resume an existing assignment. Resume accepts optional `files` for
|
|
486
|
+
explicit evidence handoff and optional `retain` (default `false`) to add the
|
|
487
|
+
instruction and supplied files to the assignment's continuing requirements;
|
|
488
|
+
this does not replace the saved task. The instruction is queued separately
|
|
489
|
+
and queueing does not prove delivery. Confirmed retention is distinct from
|
|
490
|
+
enqueue and recovery outcomes. Already running Leads are not relaunched; use `message_staff` for ordinary
|
|
491
|
+
communication with known running Leads. A successful matching Herdr removal event or verified Git
|
|
486
492
|
worktree inventory showing the checkout absent retires that assignment and
|
|
487
493
|
pending project messages. Unavailable or ambiguous inventory preserves the
|
|
488
494
|
assignment. A retired assignment cannot be resumed, but new work may reuse
|