feat: add Gonka Broker as an LLM provider

[iamoeco]

Description

Adds Gonka Broker as a first-class, named LLM provider. Gonka Broker is an OpenAI-compatible gateway to decentralized Gonka compute, implemented as a thin subclass of the existing OpenAI provider.

Because the provider exposes a public, OpenAI-compatible /v1/models endpoint, users can set model: AUTODETECT and Continue discovers the available models automatically — no hardcoded model list, so no follow-up PR is needed when models change.

This mirrors the existing OpenAI-compatible gateway providers (e.g. Nebius, Tensorix). It adds the provider class + registration, the openai-adapters route, the VS Code config-schema entry, the onboarding UI entry, and a docs page. The provider serves chat/completions only, so it is intentionally not added to the embeddings or reranker enums.

Files:

• core/llm/llms/Gonkabroker.ts — new provider class extending OpenAI (apiBase https://proxy.gonkabroker.com/v1/).
• core/llm/llms/index.ts — register the provider in LLMClasses.
• core/llm/autodetect.ts — add gonkabroker to PROVIDER_HANDLES_TEMPLATING and PARALLEL_PROVIDERS.
• packages/openai-adapters/src/index.ts — route gonkabroker through openAICompatible.
• packages/openai-adapters/src/types.ts — add gonkabroker to the OpenAI-compatible provider union.
• gui/src/pages/AddNewModel/configs/providers.ts — onboarding entry (uses AUTODETECT).
• extensions/vscode/config_schema.json — add gonkabroker to the model-provider enum + onboarding description.
• docs/customize/model-providers/more/gonkabroker.mdx — provider documentation page.
• docs/docs.json — add the docs page to the "More Providers" sidebar.

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• I've read the contributing guide
• The relevant docs, if any, have been updated or created
• The relevant tests, if any, have been updated or created

Screen recording or screenshot

Config-only provider — it adds no new UI surface beyond the standard provider entry. Verified against the live API through the openai-adapters path:

• AUTODETECT discovered the served models from /v1/models.
• A chat completion to MiniMaxAI/MiniMax-M2.7 returned a valid response.

Tests

No automated tests were added, consistent with the existing OpenAI-compatible provider additions (e.g. Nebius, Tensorix), which add none. Verified manually with a real API key:

• Model auto-discovery via AUTODETECT returns the live model list from https://proxy.gonkabroker.com/v1/models.
• chatCompletionNonStream to MiniMaxAI/MiniMax-M2.7 returns a valid completion.

---

Summary by cubic

Add gonkabroker as an OpenAI-compatible LLM provider for chat/completions, with AUTODETECT model discovery from the public /v1/models endpoint.

• New Features
  • New Gonkabroker provider extending OpenAI with apiBase https://proxy.gonkabroker.com/v1/.
  • Routed via openAICompatible in packages/openai-adapters and added to its provider types.
  • Registered in LLMClasses; added to templating and parallel-provider lists for autodetect.
  • Added VS Code config_schema.json enum entry and onboarding UI entry (uses AUTODETECT).
  • New docs page and sidebar entry; provider is chat-only (not in embeddings or reranker).

^{Written for commit 2d1e0f0. Summary will update on new commits.}

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

No issues found across 9 files

_{Re-trigger cubic}

[iamoeco]

I have read the CLA Document and I hereby sign the CLA

[iamoeco]

The only failing check is jetbrains-tests, and it's failing on the flaky testAutocomplete() IDE-integration test (com.intellij.ide.starter.driver UI driver, AssertionFailedError at Autocomplete.kt:42), surrounded by headless X-server/xkbcomp/AT-SPI warnings.

This is unrelated to this PR: Kotlin/Java compilation and the :test unit tests pass, and the change only adds an inert OpenAI-compatible provider (plus two entries in autodetect.ts) — nothing that touches autocomplete. All TypeScript checks (core, packages/openai-adapters, e2e) are green. Could a maintainer re-run the jetbrains-tests job? Thanks!

[iamoeco]

Hi @sestinj — gentle bump 🙏 The only red check is the flaky jetbrains-tests (testAutocomplete UI test) — our diff touches zero JetBrains code, so it's unrelated infra flake. Could a maintainer re-run it? CLA signed, everything else green. Thanks!