[AiCaptain357]

The quota page displayed the internal moonshot identifier even though the provider catalogue names it Kimi. Add the missing quota display label so cards, provider groups, overview headings and the provider filter use Kimi.

The existing provider identifier, filter values and refresh callbacks continue to use moonshot; Kimi Coding and unknown-provider fallback labels keep their own names.

Validation:

• Four new rendering regressions fail on pristine release/v3.8.53 at 689b1eb5. With this fix, all 16 tests in the affected UI files pass.
• Another 3 UI ordering tests and 26 provider filter/order/branding tests pass: 45 distinct tests across 7 files.
• Scoped ESLint, Prettier, whitespace and changelog checks pass. Tests use synthetic data and mocked requests; full suites, typecheck, build and live-provider validation were not run.

⚠️ base-red inherited: #17219 — pre-existing CI failures on the target release branch.

[coderabbitai]

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

• Bug Fixes
  • Kimi accounts now display “Kimi” instead of the internal Moonshot name in quota cards, overview groups, and provider filters.
  • The “Kimi Coding” label remains distinct, and filtering by Kimi selects the expected account.

The quota provider label mapping now displays Moonshot as “Kimi.” Tests cover the provider filter, provider names across quota layouts, and Moonshot refresh arguments.

Changes: Kimi quota provider label

Layer / File(s)	Summary
Provider label mapping and UI validation src/app/(dashboard)/dashboard/usage/components/ProviderLimits/constants.ts, tests/unit/quota-availability-integration.test.tsx, tests/unit/quota-upstream-layouts.test.tsx, changelog.d/fixes/0-kimi-quota-provider-label.md	The provider label mapping adds “Kimi” for Moonshot. Tests check provider filter values and results, provider labels across quota layouts, and Moonshot refresh arguments. The changelog describes the label change.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix · Severity of issue fixed: Low

Merge Risk: Minimal · up to 953a5

Quota views display Kimi without changing the provider identity. No merge-blocking risk is identified.

Pre-merge checks: 6 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 6 passed

Check name	Status	Explanation
Title check		The title "fix(dashboard): show Kimi name in provider quotas" follows the Conventional Commits format with the allowed type "fix" and a scope. It matches the changeset, which adds a moonshot label o…
Description check		The description states the problem (the quota page showed the internal moonshot identifier), the fix (a quota display label for Kimi), and the scope of what stays unchanged. It reports validation: t…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Tests For Production Code		PASS. The PR changes production code in src/app/(dashboard)/dashboard/usage/components/ProviderLimits/constants.ts by adding the moonshot label. It also updates `tests/unit/quota-availability-inte…
No Ai Attribution		No AI attribution found. All three commits have no Co-Authored-By trailer or “Generated with ” footer, and the supplied PR body contains neither prohibited form.

Full details: Title check

Explanation

The title "fix(dashboard): show Kimi name in provider quotas" follows the Conventional Commits format with the allowed type "fix" and a scope. It matches the changeset, which adds a moonshot label of "Kimi" to PROVIDER_LABEL so quota cards, provider groups, overview headings, and the provider filter show Kimi instead of the internal identifier.

Full details: Description check

Explanation

The description states the problem (the quota page showed the internal moonshot identifier), the fix (a quota display label for Kimi), and the scope of what stays unchanged. It reports validation: the regression tests, the scoped lint and format checks, and the inherited base-red CI failure. It does not fill in the template's Related Issues section, the Target Branch checklist, the Tests Added Or Updated list, or the Coverage Notes and Reviewer Notes. The Validation checklist items are not ticked, and the change type is not selected. The core content is present, but several required template sections are missing or incomplete.

Resolution

Consider completing the remaining template sections before merge: add the related issue (Closes # or Related to #), tick the Target Branch checkboxes, choose the change type under Validation, list the changed test files under Tests Added Or Updated, and add Coverage Notes for the touched src/ files.

Full details: Tests For Production Code

Explanation

PASS. The PR changes production code in src/app/(dashboard)/dashboard/usage/components/ProviderLimits/constants.ts by adding the moonshot label. It also updates tests/unit/quota-availability-integration.test.tsx and tests/unit/quota-upstream-layouts.test.tsx with coverage for Kimi labels, filtering, layouts, and refresh identifiers.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 1 functions across 3 files. (1 skipped: 1 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 4
• Waived: $1.00 (charged $0.00)
• View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

Recent review info

Run configuration

• Source mode: Auto
• Repository: cheaper-inference/OmniRoute
• Branch: release/v3.8.53
• File: .coderabbit.yaml
• Commit: f000c11
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 981c1f53-c089-4e04-a21c-f5c462b2bd15

Commits

Reviewing files that changed from the base of the PR and between f000c11 and 953a512.

Files selected for processing: 4

• changelog.d/fixes/0-kimi-quota-provider-label.md
• src/app/(dashboard)/dashboard/usage/components/ProviderLimits/constants.ts
• tests/unit/quota-availability-integration.test.tsx
• tests/unit/quota-upstream-layouts.test.tsx

Limit details: You’ve used all 10 included reviews currently available.