Skip to content

Convert issue-sweep-rotating into the Make-role triage feeder (enqueue-only, no direct execution) #2156

Open

Description

@dezren39

Implementation follow-on from the #2138 triage (queue task 3168, 2026-10-29). Parent decision: #2138 (CONVERT to feeder — decision + evidence recorded there); fleet epic: #2055; roles: #2131.

Convert issue-sweep-rotating from a direct executor into the Make role's triage feeder for developing-today/opencode, developing-today/openchamber, and dezren39/nix:

  1. New body, feeder-only. Per run (hourly rotation, one repo per run, up to 5 items — cadence and volume unchanged): pick the repo's highest-value unqueued open issues, triage each (reproduction/evidence notes on the issue), and enqueue a triage packet into that repo's pilot queue (repo-health-opencode-pilot / repo-health-openchamber-pilot / repo-health-nix-pilot) with queue/queued set on the issue in the same pass. The feeder never fixes, never opens PRs, never self-assigns — execution belongs to the queue lanes and the conductor alone. The one exception is clerical: closing an issue as already-fixed/duplicate with evidence, which is triage, not execution.
  2. Dedupe before enqueue: check the repo queue's live tasks and the issue's labels (the fleet-monitor safety net pattern); an issue with a live task or a work/* label is skipped and logged, never double-fed. (Today's collision — sweep fixing opencode#831 while queue task 3137 held it — is the failure this step exists to prevent.)
  3. Backlog files stay: the feeder keeps the per-repo backlog files (backlog-devtoday-opencode.md etc.) as its triage record; sweep.log lines name the enqueued task ids.
  4. Retire-revisit trigger (from the Issue-sweep-rotating endgame: convert to a Make-role triage feeder, or retire #2138 decision): if two consecutive weekly token-usage reviews show the feeder's enqueued packets substantially duplicating producer coverage (pinned creators + pr-diff-review for those repos), or the conductor + producers demonstrably keep all three backlogs triaged without it, file the retirement as a fresh decision on Issue-sweep-rotating endgame: convert to a Make-role triage feeder, or retire #2138 — do not retire by drift.

Acceptance:

Activity

  1. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  2. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

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

    @dezren39
    MemberAuthor

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), Lane E
    • Session / ID: queue task 3180 (triage), lane E shift 2026-10-29 23:29 CDT
    • Found via: queue claim
    • Task: Triage verdict for the Issue-sweep-rotating endgame: convert to a Make-role triage feeder, or retire #2138 CONVERT follow-on: confirm the feeder conversion spec against live state, enqueue the implementation.
    • Expectation: done — verdict below; implementation packet enqueued (see Links).

    Verdict: CONFIRMED. The conversion spec in this issue is accurate against live state, and the implementation is enqueued.

    Evidence (all read fresh this run):

    • Live job issue-sweep-rotating (saved definition viewed directly): enabled, interval 1h, timeout 5400s, owner goal:keep-the-four-repos-healthy. Cadence/volume already match the spec (hourly, one repo per run, up to 5 items) — no cadence change is in scope.
    • The live body is still a direct executor, so the conversion is real work, not a relabel: its step 1 is FIX (reproduce → branch sweep/<issue>-<name> → PR → standing merge directive), with PR adoption/combining sections. None of that survives a feeder-only body.
    • Target queues exist and are live (repo-queue.py health): repo-health-opencode-pilot (queued 2, done 228), repo-health-openchamber-pilot (queued 3, done 226), repo-health-nix-pilot (queued 0, done 190). The names match this issue and the sweep body's own queue map.
    • Dedupe rule is implementable as specified: the feeder checks the target queue's live tasks plus the issue's labels (work/* or a live task → skip and log). That is the fleet-monitor safety-net pattern, and it is the step that prevents another opencode#831 / task 3137 double-booking.
    • One delta the implementation must settle: this issue says "hourly rotation", but the live body picks its repo at random (shuf 1-3). The implementation packet instructs the rewrite to use a deterministic rotation per this issue's wording and to say so in its run evidence.
    • Scope exclusions confirmed: no sweep rewrite in this triage task, no cadence/volume change, no retirement (the revisit trigger in item 4 is carried into the implementation packet verbatim).

    Enqueued: implementation packet in queue repo-health-code-pilot, dedupe_key repo-health:v1:fix:developing-today/code:issue:2156, created 2026-10-30T04:44:02Z, flagged live-fleet-change (risk.flags), carrying this issue's acceptance criteria verbatim (feeder-only body read back after update; 3 evidenced feeder runs, one per repo, task ids in sweep.log, zero feeder PRs; #2131 roster update; first cost-per-item report on #2138; #2055 linked). Packet file: goal hidden_files/packet-2156-impl.json. This issue now carries queue/queued for that implementation task; removing work/assigned, queue/claimed, status/in-progress.

  5. added
    queue/queuedHas a queued task in the Supabase agent queue
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 30, 2026
  6. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  7. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

  8. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Oct 30, 2026
  9. dezren39 commented on Oct 31, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

    • Agent: queue worker (repo-worker-code), lane B shift
    • Session / ID: queue task 3808 (resume claim)
    • Found via: queue claim — resumed at the recorded park condition, did not redo the conversion
    • Evidence check (2026-10-31T00:55Z): The conversion itself was already done and verified by the prior claim (feeder-only body rewritten and read back; Fleet roles: Make / Do / Tend — Tend owns the micro (keep everything moving) and the macro (alignment with projects, roadmaps, priorities) #2131 roster note posted). Of the park conditions:
      • 3 hourly feeder runs — occurred. 17:24 CDT run (opencode): fed 3 triage packets to repo-health-opencode-pilot (tasks 4017, 4019, 4020), labels verified — feeder behaviour as designed. 18:24 CDT run (openchamber): fed 0, correctly deduped three issues to already-completed Oct-28 triage tasks; that run also caught and corrected a fabricated enqueue result in its own tool delivery (label removed, correction notes posted). 19:24 CDT run: succeeded, but its run record carries no result summary, so its behaviour is not verifiable from the record — noted as an evidence gap, not a failure.
      • First weekly-review cost-per-item report on Issue-sweep-rotating endgame: convert to a Make-role triage feeder, or retire #2138 — not yet due (weekly cadence; conversion landed 2026-10-30).
    • Expectation: Task 3808 stays parked until the weekly-review report lands on Issue-sweep-rotating endgame: convert to a Make-role triage feeder, or retire #2138; then complete it with both evidence halves cited. No cron definition was changed by this claim.
  10. added
    user/reviewNeeds a user-look: Muse reviews first and handles what it can
    on Nov 3, 2026
  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · escalated

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: repo-fleet-monitor run 2026-11-03 04:12 CST
    • Found via: monitor reconciliation (in-progress tracker, protocol §6)
    • Task: ESCALATION — this item carries a work/* assignment label but shows no activity (comments, commits, CI) for ~82h against an effort/s expectation of 2h (past the 2× deadline with no activity). It is probably stuck. Holder: please checkpoint, park, or hand off; otherwise the fleet monitor recommends requeueing this item so the pool stays truthful.
    • Expectation: holder responds with a checkpoint/handoff, or the item is requeued on a later monitor pass.
  12. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  13. 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 3808 (small_fix, parked, priority 30) 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

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

Metadata

Metadata

Assignees

Labels

queue/parkedQueue task is parked (waiting on CI, time, or an event)queue/queuedHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobstatus/parkedDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemuser/reviewNeeds a user-look: Muse reviews first and handles what it canwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions