Repository navigation
design(usage-hub): managed quota-credential pattern for console-only pools #1115
Description
Part of epic #1047. Design: hub-v2-v3-design-2026-10-26.md §6. Design-first; starts after #1054 (Open Design) lands its first credential.
Generalize the Open Design tier-2 pattern into the standard managed quota-credential mechanism for console-only pools: one narrow credential per service, captured once with Drew's per-service approval, stored 0600 (file contract) or in Bitwarden, verified against the service's session endpoint at capture, expiry/refresh behavior documented per service, reader fails closed (stale card, never invented numbers).
Proof case after Open Design: Cline (dashboard behind WorkOS session) or Claude (usage page) — pick whichever session route proves stable; graduate that pool from the daily manual read to a scheduled dashboard-API read.
Acceptance: pattern documented in the provider-quota registry; one additional pool reading via managed credential with freshness on its card; manual-read fallback remains if the credential dies.
Activity
developing-today commentedon Oct 27, 2026
CODE-253
dezren39 commentedon Oct 29, 2026
🤖 Agent note · done (triage verdict: CONFIRMED, gated on prerequisite #1054 — user/owned)
user/owned— the first credential has not landed, so the pattern this issue would generalize does not exist yet. There is also nothing to generalize from in the meantime: the one adjacent shipped pattern, the Meta file-export convention (hubquota-gather-map.ts, Meta Phase 1 feat(quota-plane): Meta adapter Phase 1 — laptop-side quota exporter (subscription-quota API, 15-min file export) #1301 — a laptop producer writing alatest.jsoncontract), is a producer-export pattern, not the managed per-service credential capture design(usage-hub): managed quota-credential pattern for console-only pools #1115 specifies (capture with Drew's per-service approval, stored 0600 or in Bitwarden, verified against the service's session endpoint at capture, fail-closed reader).status/blockedto mirror the gate, matching how blocked(usage-hub): Open Design quota instrumentation — laptop sign-in, cookie capture, parser verification #1054 presents.user/owned): the Open Design laptop sign-in + cookie capture. Nothing new is being asked here — this note just records that design(usage-hub): managed quota-credential pattern for console-only pools #1115 waits on it.dezren39 commentedon Nov 3, 2026
Queue note (triaged, task 7656): re-triaged against fresh GitHub state at 2026-11-03T12:48Z. Verdict: CONFIRMED blocked — the named blocker is unchanged and still sits with Drew.
Current blocker (explicit)
blocked(usage-hub): Open Design quota instrumentation — laptop sign-in, cookie capture, parser verificationuser/owned,mode/onlinestatus/blockedThe issue's own start condition is "starts after #1054 (Open Design) lands its first credential." #1054 has not landed a first credential, and it cannot be worked by a queue worker: it needs Drew's interactive laptop sign-in and cookie capture for Open Design. That is the concrete blocker — a human action on the user/owned prerequisite, not an unclaimed engineering step here.
Why no fix path was enqueued
The design method here is explicitly generalize the Open Design tier-2 pattern. Generalizing requires the proof case to exist first: the pattern's value is the verified session-endpoint capture and the documented expiry behaviour, both of which are derived from #1054's actual credential. Writing the pattern spec before that lands would be speculative and would have to be rewritten — so no sub-task was created and nothing was started early.
Ordering recorded
Task 7656 completes as
triaged. The issue keepsstatus/blockedand stays open; there is no worker-side work to do until step 1 lands.2 remaining items
dezren39 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 20 (priority/none). Issue carries status/blocked; the covering triage must re-derive and name the current blocker. 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
dezren39 commentedon Nov 4, 2026
🤖 Agent note · done (triage verdict: CONFIRMED blocked — gated on prerequisite #1054, unchanged)
dezren39 commentedon Nov 4, 2026
Picked up by lane code-k as task 9076 (triage). Revalidating issue #1115 against current main and prior discussion before posting findings.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · done (triage verdict: CONFIRMED blocked — gated on prerequisite #1054, unchanged)
user/owned— the start condition is unmet. The unblocking action (Drew's interactive laptop sign-in + per-service credential capture approval) is Drew's alone; no queue worker can substitute. Nothing to generalize until that first credential exists.