feat(providers): add Apertis preset

[theQuert]

Summary

• Add Apertis as a canonical API-key provider with the existing OpenAI Chat adapter.
• Discover its key-scoped model catalog at /v1/models and retain same-named custom provider configurations.
• Surface the preset in the GUI catalog and synchronize provider documentation across all locales.

Canonical-preset evidence

Requirement	Primary source	Verification
OpenAI-compatible Chat Completions endpoint, base URL, and Bearer API-key use	Apertis Chat Completion documentation	Checked 2026-07-31
Authenticated GET /v1/models contract and the key-scoped OpenAI-shaped model list	Apertis Models documentation	Checked 2026-07-31
Terms and operating legal entity	Apertis Terms of Service; the Apertis docs footer identifies STIMA AI LLC	Checked 2026-07-31
Resale or routing authorization	Apertis is an aggregator. Its public product page states that it uses paid multi-provider routes and does not reuse consumer subscription OAuth. Provider-specific contractual evidence is non-public and must be reviewed confidentially by a maintainer/security reviewer before this draft can merge.	Checked 2026-07-31
Maintenance owner	@theQuert; report breakage through this repository's issue/PR workflow and tag the owner. The owner will update or demote the preset if its endpoint, auth, or catalog contract changes.	2026-07-31

Contributor affiliation: @theQuert submits this contribution on behalf of Apertis / STIMA AI LLC.

Safety and scope

• Reuses the existing openai-chat adapter; no new auth flow or provider credential is added.
• Live discovery uses existing global safety bounds; fixture-only tests never contact Apertis.
• The fixed API-key preset preserves a same-named custom provider with a different adapter or destination.
• No static model, reasoning, or modality metadata is asserted for Apertis.

Verification

• bun test tests/apertis-provider.test.ts tests/provider-registry-parity.test.ts tests/provider-model-discovery-contract.test.ts — 56 passed
• bun run typecheck
• bun run privacy:scan
• bun run test — 6,293 passed, 4 skipped
• cd gui && bun test tests — 437 passed
• cd gui && bunx --bun eslint .
• cd gui && bun run build
• cd docs-site && bun install --frozen-lockfile && bun run build — 146 pages

bun run lint invokes the system Node ESLint launcher here, which cannot load the existing TypeScript config (.eslint/i18n-file-groups.ts); the same rules passed under Bun via bunx --bun eslint ..

Checklist

• Scope stays focused on the provider preset and its documentation.
• Documentation and fixture-based tests cover the new provider contract.
• Security-sensitive behavior was reviewed for secrets and unsafe defaults; explicit maintainer security review remains required before merge.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 05d2305e-3309-43da-88bf-874aaff4a799

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[Ingwannu]

The preset itself is potentially valuable and the implementation gets several important details right: fixed Bearer-authenticated /v1/models, openai-chat, liveModels, and preserveCustomDestination all match the intended registry contract. It is not mergeable yet for two concrete reasons:

1. This branch is stale against current dev. The docs change the catalog total to 61, while current dev already has 65 presets (54 key-based); Apertis would make that 66/55. The branch also conflicts in all five provider docs, registry.ts, the icon table, and registry parity because newer presets such as DeepInfra, Hyperbolic, and Volcengine landed after its base. Please rebase onto current dev, preserve every existing entry, and regenerate the counts/parity expectation.
2. A canonical aggregator preset is a credential-destination change. The PR explicitly says provider-specific routing/resale authorization is non-public. The public product-page claim is not enough to independently verify the policy requirement. Please provide the contractual authorization confidentially to the project owner/maintainers and record only the maintainer verification outcome/date in the PR; do not post confidential terms or credentials here. If that evidence cannot be shared, the acceptable fallback is an inert free-directory row rather than a canonical registry entry.

Keep this draft until both points are resolved. After the rebase, rerun the focused provider/parity/discovery suite and the full cross-platform CI.