pi-herdsman 0.8.1 → 0.10.0

package/SKILL.md

@@ -45,20 +45,32 @@ State describes what is happening; available_actions describes current control
 eligibility. Every operation revalidates exact state and identity before
 mutation.
 
-The live-agent control actions are `steer`, `reply`, and `close`; these mutate
+The live-agent control actions are `steer`, `interrupt`, `reply`, and `close`;
+these mutate
 live agent execution and are available only when listed. Read-only `inspect`
-captures bounded current evidence without changing agent state. A completed
-agent does not remain available for another assignment.
+captures bounded live terminal/process evidence. Read-only `transcript` captures
+bounded persisted Pi conversation and tool evidence when listed. Neither changes
+agent state. A completed agent does not remain available for another assignment.
 
-Use steer only to change active work. Use reply only to answer a valid
-outstanding ask_owner question. Use close only for intentional teardown or
-abandonment.
+Use steer only to change active work non-preemptively. Steering does not cancel
+an in-flight model or tool operation; Pi may queue it until the current
+operation reaches a safe boundary.
+
+Use interrupt only when the current in-flight operation itself must be
+abandoned. Interrupt is preemptive: it cancels the current Pi operation and
+continues the same assignment with the required replacement message. Do not
+interrupt merely because an agent is slow or marked stale; inactivity is
+advisory and does not prove a hang.
+
+Use reply only to answer a valid outstanding ask_owner question. Use close only
+for intentional teardown or abandonment.
 
 A lost agent is a managed assignment whose exact physical execution is proven
 gone before a durable terminal result resolved it. Loss is not completion or
-task failure. Treat the assignment as unresolved. Use close to abandon the
-lost generation before replacing it or continuing its saved session. Unknown
-evidence remains fail-closed and is not proof of loss.
+task failure. Treat the assignment as unresolved. When transcript is listed,
+use it only when the last persisted work materially affects recovery. Use close
+to abandon the lost generation before replacing it or continuing its saved
+session. Unknown evidence remains fail-closed and is not proof of loss.
 
 Never guess identities, paths, sessions, or control state. Treat unknown or
 conflicting evidence as unresolved. Keep one writer per worktree or file-
@@ -88,14 +100,14 @@ necessary independent work remains, end your turn without concluding the task.
 Agent results or attention will resume this session automatically. Do not
 conclude or produce the final synthesis while unresolved agent work remains.
 Do not invent side work, broaden scope, perform speculative or precautionary
-exploration, list or inspect merely for progress, steer merely for status, sleep,
+exploration, list, inspect, or transcript merely for progress, steer merely for status, sleep,
 poll, or otherwise keep the turn alive while agent results are pending.
 
 If list reports result_error, do not start a new delegation over unresolved
 work. Resolve mailbox persistence first, then close the exact agent before
 starting another assignment; follow the stored recovery nextAction.
 
-Before delegate, continue, steer, or reply, make the message self-contained.
+Before delegate, continue, steer, interrupt, or reply, make the message self-contained.
 
 Do not attach or mention agent instruction files such as AGENTS.md, CLAUDE.md,
 GEMINI.md, or equivalents merely because they exist. Rely on normal project or