Reclassifies Gemini usage fetch outcomes so unconfigured/unauthenticated Gemini no longer shows a noisy error card in the usage dropdown; transient failures of a configured token still surface as errors.
- fetchGeminiUsage() in packages/dashboard/src/usage.ts now sets status to `no-auth` (instead of `error`) for unsupported auth types (api-key/vertex-ai) and for HTTP 401/403 auth-expired responses, so fetchAllProviderUsage omits Gemini from the aggregate list in those cases
- HTTP 5xx, network, timeout, and parse failures for a configured Gemini token remain `error` and visible, per the existing FN-7798 keep-auth-expired-visible convention for other providers
- Added FNXC:UsageProviders comments documenting why Gemini deliberately diverges from that convention
- Updated packages/dashboard/src/__tests__/usage.test.ts to cover the new no-auth classification
- Added changeset .changeset/fn-7806-gemini-usage.md (patch) documenting the fix for release notes
Files changed:
.changeset/fn-7806-gemini-usage.md | 7 +
packages/dashboard/src/__tests__/usage.test.ts | 211 +++++++++++++++----------
packages/dashboard/src/usage.ts | 15 +-
3 files changed, 148 insertions(+), 85 deletions(-)
Fusion-Task-Id: FN-7806
Fusion-Task-Lineage: e86b23ea-14e9-472d-8b44-3951fa02ae6c
Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
c1b14c2d08