Skip to content

feat(usage-hub): v2 collectors — Modal credits (monthly read) + Bitwarden SM counts #1111

Open

Description

@dezren39

Part of epic #1047. Design: hub-v2-v3-design-2026-10-26.md §2 (in the usage-billing-hub goal files). These are the two §2.2 services from the original hub design that got no issue in the first filing pass.

  1. Modal — Starter plan, $30/mo compute credits (Drew confirmed 2026-10-22), % used UNKNOWN. No verified API meter: add Modal to the console-reads pattern at MONTHLY grain (dashboard read of credits used) until a meter route verifies; card shows measured-at + source.
  2. Bitwarden Secrets Manager — plan UNKNOWN in the tracker. bws CLI count-only read (secrets + projects count; names/values never enter the hub), weekly cadence. Also record the actual SM plan name/price into the tracker (overlaps chore(usage-hub): close master-tracker open checks (ChatGPT tier, Go exact %, Claude reset, Wispr, Bitwarden, Muse plan) #1055 item 4 — coordinate, close whichever lands second as duplicate work done).
    Acceptance: both services render dated, sourced values on /quota; snapshot records flow.

Activity

  1. developing-today commented on Oct 27, 2026

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

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  3. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done

  4. 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 29, 2026
  5. 59 remaining items

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

    @dezren39
    MemberAuthor

    agent-note:v1
    event: handed_off
    task: 6655
    lane: code-l
    execution_lane: opencode
    note: Triage task 6655 claimed by lane L and handed off to the opencode claimant, which launches the bound session to triage this issue and route follow-up packets.

  8. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    agent-note:v1 — state: handed off

    Queue task #6655 is handed to OpenCode for execution.

  9. added
    status/blockedQueue or user escalation state
    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

    Triage (2026-11-03, queue task 6655): PARTIALLY DONE; remaining slice is blocked on owner-only Bitwarden vault access.

    Keeping this issue open because the epic #1047 acceptance still requires the live cards (and the tracker overlap). It is blocked, not complete; the implementation no longer needs a separate packet.

  11. 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
    and removed on Nov 3, 2026
  12. 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 3000 (small_fix, blocked, 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

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

Metadata

Metadata

Assignees

Labels

effort/mMedium: expected under 1 day of workmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudqueue/queuedHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobstatus/blockedQueue or user escalation statetask/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