You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expose Qoder account quota to omp usage (#47, @Qiiks): OMP renders provider quotas from a provider-level usage slot, which pi's published ProviderConfig has no field for, so omp usage showed the Qoder account with no data. The registration now carries a usage provider (ignored by pi) mapping the quota payload the extension already parses for /qoder-usage: one limit per Credit bucket (user / add-on / organization) with numeric used / limit / remaining and a used fraction, the plan expiry as the window boundary (Qoder's year-9999 'no expiry' sentinel dropped), and the account kind and manage URL as notes. A failed quota read renders as missing data and never marks the credential unhealthy (validatesCredentials: false).
Tests
Stub the network before provider registration in providers.test.ts: with stored credentials on disk and a stale models cache, the startup catalog refresh hung in sandboxes without direct egress, timing the test out and polluting the next test's registration counts. Full suite: 414 tests passing.