From c537f4a809a564ecdab0380bcb356018f79a6900 Mon Sep 17 00:00:00 2001 From: godosa Date: Wed, 7 Oct 2026 17:15:33 +0200 Subject: orch: lane cloud parks a stuck task (Cloud: no), keeps picking Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01JEAjUkQRrCYX5MZhWxdtj2 --- docs/orchestrator.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'docs/orchestrator.md') diff --git a/docs/orchestrator.md b/docs/orchestrator.md index 6887f15..1e216af 100644 --- a/docs/orchestrator.md +++ b/docs/orchestrator.md @@ -88,8 +88,10 @@ Virtual lane `cloud` (projects with `cloud = true`; design: cloud-lane spec §4. `: (, $… )` (state done | awaiting | handback | lost; done also `report: commit `) → `wf orch post cloud --result [--commit ]` = the worker-report path (done: archive line, branch `/` gone, `wf check`; else leftover commit of the note/claim pull left), log line, next cloud - pick. `running` (exit 4) → nothing; pull again next wake. awaiting / handback / lost → `stop lane cloud`, tell the - owner; the task is back in its local lane (handback note `Recovery: cloud attempt …`). + pick. `running` (exit 4) → nothing; pull again next wake. awaiting / handback / lost → post parks only that + task (awaiting: blocked on its a-id; handback / lost: `Cloud: no`, so the cloud lane never re-sends it; it is back + in its local lane with the note `Recovery: cloud attempt …`), prints `alert: …; lane cloud keeps picking`, tell the + owner, next cloud pick. - Fill: one `wf orch pick cloud` per free slot (up to `max_parallel`), each in its own call. - Batch (`wf batch` on a `cloud = true` project) pulls itself: the job runs `wf_res.py batch-sidecar` around `claude -p`; every 10 min while it lives (until `out/wf-batch.stop`) it runs `wf cloud pull --all` and per ended -- cgit