pi-herdsman 0.48.0 → 0.49.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 +37 -0
- package/dist/coordinators/managed-lead.md +7 -0
- package/dist/coordinators/manager.md +11 -1
- package/dist/index.js +68 -24
- package/dist/index.js.map +2 -2
- package/docs/concepts/coordination.md +1 -1
- package/docs/coordination-api.md +8 -11
- package/docs/development/validation.md +16 -10
- package/docs/guides/container-deployment.md +37 -26
- package/docs/guides/customizing-agents.md +18 -14
- package/docs/guides/recovery.md +2 -2
- package/docs/reference/agent-definition-schema.md +2 -2
- package/docs/reference/await-owner.md +17 -6
- package/docs/reference/commands.md +15 -11
- package/docs/reference/configuration.md +3 -3
- package/package.json +2 -2
- package/skills/agent-definitions/SKILL.md +14 -14
|
@@ -194,7 +194,7 @@ warnings may use nonblocking `message_supervisor`. This is ordinary
|
|
|
194
194
|
coordination, not assignment state; there is no deduplication between a
|
|
195
195
|
message and a later result.
|
|
196
196
|
Project assignments end on successful Herdr worktree removal or verified Git
|
|
197
|
-
checkout absence
|
|
197
|
+
checkout absence, not on settlement, review, or direct user interaction.
|
|
198
198
|
Retirement preserves Managed Lead identity, session history and exact Agent
|
|
199
199
|
ownership without asserting completion or acceptance. See
|
|
200
200
|
[Project orchestration](../guides/project-orchestration.md) for the workflow.
|
package/docs/coordination-api.md
CHANGED
|
@@ -8,17 +8,11 @@ the router to their exact contracts, not a second copy of them.
|
|
|
8
8
|
## Code-mode tool access
|
|
9
9
|
|
|
10
10
|
Pi tools declared with `direct` exposure can be called by the model and through
|
|
11
|
-
Pi's supported native nested-tool execution when active.
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
`stop_lead`, `remove_worktree`, `integrate_branch`, `message_supervisor`,
|
|
17
|
-
`list_peers`, `message_peer`, `attach_handoff`, `delegate_agent`, and
|
|
18
|
-
`continue_agent`, and `notify_owner`. Delegation tools return after assignment acceptance, not
|
|
19
|
-
completion; eventual results arrive through Herdsman's normal result-delivery
|
|
20
|
-
mechanism. `await_owner` also remains `model-only` because it must be a direct,
|
|
21
|
-
exclusive tool call in its turn. See
|
|
11
|
+
Pi's supported native nested-tool execution when active. Herdsman's coordination
|
|
12
|
+
tools use `direct` exposure except `await_owner`, which remains `model-only`
|
|
13
|
+
because it must be called alone as the final tool call of its turn. Delegation
|
|
14
|
+
tools return after assignment acceptance, not completion; eventual results
|
|
15
|
+
arrive through Herdsman's normal result-delivery mechanism. See
|
|
22
16
|
[`await_owner`](reference/await-owner.md) for its contract.
|
|
23
17
|
|
|
24
18
|
Tool access still depends on the active role, ownership, extension loading, and
|
|
@@ -64,6 +58,9 @@ inspect_agent
|
|
|
64
58
|
read_agent_transcript
|
|
65
59
|
```
|
|
66
60
|
|
|
61
|
+
For `read_evidence` and `attach_handoff`, see
|
|
62
|
+
[Handoffs and files](guides/handoffs.md).
|
|
63
|
+
|
|
67
64
|
Managed Agents contact their exact direct owner through
|
|
68
65
|
[`notify_owner`](reference/notify-owner.md) for nonblocking information or
|
|
69
66
|
[`await_owner`](reference/await-owner.md) when progress depends on an answer.
|
|
@@ -7,24 +7,29 @@ run or a concrete environment blocker is recorded.
|
|
|
7
7
|
|
|
8
8
|
## Validation order
|
|
9
9
|
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
10
|
+
Complete implementation, focused tests, smoke testing, review, and all checks
|
|
11
|
+
that may require source fixes before formatting. Fix failures and rerun affected
|
|
12
|
+
checks while the code retains its working layout. Use this pre-commit sequence:
|
|
13
13
|
|
|
14
14
|
```sh
|
|
15
|
-
#
|
|
15
|
+
# Resolve any failures before formatting.
|
|
16
|
+
npm run typecheck
|
|
17
|
+
npm run lint -- --deny-warnings
|
|
18
|
+
npm run check
|
|
19
|
+
|
|
20
|
+
# Final pre-commit source mutation.
|
|
16
21
|
npm run format
|
|
17
22
|
|
|
18
23
|
# Read-only verification before staging or committing.
|
|
19
24
|
npm run format:check
|
|
20
|
-
npm run typecheck
|
|
21
|
-
npm run lint -- --deny-warnings
|
|
22
|
-
npm run check
|
|
23
25
|
git diff --check
|
|
24
26
|
```
|
|
25
27
|
|
|
26
|
-
Do not
|
|
27
|
-
|
|
28
|
+
Do not format during implementation, review, or corrective validation. After
|
|
29
|
+
formatting, do not rerun typechecking, linting, or tests as part of the normal
|
|
30
|
+
pre-commit sequence. If final verification fails or another change is needed,
|
|
31
|
+
fix it, repeat the relevant pre-format checks, and format again only after
|
|
32
|
+
those checks pass.
|
|
28
33
|
|
|
29
34
|
TypeScript typechecking (`npm run typecheck`) and warning-free Oxlint
|
|
30
35
|
(`npm run lint -- --deny-warnings`) are mandatory local and CI checks.
|
|
@@ -221,7 +226,8 @@ remains unchanged and does not replace hosted integration acceptance.
|
|
|
221
226
|
Simulated acceptance uses real Pi, Herdsman, and Herdr processes without model
|
|
222
227
|
credentials. It does not verify real-model decisions. CI runs `core`,
|
|
223
228
|
`continuation`, `chief-tree`, `supervisor-agent`, `terminal-failure`,
|
|
224
|
-
`agent-terminal-failure`, `manager-handoff`,
|
|
229
|
+
`agent-terminal-failure`, `manager-handoff`, `agent-crash-recovery`, and
|
|
230
|
+
`deep-chain`.
|
|
225
231
|
`manager-merge` is also supported but deliberately opt-in, not part of CI.
|
|
226
232
|
|
|
227
233
|
`npm run validate` remains unchanged and does not run smoke. Manual/live smoke
|
|
@@ -11,44 +11,55 @@ with a prebuilt image, SSH access, and persistent Docker-managed volumes.
|
|
|
11
11
|
You need Docker Compose and an SSH public key (for example,
|
|
12
12
|
`~/.ssh/id_ed25519.pub`).
|
|
13
13
|
|
|
14
|
-
|
|
15
|
-
the Compose file into a new directory:
|
|
14
|
+
For guided setup on Linux or macOS, run the native Bash installer:
|
|
16
15
|
|
|
17
16
|
```sh
|
|
18
|
-
|
|
19
|
-
curl -fsSLO https://raw.githubusercontent.com/boadij/pi-herdsman/main/compose.yaml
|
|
17
|
+
curl -fsSL https://raw.githubusercontent.com/boadij/pi-herdsman/main/scripts/docker-setup.sh | bash
|
|
20
18
|
```
|
|
21
19
|
|
|
22
|
-
|
|
20
|
+
On Windows with Docker Desktop, run the native PowerShell installer:
|
|
23
21
|
|
|
24
|
-
```
|
|
25
|
-
|
|
26
|
-
cd pi-herdsman
|
|
27
|
-
bash scripts/docker-setup.sh
|
|
22
|
+
```powershell
|
|
23
|
+
irm https://raw.githubusercontent.com/boadij/pi-herdsman/main/scripts/docker-setup.ps1 | iex
|
|
28
24
|
```
|
|
29
25
|
|
|
30
|
-
The
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
26
|
+
The installer reuses the current checkout when run from its script file, or
|
|
27
|
+
uses `$HOME/pi-herdsman` by default; set `PI_HERDSMAN_DIR` to choose another
|
|
28
|
+
directory. It downloads only missing official Compose files, preserves local
|
|
29
|
+
configuration and Docker volumes, validates the configuration, starts the
|
|
30
|
+
container, and prints connection instructions. Have Docker Compose v2 and an
|
|
31
|
+
SSH public key available. Setup checks the OpenSSH wire structure of the
|
|
32
|
+
provided public key but does not perform cryptographic key or curve validation.
|
|
33
|
+
A structurally valid but cryptographically invalid key (including an invalid
|
|
34
|
+
ECDSA point) may therefore be accepted by setup and later fail during SSH
|
|
35
|
+
authentication. The guided Windows flow currently offers standard Docker only;
|
|
36
|
+
Windows Tailscale and host bind-mount setup are not advertised without platform
|
|
37
|
+
acceptance evidence.
|
|
38
|
+
|
|
39
|
+
When the Bash installer must use sudo, it preserves explicitly set
|
|
40
|
+
`COMPOSE_FILE`, `COMPOSE_PATH_SEPARATOR`, `COMPOSE_PROJECT_NAME`,
|
|
41
|
+
`PUID`, `PGID`, `HERDSMAN_SSH_PORT`, and `TAILSCALE_HOSTNAME`.
|
|
42
|
+
It passes SSH authorization and a temporary Tailscale key only for startup
|
|
43
|
+
or recreation as needed. Sudo policy must allow the requested names. Other
|
|
44
|
+
environment overrides, including variables used by custom Compose files and
|
|
45
|
+
Docker engine selection variables, are not preserved by the installer under
|
|
46
|
+
sudo; configure them for the sudo environment or use direct Docker access.
|
|
47
|
+
All installer operations after sudo selection use that sudo Docker engine.
|
|
48
|
+
|
|
49
|
+
For direct Compose control, use the Compose file included in a checkout or
|
|
50
|
+
download it into a new directory:
|
|
47
51
|
|
|
48
52
|
```sh
|
|
53
|
+
mkdir -p pi-herdsman && cd pi-herdsman
|
|
54
|
+
curl -fsSLO https://raw.githubusercontent.com/boadij/pi-herdsman/main/compose.yaml
|
|
49
55
|
SSH_AUTHORIZED_KEYS="$(cat ~/.ssh/id_ed25519.pub)" docker compose up -d
|
|
50
56
|
```
|
|
51
57
|
|
|
58
|
+
Choose [Tailscale](#use-tailscale) or a [host bind mount](#use-a-host-bind-mount)
|
|
59
|
+
before first start if needed. Optional deployments record their Compose file
|
|
60
|
+
selection in a local `.env`, so subsequent commands use the same networking
|
|
61
|
+
and storage configuration.
|
|
62
|
+
|
|
52
63
|
Connect from the Docker host:
|
|
53
64
|
|
|
54
65
|
```sh
|
|
@@ -52,9 +52,10 @@ inheritance, or permission policy are not supported.
|
|
|
52
52
|
|
|
53
53
|
The bundled `flexible-lead` leaves `tools` unspecified, preserving Pi's normal
|
|
54
54
|
ordinary tool baseline, and supplies flexible direct/delegated-work guidance.
|
|
55
|
-
The bundled `orchestrator-lead`
|
|
56
|
-
|
|
57
|
-
|
|
55
|
+
The bundled `orchestrator-lead` selects `tools: [codemode]`, making Pi's
|
|
56
|
+
native Code Mode available when loaded while keeping other ordinary tools
|
|
57
|
+
disabled. Inspection and execution are delegated to Agents by default.
|
|
58
|
+
For example, an overlay can opt into direct tools:
|
|
58
59
|
|
|
59
60
|
```markdown
|
|
60
61
|
---
|
|
@@ -69,7 +70,7 @@ Use the repository's documented smoke command when validating integration work.
|
|
|
69
70
|
An explicit tool list selects registered ordinary tools; exclusions are then
|
|
70
71
|
applied. At the effective-definition level, `tools: []` disables ordinary
|
|
71
72
|
tools, whereas an absent `tools` field preserves Pi's normal selection.
|
|
72
|
-
Overlays that omit `tools` still inherit the bundled `[]`. Herdsman-owned
|
|
73
|
+
Overlays that omit `tools` still inherit the bundled `[codemode]`. Herdsman-owned
|
|
73
74
|
tools cannot be enabled through a profile, and required Lead coordination
|
|
74
75
|
tools are retained. A configured tool that is not registered
|
|
75
76
|
is simply unavailable. Profile resolution respects project trust. Definition
|
|
@@ -104,8 +105,9 @@ Leads use `managed-lead` instead.
|
|
|
104
105
|
The reserved `manager` and `chief` definitions customize the existing
|
|
105
106
|
supervisory roles without granting or changing authority. Both support the
|
|
106
107
|
runtime-profile fields described in the [schema](../reference/agent-definition-schema.md).
|
|
107
|
-
Manager and Chief default to `tools: []
|
|
108
|
-
|
|
108
|
+
Manager and Chief default to `tools: [codemode]`: when Pi loads Code Mode,
|
|
109
|
+
that is their only ordinary tool alongside mandatory Herdsman coordination
|
|
110
|
+
capabilities. Manager's saved ordinary Lead tool baseline remains
|
|
109
111
|
intact and is restored when Manager mode ends. Explicit trusted-project or
|
|
110
112
|
global Manager overrides can enable registered ordinary tools. Matching tools
|
|
111
113
|
that register after activation are included at the next Manager run or
|
|
@@ -164,24 +166,26 @@ Use the read tool when a supervised decision requires checking a local artifact.
|
|
|
164
166
|
|
|
165
167
|
`managed-lead` is the reserved definition for Manager-created/assigned project
|
|
166
168
|
Leads. Every assigned Lead uses it, independently of the ordinary execution
|
|
167
|
-
mode. It follows the
|
|
169
|
+
mode. It follows the Coordinator precedence described above, but it is launch
|
|
168
170
|
configuration rather than an Agent: it is excluded from the Agent roster
|
|
169
171
|
and cannot be delegated to. It appears under `Coordinators`, with
|
|
170
172
|
Model, Thinking, and Details settings but no `Enabled` action. These settings
|
|
171
173
|
do not add it to Agent discovery or delegation.
|
|
172
174
|
|
|
173
|
-
The bundled default
|
|
174
|
-
coordination tools
|
|
175
|
-
|
|
175
|
+
The bundled default selects `tools: [codemode]`, alongside mandatory
|
|
176
|
+
Herdsman coordination tools. Inspection and execution are delegated to
|
|
177
|
+
managed Agents by default. Manager owns project supervision and
|
|
176
178
|
assignment boundaries; the Lead owns technical decisions and execution
|
|
177
179
|
orchestration.
|
|
178
180
|
Herdsman automatically hands off the normal assignment response, deferring it
|
|
179
181
|
until delegated Agent work settles. See [Project orchestration](project-orchestration.md)
|
|
180
182
|
for the automatic result and `message_supervisor` coordination contract.
|
|
181
|
-
Managed Leads use it to contact their assigned Manager
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
183
|
+
Managed Leads use it to contact their assigned Manager. Other roles follow
|
|
184
|
+
verified direct-supervisor routing; see
|
|
185
|
+
[Supervisor tools](../reference/supervisor.md).
|
|
186
|
+
|
|
187
|
+
Override the same name when a project or user deliberately needs a different
|
|
188
|
+
prompt, model, thinking level, tool policy, skill policy, or extension policy:
|
|
185
189
|
|
|
186
190
|
```markdown
|
|
187
191
|
---
|
package/docs/guides/recovery.md
CHANGED
|
@@ -357,8 +357,8 @@ existing recovery and continuation controls. Transcript history and
|
|
|
357
357
|
working-tree changes are preserved, and the interrupted assignment is not
|
|
358
358
|
replayed automatically.
|
|
359
359
|
|
|
360
|
-
A process that is otherwise unmanaged
|
|
361
|
-
without a valid managed-Agent environment
|
|
360
|
+
A process that is otherwise unmanaged (for example, one launched outside Herdr
|
|
361
|
+
without a valid managed-Agent environment) does not receive the root Lead
|
|
362
362
|
quarantine. If Pi is launched without Herdsman's extension, Herdsman cannot
|
|
363
363
|
enforce tool restrictions at all. Separately, when the extension detects an
|
|
364
364
|
invalid partial managed-Agent environment, its fail-closed hooks disable tools
|
|
@@ -517,6 +517,7 @@ shared herdr agent guidance
|
|
|
517
517
|
<pi_herdsman_agent>
|
|
518
518
|
identity: <definition>:<label>
|
|
519
519
|
direct_owner: lead | <owner-definition>:<owner-label>
|
|
520
|
+
direct_owner_session: <verified Pi session ID>
|
|
520
521
|
</pi_herdsman_agent>
|
|
521
522
|
```
|
|
522
523
|
|
|
@@ -530,8 +531,7 @@ prompt snapshots. Managed agents retain the generic literal
|
|
|
530
531
|
`<active_agent name="<definition>"/>` interoperability signal for compatible
|
|
531
532
|
extensions. Separately, the managed-Agent runtime supplies a structured
|
|
532
533
|
`pi_herdsman_agent` section with the current semantic identity and direct owner.
|
|
533
|
-
`direct_owner`
|
|
534
|
-
continue to use internal Pi session identity. A continued generation
|
|
534
|
+
`direct_owner` and `direct_owner_session` are model-facing context only; exact ownership and routing continue to use internally validated Pi session identity. The session ID identifies the direct owner but does not prove exclusive execution. A continued generation
|
|
535
535
|
recomputes its direct owner from the current caller rather than restoring the
|
|
536
536
|
historical owner.
|
|
537
537
|
|
|
@@ -2,10 +2,17 @@
|
|
|
2
2
|
|
|
3
3
|
[Documentation index](../README.md)
|
|
4
4
|
|
|
5
|
-
`await_owner` is mandatory managed agent infrastructure for
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
It
|
|
5
|
+
`await_owner` is mandatory managed agent infrastructure for necessary input
|
|
6
|
+
from the direct owner that is required to continue the current assignment.
|
|
7
|
+
This may be an unresolved decision, authorization, or specific information the
|
|
8
|
+
owner must supply. It can also be a specific future readiness signal when the
|
|
9
|
+
owner is the designated coordination point for providing it; the single pending
|
|
10
|
+
question remains open until the owner can provide that signal.
|
|
11
|
+
|
|
12
|
+
Agents should complete independently safe work first and must not use
|
|
13
|
+
`await_owner` for progress polling or repeat a pending request without materially
|
|
14
|
+
new evidence. It is not a generic messaging channel, arbitrary external wait,
|
|
15
|
+
or event-subscription API.
|
|
9
16
|
|
|
10
17
|
## Availability
|
|
11
18
|
|
|
@@ -23,7 +30,9 @@ this infrastructure capability.
|
|
|
23
30
|
}
|
|
24
31
|
```
|
|
25
32
|
|
|
26
|
-
`question` must contain non-whitespace text
|
|
33
|
+
`question` must contain non-whitespace text describing the required owner
|
|
34
|
+
input. When that input depends on a future condition, ask for the specific
|
|
35
|
+
readiness information rather than requesting an immediate acknowledgment.
|
|
27
36
|
`files` supplies supporting evidence using the same rules as `agent`: ordinary
|
|
28
37
|
paths, exact reusable direct-agent refs such as `result:researcher#1`, and
|
|
29
38
|
canonical `result:<request-id>` refs already supplied as evidence are accepted.
|
|
@@ -122,7 +131,9 @@ the same assignment with the owner answer.
|
|
|
122
131
|
|
|
123
132
|
Only one `await_owner` question may be outstanding per assignment at a time.
|
|
124
133
|
|
|
125
|
-
There is no ask timeout.
|
|
134
|
+
There is no ask timeout. A reply should be sent only when the requested input
|
|
135
|
+
or an actionable alternative is available. If an external condition is still
|
|
136
|
+
unresolved, leave the question pending rather than promising to answer later.
|
|
126
137
|
|
|
127
138
|
The agent must not guess the owner answer and complete while blocked.
|
|
128
139
|
|
|
@@ -24,7 +24,9 @@ Herdsman package version.
|
|
|
24
24
|
/manager
|
|
25
25
|
/manager refresh
|
|
26
26
|
/manager leave
|
|
27
|
-
/manager remove <branch>
|
|
27
|
+
/manager remove [<branch>]
|
|
28
|
+
/manager remove-preapproval [on|off]
|
|
29
|
+
/manager forget <branch>
|
|
28
30
|
/chief
|
|
29
31
|
/chief refresh
|
|
30
32
|
/chief leave
|
|
@@ -63,9 +65,11 @@ Selecting `Agents` opens the focused `Running`, `Layout`, and `Stop all…` menu
|
|
|
63
65
|
Its running count and current layout are secondary metadata. The root does not
|
|
64
66
|
depend on Agent status or definitions to render.
|
|
65
67
|
|
|
66
|
-
`Settings` contains `Default Lead execution`, `Manager auto-start`,
|
|
67
|
-
|
|
68
|
-
|
|
68
|
+
`Settings` contains `Default Lead execution`, `Manager auto-start`,
|
|
69
|
+
`Skip Manager Git setup confirmation`, `Context retirement`,
|
|
70
|
+
`Manager local merge`, `Status widget rows`, `Max Agent depth`,
|
|
71
|
+
`Message limits`, and `Project overrides…`. The default Lead execution is
|
|
72
|
+
`flexible` and applies only when a future ordinary Lead session has no persisted execution choice; changing
|
|
69
73
|
it does not change the current session. Manager auto-start and context
|
|
70
74
|
retirement show their effective values and identify project overrides, when
|
|
71
75
|
present. Global controls edit global defaults only. `Project overrides…` lets a trusted
|
|
@@ -75,8 +79,7 @@ untrusted project settings do not prevent global controls from being used. An
|
|
|
75
79
|
active Manager can also inspect and change the verified repository's worktree
|
|
76
80
|
removal confirmation policy here. That choice is stored in user-level Herdsman
|
|
77
81
|
authorization, not project settings; enabling still requires typing `enable`.
|
|
78
|
-
|
|
79
|
-
Message limits view edits the user-wide inline attachment and mailbox payload
|
|
82
|
+
`Message limits` edits the user-wide inline attachment and mailbox payload
|
|
80
83
|
limits. It is available only to a lead Pi session with UI.
|
|
81
84
|
Current values and presets show a rough token equivalent using four UTF-8
|
|
82
85
|
bytes per token. The enforced limits are bytes, not tokens.
|
|
@@ -295,11 +298,12 @@ turn to become idle. `/manager refresh` revalidates and applies the active
|
|
|
295
298
|
Manager definition after the current turn becomes idle; a failed refresh keeps
|
|
296
299
|
the previous profile. Refresh requires active Manager mode.
|
|
297
300
|
Manager definitions accept trusted project and global overlays; omitted fields
|
|
298
|
-
inherit from lower-precedence definitions
|
|
299
|
-
|
|
300
|
-
|
|
301
|
-
|
|
302
|
-
|
|
301
|
+
inherit from lower-precedence definitions. See the
|
|
302
|
+
[Agent-definition schema](agent-definition-schema.md#reserved-coordinator-definitions)
|
|
303
|
+
for the current ordinary-tool defaults and override behavior.
|
|
304
|
+
|
|
305
|
+
Leaving Manager restores the session's ordinary Lead tool baseline and selected
|
|
306
|
+
execution profile. Their `agents` allowlist independently controls fresh direct delegation. See
|
|
303
307
|
[Coordination](../concepts/coordination.md) for the role and project boundaries.
|
|
304
308
|
|
|
305
309
|
The effective `Manager auto-start` setting optionally makes a new session
|
|
@@ -168,9 +168,9 @@ configuration, not `.pi/settings.json` or project overrides. Enabling it still
|
|
|
168
168
|
requires explicit typed confirmation; it waives only the extra per-removal
|
|
169
169
|
prompt and never the guarded removal checks.
|
|
170
170
|
Updates to an existing project settings file coordinate with Pi's settings
|
|
171
|
-
lock.
|
|
172
|
-
|
|
173
|
-
|
|
171
|
+
lock. When `.pi/settings.json` does not exist yet, concurrent independent
|
|
172
|
+
writers can still race: Pi checks for the missing file before acquiring the
|
|
173
|
+
lock for its creation.
|
|
174
174
|
|
|
175
175
|
### Manager local merge
|
|
176
176
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-herdsman",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.49.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Asynchronous Pi subagents and agent fleet orchestration for parallel coding agents with nested delegation, background work, and supervision in herdr.",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -91,7 +91,7 @@
|
|
|
91
91
|
"@types/node": "22.20.5",
|
|
92
92
|
"@types/proper-lockfile": "4.1.4",
|
|
93
93
|
"esbuild": "^0.28.2",
|
|
94
|
-
"oxlint": "1.
|
|
94
|
+
"oxlint": "1.94.0",
|
|
95
95
|
"prettier": "3.10.1",
|
|
96
96
|
"typebox": "^1.3.7",
|
|
97
97
|
"typescript": "7.0.2"
|
|
@@ -14,15 +14,14 @@ this skill does not define a second schema or management API.
|
|
|
14
14
|
1. Inspect the Markdown definition layers before changing configuration.
|
|
15
15
|
- Identify a definition by its frontmatter `name`, never by its filename.
|
|
16
16
|
Inspect bundled, global, trusted project, and private repository layers
|
|
17
|
-
in precedence order
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
project.
|
|
17
|
+
in precedence order
|
|
18
|
+
(`bundled < global < trusted project < private repository`), including
|
|
19
|
+
which files contribute to the effective definition. Project and private
|
|
20
|
+
definitions apply only when Pi trusts the project.
|
|
21
21
|
- Resolve matching overlays and effective field values before choosing the
|
|
22
|
-
requested
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
edit to invoke Herdsman's existing discovery and validation, but its
|
|
22
|
+
requested edit scope. Compare editable values with effective project or
|
|
23
|
+
private values and report masked changes accurately. `list_agents` is useful
|
|
24
|
+
after an edit to invoke Herdsman's existing discovery and validation, but its
|
|
26
25
|
enabled-definition capability summary does not expose source paths or
|
|
27
26
|
complete configuration. It cannot establish effective configuration by
|
|
28
27
|
itself.
|
|
@@ -111,12 +110,13 @@ repository`), including which files contribute to the effective
|
|
|
111
110
|
tools-default switches, skills, extensions, or context inheritance on
|
|
112
111
|
these profiles. Their tool policy affects registered ordinary tools;
|
|
113
112
|
Herdsman-owned tools cannot be activated through a profile and mandatory
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
global overrides only. Inspect effective definition layers,
|
|
119
|
-
edits, and
|
|
113
|
+
coordination tools remain available. Bundled Manager and Chief
|
|
114
|
+
profiles select only `codemode` as an ordinary tool when available;
|
|
115
|
+
explicit overlays can select other registered ordinary tools. The saved
|
|
116
|
+
ordinary Lead tool baseline is restored when Manager mode ends. Chief
|
|
117
|
+
accepts global overrides only. Inspect effective definition layers,
|
|
118
|
+
validate edits, and use `/manager refresh` or `/chief refresh` for the
|
|
119
|
+
active role.
|
|
120
120
|
|
|
121
121
|
4. Validate through Herdsman's existing definition engine where available.
|
|
122
122
|
- After an edit in a Lead session, call `list_agents` again. Treat any
|