Repository navigation
fix(aggregator): Meta pool showed 100% + false 'charge-past-plan disabled' note — corrected at the quota-view source #895
Description
Follow-up to #890 (slice 1, PR #892). The aggregator page/plumbing were correct; the Meta pool's DATA was stale and carried a claim the 2026-10-25 Meta console read disproved.
Where the stale text lived: the current read in the stewardship quota view (visibility/quota-view.md, section 'Meta Model API' → 'Usage / dates'), which src/quota-extract.ts (extractMeta) reads. That text said the weekly quota was 'burned to empty' and that Drew had 'disabled the charge-past-the-plan path' — the extractor's burned-branch then pinned the pool at 100% and attached its canned note ('the wall errors rather than bills') to /api/quota.json.
What the console read verified (dev.meta.ai, 2026-10-25 09:38 CDT): weekly limit was 85% used, resets Sun 2026-10-25 19:00 CDT — the weekly window never ran out; the morning's wall was the plan's SHORT window. There is no charge-past-plan disable on the account (no such toggle exists; the only spend control is a $0.01 email alert) — when a window ends, usage rolls to PAYG and bills. PAYG Oct 19–25: $23.92 accrued / $23.91 collected, nothing outstanding. (Correction also recorded in provider-quota-registry.md's billing-incidents section and MEMORY.md.)
Fix (source only, no aggregator code change): the quota view's Meta current read now states the console-verified facts above, preserving the dated history (46% at 03:20 CDT; the two charges) with the mechanism corrected. Collector re-run via fleet-feed-collector.service and pushed to the laptop.
Verified live on the laptop: /api/quota.json shows exactly ONE Meta pool — weekly 85/100, percent 85, resetsAt 2026-10-25T19:00:00-05:00, state 'near', false note gone; all 10 other pools unchanged. /quota HTML renders the Meta card at 85% with zero occurrences of the old 'Burned to empty' text.
Note: the extractor's normal percent path carries no pool note, so the Meta pool now renders without a note rather than with a corrected one — adding a note string would be a code change, out of scope for this data fix; the corrected facts live in the quota view's current read.
Acceptance criteria
- The stewardship quota view's Meta current read states the console-verified facts (weekly window 85% used at the 2026-10-25 read, resets Sun 2026-10-25 19:00 CDT, no charge-past-plan disable exists, PAYG rolls over and bills) with the dated history preserved.
- After a collector re-run,
/api/quota.jsonshows exactly one Meta pool at the corrected percent with the false 'charge-past-plan disabled' / 'wall errors rather than bills' note gone, and all other pools unchanged. - The
/quotapage renders the Meta card from the corrected data with zero occurrences of the stale 'burned to empty' text.
Activity
developing-today commentedon Oct 25, 2026
CODE-141
dezren39 commentedon Oct 26, 2026
Intake review
Fleet monitor intake pass (2026-10-25 run). Acceptance criteria appended to the body this pass (original body preserved verbatim above it).
Looks already solved — NOT closed by the monitor: The body itself reports the fix completed and verified live on the laptop (
/api/quota.jsonshowing the Meta pool at 85% with the false note gone, all other pools unchanged;/quotarendering without the stale text). This was a data fix at the quota-view source, not a merged PR in this repo, so there is no fixes-reference for the monitor to close against — I'm flagging itstatus/needs-reviewinstead of closing it.Suggested next step: Whoever reviews: one fresh spot-check of
/api/quota.json(single Meta pool, corrected percent/note state) and this issue can be closed as completed, citing the body's verification. If the spot-check shows the stale text back, the extractor's source read has regressed and this reopens as a bug.Related: #890 (slice 1, PR #892 — the aggregator page/plumbing this was a follow-up to).
dezren39 commentedon Nov 1, 2026
🤖 Agent note — triage verdict: ALREADY DONE (queue task 2282, lane D, 2026-11-01T02:3xZ)
Reviewed (this issue carried
status/needs-review; the review is this note). All three acceptance criteria check out:visibility/quota-view.md, § Meta Model API → Usage / dates) now states the console-verified facts verbatim: weekly limit 85% used at 09:38 CDT 2026-10-25, the morning wall was the plan's SHORT window, "no charge-past-plan disable on the account (no such toggle exists; the only spend control is a $0.01 email alert): when a window ends, usage rolls to PAYG and bills", PAYG Oct 19–25 $23.92 accrued / $23.91 collected — with the dated history preserved (46% at 03:20 CDT; the two charges). The stale assertions ("burned to empty", a Drew-set charge-past-plan disable) survive nowhere as claims — only inside the correction narrative that refutes them. Later dated reads (2026-10-27 console read: weekly 8.83%) have since superseded the numbers, as designed for a living view./api/quota.jsonshowed exactly one Meta pool at 85/100, state 'near', the false 'wall errors rather than bills' note gone, all 10 other pools unchanged./quotapage — same live verification: Meta card at 85% with zero occurrences of the old 'Burned to empty' text.No aggregator code change was ever needed (the plumbing was correct; the data was wrong), and none is outstanding. Closing as already done.