@zachwill/pi-orchestrate 0.4.0 → 0.4.1

package/README.md

@@ -65,11 +65,12 @@ Workers, runs, and queued delivery survive extension reloads and session switche
 
 Pi Orchestrate injects the authoritative orchestration contract and trusted catalog into the parent system prompt. The parent remains responsible for the task end to end:
 
-1. Keep trivial or tightly coupled work in the parent session.
-2. Give every worker a complete brief: objective, scope and paths, forbidden actions, context, constraints, success criteria, checks, and expected output.
+1. Keep trivial or tightly coupled work in the parent. Divide broad work into bounded, independent scopes and dispatch all currently independent scopes in parallel.
+2. Give every worker a thorough, self-contained brief with the objective, paths and scope, context, success criteria, and expected output. State forbidden actions explicitly.
 3. Dispatch independent scopes together, then yield after asynchronous acceptance.
-4. Review evidence and changes, resolve conflicts, integrate deliberately, and verify the result.
-5. Produce the final answer from the parent session.
+4. As results expose new independent work, dispatch another parallel wave and continue until the whole task is complete.
+5. Review evidence and changes, resolve conflicts, integrate deliberately, and verify the result.
+6. Produce the final answer from the parent session.
 
 Workers provide bounded evidence or changes. They do not replace parent judgment.
 

package/extension/contract.ts

@@ -29,14 +29,14 @@ function buildContract(catalog: WorkerCatalog): string {
 
 You are the parent orchestrator and own the task end to end.
 
-- Keep trivial or tightly coupled work in the parent. Use as many useful workers as independent scopes justify.
+- Keep trivial or tightly coupled work in the parent. Divide broad work into bounded, independent scopes and dispatch all currently independent scopes in parallel.
 - Delegate each independent scope with its own \`orchestrate\` call using \`{ worker, title, instructions }\`. Emit sibling \`orchestrate\` calls in one assistant message so Pi executes them concurrently.
-- Give every worker a full brief: objective; paths/scope; forbidden actions; context; constraints; observable success; checks; expected output.
+- Give every worker a thorough, self-contained brief with the objective, paths and scope, context, success criteria, and expected output. State forbidden actions explicitly.
 - 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.
 - A sole \`orchestrate\` call or a pure group of sibling \`orchestrate\` calls runs asynchronously. Pi accepts a pure group concurrently, 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. \`worker_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 an accepted async run, yield the parent turn. Worker responses arrive individually as each worker settles, and the final response starts parent synthesis. Do not duplicate delegated work, poll \`orchestration_status\`, or use it as a normal completion mechanism.
-- The active-work widget shows only workers currently starting, running, or stopping. Inline worker responses appear progressively in live tool output.
+- As results expose new independent work, dispatch another parallel wave. Continue 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 \`worker_send\` for follow-up work on a ready reusable worker, \`worker_close\` when that ready worker is finished, and \`worker_abort\` only when active work must stop.
 - The public tools are \`orchestrate\`, \`orchestration_status\`, \`worker_send\`, \`worker_abort\`, and \`worker_close\`.

package/package.json

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