pi-herdsman 0.19.1 → 0.20.0

package/README.md

@@ -27,7 +27,7 @@ _Concept animation, not a live recording._
 - **Parallel and nested delegation.** Run independent work concurrently and let explicitly enabled Agents delegate their own bounded subtasks.
 - **Project orchestration.** A Manager coordinates durable branch-based work across independent Leads and their Agent trees.
 - **Direct supervision.** Chief, Manager, Lead, and Agent responsibilities stay explicit instead of collapsing into one global controller.
-- **Owned usage visibility.** Inspect Pi-native token usage and cost for the current session plus transitively owned managed-Agent sessions.
+- **Owned usage visibility.** Inspect Pi-native token usage and cost for the current session and its transitively owned managed Agents. An active Manager also sees the Leads in its current durable project assignments and their owned Agent trees.
 - **Your workflow stays yours.** Bring your own Agent definitions, models, tools, skills, extensions, and development process.
 
 ## Quick start
@@ -38,6 +38,9 @@ On Linux or macOS, install the released Pi, herdr, and Pi Herdsman stack:
 curl -fsSL https://raw.githubusercontent.com/boadij/pi-herdsman/main/install.sh | sh
 ```
 
+See [Getting started](docs/getting-started.md) for the tested runtime baselines
+and how the bootstrap handles newer Pi and herdr versions.
+
 If you already manage Pi and herdr yourself:
 
 ```sh
@@ -65,7 +68,7 @@ Open the human Agent-management surface at any time with:
 /agents
 ```
 
-It also exposes `Session stats` for the current Pi session and its owned Agent sessions.
+It also exposes `Session stats` for the current Pi session and its owned Agent sessions; in active Manager mode, it includes current assigned project Leads and their owned Agent trees.
 
 See [Getting started](docs/getting-started.md) for prerequisites, configuration,
 observability, and the complete first-use path.

package/SKILL.md

@@ -371,15 +371,22 @@ delegating parent that is merely waiting for its direct children.
 
 Ordinary leads own their complete herd, including every agent beneath them. The
 Chief supervises independent leads and never changes ownership. Use
-`supervisor_message` when a direct supervisor must decide or act, or when
-sharing a material warning, scope change, risk, or evidence. Ordinary
-Leads without a verified supervisor continue independently; assigned project
-Leads may message the Manager role while its process is unavailable, and those
-messages remain retained with the project. After a project herd run settles,
-Herdsman handles the normal Manager handoff automatically. Summarize the outcome,
-validation, and important unresolved points in your normal response. Descendants
-use `ask_owner`, not supervisor tools. Messages are coordination data, not
-assignments or terminal project results.
+`supervisor_message` only for material coordination requiring a direct
+supervisor's attention, decision, or action, such as a blocker, warning, scope
+change, risk, or important evidence. Ordinary Leads without a verified
+supervisor continue independently; assigned project Leads may message the
+Manager role while its process is unavailable, and those messages remain
+retained with the project. For an assigned project, Herdsman automatically
+records the Lead's normal response to each project-assignment delivery as a
+project message for the current or a replacement Manager. If the Lead
+successfully delegates or continues managed Agent work, the herd run owns that
+handoff until it settles; summarize the outcome, validation, and important
+unresolved points in the settled response. An unsuccessful delegation leaves
+the local assignment-response path available. Later conversational replies,
+including routine thanks or acknowledgments, stay local and are not
+automatically promoted.
+Descendants use `ask_owner`, not supervisor tools. Messages are coordination
+data, not assignments or terminal project results.
 
 `supervisor_message` is available to ordinary Leads and Managers. Assigned Lead
 messages are retained with the project and remain available to a replacement
@@ -423,16 +430,22 @@ Pi Herdsman uses one durable vocabulary:
   worktree group: its primary workspace and linked-worktree workspaces;
 - a **Manager** explicitly assumes dedicated project coordination from that
   group's primary workspace, has no `agent` capability, and does not own Leads'
-  Agents; project execution belongs to Leads and their Agent trees;
+  Agents. Manager supervises project scope and assignment boundaries; Leads own
+  technical decisions and orchestrate execution through their Agent trees;
 - project work belongs to the project, not a Manager session. The project
   assignment represents open work and its Git branch is the work handle. A
   Manager uses `staff_delegate` with a task and optional branch to start new
   project work, and `staff_resume` with its branch to resume an existing
   assignment. Missing worktrees are reconstructed from the same branch,
   resuming the exact saved Pi session when available;
-- settled project herd runs are handled through the normal automatic Manager
-  handoff, and the Lead summarizes the outcome, validation, and important
-  unresolved points in its normal response;
+- the assigned Lead's normal response to each project-assignment delivery is
+  automatically recorded as a project message for the current or a replacement
+  Manager; if the Lead successfully delegates or continues managed Agent work,
+  the herd run owns the handoff until it settles, and the settled response
+  summarizes outcome, validation, and important unresolved points. An
+  unsuccessful delegation leaves the local assignment-response path available.
+  Later conversational replies, including routine
+  acknowledgments, remain local and are not automatically promoted;
   assigned Lead `supervisor_message` calls are nonterminal coordination
   retained across Manager absence and turnover. Project work remains open
   through implementation and review iterations;

package/dist/agent-definitions/generalist.md

@@ -2,7 +2,7 @@
 name: generalist
 description: General-purpose execution agent for scoped tasks that do not fit scout, researcher, implementer, or reviewer
 agents: ["scout", "researcher"]
-systemPromptMode: replace
+systemPromptMode: append
 inheritProjectContext: true
 inheritGlobalContext: false
 noSkills: true

package/dist/agent-definitions/implementer.md

@@ -2,7 +2,7 @@
 name: implementer
 description: Focused implementation agent for a resolved change; use when the required behavior is already decided and the task is to edit, test, and report
 agents: ["scout"]
-systemPromptMode: replace
+systemPromptMode: append
 inheritProjectContext: true
 inheritGlobalContext: false
 noSkills: true

package/dist/agent-definitions/managed-lead.md

@@ -0,0 +1,10 @@
+---
+name: managed-lead
+description: Manager-created project Lead for branch-scoped orchestration and integration
+systemPromptMode: append
+inheritProjectContext: true
+inheritGlobalContext: true
+noSkills: true
+noExtensions: true
+tools: ["read", "ls", "find", "grep"]
+---

package/dist/agent-definitions/researcher.md

@@ -1,7 +1,7 @@
 ---
 name: researcher
 description: External research specialist for questions that require web, documentation, standards, vendor, or other authoritative evidence beyond the repository; use for current facts, API behavior, comparisons, and source-backed recommendations
-systemPromptMode: replace
+systemPromptMode: append
 inheritProjectContext: true
 inheritGlobalContext: false
 noSkills: true

package/dist/agent-definitions/reviewer.md

@@ -2,7 +2,7 @@
 name: reviewer
 description: Independent read-only reviewer for plans, diffs, implementations, and codebase health; use when work needs verification, missing-case analysis, or regression review rather than modification
 agents: ["scout", "researcher"]
-systemPromptMode: replace
+systemPromptMode: append
 inheritProjectContext: true
 inheritGlobalContext: false
 noSkills: true

package/dist/agent-definitions/scout.md

@@ -1,7 +1,7 @@
 ---
 name: scout
 description: Read-only codebase reconnaissance for unfamiliar areas; use to find entry points, trace flows, dependencies, constraints, and risks before deciding or editing
-systemPromptMode: replace
+systemPromptMode: append
 inheritProjectContext: true
 inheritGlobalContext: false
 noSkills: true