Repository navigation
Description
Finding
Evidence (live review 2026-10-26 22:40 CDT, laptop loopback + gh, cross-checked): /api/quota.json tonight: 10 token pools but only 8 SaaS services, while the account/SaaS trackers (/workspace/ai-subscriptions/) cover dozens of services - most with no dashboard presence at all, not even "unmeasured". The Oct 26 SaaS review: free-services-to-check.md still lists boats.cloud, quic.cloud, Backblaze B2, OVHcloud, Railway, Render, DigitalOcean, Hetzner, Heroku, GCP, AWS as unchecked. Absence from /quota reads as "not a service we have", which is wrong.
Proposal
The usage model gains an "uninstrumented" registry (from the tracker's service list): each entry renders on /quota in a collapsed section with its state (no account / console-only / unchecked / intentionally skipped + date). Instrumented services keep their cards. Registry maintained as data (saas-extract input), not render code.
Acceptance
- /quota's uninstrumented section lists at least the unchecked-services set above with states matching the tracker at merge time.
Refs: design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851, docs(dashboard): build out the Cloud program / SaaS project section (/program/cloud-program) #1128.
Acceptance criteria
- /quota gains a collapsed 'uninstrumented' section listing at least the unchecked-services set named in the body (boats.cloud, quic.cloud, Backblaze B2, OVHcloud, Railway, Render, DigitalOcean, Hetzner, Heroku, GCP, AWS) with each service's state (no account / console-only / unchecked / intentionally skipped + date) matching the tracker at merge time.
- The registry is maintained as data (saas-extract input), not render code; instrumented services keep their existing cards.
Activity
developing-today commentedon Oct 27, 2026
CODE-308
dezren39 commentedon Oct 28, 2026
Intake review
Fleet monitor intake enrichment (protocol §5) — 2026-10-28T06:27Z. This issue was filed 2026-10-27 by Drew (dezren39) from the 2026-10-26 live pm-stack review and had no
priority/*label and no standard## Acceptance criteriasection; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).kind/*(kept existing),source/human,status/needs-triage,priority/normal,effort/s,app/pm-stack(existing),meta/enriched.dezren39 commentedon Nov 1, 2026
Picked up queue task 2461 for current-main triage; will verify coverage and existing ownership before routing.
30 remaining items
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
opencode; handed off to the laptop claimant (opencode-claimant), which launches the bound session that drives task 7663 to its terminal state.dezren39 commentedon Nov 3, 2026
agent-note:v1
state: picked-up
queue: repo-health-code-pilot
task: 7663 (triage, worker repo-worker-code, lane 262eb403-3347-4a7c-ba6b-e7bc263ca853)
by: openchamber-scheduled-lane
at: 2026-11-03T21:46:30Z
Claimed for current-state triage. Fresh GitHub state confirms #1172 is OPEN and assigned to Drew; matching implementation PR #3939 (
queue/4894-1172-quota-uninstrumented) is OPEN and Drew-authored. This is active Drew-owned work, so I will not inspect/modify its branch or create a competing PR; parking this claim for 30 minutes.dezren39 commentedon Nov 3, 2026
agent-note:v1
state: parked
queue: repo-health-code-pilot
task: 7663 (triage, worker repo-worker-code, lane 262eb403-3347-4a7c-ba6b-e7bc263ca853)
by: openchamber-scheduled-lane
at: 2026-11-03T21:47:11Z
Parked for 30 minutes due active Drew-owned implementation: issue #1172 remains OPEN and assigned to Drew, and PR #3939 (
queue/4894-1172-quota-uninstrumented) is OPEN under Drew. No branch or files touched. Resume with fresh issue, PR, and ownership checks; continue only if the active owner is no longer working it.dezren39 commentedon Nov 3, 2026
Task 7663 was launched and bound to OpenCode session
ses_e5e5c5e8dd2ffeBLgginCzmvfWbyopencode-claimant. It is executing asrepo-worker-codeand has instructions to verify the current parked issue state and route based on fresh evidence.dezren39 commentedon Nov 3, 2026
Current-main triage — 2026-11-03
Verdict: still live; do not close as handled. A fresh GitHub read shows #1172 is OPEN and assigned to
dezren39. I fetched and inspected currentmainat7a8500417188465deea72339db81fcf1a92c8448;pm-stack/aggregator/src/saas-extract.tsandsrc/render.tsstill lack the tracker-derived uninstrumented registry/collapsed/quotasection. The existing instrumented cards do not satisfy this request.Scoped route: continue with the existing implementation PR #3939, not a competing PR or new queue task. Its scope matches: derive the registry from
free-services-to-check.md, show its state/check date/overage behavior/guardrails in a collapsed/quotasection, and preserve existing cards. Acceptance remains at least: boats.cloud, quic.cloud, Backblaze B2, OVHcloud, Railway, Render, DigitalOcean, Hetzner, Heroku, GCP, and AWS; each needs tracker-backedno account/console-only/unchecked/intentionally skippedstate and date as applicable.Blockers and ordering: PR #3939 is still OPEN, assigned to the issue assignee, and targets
main; its head is96c3a3a467019aa296190dcd515ad413ee13b6fc. The PR API currently reportsmergeable_state=dirty(base SHA0fedbfc0f37c3ca9f57f09195ca0cf6b87ff2198, while current main is7a850041...). Its check rollup is SUCCESS (1/1), but two unresolved P2 review threads remain: (1) escaped Markdown pipes can shift tracker columns and corrupt displayed status/guardrails; (2)/api/quota.jsonomitsuninstrumentedServices, despite the machine-first endpoint contract. Order: refresh/resolve the PR against current main, fix both findings (including JSON parity), pass the focused checks, merge, then re-check current main and close this issue only if the listed coverage is present. No unrelated refactors or other issues are in scope. Theparkedlabels were not treated as evidence that the issue is handled.