3dd3cc9f68
* Clarify Orca orchestration tool boundary and sidebar lineage Add a "Tool Boundary" section to the orchestration skill, requiring explicit Orca runtime state instead of generic subagent tools or chat-only parallel workers. Also add tests to verify the tool boundary and clarify sidebar lineage for same-worktree workers. * Clarify worktree lineage guidance and parent-child boundaries Update orchestration guidance and tests to clarify when to use child versus top-level worktree lineages, and when to prefer same-worktree workers. * Require stating the desired Orca lineage before creating a worktree from an active feature branch. * Limit child worktrees to conceptually stacked or dependent tasks. * Prefer same-worktree workers unless isolated checkouts are explicitly needed and do not require uncommitted changes. |
||
|---|---|---|
| .. | ||
| computer-use | ||
| linear-tickets | ||
| orca-cli | ||
| orca-emulator | ||
| orca-emulator-android | ||
| orca-linear | ||
| orca-per-workspace-env | ||
| orchestration | ||