feat(model): add OrcaRouter as an official model provider

[XiaoHuo888-hue]

Description

Add OrcaRouter as an official model provider in the Model Management page, mirroring the existing DeepSeek/MiniMax provider cards.

OrcaRouter is an OpenAI-compatible LLM routing gateway: a single API key routes chat requests across leading models (orcarouter/auto). It also runs gateway-level, zero-trust security for AI agents on the same endpoint — screening every prompt/response and governing every tool call on a default-deny basis, with no application code changes.

This gives users a one-click, named OrcaRouter provider (pre-filled https://api.orcarouter.ai/v1 base URL) instead of having to fill a generic OpenAI-compatible endpoint by hand.

Type of Change

• New feature
• Bug fix
• Breaking change
• Documentation update

Changes

• src/types/model.ts: register ORCAROUTER in ModelProviderType
• src/pages/model-management/utils/provider-group.ts: map OrcaRouter to the OpenAI-compatible vendor group; add the OrcaRouter option to the Official Providers filter
• src/pages/model-management/utils/provider.ts: resolve the OrcaRouter provider label
• src/pages/model-management/official-model/official-model-home.tsx: add the OrcaRouter provider card (base URL https://api.orcarouter.ai/v1, model orcarouter/auto) + provider icon
• src/pages/model-management/components/modal-component.tsx / grouped-provider-cards.tsx: treat OrcaRouter as an OpenAI-compatible provider
• src/locales/en-En/model.ts + src/locales/zh-ZH/model.ts: provider label + card description
• src/assets/imgs/modelManage/providers/custom/orcarouter.svg: provider icon
• _tests_/model-provider-orcarouter.test.js: unit tests for provider registration, vendor mapping, and catalog option
• _tests_/alias-loader.mjs + package.json: test-only @/ path-alias loader so unit tests can import modules that reference the Vite alias

Testing

• npm run test:unit: 65/65 pass (61 baseline + 4 new OrcaRouter tests)
• npm run type-check: 0 new errors (3,763 pre-existing errors on clean main, none in touched files)
• npx eslint on touched files: 0 errors
• npx prettier --check on touched files: clean
• npm run build: success
• L3 live test against the endpoint configured in the PR (real key): POST https://api.orcarouter.ai/v1/chat/completions with model orcarouter/auto → HTTP 200, OpenAI-compatible choices response. The backend's model-validation path (OpenAI-compatible response check) accepts this shape unchanged.

Checklist

• Code follows project style guidelines
• Self-review completed
• Documentation updated
• No breaking changes

Disclosure: I'm an engineer on the OrcaRouter team.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

XiaoHuo888-hue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[FenjuFu]

Thanks for the contribution, but I'm going to recommend against this and close it.

OrcaRouter is a third-party commercial LLM-gateway product, and this PR adds it to the Official Providers list with promotional framing (a routing gateway that also sells "gateway-level, zero-trust security" on the same endpoint). Which providers appear as official, pre-configured cards is a product decision for the Astron maintainers — not something a drive-by PR should establish, the same way we don't accept unsolicited additions of other commercial gateways here.

This also isn't a one-off integration request for Astron: the identical "add OrcaRouter as a provider" change has been opened across 30+ unrelated projects in the last day or two (CopilotKit, langfuse, google/adk-java, gptel, obsidian-copilot, and many more). That mass-templated pattern is what we treat as promotional outreach rather than a genuine integration need.

For what it's worth, Astron users who want to use OrcaRouter today already can, via the generic OpenAI-compatible endpoint — no code change required. If the OrcaRouter team would like an official, named provider card, please open an issue proposing it so the maintainers can weigh it, rather than a pre-built PR.

Closing for now.