Skip to content

Standing sweep: git-hygiene-sweep job — publish reconciliation + idle build-artifact cleanup (tracking) #4604

Open

Description

@dezren39

Tracking issue for the standing git-hygiene-sweep job, filed to close acceptance box 5 of #1371. Verified live 2026-11-02 (queue task 1352): cron git-hygiene-sweep enabled, every 4h, last run 2026-11-02 15:27 CST succeeded. Instruction at hidden_files/git-hygiene-sweep-instruction.md in the fleet goal workspace. Duties: publish reconciliation (push fleet branches, PR finished queue branches, classify dirty trees, flag divergent duplicates) + idle build-artifact cleanup. #1371 closes against this tracking issue.

Acceptance criteria

Activity

  1. added
    kind/infrastructureInfrastructure / host-portability work
    source/queue-workerFiled or worked by the queue/worker pilot
    priority/normalOrdinary priority (the default)
    effort/mMedium: expected under 1 day of work
    area/infraInfrastructure, deployment, and operations
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 2, 2026
  2. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    Intake review

    Filed by queue worker lane D (task 1352 triage of #1371) as the standing tracking issue for the git-hygiene-sweep job; #1371 closed against it. Still live: the job is a standing duty, not a one-off fix, so no merged PR resolves it. Risks: a standing tracking issue can drift from the job's actual instruction file — the triage/queue lane should re-verify cadence + last-run state periodically (the sibling issue #4606 covers a similar cadence-verification pattern for pool-composition-review). Suggested approach: leave open as the tracking anchor; verify on fleet-monitor cadence checks.

    🤖 Agent note · filed

    • Agent: fleet monitor
    • Session / ID: repo-fleet-monitor run 2026-11-02 16:12 CST
    • Found via: monitor reconciliation
    • Task: Intake enrichment (§5) for this issue — acceptance criteria appended, labels normalized, this review posted.
    • Expectation: done = the acceptance criteria above; routing to a worker happens through the queue/feeder as usual.
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  4. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

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

    @dezren39
    MemberAuthor

    🤖 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/mMedium: expected under 1 day of workkind/infrastructureInfrastructure / host-portability workmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/queue-workerFiled or worked by the queue/worker pilottask/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