[octo-patch]

Reason: Lime's MiniMax subscription templates still select MiniMax-M2.7, and discovered MiniMax catalogs can promote retired text models. New subscriptions should select MiniMax-M3.1-Flash, while explicitly configured legacy model IDs continue to work.

Change summary

• Default China and international M Plan templates to Flash and use the documented subscription-key links. The China M Plan endpoint is https://api.minimax.cn/anthropic.
• Default direct API catalog templates to Flash followed by M3. Do not add M3 to subscription presets: the subscription documentation establishes Flash only.
• Filter retired MiniMax M-series, abab…-chat, and MiniMax-Text-01 IDs from discovered catalogs and API model choices, rank Flash first, and preserve explicitly configured legacy/custom IDs, their metadata, other providers and non-text entries.
• Recognize the current China Anthropic host in the existing regional catalog/prompt-cache mapping.
• Add UI activation cases and loopback HTTP capture coverage for explicit Flash, M3 and M2.7 requests. Transport behavior is unchanged: Anthropic requests omit thinking/effort/service-tier fields, leaving the service's defaults in effect.

Sources: China M Plan configuration, international M Plan configuration, current API model overview.

i18n impact

• No user-visible copy changes
• User-visible copy changes; namespaces listed below
• Locale-resource changes submitted as a draft for review

Added / changed namespaces

settings: MiniMax template display names and the default-model description in en-US, zh-CN, zh-TW, ja-JP and ko-KR. Existing keys and saved template identifiers remain stable. Changes are limited to the product name/model identifier, plus the English subscription description.

Terminology confirmation

• Checked internal/roadmap/i18n/glossary.md
• Product names and protocol identifiers remain consistent

Validation

• npm run i18n:check
• npm run verify:local
• Other: 43 tests passed across providerTypeMapping, providerPromptCacheSupport, modelPickerPolicy and minimaxCatalogPolicy using cached Vitest 2.1.9, with a credential-free environment and one worker. Expanded legacy-text regressions failed in three cases before the classifier fix, then passed; they verify both regional ordinary catalogs plus preservation of saved legacy IDs, metadata and speech models.
• Seven changed TypeScript sources transpile with cached TypeScript; source assertions verify both subscription defaults/endpoints/key links, direct API defaults and five locale JSON files. This is not full type checking or UI execution.
• git diff --check; request-capture Rust source passes cached rustfmt syntax/format checking.
• New UI activation tests and actual Rust HTTP capture tests executed. Rust 1.95.0 is not installed; the complete pinned project dependencies/build environment are unavailable. No dependency downloads or heavy builds were attempted because available disk is below 5 GiB.

Architecture diagram confirmation

• This is not a major architecture change

Reason: changes stay within the existing provider-template and model-catalog owners; the request transport and protocol boundaries are unchanged.

Architecture impact: existing catalog filtering and endpoint recognition only.

Architecture diagram update sections: not applicable.

Responsible developer confirmation:

• Checked directory ownership, data flow, dependency direction, protocol boundary and validation gates.

Notes

Draft pending the repository-pinned frontend/i18n checks and execution of the real request-boundary capture suite. No paid inference or account-specific entitlement verification was performed. The capture fixture is credential-free and targets loopback only; its assertions have been added but are not claimed as executed. Cached check versions are not a substitute for the pinned CI gate.