5.1.2 — final release; migrate to upstream

Final release of @cardinal4/opencode-quota. Development has ceased because @slkiser/opencode-quota 5.0.0 now supports OpenCode 2. Includes the upstream V2 implementation, a TUI deprecation warning, and a persistent /quota_announcements migration notice. Remove this fork's server and TUI plugin entries, run npx @slkiser/opencode-quota@latest init, and restart OpenCode. Do not load both packages together. Requires OpenCode 2.0.16+ and Node.js ^22.13.0 || >=23.4.0. Verification and packed-consumer smoke tests pass on Node 22 and 24.

v5.0.3

Fixes

• OpenAI quota now resolves from the OpenCode 2 credential store. OpenCode 2 keeps provider credentials in the credential table of opencode.db, but the OpenAI quota provider only read the legacy auth.json. After a fresh opencode auth login openai, OpenAI therefore showed up in /quota and the TUI sidebar with no data. Resolution now prefers OAuth-shaped v2 credentials (integration ids openai / chatgpt / codex) and still falls back to auth.json for legacy installs.
• v2 metadata.accountID is mapped to the legacy accountId field so per-account quota caching and the ChatGPT-Account-Id header keep working.
• Status diagnostics report the winning credential source via a new auth_store row.

Tested against OpenCode 2.0.12.

v5.0.2

Fixes duplicate quota slash commands in the TUI.

The CLI/TUI plugin no longer registers slash names for its keymap commands; slash names are owned by the server command catalog. OpenCode's prompt autocomplete merges keymap slash names with the server catalog without deduping, which listed every quota command twice. The command palette (Ctrl+P) entries keep the TUI dialog and argument-prompt behavior, while the quota and token report commands now resolve once through the server catalog. Web and Desktop clients are unchanged.

Also fixes the packed-package smoke assertion to use the actual @Cardinal4 scope.

Tested against OpenCode 2.0.11.