pi-herdsman 0.43.0 → 0.44.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.
@@ -252,6 +252,14 @@ For peers on another Herdr socket, Herdsman uses their live generation-bound
252
252
  published group and socket-scoped assignment evidence; it does not add a
253
253
  cross-socket topology RPC. Delivery always rechecks the recipient locally.
254
254
 
255
+ Independently eligible coordination messages and completed Agent notifications
256
+ may be inserted together at a recipient's next Pi turn boundary. Steering
257
+ remains eligible at the earlier turn boundary; ordinary follow-ups wait until
258
+ settlement. Fan-in is bounded per boundary, so additional eligible items remain
259
+ pending for a later drain. Each communication keeps its own identity, authority
260
+ checks, and delivery receipt: a shared model request does not combine receipts,
261
+ accept work, or complete an assignment.
262
+
255
263
  Leads use nonblocking `message_supervisor` for timely coordination with their
256
264
  effective supervisor; Manager uses nonblocking `message_staff` for requests,
257
265
  clarifications, instructions, or steering. Routine information that can wait
@@ -204,8 +204,14 @@ for divergent histories. With explicit conflict-free merge permission, Git
204
204
  preflight identifies conflicts before stopping the Lead; clean divergence can
205
205
  create a verified merge commit. This does not prove combined functionality or
206
206
  tests passed. Ask the responsible Lead for required validation evidence before
207
- accepting the result. A stopped Lead is not automatically restarted if a later
208
- integration step fails.
207
+ accepting the result. New integration requires a matching completed Lead
208
+ handoff for the accepted source revision and no unresolved assigned execution.
209
+ A visible Git SHA, idle status, or interim supervisor message is insufficient.
210
+ If the completion handoff has not arrived or is stale, wait for normal delivery
211
+ or request a fresh completion report; do not repeatedly poll staff or
212
+ integration tools. The handoff is evidence of a completed report, not proof
213
+ that tests passed or requirements were met. A stopped Lead is not automatically
214
+ restarted if a later integration step fails.
209
215
 
210
216
  Independent feature branches may be integrated one at a time; a later branch
211
217
  may need to incorporate earlier integration first. The Git branch is preserved.
@@ -217,6 +223,8 @@ guarded cleanup. If the checkout is already absent, reconciliation requires
217
223
  independent Git proof that the accepted SHA is on the verified primary branch
218
224
  and exact assignment/provenance checks. Checkout removal or assignment
219
225
  retirement alone does not prove integration or project validation succeeded.
226
+ An already-integrated accepted SHA uses this existing cleanup-recovery path and
227
+ does not require a new completion handoff.
220
228
 
221
229
  ## Coordinate and review
222
230
 
@@ -339,12 +339,12 @@ must pass `tools` and `excludeTools` to be model-callable. Tool filtering is
339
339
  not extension sandboxing: loaded extensions may still run handlers, commands,
340
340
  shortcuts, providers, initialization, and other non-tool behavior.
341
341
 
342
- Pi's native tool policy is the callable boundary verified for the documented
343
- integration. A provider or conversion integration may add its own presentation
344
- layer, so provider-visible tool descriptions should not be treated as a Pi
345
- Herdsman permission registry or as proof that extension code is sandboxed. Pi Herdsman
346
- passes the native policy through; it does not independently guarantee every
347
- provider presentation boundary.
342
+ Pi's native tool policy governs native Pi direct and nested tool execution.
343
+ It does not guarantee that a provider or conversion integration will hide
344
+ ineligible tools from its own discovery or presentation layer, or restrict an
345
+ independent runtime that executes tools outside Pi's native dispatch. Provider-
346
+ visible descriptions are not a Pi Herdsman permission registry, and tool
347
+ filtering does not sandbox loaded extension code.
348
348
 
349
349
  Tools with the same name are not independently permissionable by source, and
350
350
  the winner for a name collision is not a supported ordering contract.
@@ -341,6 +341,13 @@ preflight unavailable on older Git returns `blocked`. Git success does not
341
341
  prove tests or semantic acceptance; obtain required combined validation before
342
342
  acceptance.
343
343
 
344
+ New integration requires a matching completed Lead handoff for the accepted
345
+ source revision and no unresolved assigned execution. A visible Git SHA, idle
346
+ status, or interim supervisor message is insufficient. If completion evidence
347
+ is missing or stale, wait for the normal handoff or request a fresh completion
348
+ report; do not poll staff or integration tools. A completed handoff confirms
349
+ the report boundary, not that tests passed or requirements were met.
350
+
344
351
  The structured result reports `status`, `integrated`, `checkout_removed`, and
345
352
  `assignment_retired` independently. `needs_update` leaves both checkouts
346
353
  untouched. Successful integration triggers guarded cleanup of the exact
@@ -351,9 +358,10 @@ same accepted SHA rechecks the exact assignment and policy and retries
351
358
  guarded cleanup. If the checkout is already absent, it is reconciled only
352
359
  after fresh Git evidence proves the accepted SHA is contained in the verified
353
360
  primary branch, plus checkout provenance and exact-assignment checks. Absence
354
- alone never proves integration. Other validation or Git-state uncertainty
355
- fails closed; a `blocked` result may require inspecting the primary checkout
356
- before retrying.
361
+ alone never proves integration. An already-integrated accepted SHA follows
362
+ this existing cleanup-recovery path rather than requiring a new completion
363
+ handoff. Other validation or Git-state uncertainty fails closed; a `blocked`
364
+ result may require inspecting the primary checkout before retrying.
357
365
 
358
366
  ## See also
359
367
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-herdsman",
3
- "version": "0.43.0",
3
+ "version": "0.44.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",