Skip to content

impl(aggregator): /quota covers 8 SaaS services; the tracked estate is dozens - list the uninstrumented with reasons #1172

Open

Description

@dezren39

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

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

  1. added
    kind/featureNew feature or capability request
    app/pm-stackpm-stack (Pad/Grist) in developing-today/code
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    source/humanFiled directly by a human
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/normalOrdinary priority (the default)
    effort/sSmall: expected under 2 hours of work
    on Oct 28, 2026
  4. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    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 criteria section; both are now supplied (the body's own Acceptance text is restated under the standard heading, original body preserved verbatim above it).

  5. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Picked up queue task 2461 for current-main triage; will verify coverage and existing ownership before routing.

  6. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  7. 41 remaining items

  8. added
    status/parkedDeliberately paused with a recorded resume condition
    on Nov 3, 2026
  9. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    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.

  10. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    Task 7663 was launched and bound to OpenCode session ses_e5e5c5e8dd2ffeBLgginCzmvfW by opencode-claimant. It is executing as repo-worker-code and has instructions to verify the current parked issue state and route based on fresh evidence.

  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    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 current main at 7a8500417188465deea72339db81fcf1a92c8448; pm-stack/aggregator/src/saas-extract.ts and src/render.ts still lack the tracker-derived uninstrumented registry/collapsed /quota section. 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 /quota section, 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-backed no account / console-only / unchecked / intentionally skipped state and date as applicable.

    Blockers and ordering: PR #3939 is still OPEN, assigned to the issue assignee, and targets main; its head is 96c3a3a467019aa296190dcd515ad413ee13b6fc. The PR API currently reports mergeable_state=dirty (base SHA 0fedbfc0f37c3ca9f57f09195ca0cf6b87ff2198, while current main is 7a850041...). 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.json omits uninstrumentedServices, 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. The parked labels were not treated as evidence that the issue is handled.

  12. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    Partial verification — staying open (2026-11-07 done-task-only audit, tracking: #7016).

    Queue task(s) [7663, 2461, 4894] 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 11549.

  13. developing-today commented on Nov 8, 2026

    @developing-today
    Contributor

    state: triaged
    queue: repo-health-code-pilot
    task: 11912 (triage)
    by: lane code-k (worker repo-worker-code)
    at: 2026-11-08

    Verdict: #1172 is REAL and CURRENT; its remainder is exactly PR #3939, still unfinished. Fresh reads this shift:

    Converted: follow-up task 12652 (pr_shepherd, dedupe repo-health:v1:pr:developing-today/code:pr:3939 — the validator requires the pr family for pr_shepherd kind) is enqueued to refresh PR #3939 against main, fix/disposition both Codex P2s, verify the acceptance list, and merge it — no competing PR. Task 11912 completes as triaged. Nothing needs Drew.

  14. added
    queue/claimedQueue worker lifecycle state
    queue/queuedHas a queued task in the Supabase agent queue
    status/triagedTriaged and routed (see agent note)
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workkind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)queue/queuedHas a queued task in the Supabase agent queuesource/humanFiled directly by a humanstatus/triagedTriaged and routed (see agent note)task/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions