From d678967fcf9489fd943bb17c7baf3c59f930d821 Mon Sep 17 00:00:00 2001 From: godosa Date: Wed, 7 Oct 2026 17:01:53 +0200 Subject: orch: needs-owner parks task After: its human task, lane keeps picking Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01JEAjUkQRrCYX5MZhWxdtj2 --- docs/manual.md | 2 +- docs/orchestrator.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/manual.md b/docs/manual.md index 3d50ade..101f731 100644 --- a/docs/manual.md +++ b/docs/manual.md @@ -122,7 +122,7 @@ switches them to worktree mode (one branch per task, `wf finish` merges it). One After `/clear`, type `/wf-orchestrate` (`go` = start the proposed run without asking, `batch N` = prepare an unattended batch). The orchestrator holds no lane and never reads code. It spawns one fresh `wf-worker` per task (`wf orch pick` / `wf orch post`), one per lane in -parallel, on the task's model, and parks a task that ends awaiting, handback or red post-check +parallel, on the task's model, and parks a task that ends awaiting, needs-owner (waits `After:` a Needs-human task), handback or red post-check (blocked / `Sessions: owner`, alert) while its lane keeps going. Use it when the backlog is runner-ready (section 3) and you want to steer. ### Overnight: `/wf-pilot` diff --git a/docs/orchestrator.md b/docs/orchestrator.md index f3e1432..6887f15 100644 --- a/docs/orchestrator.md +++ b/docs/orchestrator.md @@ -63,7 +63,7 @@ The steps they automate: | model raised by the worker | continue; next pick spawns it on the new model | | sliced | next task in the lane | | done+gate-red (async gate red, earlier task's break) | post-check as done; next pick in the lane = the P0 fix (no Done/Model → add them first); never stop the lane | - | awaiting / handback / post-check red | `wf orch post` parks only that task (blocked on its a-id, else `Sessions: owner` + note; handback clears the claim), prints `alert: …`; tell the owner, the lane keeps picking (never wait on the owner while tasks are pickable) | + | awaiting / needs-owner / handback / post-check red | `wf orch post` parks only that task (needs-owner: `After:` its Needs-human h-task, pickable again after the owner's `wf done`; awaiting: blocked on its a-id, else `Sessions: owner` + note; handback clears the claim), prints `alert: …`; tell the owner, the lane keeps picking (never wait on the owner while tasks are pickable) | | wip (after a wrap-up) | stop the lane; reslice or rerun later | | crashed / killed (no report) | one fresh worker, prompt plus `Recovery: ` (it inspects git status, git log master..HEAD, `git diff -- TASKS.md` — often just the claim — and `wf show `), then stop | 7. Log one line per task to `out/wf-orch.log` (git-ignored): time, lane, model, id, outcome, commit, duration. -- cgit