@zachwill/pi-orchestrate 0.6.0 → 0.7.0

package/README.md

@@ -17,7 +17,7 @@ Pi Orchestrate adds exactly five tools:
 | Tool | Call | Purpose |
 | --- | --- | --- |
 | `orchestrate` | `orchestrate({ worker, title, instructions })` | Start one worker task |
-| `orchestration_status` | `orchestration_status({})` | Inspect the trusted catalog, diagnostics, runs, and worker states |
+| `worker_status` | `worker_status({})` | Inspect the aggregate worker-system diagnostics and recovery snapshot |
 | `interactive_send` | `interactive_send({ worker_id, instructions })` | Send a follow-up to a ready interactive worker |
 | `worker_abort` | `worker_abort({ worker_ids })` or `worker_abort({ all: true })` | Stop active owned work |
 | `interactive_close` | `interactive_close({ worker_id })` | Close a ready interactive worker |
@@ -47,7 +47,7 @@ Asynchronous worker results enter the transcript individually. An ungrouped resu
 
 All state and delivery are owner-scoped. If an owning session is busy or inactive, completed results queue until that exact session is active and idle again. They are never delivered to another session.
 
-`orchestration_status` is for diagnostics and recovery, not completion polling. It exposes bounded owner-scoped state without full task instructions or worker prompts.
+`worker_status` is the aggregate worker-system diagnostics and recovery snapshot, containing the trusted catalog, diagnostics, runs, and worker states. It is not for completion polling and exposes bounded owner-scoped state without full task instructions or worker prompts.
 
 The bottom widget shows active work only. Completed, failed, aborted, and interactive ready workers disappear immediately. Inline work shows its current response in the live tool output while it blocks.
 

package/extension/contract.ts

@@ -41,11 +41,11 @@ You are the parent orchestrator and own the task end to end.
 - Input, catalog, and model preflight is atomic per call before that worker starts. Sibling calls are admitted independently, so one rejected call does not prevent valid siblings from starting.
 - Pi Orchestrate treats a successfully admitted sole \`orchestrate\` call or pure sibling group as async. Pi executes native sibling tools concurrently. A pure group yields the parent turn, delivers each result as it settles, and starts synthesis only after the whole group settles. Mixing \`orchestrate\` with another tool makes it inline and blocking. \`interactive_send\` is asynchronous only as the sole tool call in its assistant message.
 - Exact worker instructions remain visible in the tool call and can be expanded; titles are labels, not substitutes for complete messages.
-- After the full current wave has been dispatched, yield the parent turn once its admissions have resolved; a rejected sibling does not block yielding. Worker responses arrive individually as each worker settles, and the final response starts parent synthesis. Do not poll \`orchestration_status\` or use it as a normal completion mechanism.
+- After the full current wave has been dispatched, yield the parent turn once its admissions have resolved; a rejected sibling does not block yielding. Worker responses arrive individually as each worker settles, and the final response starts parent synthesis. Do not poll \`worker_status\` or use it as a normal completion mechanism.
 - As results expose more useful independent scopes or materially distinct perspectives, enumerate and dispatch another full parallel wave before yielding. Continue adaptive full waves until the whole task is complete.
 - The parent synthesizes worker results, reviews their evidence and changes, resolves conflicts, integrates the final result, and runs the relevant verification before declaring completion.
 - Prefer one-shot workers. Use \`interactive_send\` only for follow-up work on an owned lifecycle interactive worker whose status is ready, and \`interactive_close\` only when that ready interactive worker is finished. Never use either tool for one-shot or completed workers because one-shot sessions terminate automatically. Use \`worker_abort\` only when active work must stop.
-- The public tools are \`orchestrate\`, \`orchestration_status\`, \`interactive_send\`, \`worker_abort\`, and \`interactive_close\`.
+- The public tools are \`orchestrate\`, \`worker_status\`, \`interactive_send\`, \`worker_abort\`, and \`interactive_close\`.
 
 ### Trusted worker catalog
 

package/extension/tools.ts

@@ -175,17 +175,17 @@ export function registerOrchestrationTools(
   });
 
   pi.registerTool({
-    name: "orchestration_status",
-    label: "Orchestration Status",
+    name: "worker_status",
+    label: "Worker Status",
     description:
       "Diagnostics and recovery only: inspect trusted catalog entries, catalog diagnostics, and this session's runtime state. Never poll for completion.",
-    promptSnippet: "Inspect owned orchestration state for diagnostics or recovery",
+    promptSnippet: "Inspect owned worker state for diagnostics or recovery",
     promptGuidelines: [
-      "Use orchestration_status only for diagnostics or recovery; never poll it for completion.",
+      "Use worker_status only for diagnostics or recovery; never poll it for completion.",
     ],
     parameters: statusSchema,
     renderCall(_args, theme) {
-      return new Text(theme.fg("toolTitle", theme.bold("orchestration_status")), 0, 0);
+      return new Text(theme.fg("toolTitle", theme.bold("worker_status")), 0, 0);
     },
     renderResult(result, { isPartial }, theme) {
       return renderDiagnosticsResult(result, isPartial, theme);
@@ -204,7 +204,7 @@ export function registerOrchestrationTools(
         content: [
           {
             type: "text",
-            text: readableDetails("Orchestration diagnostics and recovery snapshot.", readable),
+            text: readableDetails("Worker diagnostics and recovery snapshot.", readable),
           },
         ],
         details: readable,
@@ -837,7 +837,7 @@ function formatElapsed(milliseconds: number): string {
 }
 
 function renderDiagnosticsResult(result: AgentToolResult<unknown>, isPartial: boolean, theme: Theme): Text {
-  if (isPartial) return new Text(theme.fg("muted", "Reading orchestration diagnostics…"), 0, 0);
+  if (isPartial) return new Text(theme.fg("muted", "Reading worker diagnostics…"), 0, 0);
   const details = result.details;
   if (isRecord(details) && isRecord(details.state) && Array.isArray(details.state.workers)) {
     const workers = details.state.workers.filter(isRecord);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zachwill/pi-orchestrate",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "type": "module",
   "description": "Concurrent worker orchestration for Pi",
   "files": ["extension/", "examples/", "README.md", "LICENSE"],