aboutsummaryrefslogtreecommitdiffziptar.gz
path: root/CHANGES.md
diff options
context:
space:
mode:
authorgodosa <godosa@godosa.eu>2026-10-07 20:09:02 +0200
committergodosa <godosa@godosa.eu>2026-10-07 20:09:02 +0200
commitf2135607b20931c65e88fede53014a1346fa54ee (patch)
treea32c77e07d317f9e662321934717f75f244a1bd9 /CHANGES.md
parentaedabd0983c53edea462d41a7dd7ce511f59465d (diff)
downloadworkflow-master.tar.gz
workflow-master.zip
res: queue coalesces same-lock gates on descendant commitsHEADmaster
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JEAjUkQRrCYX5MZhWxdtj2
Diffstat (limited to 'CHANGES.md')
-rw-r--r--CHANGES.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/CHANGES.md b/CHANGES.md
index a25df8b..f55a7e4 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -1,4 +1,5 @@
# Changes (newest first)
+- 2026-10-07 `wf res` queue coalesces gates: a queued locked job on commit C (`--commit REV`, default a hex word of a locked job's title, `gate 1a2b3c4`) supersedes same-lock queued jobs on ancestors of C (they end `superseded by r-N`, it keeps the earliest turn, ledger `covers`); one on an ancestor of a queued job is covered, not queued. A batch of N commits → ≤ 1 queued gate per lock. `wf res wait` follows superseded ids; a red coalesced job names the range and bisect. Gate red procedure mentions it. Projects: a gate script that greps its own log by sha should `wf res wait` the printed id (covered/superseded logs are never written).
- 2026-10-07 `wf res`: a job started from inside a live job (`by.batch`, e.g. a batch worker's gate) borrows the parent's claim (mem + cpus, lent once) when fitting, so a batch waiting on its own queued gate no longer deadlocks; a queued entry whose batch ended is dropped at prune (`r-N dropped (batch r-M gone)`), never heads the queue. Projects: nothing.
- 2026-10-07 Lane cloud: one stuck task no longer stops it: `wf orch post <id> cloud` with awaiting / handback / lost parks only that task (awaiting: park as local lanes; handback / lost: `Cloud: no` + status cleared + note, local lanes may retry with pull's Recovery note), prints `alert: …; lane cloud keeps picking`, then the next cloud pick (never the same id). Projects: nothing.
- 2026-10-07 Owner-absent default: workers never wait; owner-only step → `wf add -s human` + `wf set <id> --after <h-id>` + status clear, result `needs-owner <h-id>`. `wf orch post` parks it (After: the h-task, claim cleared, alert), lane keeps picking; owner's `wf done <h-id>` makes it pickable again. Worker def, shared CLAUDE.md, wf-orchestrate, wf-pilot, batch prompt, docs. Projects: nothing.