Skip to content

impl(aggregator): queue visibility views - in-progress, blocked, recently-done as first-class cross-project lists #1160

Closed

Description

@dezren39

Finding

Drew's requirement: clearly see what's being worked on, what's blocked, what was done recently - across projects. Today: in-progress is three disagreeing sources (board lane, Project Status, session claims - see reconciled-in-progress issue); blocked lives only inside orchestration tiers (invisible while tiers are broken); recently-done has no home (board's 95 done cards are the closest, unfiltered by date and mixed with bookkeeping noise).

Proposal

One /queue page (or /today sections) with three lists, all from published data: In progress (reconciled list), Blocked (every item with blockedBy, blocker state + worker + age of block), Done recently (pool Done + merged PRs, last 7 days, bookkeeping class filtered). Each row: project/Area chip, epic parent where known, age, link to item page.

Acceptance

Acceptance criteria

  • /queue (or /today sections) renders the three first-class lists — In progress (reconciled set, impl(aggregator): one reconciled in-progress list - board lane, Project status, and session claims currently disagree #1162), Blocked (every item with blockedBy + blocker state + worker + age of block), Done recently (pool Done + merged PRs, last 7 days, bookkeeping class filtered) — restating the body's Acceptance section as the criteria section.
  • Each list's counts reconcile with its source on spot-check (an item sampled per list matches GitHub/Project state).
  • The Blocked list renders non-empty on tonight's data via a test fixture that proves rendering independent of orchestration tier health.

Activity

  1. added
    kind/featureNew feature or capability request
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    priority/normalOrdinary priority (the default)
    effort/mMedium: expected under 1 day of work
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 28, 2026
  4. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    Intake review

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  6. 26 remaining items

  7. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

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

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 7647
    • Found via: monitor reconciliation
    • Task: Claim-eviction repair: the queue task for this issue is queued and unclaimed (its previous claim's lease expired without a complete/park/block), but the issue labels still said claimed. Labels reset to the truth: queue/queued + status/needs-triage. Checkpoint stage on the task: handed_off.
    • Expectation: a queue lane re-claims the task and resumes from the checkpoint stage named in the task progress.
  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Task 7647 was launched and bound to OpenCode session ses_e5e5c633b13ffeOSAboIp3Mg4W by opencode-claimant. It is executing as repo-worker-code with instructions to verify the current issue state and reconcile the stale label/queue state before routing.

  12. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Fresh triage verdict (2026-11-03): already implemented — closing completed

    At the fresh check, #1160 was open and carried task/triage, status/needs-triage, and queue/queued (those queue/triage labels no longer reflect this claimed triage or the implemented state). No hard-stop labels were present.

    The requested work is present on current main (7a8500417188465deea72339db81fcf1a92c8448): PR #3959 merged as 5de0661d2ad4b1e1446737976226811ac7d161ba, and a fresh compare confirms that merge commit is an ancestor of main (behind_by: 0). Current pm-stack/aggregator/src/server.ts registers /queue and /api/queue.json; src/queue-view.ts derives In progress, Blocked, Done recently, and Next up. test/queue-view.test.ts covers reconciliation with orchestration absent, a non-empty blocked list with empty orchestration tiers plus Project blockers (including blocker/worker/age), seven-day done/merged-PR filtering excluding bookkeeping, and rendering all sections. PR #3959 reports its check successful.

    Disposition: no fix remains and no follow-up task is warranted; this is already handled by #3959. No blockers or ordering dependencies. I’m removing stale queue/triage labels, marking triage disposition, and closing this issue as completed.

  13. added
    status/triagedTriaged and routed (see agent note)
    and removed
    task/triageQueue packet kind: verify, reproduce, and route this item
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/mMedium: expected under 1 day of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/humanFiled directly by a humanstatus/triagedTriaged and routed (see agent note)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions