feat: add MiniMax as a built-in onboarding provider (default M3)

[octo-patch]

Summary

• Add minimax to SUPPORTED_ONBOARDING_PROVIDERS and BUILTIN_PROVIDERS with wire: 'openai-chat' and baseUrl: 'https://api.minimax.io/v1'
• Ship MiniMax-M3 (default), MiniMax-M2.7, and MiniMax-M2.7-highspeed as static model hints (no /models endpoint call needed)
• Support MINIMAX_API_KEY env var via the envKey field — works for Codex import and env-fallback resolution
• Add MINIMAX_API_KEY to ALLOWED_IMPORT_ENV_KEYS allowlist in codex-config
• Add pingProvider case for minimax in validate.ts (Bearer auth, https://api.minimax.io/v1/models)
• Add unit tests for MiniMax config properties and validation behavior
• Add changeset (minor bump for @open-codesign/shared)

Why

MiniMax offers an OpenAI-compatible API (https://api.minimax.io/v1) with competitive models. Adding it as a built-in provider lets users select it directly from the onboarding screen without needing to configure a custom endpoint manually.

MiniMax-M3 is the latest model and is shipped as the default; MiniMax-M2.7 and MiniMax-M2.7-highspeed remain available as alternatives for users who prefer the previous generation.

API reference

• Chat (OpenAI Compatible): https://platform.minimax.io/docs/api-reference/text-openai-api

Test plan

• All tests in packages/shared pass (pnpm --filter @open-codesign/shared test)
• All tests in packages/providers pass (pnpm --filter @open-codesign/providers test)
• All tests in apps/desktop onboarding-ipc pass
• Typecheck passes for packages/shared and packages/providers
• Biome lint passes on changed files
• Changeset included for user-visible change

[github-actions]

Review mode: initial

Findings

• [Minor] onboarding-ipc.ts error message missing ollama from the list of supported providers — the message now reads "Only anthropic, openai, openrouter, minimax" but the corresponding message in packages/providers/src/validate.ts includes ollama as well. For consistency, the error message in onboarding-ipc.ts should also mention ollama. This is a pre-existing inconsistency, but the PR touched that line.
  Suggested fix:

  - `Provider "${provider}" is not supported in v0.1. Only anthropic, openai, openrouter, minimax.`
  + `Provider "${provider}" is not supported in v0.1. Only anthropic, openai, openrouter, ollama, minimax.`

• [Nit] Test description change from "seeds three builtin providers" to "seeds all builtin providers" is accurate but the test body only checks that all entries exist, not the count. Consider also adding an assertion on the number of seeded providers to future-proof the test.
  Suggested fix (optional):

  const providerCount = SUPPORTED_ONBOARDING_PROVIDERS.length;
  expect(Object.keys(v3.providers).length).toBe(providerCount);

Questions

• Does the frontend onboarding UI automatically pick up the new provider from SUPPORTED_ONBOARDING_PROVIDERS and PROVIDER_SHORTLIST, or is there a hardcoded list in the renderer that should be updated? The diff only touches shared config and IPC logic; if there's a renderer-side static list, it would remain unaware of MiniMax.

Summary
The PR correctly adds MiniMax as a built-in onboarding provider with OpenAI-compatible wire, static model hints, environment variable support, and validation. The changes are focused, well-tested, and consistent with the project's architecture. No blockers or major issues found. See minor consistency improvement above.

Testing

• Unit tests added in packages/providers/src/validate.test.ts and packages/shared/src/config.test.ts cover the new provider's configuration properties, validation, and error behavior. Tests are adequate.
• No E2E tests impacted (no UI changes).

Open-CoDesign Bot

[hqhq1025]

Thanks, this is close. The core provider wiring looks good, and I verified the focused tests locally. Before merging, could you please address a few small integration issues?

1. Please add a real MiniMax entry to the Settings “Add provider” menu. Right now MiniMax is registered in shared/provider config, but users still cannot choose it directly from the UI; they can only use Custom Provider or Codex import. Since this PR describes MiniMax as a first-class onboarding provider, the UI should expose it.

2. Please update the MiniMax capability profile. The PR sets supportsModelsEndpoint: false, but the new validation code calls https://api.minimax.io/v1/models, and MiniMax documents an OpenAI-compatible List Models endpoint. I think this should be true or omitted, while keeping modelsHint / static-hint if we still want a stable default model list.

3. Please include ollama in the unsupported-provider error message in apps/desktop/src/main/onboarding-ipc.ts. The current message says anthropic, openai, openrouter, minimax, but the actual supported list also includes ollama.

I verified locally:

pnpm --filter @open-codesign/shared test && pnpm --filter @open-codesign/shared typecheck
pnpm --filter @open-codesign/providers test && pnpm --filter @open-codesign/providers typecheck
pnpm --filter @open-codesign/desktop test -- src/main/onboarding-ipc.test.ts src/main/provider-settings.test.ts src/main/connection-ipc.test.ts
pnpm --filter @open-codesign/desktop typecheck
pnpm exec biome check .changeset/add-minimax-provider.md apps/desktop/src/main/imports/codex-config.ts apps/desktop/src/main/onboarding-ipc.ts packages/providers/src/validate.ts packages/providers/src/validate.test.ts packages/shared/src/config.ts packages/shared/src/config.test.ts

Once those are addressed, this should be good to merge.

[ViX3L]

Is this PR be merged with the latest release? If so when can that be expected. Thank you!

[github-actions]

Review mode: follow-up after new commits

Findings

• [Minor] The onboarding-ipc.ts error message still omits ollama from the list of supported providers, as noted in the previous review. The message reads "Only anthropic, openai, openrouter, minimax" but should also include ollama for consistency with validate.ts. This was not addressed in the latest commits.
  Suggested fix:

  - `Provider "${provider}" is not supported in v0.1. Only anthropic, openai, openrouter, minimax.`
  + `Provider "${provider}" is not supported in v0.1. Only anthropic, openai, openrouter, ollama, minimax.`

• [Nit] The changeset and test descriptions now correctly reflect MiniMax-M3 as the default model, and model arrays consistently include MiniMax-M3, MiniMax-M2.7, and MiniMax-M2.7-highspeed. No further inconsistencies.

Questions

• The previous review asked whether the frontend onboarding UI automatically picks up the new provider from SUPPORTED_ONBOARDING_PROVIDERS and PROVIDER_SHORTLIST, or whether there is a hardcoded list in the renderer. This question remains unanswered — the diff only touches shared config and IPC logic. If a renderer-side static list exists, it would need updating. Please clarify.

Summary
The latest commit updates the default model from MiniMax-M2.7 to MiniMax-M3, matching the official model lineup. The rest of the implementation is consistent and well-tested. The only remaining open item is the onboarding-ipc.ts error message missing ollama, and the unanswered question about the renderer UI.

Testing

• The new tests (validation, config properties) have been updated to match the MiniMax-M3 default. All tests pass. No additional test gaps identified.

Open-CoDesign Bot

[github-actions]

Review mode: follow-up after new commits

Findings

• [Minor] The onboarding-ipc.ts error message now correctly includes ollama in the list of supported providers. This resolves the previous review's finding. No new issues introduced.

Questions

• The previous review asked whether the frontend onboarding UI automatically picks up the new provider from SUPPORTED_ONBOARDING_PROVIDERS and PROVIDER_SHORTLIST, or whether there is a hardcoded list in the renderer. This question remains unanswered — the diff only touches shared config and IPC logic. If a renderer-side static list exists, it would need updating. Please clarify whether a renderer change is needed.

Summary
All previously identified issues have been addressed. The error message now lists all supported providers including ollama. The implementation is consistent and well-tested. The only open item is confirming the renderer UI behavior.

Testing
Not run (automation)

Open-CoDesign Bot

[octo-patch]

Thanks for the follow-up review! Pushed db8f2ce to include ollama in the onboarding-ipc.ts supported provider error message, matching packages/providers/src/validate.ts.