kurihada/ai-workflow-skill
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

orch: require explicit dispatch execution mode

Browse Source
This commit is contained in:
kurihada
2026-03-20 19:27:30 +08:00
parent 7840b2767f
commit 5859ff219e
43 changed files with 277 additions and 312 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+2 -2
View File
@@ -70,11 +70,11 @@ It should not be implemented as core `orch` runtime behavior because worker laun
For code tasks, execution should be isolated from the user's primary checkout.
- `orch dispatch` should create a task-attempt worktree
- `orch dispatch --execution-mode code` should create a task-attempt worktree
- the assigned worktree path should be stored in attempt metadata and inbox task payload
- the worker runtime should execute inside that worktree
- strict mode should require a committed base revision
- non-code tasks may stay on a thread-only dispatch path with no worktree, but they still require a separate worker runtime to claim the inbox thread
- `orch dispatch --execution-mode analysis` should stay on a thread-only path with no worktree, but it still requires a separate worker runtime to claim the inbox thread
See [worktree-execution.md](/home/kurihada/project/ai-workflow-skill/docs/worktree-execution.md) for the full lifecycle.