Add Command Code provider

[nclsjn]

Problem

No Command Code support.

Proposed Solution

Add Command Code provider.

Alternatives Considered

No response

Additional Context

No response

[winemarshal68]

I can build this. Command Code (commandcode.ai) exposes everything OpenUsage needs through the same API its own CLI uses, authenticated by the local login already on disk — no OAuth, no scraping:

• Credentials: ~/.commandcode/auth.json → apiKey, sent as Authorization: Bearer (same pattern as the Codex/Claude auth stores).
• Endpoints (https://api.commandcode.ai/alpha/…): billing/credits → 5-hour and weekly windows (used, cap, resetAt) plus monthly/purchased/free credits remaining; billing/subscriptions → plan id and period start/end; usage/summary?since=<periodStart> → period spend, request and token counts.
• Plans: Go/Pro/GOAT/Max/Ultra/Teams; monthly credit totals per plan are constants in the CLI bundle, so a bounded monthly meter is possible alongside the two rolling windows.

Proposed widgets mirror the Claude provider: 5-hour, weekly, monthly credits, with pacing. Provider folder + focused tests + docs/providers/command-code.md. Verified against a live account today. Happy to be assigned.

[hwong103]

Adding another +1 for this. I use Command Code, and native usage tracking in OpenUsage would be genuinely useful. The issue's proposed local-auth/API approach looks like a good fit; please count me as another interested user.