Skip to content

rollout(fleet): OpenCode-half pilot on the code queue + extension to opencode/openchamber/nix (OpenCode-half step 5) #1658

Open

Description

@dezren39

Part of the OpenCode-half redesign (design: files/opencode-half-redesign-2026-10-28.md in the keep-the-four-repos-healthy goal workspace; tracking: #1425). Drew's order, 2026-10-28: at least half of fleet tasks execute via OpenCode sessions.

Scope

Rollout sequencing once the pieces land (lane assignment, executor mode, keeper coverage, lane-share measurement):

  1. Pilot: enable the split on the code queue only (lanes A–D), concurrency cap 4 queue-spawned sessions, for one week.
  2. Pilot review against the exit criteria: rolling 7-day executed share ≥50%; zero evaporated claims attributable to the split; no rise in packet-defect or verification-failure rates attributable to session execution; miss reasons understood (a chronic saturated or quota share is a capacity finding, reported as itself).
  3. Extension: enable for the opencode, openchamber, and nix queues (their lanes share lane-shift-instruction.md, so the instruction change is written once) with the cap revisited against observed laptop load and pool headroom — noting the Go plan lapses (Personal Nov 2, Lab Nov 6) shrink workhorse seats during this window.
  4. Record the pilot outcome and the extension decision as comments on Deployed laptop opencode config has drifted from canonical HEAD — claude-code pause (PR #1316) not in effect live #1425 and in the design doc's rollout section.

Acceptance criteria

Activity

  1. developing-today commented on Oct 28, 2026

    @developing-today
    Contributor
  2. added
    priority/highImportant and time-sensitive
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    source/humanFiled directly by a human
    area/infraInfrastructure, deployment, and operations
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 28, 2026
  3. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    Intake review

  4. dezren39 commented on Oct 31, 2026

    @dezren39
    MemberAuthor

    Status — owner order 2026-10-28, stalled, re-surfaced 2026-10-31 (supersession check vs #2132).

    Verdict of the owed supersession check, 2026-10-31:

    NOT superseded by #2132. #2132/#2153 reorganise two OpenChamber jobs; this step is the rollout sequencing for the OpenCode-half redesign itself (code-queue pilot → review against exit criteria → extension to the opencode/openchamber/nix queues) and depends on steps 2–4 (#1655 executor mode, #1656 binding-aware supervision, #1657 lane-share measurement) landing first. The conductor work neither sequences nor gates it.

    Queue state, verified by direct read 2026-10-31: live triage task 2626 (repo-health-code-pilot, queued, priority 70, attempts 0/3). No duplicate packet enqueued. Triage should treat the #1655–#1657 landing state as this step's gate, exactly as the issue body scopes it.

  5. 5 remaining items

  6. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    work/assignedQueue worker lifecycle state
    on Nov 3, 2026
  7. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    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 7246 (triage, queued, 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

  8. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  10. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Triage verdict — NOT done as specified; still live, gated (task 7246)

    Re-verified fresh on 2026-11-03 (~23:10Z), superseding the packet's "believed DONE" claim and updating the task 2626 triage (2026-11-03T00:45Z):

    What is genuinely live (the packet's kernel of truth):

    • Lane assignment + OpenCode execution run on the code queue today: this very shift lane-assigned task 6638, task 4876, and task 8500 to opencode (task 4876's ledger row shows executed_lane: opencode with a bound session), and the laptop claimant launches the bound sessions.
    • All four queues exist and process work (health 2026-11-03 ~23:00Z: code 316 queued / 3764 done; opencode 46 queued / 607 done; openchamber 18 queued / 665 done; nix 0 queued / 346 done), and per the worker instruction §11 the other queues' lane shifts run the shared lane-shift instruction.

    Why the acceptance criteria are NOT met — do not close:

    Routing: no follow-up packet enqueued from this triage — the rollout is effort/l and gated, exactly as task 2626 routed it. Resume condition unchanged: when #1656 and #1657 are both CLOSED and a live tracking home for the pilot review is confirmed, enqueue the rollout implementation task and start the one-week code-queue pilot clock. This issue stays open.

    🤖 Agent note · done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure, deployment, and operationseffort/lLarge: multi-day or open-ended; expect staged check-inskind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedmeta/follow-upFollow-up spun out of earlier workpriority/highImportant and time-sensitivesource/humanFiled directly by a humantask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions