Skip to content

impl(aggregator): quota page shows numbers, not actions - surface expiring/cancelled-pool actions into /today + /attention #1174

New issue
New issue
Open
Open
impl(aggregator): quota page shows numbers, not actions - surface expiring/cancelled-pool actions into /today + /attention#1174
Assignees
dezren39
Labels
app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivequeue/blockedQueue or user escalation statesource/humanFiled directly by a humanstatus/blockedQueue or user escalation statetask/small-fixQueue packet kind: bounded fix with reproduction and targeted testsuser/escalatedQueue or user escalation state

Description

@dezren39
dezren39
opened on Oct 27, 2026

Finding

Evidence (live review 2026-10-26 ~22:40 CDT, laptop loopback + gh, cross-checked): The quota data contains deadlines with actions attached (e.g. OpenCode Go Personal: cancelled, paid through Nov 2 - "burn before Lab per rotation order" is written as prose in a pool note). Such actions surface nowhere actionable: /today doesn't carry them and /attention never sees them, so a burn-before-expiry window can lapse while the dashboard that knows about it stays silent.

Proposal

Pools with (a) expiry/cancellation inside 14 days, (b) walled/billing state, or (c) >85% with a reset >24h away generate attention entries via the same derivation the quota guidance uses - rendered on /quota's attention strip (exists) AND mirrored into /today objectives + /attention's orchestrator tier with the concrete action text.

Acceptance

Acceptance criteria

  • Pools with (a) expiry/cancellation inside 14 days, (b) walled/billing state, or (c) >85% used with a reset >24h away generate attention entries carrying the concrete action text.
  • Entries render on /quota's attention strip AND mirror into /today objectives + /attention's orchestrator tier.
  • Tonight's OpenCode Go Personal state (cancelled, paid through Nov 2) produces a visible action entry on /today with the Nov 2 date; entries expire automatically when the pool state clears.

Activity

  1. dezren39
    added
    kind/featureNew feature or capability request
    task/small-fixQueue packet kind: bounded fix with reproduction and targeted tests
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026

  2. developing-today commented on Oct 27, 2026

    @developing-today
    developing-todayBot
    on Oct 27, 2026 – with developing.today
    Contributor

    CODE-310

  3. github-actions
    assigned
    dezren39
    on Oct 27, 2026
  4. dezren39
    added a parent issue on Oct 27, 2026
  5. dezren39
    added
    status/needs-triageNot yet triaged; needs a first look
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/highImportant and time-sensitive
    effort/sSmall: expected under 2 hours of work
    on Oct 28, 2026

  6. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    MemberAuthor

    Intake review

    Fleet monitor intake enrichment (protocol §5) — 2026-10-28T06:26Z. This issue was filed 2026-10-27 by Drew (dezren39) from the 2026-10-26 live pm-stack review and had no priority/* label and no standard ## Acceptance criteria section; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).

    • Related: Refs in body: design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851. No merged PR explicitly references or resolves this issue. Time-sensitive: the worked example in the body is a burn-before-expiry window ending Nov 2.
    • Labels normalized: one kind/* (kept existing), source/human, status/needs-triage, priority/high, effort/s, app/pm-stack (existing), meta/enriched.
    • Still live: verified open this run; no merged PR or commit found that implements it.
    • Risks: Duplicate or non-expiring entries would train readers to ignore the strip — automatic expiry on state clear is part of the acceptance, not a nicety.
    • Suggested approach: Derive entries with the same logic the quota guidance uses, render into the existing /quota attention strip first, then mirror to /today and /attention.
  7. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    on Nov 2, 2026

  8. 55 remaining items

  9. dezren39
    added
    status/needs-triageNot yet triaged; needs a first look
    on Nov 4, 2026

  10. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: task 7213
    • Found via: monitor reconciliation
    • Task: claim-evaporated repair — the queue claim on task 7213 ended without complete/park/block, its lease expired, and the task returned to queued unclaimed while 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 to claim task 7213 posts a fresh pickup note.
  11. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    and removed
    status/needs-triageNot yet triaged; needs a first look
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 4, 2026

  12. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · state: picked-up

  13. dezren39
    added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    user/escalatedQueue or user escalation state
    and removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 4, 2026

  14. dezren39 commented on Nov 4, 2026

    @dezren39
    dezren39
    on Nov 4, 2026
    MemberAuthor

    🤖 Agent note · state: escalated

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 requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivequeue/blockedQueue or user escalation statesource/humanFiled directly by a humanstatus/blockedQueue or user escalation statetask/small-fixQueue packet kind: bounded fix with reproduction and targeted testsuser/escalatedQueue or user escalation state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions