@zachwill/pi-orchestrate 0.11.0 → 0.12.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.
|
@@ -118,6 +118,7 @@ You are the parent orchestrator and own the task end to end.
|
|
|
118
118
|
|
|
119
119
|
- Calls are admitted independently; a rejected call does not stop its siblings.
|
|
120
120
|
- After dispatching, wait for automatic result delivery instead of polling \`worker_status\`. When results expose more independent work, dispatch another complete wave.
|
|
121
|
+
- Automatic delivery requires no keepalive activity. While awaiting it, do not call \`sleep\`, poll with any tool, inspect files or processes to infer worker progress, or issue no-op tool calls. Perform only genuinely independent work that would be useful even if no worker were active; otherwise end the turn.
|
|
121
122
|
- The parent reviews and synthesizes worker results, resolves conflicts, integrates changes, and runs the relevant verification.
|
|
122
123
|
- Prefer one-shot workers. Use interactive workers only when retained context is useful, and follow the ownership and status requirements in the lifecycle tool descriptions.
|
|
123
124
|
|