feat(usage-hub): v3 charges auto-matching — Plaid + Gmail alerts to services #1057

Activity

1. dezren39

   added

   meta/follow-upFollow-up spun out of earlier workFollow-up spun out of earlier work

   on Oct 27, 2026
2. developing-today commented on Oct 27, 2026

   

   developing-todayBot

   on Oct 27, 2026 – with developing.today

   Contributor

   More actions

   CODE-202
3. github-actions

   assigned

   dezren39

   on Oct 27, 2026
4. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Oct 29, 2026
5. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triaged

   • Agent: queue worker (repo-worker-code), lane C shift
   • Session / ID: queue task 2325 (triage)
   • Found via: queue claim · repo-health-code-pilot
   • Task: Triage verdict — CONFIRMED feasible, all inputs live (verified 2026-10-29):
   • Plaid: connector status = connected, 4 linked institutions; transactions-get reads an inclusive date range. The Citi gap stands exactly as filed (account campaign owns it; this work does not work around it).
   • Gmail: connector status = connected; search/read reaches receipt/card alert mail.
   • Hub side: pm-stack/aggregator already serves the /quota charges evidence strip (/api/quota.json extended with charges) and already accepts Muse-side poster feeds for external data — the matcher plugs into the daily collector flow, it does not need a new hub surface.
   • Pinned for the fix: one row per charge with source labelled (Plaid vs Gmail alert); cross-source dedupe on amount + normalized merchant + date window, Plaid as source of record on a tie; unmatched SaaS/AI-looking charges surface in the attention strip once (persisted state, never repeatedly); no balances/debt in the hub (links out, design §2.4).
   • Expectation: small_fix enqueued (dedupe repo-health:v1:fix:developing-today/code:issue:1057; packet hidden_files/packet-2325-fix.json). Issue stays open for that task.
6. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Oct 29, 2026
7. 95 remaining items

   Load more
8. developing-today

   added

   status:in-review

   and removed

   status:done

   on Oct 29, 2026
9. developing-today

   reopened this on Oct 29, 2026
10. dezren39

    added a commit that references this issue on Oct 30, 2026

    Merge pull request #2467 from developing-today/queue/2990-1057-charge…

    ...

    0ba7e6f
11. dezren39

    added

    effort/mMedium: expected under 1 day of workMedium: expected under 1 day of work

    mode/onlineFully doable remotely: design, config, code, cloudFully doable remotely: design, config, code, cloud

    on Nov 1, 2026
12. dezren39

    added a parent issue on Nov 1, 2026

    • epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047
13. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

    on Nov 3, 2026
14. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    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 30 (priority/none). 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
15. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done (closed with evidence)

    • Agent: queue worker (repo-worker-code), openchamber scheduled lane
    • Session / ID: queue task 7619
    • Found via: queue claim · repo-health-code-pilot (coverage sweep 2026-11-03)
    • Task: re-triage feat(usage-hub): v3 charges auto-matching — Plaid + Gmail alerts to services #1057 against current main and the live feed; work already complete, closing
    • Expectation: none outstanding for the issue's acceptance; the design follow-on is Design: a charge is evidence — one identity and lifecycle contract for the charges pipeline #3161, separate
    • Links: PR feat(aggregator): wire charges auto-matcher into collector + Plaid/Gmail producer (#1057) #2149 (merged 478797cd) · live /api/quota.json

    Triage verdict: DONE — closing (the issue was left open after the final done note)

    The last note here (2026-10-29T09:20Z, "done") recorded the acceptance step verified live, but the issue was never re-closed after the 2026-10-29T05:45Z reopen (timeline checked fresh — no close event after the reopen). Re-verified today, 2026-11-03:

    Implementation on main (1e3763faf4)

    • pm-stack/aggregator/src/charges-match.ts — cross-source dedupe + service matching; matched rows carry source: "Plaid" or "Gmail alert".
    • pm-stack/aggregator/src/charges-collect.ts — mergeChargeRows (auto rows first, hand-fed rows not double-counted), filterNewUnmatched (surfaced-once state).
    • pm-stack/aggregator/scripts/produce-charge-candidates.ts + confirm-charges-surfaced.ts — the producer/confirm side, since extended with staged-input mode (Split charge-candidates producer: staged inputs staged on the sandbox, producer runs on the laptop #4641) and staged-manifest period validation (aggregator(charges-producer): staged mode never validates the manifest period — a field-less manifest writes a candidates file with period {} and exits 0 #4663), so the pipeline has kept being maintained.
    • Tests: charges-match.test.ts, charges-collect.test.ts, charges-feed-gate.test.ts, charges-push.test.ts, produce-charge-candidates.test.ts.

    Live acceptance, checked this run — GET https://amd-6.raptor-pumpkinseed.ts.net/api/quota.json returns a charges array containing auto rows in the matcher's own source format, including two dated today: 2026-11-03 OpenCode $10 (Gmail alert) and 2026-11-03 Command Code $1.36 (Gmail alert), matched to service labels. No duplicate of either is present from the hand-fed set, so the no-double-count merge is holding in the published feed. Unmatched SaaS/AI items are in the attention strip (5 items, persisted-state behaviour unchanged).

    Not in scope / not touched: the Citi link gap (account campaign), balances/debt (finance tooling). Charge identity/lifecycle as a contract is a separate design tracked in #3161 — not a regression here.

    Closing as complete.
16. dezren39

    removed

    status:in-review

    on Nov 3, 2026
17. dezren39

    closed this as completedon Nov 3, 2026