Repository navigation
Lane scale-out: A/B queue-worker shifts for opencode, openchamber, and nix #1335
Description
Work (Drew, 2026-10-27)
The code queue has two 40-minute lane shifts (A/B) with per-lane
locks and atomic claims; the opencode, openchamber, and nix queues
are still worked by the single 2-hourly agent-queue-worker — the
evaporation factory behind #530/#495's near-deaths. Give every queue
the lane treatment:
repo-queue-worker-shift-opencode+-b(queue
repo-health-opencode-pilot, repo developing-today/opencode)repo-queue-worker-shift-openchamber+-b(repo-health-
openchamber-pilot, developing-today/openchamber)repo-queue-worker-shift-nix+-b(repo-health-nix-pilot,
dezren39/nix)
Same discipline as the code lanes: bundle ≤10, ~90-minute budget,
per-lane lock files, claim-before-work, checkpoint on claim, park
instead of waiting, verified terminal states, label sync, delivery
only when a task was worked. One shared multi-queue instruction file
parameterized by queue/repo/lane (the code instruction stays as-is).
The 2-hourly agent-queue-worker stays as the fallback sweep until
the lanes prove out; the Phase 2 evaluation notes the overlap.
Acceptance criteria
- Six new shift jobs exist (cron list) and each has completed a
first shift or gated out cleanly at an empty queue. - Tasks 1149 (lab-ops-hub: judge container crawl hosts on the full UTS-46 mapped form (#516, #526) #530) and 1157 (fix(bin): validate ANTIGRAVITY_LS_ADDRESS port strictly (#494) #495) reach terminal states under
lane discipline without another operator cap raise. - Evaporation repairs for these queues trend to zero in the
fleet monitor's daily count within a week.
Implements the lane half of #1130. Child of the pool & routing
intelligence epic. Filed by Muse (operator) 2026-10-27.
Activity
developing-today commentedon Oct 27, 2026
CODE-439
dezren39 commentedon Oct 27, 2026
Lane rebalance (2026-10-27, Drew's direction, ~1h after this issue was filed): queue depths at decision time — code 39 queued + 8 parked (67 terminal events/24h), opencode 22 queued, openchamber 17 queued, nix 4 queued + 1 claimed + 1 parked. So: code goes to FOUR lanes (shifts C and D created, same instruction/locks pattern), and nix runs ONE lane (shift B created with this issue, then disabled before its first run — the nix backlog is ~6 live tasks of small shell/script fixes; a second lane would mostly gate out). Opencode and openchamber keep two lanes each. Revisit if depths change materially; the meta-reviewer has the data to say when.
8 remaining items
dezren39 commentedon Oct 31, 2026
🤖 Agent note · picked up
dezren39 commentedon Oct 31, 2026
🤖 Agent note · blocked
openclaw cron list --allcommand cannot resolve the configured gateway authentication reference, so current job state cannot be verified from this execution path.developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 1319 (triage, blocked, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03