pi-herdsman 0.25.0 → 0.26.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/README.md +3 -3
- package/dist/agent-definitions/manager.md +4 -0
- package/dist/index.js +1197 -218
- package/dist/index.js.map +3 -3
- package/docs/README.md +2 -0
- package/docs/adr/0012-manager-owns-project-assignment-resolution.md +8 -1
- package/docs/adr/0013-use-herdr-worktree-removal-for-project-retirement.md +1 -1
- package/docs/adr/0017-use-project-assignments-for-managed-lead-authority.md +4 -1
- package/docs/adr/0019-retire-project-assignments-when-worktrees-are-absent.md +1 -3
- package/docs/adr/0020-authorize-confirmed-manager-worktree-removal.md +47 -0
- package/docs/concepts/delegation.md +5 -35
- package/docs/coordination-api.md +3 -1
- package/docs/development/documentation.md +12 -2
- package/docs/development/instruction-interface-design.md +6 -19
- package/docs/development/product-philosophy.md +2 -0
- package/docs/development/smoke-testing.md +49 -0
- package/docs/development/validation.md +14 -7
- package/docs/guides/agent-definitions.md +7 -13
- package/docs/guides/container-deployment.md +2 -0
- package/docs/guides/customizing-agents.md +4 -11
- package/docs/guides/project-orchestration.md +42 -5
- package/docs/guides/recovery.md +31 -0
- package/docs/reference/commands.md +31 -1
- package/docs/reference/staff.md +34 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -104,8 +104,8 @@ ownership: Lead → Agent → Agent
|
|
|
104
104
|
```
|
|
105
105
|
|
|
106
106
|
Project work is durable by Git branch. It does not belong to the Manager session
|
|
107
|
-
that happened to start it, so
|
|
108
|
-
|
|
107
|
+
that happened to start it, so assignments can be paused, resumed, or retired
|
|
108
|
+
across Manager turnover.
|
|
109
109
|
|
|
110
110
|
See [Coordination](docs/concepts/coordination.md) for the mental model and
|
|
111
111
|
[Project orchestration](docs/guides/project-orchestration.md) for the Manager
|
|
@@ -121,7 +121,7 @@ workflow.
|
|
|
121
121
|
| Customize Agents | [Agent definitions](docs/guides/agent-definitions.md) |
|
|
122
122
|
| Build against the model-facing tools | [Coordination API](docs/coordination-api.md) |
|
|
123
123
|
| Deploy an SSH-ready environment | [Container deployment](docs/guides/container-deployment.md) |
|
|
124
|
-
| Contribute to Pi Herdsman | [
|
|
124
|
+
| Contribute to Pi Herdsman | [Contributing](CONTRIBUTING.md) |
|
|
125
125
|
|
|
126
126
|
## Community
|
|
127
127
|
|
|
@@ -16,6 +16,10 @@ successful Herdr worktree removal, or authoritative verification that its
|
|
|
16
16
|
checkout no longer exists. Failed or ambiguous verification preserves the
|
|
17
17
|
assignment.
|
|
18
18
|
|
|
19
|
+
Use `remove_worktree` only when the user explicitly requests removal of a
|
|
20
|
+
project checkout. Do not infer removal from task completion, review, or
|
|
21
|
+
inactivity. The user must confirm removal interactively.
|
|
22
|
+
|
|
19
23
|
While a project Lead remains assigned, Herdsman automatically returns each
|
|
20
24
|
completed direct Lead response to the Manager role. If managed Agent work is
|
|
21
25
|
active, the herd run owns that handoff until it settles. These handoffs are
|