pi-herdsman 0.35.0 → 0.36.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/SKILL.md +25 -15
- package/dist/index.js +906 -407
- package/dist/index.js.map +4 -4
- package/dist/peer-bridge.js +188 -83
- package/dist/peer-bridge.js.map +4 -4
- package/docs/adr/0034-separate-definition-namespaces.md +30 -0
- package/docs/development/smoke-testing.md +4 -4
- package/docs/development/validation.md +10 -4
- package/docs/guides/agent-definitions.md +15 -5
- package/docs/guides/container-deployment.md +15 -1
- package/docs/guides/customizing-agents.md +15 -10
- package/docs/guides/handoffs.md +25 -17
- package/docs/guides/project-orchestration.md +1 -1
- package/docs/reference/agent-definition-schema.md +16 -5
- package/docs/reference/agent.md +14 -7
- package/docs/reference/commands.md +1 -1
- package/docs/reference/peer.md +23 -21
- package/docs/reference/staff.md +38 -23
- package/package.json +1 -1
- package/skills/agent-definitions/SKILL.md +16 -7
- /package/dist/{agent-definitions → agents}/generalist.md +0 -0
- /package/dist/{agent-definitions → agents}/implementer.md +0 -0
- /package/dist/{agent-definitions → agents}/researcher.md +0 -0
- /package/dist/{agent-definitions → agents}/reviewer.md +0 -0
- /package/dist/{agent-definitions → agents}/scout.md +0 -0
- /package/dist/{agent-definitions → roles}/chief.md +0 -0
- /package/dist/{agent-definitions → roles}/flexible-lead.md +0 -0
- /package/dist/{agent-definitions → roles}/managed-lead.md +0 -0
- /package/dist/{agent-definitions → roles}/manager.md +0 -0
- /package/dist/{agent-definitions → roles}/orchestrator-lead.md +0 -0
|
@@ -34,11 +34,17 @@ this skill does not define a second schema or management API.
|
|
|
34
34
|
- `../../docs/guides/customizing-agents.md`
|
|
35
35
|
|
|
36
36
|
2. Choose the configuration layer from the requested scope.
|
|
37
|
-
-
|
|
38
|
-
|
|
39
|
-
|
|
37
|
+
- Agent project policy: `<cwd>/.pi/agents/`; global policy:
|
|
38
|
+
`<agentDir>/agents/`.
|
|
39
|
+
- Role project policy: `<cwd>/.pi/pi-herdsman/roles/`; global
|
|
40
|
+
policy: `<agentDir>/pi-herdsman/roles/`. Pi's agent directory
|
|
41
|
+
normally is `~/.pi/agent`. Managed Lead project policy resolves from
|
|
42
|
+
the trusted delegated worktree.
|
|
43
|
+
- Reserved role names are invalid in Agent directories; non-role names are
|
|
44
|
+
invalid in role-profile directories.
|
|
40
45
|
- If scope is genuinely ambiguous and materially changes the result, ask.
|
|
41
|
-
- Never edit bundled
|
|
46
|
+
- Never edit bundled files under `dist/agents/` or
|
|
47
|
+
`dist/roles/`. The Definitions UI writes global overrides only.
|
|
42
48
|
|
|
43
49
|
3. Make the smallest correct Markdown change.
|
|
44
50
|
- Prefer a partial overlay over copying a complete lower-precedence
|
|
@@ -61,8 +67,9 @@ this skill does not define a second schema or management API.
|
|
|
61
67
|
its restrictions and authority boundaries.
|
|
62
68
|
- Lead, Manager, and Chief runtime profiles are not launch definitions. They
|
|
63
69
|
support only `name`, `description`, `body`, `bodyMode` on overlays,
|
|
64
|
-
`tools`, and `excludeTools
|
|
65
|
-
|
|
70
|
+
`tools`, and `excludeTools`; Manager and Chief also support `agents` as
|
|
71
|
+
their direct-delegation allowlist. Do not configure
|
|
72
|
+
model, thinking, prompt launch mode, enabled or permission policy,
|
|
66
73
|
tools-default switches, skills, extensions, or context inheritance on
|
|
67
74
|
these profiles. Their tool policy affects registered ordinary tools;
|
|
68
75
|
Herdsman-owned tools cannot be activated through a profile and mandatory
|
|
@@ -77,7 +84,9 @@ this skill does not define a second schema or management API.
|
|
|
77
84
|
- After an edit in a Lead session, call `list_agents` again. Treat any
|
|
78
85
|
discovery or validation failure as a failed edit and repair or restore the
|
|
79
86
|
target file. Its returned summary can confirm discoverability and
|
|
80
|
-
validation, not the complete effective configuration
|
|
87
|
+
validation, not the complete effective configuration or role-profile
|
|
88
|
+
validation. Validate role profiles through the relevant role resolution;
|
|
89
|
+
Manager and Chief allowlist references must resolve against the Agent roster.
|
|
81
90
|
- If `list_agents` is unavailable, do not claim that the effective Herdsman
|
|
82
91
|
definition set was runtime-validated. The next normal definition discovery
|
|
83
92
|
will validate it.
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|