Repository navigation
aggregator: finish quota throughput data + record the design contract (#851) #3933
Description
Context
Follow-up from #851 and tracker hygiene task #1183. Slice 1 shipped the quota panel in PR #892, but its implementation issue #890 explicitly deferred throughput burn segments and token-rate history to slice 2. On current main, QuotaView has historical BurnSegment and QuotaPool has active-session/model/token and burnTokensPerMin fields, but scripts/collect-fleet-feed.ts emits burn: [] and does not populate live burnTokensPerMin; those fields are only present in fixtures. The root project-management design record also does not yet record the quota data contract, per-source refresh cadence, and wall-detection rule required by #851.
Existing related work remains distinct: #1172 tracks uninstrumented-provider coverage, #1174 tracks quota actions on /today and /attention, and #1184 is the coherence epic. This issue carries the remaining #851 throughput/design-record gap; it does not replace those follow-ups.
Acceptance criteria
- Update the project-management stack design record with the joined quota/throughput model, refresh cadence by source, and per-pool wall/near-limit rules; link this issue from the record.
- Live quota data attributes active sessions and cumulative tokens by provider/pool/model, and reports measured recent token rate where its source supports it (no fabricated estimates).
- Historical burn segments are populated from observed usage across reset windows when the source data supports them; empty/missing history is represented honestly.
/api/quota.jsonand/quotaexpose the same live data, including model-choice/headroom guidance; the OpenChamber quota picker remains the source for values it already exposes.- Targeted tests cover live mapping, reset-boundary history, and honest missing-data behavior.
Activity
developing-today commentedon Nov 3, 2026
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 40 (priority/normal). 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
6 remaining items
developing-today commentedon Nov 8, 2026
🤖 Agent note · done
origin/main, 2026-11-08):pm-stack/aggregator/scripts/collect-fleet-feed.tscomputespoolBurn(...)from live server sessions and populatespool.activeSessions. The active-session attribution acceptance is satisfied.burn: [], so historicalBurnSegment[](defined insrc/model.ts, validated insrc/feed.ts) is never populated from observed usage.burnTokensPerMinappears nowhere in the collector — the measured-rate field exists in the model, is consumed bysrc/digest.tswall projections andsrc/render.ts, and is otherwise only set in fixtures. (src/sources/live.tscurrently drops derived rates at sanitize time, aggregator(feed): isFleetFeed checks only that quota.pools is an array — burn/choices, pool entries and windows unvalidated, one malformed pool crashes /quota #2429/aggregator(feed): isQuotaPool never checks credential-row label/freshness or activeSessions — a windows-only credential row or a null session crashes renderQuota #3921/aggregator(feed): sanitizeQuotaView never checks pool-level freshness, and session tokens / freshness dates are value-blind — malformed freshness and negative counts survive the #3921 pass #4546 — measured rates must be reconciled with that path, not estimated around it.)pm-stackanddocreturns nothing; the forecasting design references issue aggregator: finish quota throughput data + record the design contract (#851) #3933 but is not the issue design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851 contract record.repo-health:v1:fix:developing-today/code:issue:3933, packet saved ashidden_files/12134-fix-packet-3933.json) — wire historical burn segments and measuredburnTokensPerMininto the collector, write the design-contract record, and cover live mapping / reset-boundary history / honest missing-data with targeted tests.dezren39 commentedon Nov 8, 2026
Partial verification — staying open (2026-11-07 done-task-only audit, tracking: #7016).
Queue task(s) [8320] were marked done, and some work did land:
No merged change closes this issue's full scope, so the done status is not treated as completion. Remainder re-queued as triage task 11684.