Repository navigation
aggregator: forecast per-pool quota exhaustion intervals #3983
Description
Parent chain: #1184 → #1256 → this issue. GitHub currently caps #1184 at 100 direct sub-issues and rejects additional links (REST 422), so implementation slices are nested under #1256, already a native child of #1184; no existing parent links were changed.
Design context: #1256; doc/2026-11-01T21-07-00Z_design_pm-stack_forecasting/2026-11-01T21-07-00Z_design_pm-stack_forecasting.md (§2). Depends on the measured live-rate contract in #3933; do not duplicate its quota extraction or near-limit/wall threshold rules.
Goal
Add a time-to-exhaustion interval that composes live per-pool usage, observed rate, and reset time, complementing (not replacing) the existing point-pace and quota-wall derivations.
Acceptance criteria
- Consume the live quota contract from aggregator: finish quota throughput data + record the design contract (#851) #3933: pool identity, remaining/limit, reset time, measured timestamped burn, source age/coverage, and explicit missing/estimated markers.
- Where enough fresh rate observations exist, return an exhaustion interval and whether its P50/P80 falls before or after reset; expose the rate window and source.
- If rate, remaining amount, or reset is missing/stale, or there is no measured burn history, return an explicit unknown state rather than “safe” or a fabricated date.
- Reuse aggregator: finish quota throughput data + record the design contract (#851) #3933 existing near-limit/wall rules; do not add another threshold/attention path. Queued issues are not converted into token demand; any scheduled-work scenario must be separately labelled and use attributable measured inputs.
- Tests cover reset boundaries, stale/missing rates, zero rate, limit already reached, and a measured exhaustion-before-reset case.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeMedium: expected under 1 day of workNew feature or capability requestOrdinary priority (the default)Has a queued task in the Supabase agent queueFiled or worked by the queue/worker pilotNot yet triaged; needs a first lookQueue packet kind: verify, reproduce, and route this item
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
34 remaining items
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: parked
queue: repo-health-code-pilot
task: 8750 (small_fix, worker repo-worker-code, lane 262eb403-3347-4a7c-ba6b-e7bc263ca853), attempt 6
by: openchamber-scheduled-lane
at: 2026-11-04T01:45:14Z
Parked for 30 minutes on dependency #3933. GitHub main confirms the required contract is not finished: collect-fleet-feed.ts still emits quota.burn: [] and src/model.ts has only the optional burn-related types; no matching open PR exists for #3933 or #3983. Resume after #3933's finished contract lands, then verify pool identity, remaining/limit, reset, timestamped measured burn, source age/coverage, and missing/estimated markers. No branch or worktree was created because the gate failed. Labels synced: queue/parked + status/parked; work/assigned retained; claimed/in-progress labels removed.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off