Skip to content

chore(usage-hub): OpenCode Go lapse handling — Personal Nov 2, Lab Nov 6 #1118

New issue
New issue
Open
Open
chore(usage-hub): OpenCode Go lapse handling — Personal Nov 2, Lab Nov 6#1118
Assignees
dezren39
Labels
effort/sSmall: expected under 2 hours of workmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudqueue/queuedHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobstatus/needs-triageNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this item

Description

@dezren39
dezren39
opened on Oct 27, 2026

Part of epic #1047. Design: hub-v2-v3-design-2026-10-26.md §6. Time-sensitive: Personal's paid period ends Nov 2, 2026 ~21:02 CT; Lab's ends Nov 6 ~23:55 CT. go-plan-expiry-watch tracks the burn-down hourly until then. Drew's ruling (2026-10-25): leave BOTH Go plans cancelled — do not re-subscribe.

At each lapse: (1) hub card switches to a lapsed state — history retained, no stale % presented as current; (2) route pools / quota guidance lose the workspace; (3) check-usage + the registry record the final readings; (4) a short decision record in the registry captures whether a replacement is wanted (default: none, per Drew's ruling).
Acceptance: after Nov 6, /quota shows both workspaces as lapsed with final dated readings; no placement guidance references Go pools.

Activity

  1. dezren39
    added
    meta/follow-upFollow-up spun out of earlier work
    on Oct 27, 2026

  2. developing-today commented on Oct 27, 2026

    @developing-today
    developing-todayBot
    on Oct 27, 2026 – with developing.today
    Contributor

    CODE-256

  3. github-actions
    assigned
    dezren39
    on Oct 27, 2026
  4. dezren39
    added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    status/in-progressQueue worker lifecycle state
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026

  5. dezren39 commented on Oct 29, 2026

    @dezren39
    dezren39
    on Oct 29, 2026
    MemberAuthor

    🤖 Agent note · done (triage verdict: CONFIRMED — routed to time-gated follow-up task 3018)

    • Agent: queue worker (repo-worker-code), Lane C shift
    • Session / ID: queue task 2406 (triage)
    • Found via: queue claim
    • Task: Triage chore(usage-hub): OpenCode Go lapse handling — Personal Nov 2, Lab Nov 6 #1118 against current main and route it.
    • Verdict — CONFIRMED, time-gated: The handling this issue specifies does not exist yet and cannot be executed early: code search finds no "lapsed" state anywhere in the hub/aggregator, and the route pools still carry both workspaces (pm-stack/aggregator/src/aa.ts: opencode-go.personal / opencode-go.lab; src/quota-extract.ts: opencode-go:personal / opencode-go:lab). The trigger dates are pinned and close: Personal ends 2026-11-02 ~21:02 CT, Lab ends 2026-11-06 ~23:55 CT (registry console reads 2026-10-28 confirm both Cancelled with those end times, burn-down tracked by go-plan-expiry-watch). Drew's ruling is already recorded (both stay cancelled; replacement default: none), so no decision is outstanding.
    • Route: follow-up task 3018 enqueued with not_before 2026-11-07T06:00Z (dedupe key repo-health:v1:fix:developing-today/code:issue:1118), matching the issue's own acceptance ("after Nov 6"): lapsed card/API presentation with final dated readings and history retained, Go workspaces out of route pools and quota guidance, final readings + decision record appended to the provider-quota registry. The Nov 2–6 interim (Personal lapsed, Lab live) stays covered by go-plan-expiry-watch/stewardship reads, as today.
    • Links: epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047 · pm-stack/aggregator/src/aa.ts · provider-quota registry
  6. dezren39
    added
    effort/sSmall: expected under 2 hours of work
    mode/onlineFully doable remotely: design, config, code, cloud
    and removed
    status/in-progressQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Oct 29, 2026
  7. dezren39
    added a parent issue on Nov 1, 2026
  8. developing-today
    added
    source/creatorFiled by the new-issue-creator job
    status/needs-triageNot yet triaged; needs a first look
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026

  9. developing-today commented on Nov 3, 2026

    @developing-today
    developing-todayBot
    on Nov 3, 2026 – with developing.today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 3018 (small_fix, queued, priority 30) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

effort/sSmall: expected under 2 hours of workmeta/follow-upFollow-up spun out of earlier workmode/onlineFully doable remotely: design, config, code, cloudqueue/queuedHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobstatus/needs-triageNot yet triaged; needs a first looktask/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