Skip to content

ready-for-agent: surface per-issue dispatch state on the item view (residual of #1203) #4969

Open

Description

@dezren39

Residual of #1203 after PR #3311 merged (8ee2e1c).

What landed

pm-stack/aggregator/src/sources/ready-for-agent.ts now reads the harness live and exports dispatchStateFor(state, projectPath, issueNumber) — the work item's real state, or the explicit "not picked up". The harness facet (backend readiness, repository settings, work-item counts, GraphQL errors) is on /health and /api/health, and a failed harness read degrades health rather than hiding.

What is still not met

Acceptance item 3 of #1203 has two halves. The second half — "harness status appears on /health" — is met. The first half — "An issue labelled ready-for-agent shows its real dispatch state or an explicit 'not picked up'" — is not wired to any rendered surface: dispatchStateFor() has no production caller, and src/derive.ts:21 still counts the ready-for-agent label itself as implementing, so a labelled-but-undispatched issue still claims dispatch it never got.

Scope

  • Give the aggregator a place to resolve RFA state for the issues it renders (the rfa facet reachable from the item/board build path, cached as it already is).
  • Render the per-issue dispatch state on the item page and carry it in the item's JSON twin — real work-item state, or the literal "not picked up"; never inferred from the label.
  • Stop derive.ts's IMPLEMENTING_LABELS from treating the bare label as dispatch proof, or label it explicitly as an inference next to the real state.

Acceptance

  • An item page for an issue labelled ready-for-agent shows the harness's real work-item state, or not picked up when the harness has no work item for it.
  • The item's JSON twin carries the same dispatch state with its provenance.
  • A test covers both the picked-up and not-picked-up cases (fixture state, no live harness needed).
  • The label alone no longer reads as "implementing" without the dispatch state beside it.

Context: #1203, #1184, PR #3311.

Activity

  1. added
    kind/featureNew feature or capability request
    priority/normalOrdinary priority (the default)
    effort/sSmall: expected under 2 hours of work
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Nov 3, 2026
  2. added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  3. 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 8108 (small_fix, queued, priority 40) 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

  4. 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
  5. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  6. 33 remaining items

  7. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  8. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  10. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  11. 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 Nov 4, 2026
  12. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  13. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · bound

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

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor
    • Session / ID: task 8108 (repo-fleet-monitor run 2026-11-05T15:45:48Z)
    • Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
    • Task: Claim evaporated: task 8108 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
    • Expectation: The next lane claim picks task 8108 up from the queued state and posts a fresh pickup note.
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/sSmall: expected under 2 hours of workkind/featureNew feature or capability requestpriority/normalOrdinary priority (the default)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/needs-triageNot yet triaged; needs a first lookstatus/parkedDeliberately paused with a recorded resume conditiontask/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