aboutsummaryrefslogtreecommitdiffziptar.gz
path: root/docs/orchestrator.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/orchestrator.md')
-rw-r--r--docs/orchestrator.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/orchestrator.md b/docs/orchestrator.md
index 845c527..f878855 100644
--- a/docs/orchestrator.md
+++ b/docs/orchestrator.md
@@ -35,7 +35,7 @@ The steps they automate:
1. Pick: `wf list --runner --lane <lane>` → first id (lanes: `wf lanes`). Claim: `wf status <id> progress "worker"`. No commit of
its own: `wf merge` or any later bookkeeping commit takes TASKS.md (and the claim) along; harmless.
-2. Worktree: `<main>/.worktrees/<lane>`; if a live session or another worker uses it, `<lane>-2`, `-3`, …
+2. Worktree: `<main>/.worktrees/<lane>` (split project: under the code repo, `<code_root top>/.worktrees/<lane>`); if a live session or another worker uses it, `<lane>-2`, `-3`, …
(live interactive sessions: `~/.claude/sessions/*.json` field `cwd`). Branch `<lane>/<id>`.
3. Spawn: Agent tool, `subagent_type: wf-worker`, `model: <task Model, none = opus>`, background, no worktree isolation
(it blocks `wf merge` on the main checkout). Prompt:
@@ -150,3 +150,8 @@ TASKS.md, the log and the batch summaries.
Safe to clear only with no background worker running. Tested (2026-10-05): `/clear` leaves a background
subagent alive and its hand-back + completion notice reach the new context, but SIGKILLs its running Bash
command (exit 137): a worker mid-test or mid-commit loses that step and reports a false failure or half state.
+
+## Split projects
+`code_root` = another git repo: worktrees and branches live in the code repo, `wf start` makes them (with `.wf-home`
+pointing at the private project). `wf orch post` checks the code repo. A done worker whose push (`push` key) failed
+leaves `.wf/push-failed`: the lane stops (`push-failed`); fix the push, delete the marker, continue.