pi-herdsman 0.34.0 → 0.35.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 CHANGED
@@ -412,8 +412,8 @@ through `files`.
412
412
 
413
413
  Chief uses `list_staff`, `inspect_staff`, `read_staff_transcript`, and
414
414
  `message_staff`. Manager has those same direct-report tools, peer tools, and
415
- `delegate_project`, `resume_project`, and `stop_lead`.
416
- For administrative removal of project-owned evidence, use the Manager's
415
+ `delegate_work`, `resume_work`, `stop_lead`, `remove_worktree`, and `integrate_branch`.
416
+ For administrative removal of assignment-owned evidence, use the Manager's
417
417
  **Retained evidence** menu and its **Remove requirement…** action. Inherited
418
418
  requirements are protected; snapshots and accepted Agent evidence remain
419
419
  unchanged.
@@ -447,8 +447,9 @@ not ownership or project-resolution authority.
447
447
 
448
448
  Pi Herdsman uses one durable vocabulary:
449
449
 
450
- - a **project** is the Herdsman coordination scope corresponding to one Herdr
451
- worktree group: its primary workspace and linked-worktree workspaces;
450
+ - a **project** is the coordination scope of one verified local Git repository's
451
+ Herdr worktree group. A worktree is a physical checkout, not an independent
452
+ project or ownership record;
452
453
  - a **Manager** explicitly assumes dedicated project coordination from that
453
454
  group's primary workspace and does not own supervised Leads' Agents. It may
454
455
  separately delegate directly to definitions in its effective `agents`
@@ -456,10 +457,11 @@ Pi Herdsman uses one durable vocabulary:
456
457
  ordinary Leads in the verified worktree group are direct reports for
457
458
  observation and communication. Leads own technical decisions and orchestrate
458
459
  execution through their Agent trees;
459
- - project work belongs to the project, not a Manager session. The project
460
- assignment represents open work and its Git branch is the work handle. A
461
- Manager uses `delegate_project` with a task and optional branch to start new
462
- project work, and `resume_project` with its branch to resume an existing
460
+ - a work assignment is a durable branch-scoped objective assigned to an exact
461
+ managed Lead, keyed by repository identity and semantic branch, not by Manager
462
+ session. Its branch is the work handle. A
463
+ Manager uses `delegate_work` with a task and optional branch to start new
464
+ project work, and `resume_work` with its branch to resume an existing
463
465
  assignment. A successful matching Herdr removal event or verified Git
464
466
  worktree inventory showing the checkout absent retires that assignment and
465
467
  pending project messages. Unavailable or ambiguous inventory preserves the
@@ -467,7 +469,7 @@ Pi Herdsman uses one durable vocabulary:
467
469
  its remaining Git branch;
468
470
  - the Manager owns project-level integration decisions. When separately
469
471
  authorized by the Manager local-merge policy, it can accept the exact
470
- validated source revision and use `merge_project` to fast-forward that
472
+ validated source revision and use `integrate_branch` to fast-forward that
471
473
  assigned branch into the verified primary branch. A `needs_update` result
472
474
  means ask the responsible Lead to incorporate the reported target revision,
473
475
  resolve actual conflicts, validate, and report the new exact HEAD; it does
@@ -478,7 +480,7 @@ Pi Herdsman uses one durable vocabulary:
478
480
  including reconciling an already-absent checkout only after Git proves that
479
481
  SHA is on the verified primary branch;
480
482
  - each completed direct turn by an assigned Lead is automatically returned as a
481
- project message to the current or a replacement Manager; if managed Agent
483
+ assignment update to the current or a replacement Manager; if managed Agent
482
484
  work is active, the herd run owns the handoff until it settles, and the
483
485
  settled response summarizes outcome, validation, and important unresolved
484
486
  points. These handoffs are nonterminal; Managers treat routine results as
@@ -17,7 +17,7 @@ Leave technical investigation, implementation, review, validation, and
17
17
  integration to that Lead and its Agents rather than doing or delegating
18
18
  the work yourself.
19
19
 
20
- When local Manager merge permission is enabled, you may use `merge_project`
20
+ When local Manager merge permission is enabled, you may use `integrate_branch`
21
21
  only for an exact assigned branch after accepting its validated full source
22
22
  SHA. It fast-forwards the verified primary branch only. If the target has
23
23
  advanced, ask the responsible Lead to incorporate the target, preserve prior