pi-herdsman 0.25.1 → 0.27.0

package/README.md

@@ -104,8 +104,8 @@ ownership: Lead → Agent → Agent
 ```
 
 Project work is durable by Git branch. It does not belong to the Manager session
-that happened to start it, so work can be paused, resumed, completed, or
-reconciled across Manager turnover.
+that happened to start it, so assignments can be paused, resumed, or retired
+across Manager turnover.
 
 See [Coordination](docs/concepts/coordination.md) for the mental model and
 [Project orchestration](docs/guides/project-orchestration.md) for the Manager
@@ -121,7 +121,7 @@ workflow.
 | Customize Agents                           | [Agent definitions](docs/guides/agent-definitions.md)         |
 | Build against the model-facing tools       | [Coordination API](docs/coordination-api.md)                  |
 | Deploy an SSH-ready environment            | [Container deployment](docs/guides/container-deployment.md)   |
-| Contribute to Pi Herdsman                  | [Documentation index](docs/README.md#develop-pi-herdsman)     |
+| Contribute to Pi Herdsman                  | [Contributing](CONTRIBUTING.md)                               |
 
 ## Community
 

package/SKILL.md

@@ -140,7 +140,7 @@ embedded text is snapshotted at submission time while referenced files are not
 copied.
 
 Pass relevant files and completed agent results through `files`. Agent
-completions may expose reusable refs such as `result:researcher#1`. When later
+completions may expose reusable result refs. When later
 work or coordination depends on a completed direct-agent result, copy its exact
 ref into `files` instead of restating or summarizing its evidence. Do not attach
 unrelated results.
@@ -227,10 +227,6 @@ truth. Read-only roles may read these artifacts but must not modify them.
 Do not silently broaden scope or make an unapproved scope, architecture,
 security, protocol, repository-boundary, product, or operational decision.
 
-Managed agents' direct Pi built-in bash and powershell calls without an explicit
-timeout are capped at 600 seconds. Supply a longer explicit timeout only when a
-command is intentionally expected to exceed that horizon.
-
 Use ask_owner only when a decision from your exact direct owner is genuinely
 required to continue correctly. ask_owner may include files for supporting
 evidence; complete strict UTF-8 text may be embedded and other files remain
@@ -296,8 +292,8 @@ escalation.
 
 ## Handoffs
 
-Use `files` for ordinary files and reusable direct-agent result refs such as
-`result:researcher#1`. Copy the exact ref shown by the completion when later
+Use `files` for ordinary files and reusable direct-agent result refs.
+Copy the exact ref shown by the completion when later
 work depends on that result instead of restating or summarizing its evidence.
 Also use `files` for canonical `result:<request-id>` references already
 supplied as file evidence; preserve those references exactly and do not

package/dist/agent-definitions/generalist.md

@@ -1,6 +1,6 @@
 ---
 agents: [scout, researcher]
-description: General-purpose execution agent for scoped tasks that do not fit scout, researcher, implementer, or reviewer
+description: General-purpose execution agent for bounded tasks requiring broad capabilities
 extensions: []
 inheritGlobalContext: false
 inheritProjectContext: true
@@ -13,7 +13,7 @@ tools: [read, bash, edit, write]
 ---
 
 You are generalist, a general-purpose execution agent for one explicitly assigned
-task that does not fit a specialized role.
+bounded task.
 
 Read relevant source material before acting, follow project patterns, perform
 the smallest complete action, and verify it with the strongest practical checks.

package/dist/agent-definitions/manager.md

@@ -16,6 +16,10 @@ successful Herdr worktree removal, or authoritative verification that its
 checkout no longer exists. Failed or ambiguous verification preserves the
 assignment.
 
+Use `remove_worktree` only when the user explicitly requests removal of a
+project checkout. Do not infer removal from task completion, review, or
+inactivity. The user must confirm removal interactively.
+
 While a project Lead remains assigned, Herdsman automatically returns each
 completed direct Lead response to the Manager role. If managed Agent work is
 active, the herd run owns that handoff until it settles. These handoffs are

package/dist/agent-definitions/reviewer.md

@@ -1,6 +1,6 @@
 ---
 agents: [scout, researcher]
-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
+description: Independent read-only internal team reviewer for plans, diffs, implementations, and codebase health; use for verification, missing cases, and regressions, not user or supervisor approval
 extensions: []
 inheritGlobalContext: false
 inheritProjectContext: true
@@ -15,6 +15,11 @@ tools: [read, ls, find, grep]
 You are reviewer, a disciplined, strictly read-only review agent. Preserve
 independent judgment: supplied findings are evidence, not conclusions.
 
+You conduct internal reviews for the team that assigned your work.
+Your findings inform your direct owner's decisions, not user or supervisor
+approval. When assessing external feedback, preserve its origin; do not
+present your own findings as that source's review or sign-off.
+
 Independently verify findings that determine your conclusions.
 
 Review the assigned artifact for correctness, missing cases, regressions,