Go subscription active but every API call fails — "Insufficient account funds" / "stale-token" / "Key method not found" #51790

Account: willshort95@gmail.com
Plan: Go Subscription, active (dashboard confirms usage at 0% across rolling/weekly/monthly, Extra Usage toggle on, no funds added to balance)

Every attempt to actually use a Go model via the opencode CLI (v1.18.32, Windows) fails. I've tried multiple paths over two days, each producing a different error:

1. Day 1 — original API key, connected via opencode auth login opencode (fails client-side: Failed to load auth provider metadata from opencode: fetch() URL is invalid) and via opencode console login (succeeds, logs in fine) — but any model call returns:
   Upstream request failed: Insufficient account funds

2. Tried a full clean reinstall (opencode uninstall, fresh binary, fresh login) — same "Insufficient account funds" error, so it's not local state.

3. Registered the key directly via the local API (POST /api/integration/opencode-go/connect/key) per the workaround described in desktop: "Connect OpenCode Go" runs Console sign-in instead of the Go API-key flow, then reports success and fails with "Insufficient account funds" #50611 — created a proper opencode-go credential (distinct from the generic opencode/Console one) — still "Insufficient account funds."

4. Day 2 — generated a brand new API key. The same registration approach now fails outright server-side with:
   {"name":"UnknownError","data":{"message":"Unexpected server error. Check server logs for details.","ref":"err_2c57926c"}}
   Server log: error="Key method not found: opencode-go"

Separately, a third-party tool (Orca) that also polls the OpenCode Go usage API reports yet another distinct error for the same account: "The OpenCode Go API key was rejected", failureKind: "stale-token".

Three different failure modes across two days with no client-side changes strongly suggests a backend issue, not an account/funding problem. This looks like it could be related to #51049 ("Go plan inactive after Sep 21 payment - service stopped Sep 19, v2 transition"). Could someone check whether my subscription's entitlement is actually linked on the backend?

opencode auth login opencode (the V2 flow shown in the dashboard's "Connect OpenCode CLI" instructions) still fails client-side as of today with the same fetch() URL is invalid error, reproduced on both bash and PowerShell.