docs(readme): fold the evolution section into one compact table with New markers

Co-authored-by: backryun <bakryun0718@proton.me>

.dockerignore

@@ -53,8 +53,10 @@ reports/mutation
 # Local caches and quality-gate artifacts (all gitignored). `_*` does not match
 # dot-prefixed names, so these need explicit entries.
 .artifacts
-.eslintcache
-.eslintcache-complexity
+.eslintcache*
+.fakebin-*
+MAX
+quality-ratchet/
 
 # Documentation
 # Issue #2348: The Dashboard Docs viewer reads markdown from `/app/docs` at

.github/pull_request_template.md

@@ -10,7 +10,7 @@
 ## Validation
 
 Choose the change type and focused loop from the
-[Contribution Golden Path](../docs/dev/CONTRIBUTION_GOLDEN_PATH.md). The full unit suite,
+[Contribution Golden Path](../docs/ops/CONTRIBUTION_GOLDEN_PATH.md). The full unit suite,
 Vitest, the 60% coverage gate, and the production build all run in CI on this PR (#8329):
 
 - [ ] Change type: provider / routing / UI / i18n / CLI / DB / build-deploy / other

.gitignore

@@ -18,7 +18,7 @@ _tasks/
 .logs/**
 .tests/**
 .coverage/**
-coverage/
+/coverage/
 .dist/**
 .next/**
 .build/**
@@ -44,6 +44,7 @@ memory-bank/
 
 # Root-level underscore-prefixed directories (private/draft — never commit)
 /_*/
+/_*
 
 # Draft features documentation (internal only)
 docs/new-features/
@@ -57,10 +58,6 @@ node_modules/
 *.map
 .DS_Store
 
-# Obsidian sync plugin — committed for community distribution
-!obsidian-plugin/
-obsidian-plugin/node_modules/
-
 # Serena AI assistant config (local-only tool, not project code)
 .serena/
 
@@ -74,6 +71,7 @@ yarn-error.log*
 .env*
 !.env.example
 !.env.homolog.example
+!.env.devin-bridge.example
 # Provider API keys (never commit)
 *.api-key
 .nvidia-api-key
@@ -86,7 +84,7 @@ yarn-error.log*
 next-env.d.ts
 
 # data and logs
-data/
+/data/
 .data/
 logs/*
 test_output.log
@@ -108,7 +106,7 @@ open-sse/test/*
 test-results/
 playwright-report/
 blob-report/
-cloud/
+/cloud/
 .tmp/
 
 # Security Analysis (standalone project with own git)
@@ -175,7 +173,6 @@ config/quality/test-impact-map.json
 # GitNexus local index
 .gitnexus
 .worktrees
-bin/omniroute.mjs
 
 # Consistent with .dockerignore / .npmignore
 .omc/
@@ -213,7 +210,7 @@ scripts/i18n/_pending-keys.json
 # AI agent local settings and configs
 .agents/
 .antigravitycli/
-.claude/
+/.claude/
 
 # PR Reviews and local feedback files
 pr_reviews*.json
@@ -271,6 +268,8 @@ _artifacts/          # release-green artifacts
 
 # CI/local quality artifacts (eslint-results.json, quality-ratchet.md, etc.)
 .artifacts/
+/perf-audit*.md
+/quality-ratchet/
 
 # Homologation E2E suite (npm run homolog) — real-environment credentials + report output
 .env.homolog

.npmignore

@@ -94,6 +94,10 @@ vscode-extension/
 /_*/
 
 # Consistent with .gitignore and .dockerignore
+.claude/
+.fakebin-*
+.eslintcache*
+_tasks/
 .DS_Store
 .idea/
 .config/

AGENTS.md

@@ -46,7 +46,7 @@ Repository map and Reference Documentation sections below.
 
 ## Project at a Glance
 
-**OmniRoute** — unified AI proxy/router. One endpoint, 291 LLM providers, auto-fallback.
+**OmniRoute** — unified AI proxy/router. One endpoint, 338 LLM providers, auto-fallback.
 
 | Layer         | Location                | Purpose                                                                                                                                                 |
 | ------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -56,9 +56,9 @@ Repository map and Reference Documentation sections below.
 | Translators   | `open-sse/translator/`  | Format conversion (OpenAI↔Claude↔Gemini)                                                                                                                |
 | Transformer   | `open-sse/transformer/` | Responses API ↔ Chat Completions                                                                                                                        |
 | Services      | `open-sse/services/`    | Combo routing, rate limits, caching, etc                                                                                                                |
-| Database      | `src/lib/db/`           | SQLite domain modules (130 migrations)                                                                                                                  |
+| Database      | `src/lib/db/`           | SQLite domain modules (144 migrations)                                                                                                                  |
 | Domain/Policy | `src/domain/`           | Policy engine, cost rules, fallback logic                                                                                                               |
-| MCP Server    | `open-sse/mcp-server/`  | 105 tools (42 base + memory/skill/agentSkill/pool/notion/obsidian/gamification/plugin modules), 3 transports (stdio / SSE / Streamable HTTP), 31 scopes |
+| MCP Server    | `open-sse/mcp-server/`  | 105 tools (43 base + memory/skill/agentSkill/pool/notion/obsidian/gamification/plugin modules), 3 transports (stdio / SSE / Streamable HTTP), 31 scopes |
 | A2A Server    | `src/lib/a2a/`          | JSON-RPC 2.0 agent protocol                                                                                                                             |
 | Skills        | `src/lib/skills/`       | Extensible skill framework                                                                                                                              |
 | Memory        | `src/lib/memory/`       | Persistent conversational memory                                                                                                                        |
@@ -83,7 +83,7 @@ Client → /v1/chat/completions (Next.js route)
 
 API routes follow a consistent pattern: `Route → CORS preflight → Zod body validation → Optional auth (extractApiKey/isValidApiKey) → API key policy enforcement → Handler delegation (open-sse)`. No global Next.js middleware — interception is route-specific.
 
-**Combo routing** (`open-sse/services/combo.ts`): 19 public strategies (priority, weighted, fill-first, round-robin, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, cache-optimized, context-relay, fusion, pipeline). Each target calls `handleSingleModel()` which wraps `handleChatCore()` with per-target error handling and circuit breaker checks. The `fusion` strategy is the exception: it fans out to a panel of models in parallel, then a judge model synthesizes one final answer (`open-sse/services/fusion.ts`). See `docs/routing/AUTO-COMBO.md` for the 13-factor Auto-Combo scoring + the full strategy table and `docs/architecture/RESILIENCE_GUIDE.md` for the 3 resilience layers.
+**Combo routing** (`open-sse/services/combo.ts`): 19 public strategies (priority, weighted, fill-first, round-robin, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, cache-optimized, context-relay, fusion, pipeline). Each target calls `handleSingleModel()` which wraps `handleChatCore()` with per-target error handling and circuit breaker checks. The `fusion` strategy is the exception: it fans out to a panel of models in parallel, then a judge model synthesizes one final answer (`open-sse/services/fusion.ts`). See `docs/routing/AUTO-COMBO.md` for the 14-factor Auto-Combo scoring + the full strategy table and `docs/architecture/RESILIENCE_GUIDE.md` for the 3 resilience layers.
 
 ---
 
@@ -247,17 +247,26 @@ Read the nearest `AGENTS.md` and the linked deep-dive before making a non-trivia
 ## File placement & repo-root hygiene
 
 - **Test files**: ALL unit tests, integration tests, ecosystem tests, or Vitest files MUST strictly be placed within the `tests/` directory (e.g., `tests/unit/`, `tests/integration/`). NEVER create test files in the project root (`/`).
-- **Scripts and utilities**: ALL maintenance, debugging, generation, or experimental scripts (`.cjs`, `.mjs`, `.js`, `.ts`) MUST be placed strictly inside one of the `scripts/` subfolders (`build/`, `dev/`, `check/`, `docs/`, `i18n/`, `ad-hoc/`). One-shot or experimental code goes under `scripts/ad-hoc/`. NEVER dump loose scripts in the project root (`/`) or the top-level `scripts/` folder.
+- **Scripts and utilities**: ALL maintenance, debugging, generation, or experimental scripts (`.cjs`, `.mjs`, `.js`, `.ts`) MUST be placed strictly inside one of the `scripts/` subfolders (`build/`, `dev/`, `check/`, `docs/`, `i18n/`, `ad-hoc/`, `quality/`, `release/`, `ci/`, `ops/`, `perf/`, `research/`, `sre/`, `vps/`, `homolog/`, `raycast/`, `skills/`, `test/`, `cli/`, `compression/`, `compression-eval/`, `devin-bridge/`, `docker/`, `features/`, `router-eval/`). One-shot or experimental code goes under `scripts/ad-hoc/`. NEVER dump loose scripts in the project root (`/`) or the top-level `scripts/` folder.
 
 **The project root MUST ONLY contain:**
 
 - Configuration files (`vitest.config.ts`, `next.config.mjs`, `eslint.config.mjs`, `tsconfig*.json`, `playwright.config.ts`, `prettier.config.mjs`, `postcss.config.mjs`, `sonar-project.properties`, `fly.toml`, `docker-compose*.yml`, `Dockerfile`)
 - Dependency files (`package.json`, `package-lock.json`)
-- Documentation files (`README.md`, `CHANGELOG.md`, `LICENSE`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, `llm.txt`, `Tuto_Qdrant.md`)
+- Documentation files (`README.md`, `CHANGELOG.md`, `ROADMAP.md`, `LICENSE`, `AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, `llm.txt`, `Tuto_Qdrant.md`)
 - CI/CD files and ignore definitions (`.gitignore`, `.dockerignore`, `.npmignore`, `.npmrc`, `.node-version`, `.nvmrc`, `.env.example`)
 
 When creating _any_ validation tests or one-off logic scripts, default to `scripts/ad-hoc/` or `tests/unit/` according to your goals. Do not pollute the `/` root context.
 
+- **Root `_*` paths are private and NEVER tracked** (`_tasks/`, `_references/`, `_mono_repo/`,
+  `_ideia/`, `_cache/` and any future `_<name>`): they live on disk only, are gitignored by the
+  anchored patterns `/_*/` + `/_*`, and some are full git repositories of their own (`_tasks` →
+  private remote `_tasks_omniroute`). Never `git add` anything inside them (a plain `add` is
+  already blocked by the ignore; never use `-f`), and never "clean them up" from the main repo —
+  untracking is done with `git rm --cached` so the disk content stays. The
+  `check:tracked-artifacts` gate (pre-commit + CI) fails on ANY tracked root path starting with
+  `_`, present or future. See Hard Rule #23 for the `_tasks` specifics.
+
 ---
 
 ## Key Conventions
@@ -395,7 +404,7 @@ For any non-trivial change, read the matching deep-dive first:
 | Repo navigation                               | `docs/architecture/REPOSITORY_MAP.md`                   |
 | Architecture                                  | `docs/architecture/ARCHITECTURE.md`                     |
 | Engineering reference                         | `docs/architecture/CODEBASE_DOCUMENTATION.md`           |
-| Auto-Combo (13-factor scoring, 19 strategies) | `docs/routing/AUTO-COMBO.md`                            |
+| Auto-Combo (14-factor scoring, 19 strategies) | `docs/routing/AUTO-COMBO.md`                            |
 | Resilience (3 mechanisms)                     | `docs/architecture/RESILIENCE_GUIDE.md`                 |
 | Reasoning replay                              | `docs/routing/REASONING_REPLAY.md`                      |
 | Skills framework                              | `docs/frameworks/SKILLS.md`                             |
@@ -419,7 +428,7 @@ For any non-trivial change, read the matching deep-dive first:
 | Electron desktop app                          | `docs/guides/ELECTRON_GUIDE.md`                         |
 | Release flow                                  | `docs/ops/RELEASE_CHECKLIST.md`                         |
 | Embedded services                             | `docs/frameworks/EMBEDDED-SERVICES.md`                  |
-| Quality gates (~48 scripts, allowlist policy) | `docs/architecture/QUALITY_GATES.md`                    |
+| Quality gates (~80 scripts, allowlist policy) | `docs/architecture/QUALITY_GATES.md`                    |
 
 ---
 
@@ -611,7 +620,7 @@ focused checks, and use a Conventional Commit message (for example, `docs: slim
 
 ## Quality Gates & Ratchets
 
-OmniRoute has **~48 quality-gate scripts** (`scripts/check/` + `scripts/quality/`) wired
+OmniRoute has **~80 quality-gate scripts** (`scripts/check/` + `scripts/quality/`) wired
 across **9 gate-running jobs** in `.github/workflows/ci.yml` (`lint`, `quality-gate`,
 `quality-extended`, `docs-sync-strict`, `i18n-ui-coverage`, `i18n`, `pr-test-policy`,
 `test-vitest`, `sonarqube`), plus the `quality.yml` fast-gates job (PR→`release/**`) and
@@ -662,6 +671,18 @@ the stale-enforcement added in Fase 6A.3.
 22. **Cross-session safety — this repo is worked by MANY parallel sessions/agents at once; never step on another's in-flight work.** Two absolute bans, both recurring incidents (this rule exists because they keep happening):
     - **(a) Never `git stash` / `git stash pop` — ANYWHERE in this repo, including inside an isolated worktree, and including inside any subagent you dispatch.** `git stash` operates on the **shared repository object store**, not the per-worktree working tree — so a stash pushed or popped in one session can silently clobber or resurrect another parallel session's uncommitted changes. This is not hypothetical: 2026-07-02 a `#5923` quotaCache change leaked into the unrelated `#2296` worktree via a global `stash pop`, and the same class reincided through a **subagent**. To compare working changes against a base ref **without** stashing, use `git show <ref>:<path>` or `git diff <ref> -- <path>`; to confirm a typecheck/lint error is pre-existing on the base, inspect the base ref directly (`git show origin/release/vX.Y.Z:<path>`) — never stash your tree away to "get it clean". **Put this ban verbatim in the prompt of every subagent that touches git** (agents don't inherit this file's context — the recurrence was a subagent).
     - **(b) Never merge, push, rebase, or force-push a PR / branch / worktree that another session is actively working.** An open PR whose head is a live fix worktree in `.claude/worktrees/` you did **not** create (e.g. `fix-5852`/`fix-5923` carrying fresh commits, even when they share your `diegosouzapw` identity), or any branch another session owns, is **off-limits — HOLD**, and let the owning session merge it. **Before** merging or pushing to any PR you did not create _this_ session, run `git worktree list` to check for a matching in-flight worktree and re-check `gh pr view <N> --json state,headRefOid`. Only the owning session merges its own in-flight PR; mid-flight merges race the owner and re-trigger the exact commit/CHANGELOG races Rule #19 and Rule #21 guard against. (Reinforces Rule #19.)
+23. **`_tasks/` é INTOCÁVEL como estrutura — append/edit-only.** É um repositório git SEPARADO
+    (remote privado `diegosouzapw/_tasks_omniroute`) montado como diretório real na raiz do
+    checkout principal. Regras absolutas: (a) NUNCA mover, renomear, deletar, esvaziar ou
+    transformar `_tasks` em symlink; sessões só podem CRIAR ou EDITAR arquivos dentro dele;
+    (b) NUNCA rastrear `_tasks` (nem como symlink) no repo principal — o blob rastreado foi a
+    causa-raiz de DOIS wipes (2026-08-08 e 2026-08-10: `git reset --hard` materializou o
+    symlink rastreado por cima do diretório real e o git apagou todo o conteúdo ignorado sem
+    aviso); (c) após qualquer escrita relevante, `git -C _tasks add -A && git -C _tasks commit
+    && git -C _tasks push` — o push frequente é o backup real; (d) repetir esta proibição
+    VERBATIM no prompt de todo subagente que toque git; (e) se `_tasks` aparecer como symlink
+    quebrado, NÃO commitar nada — restaurar do remote e avisar o operador. O gate
+    `check:tracked-artifacts` (pre-commit + CI) bloqueia `_tasks` rastreado em qualquer forma.
 
 ---
 

CLAUDE.md

@@ -3,7 +3,7 @@
 @AGENTS.md
 
 **All project rules live in [`AGENTS.md`](AGENTS.md)** — the single source of truth for every AI
-assistant (architecture, conventions, testing, quality gates, git workflow, the 22 Hard Rules,
+assistant (architecture, conventions, testing, quality gates, git workflow, the 23 Hard Rules,
 PII learnings). Read it in full; do not re-add project rules here. Everything below applies ONLY
 to Claude Code — operational refinements of rules already defined in `AGENTS.md`.
 

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 Thank you for your interest in contributing! This guide covers everything you need to get started.
 
 For the official per-change workflow, start with the
-[Contribution Golden Path](docs/dev/CONTRIBUTION_GOLDEN_PATH.md). It maps provider, routing,
+[Contribution Golden Path](docs/ops/CONTRIBUTION_GOLDEN_PATH.md). It maps provider, routing,
 UI/UX, i18n, CLI, database, and build/deploy changes to their contracts, focused tests, CI
 coverage, and reconciliation steps.
 
@@ -210,7 +210,7 @@ Coverage notes:
 ### Pull Request Requirements
 
 Before opening a PR, use the
-[Contribution Golden Path](docs/dev/CONTRIBUTION_GOLDEN_PATH.md) to run the focused loop for
+[Contribution Golden Path](docs/ops/CONTRIBUTION_GOLDEN_PATH.md) to run the focused loop for
 what you changed. The full unit suite (4 CI shards), Vitest, the **60%+** coverage gate, and
 the production build are CI's responsibility — running them locally adds no signal the PR
 checks will not already give you, and on smaller machines it can saturate the host (#8084):

GEMINI.md

@@ -1,7 +1,7 @@
 # GEMINI.md
 
 > **Single source of truth:** all project rules for AI assistants live in
-> [`AGENTS.md`](AGENTS.md). Read it in full before any change — it contains the 22 Hard Rules,
+> [`AGENTS.md`](AGENTS.md). Read it in full before any change — it contains the 23 Hard Rules,
 > quality gates, code conventions, file-placement / repo-root hygiene rules, the repository map
 > and the local development access notes that used to live in this file.
 

README.md

@@ -7,19 +7,19 @@
 
 # 🚀 OmniRoute — The Free AI Gateway
 
-<img src="./docs/diagrams/readme-hero.svg" width="100%" alt="OmniRoute — Never stop coding. Every AI tool → 291 providers — 90+ free — through one endpoint. Claude Code, Codex, Cursor, Cline, Copilot & Antigravity into FREE Claude / GPT / Gemini with auto-fallback. RTK + Caveman stacked compression saves 15–95% tokens (~89% avg) — never hit limits. 291 AI providers · 90+ free tiers · ~1.53B free tokens/mo · 19 routing strategies · $0 to start."/>
+<img src="./docs/diagrams/readme-hero.svg" width="100%" alt="OmniRoute — Never stop coding. Every AI tool → 338 providers — 90+ free — through one endpoint. Claude Code, Codex, Cursor, Cline, Copilot & Antigravity into FREE Claude / GPT / Gemini with auto-fallback. RTK + Caveman stacked compression saves 15–95% tokens (~89% avg) — never hit limits. 338 AI providers · 90+ free tiers · ~1.51B free tokens/mo · 19 routing strategies · $0 to start."/>
 
 </div>
 
 <div align="center">
 
-## 💰 ~1.53B Free Tokens / Month
+## 💰 ~1.51B Free Tokens / Month
 
 </div>
 
-> Stacking free tiers by hand is painful — dozens of SDKs, dozens of rate limits, and no idea how much you actually have. OmniRoute aggregates the **documented** free tiers of **43 provider pools / 516 models** into one honest number and shows it live on the dashboard (`/dashboard/free-tiers`).
+> Stacking free tiers by hand is painful — dozens of SDKs, dozens of rate limits, and no idea how much you actually have. OmniRoute aggregates the **documented** free tiers of **42 provider pools / 495 models** into one honest number and shows it live on the dashboard (`/dashboard/free-tiers`).
 
-<img src="./docs/diagrams/free-tier-budget.svg" width="100%" alt="OmniRoute free-tier budget card: ~1.53B free tokens per month steady, up to ~2.15B in the first month with signup credits, from the documented free tiers of 43 provider pools / 516 models behind one endpoint. Honest pool-deduped math — each shared pool counted once (counting every rate limit 24/7 would read ~10B; not published), 15 providers ToS-flagged so you decide. Budget bar of the countable free pools with per-model grid (Mistral Large 3 1B, GPT-4o mini 150M, Gemini 2.5 Flash 60M … Claude Sonnet 4.5 25K), one-time first-month signup credits (vertex 300M, agentrouter 200M, predibase 25M, together 25M, glm-cn 20M, doubao 15M, ai21 10M, longcat 10M, deepseek 5M, hyperbolic 5M, nscale 5M), plus permanently-free no-token-cap providers (SiliconFlow, Z.AI GLM-Flash, Kilo, OpenCode Zen, baidu …) and a $10 OpenRouter top-up unlocking +24M/mo — surfaced separately so they never inflate the headline. Live used/remaining on /dashboard/free-tiers."/>
+<img src="./docs/diagrams/free-tier-budget.svg" width="100%" alt="OmniRoute free-tier budget card: ~1.51B free tokens per month steady, up to ~2.13B in the first month with signup credits, from the documented free tiers of 42 provider pools / 495 models behind one endpoint. Honest pool-deduped math — each shared pool counted once (counting every rate limit 24/7 would read ~10B; not published), 15 providers ToS-flagged so you decide. Budget bar of the countable free pools with per-model grid (Mistral Large 3 1B, GPT-4o mini 150M, Gemini 2.5 Flash 60M … Claude Sonnet 4.5 25K), one-time first-month signup credits (vertex 300M, agentrouter 200M, predibase 25M, together 25M, glm-cn 20M, doubao 15M, ai21 10M, longcat 10M, deepseek 5M, hyperbolic 5M, nscale 5M), plus permanently-free no-token-cap providers (SiliconFlow, Z.AI GLM-Flash, Kilo, OpenCode Zen, baidu …) and a $10 OpenRouter top-up unlocking +24M/mo — surfaced separately so they never inflate the headline. Live used/remaining on /dashboard/free-tiers."/>
 
 > Animated summary of the live `/dashboard/free-tiers` page. Full methodology (pool dedupe, credit tiers, provider terms): **[docs/reference/FREE_TIERS.md](docs/reference/FREE_TIERS.md)**.
 >
@@ -56,6 +56,25 @@
 
 <br/>
 
+## 📈 The Gateway Keeps Growing
+
+<div align="center">
+
+|                           | v3.8.49 | **v3.8.50** | `v3.8.51+`  |
+| ------------------------- | :-----: | :---------: | :---------: |
+| 🌐 Providers              |   291   |   **338**   | more queued |
+| 🧠 Documented models      |  500+   |  **1200+**  |      —      |
+| 🖼️ Modality Bridge        |    —    |  🆕 vision  |    video    |
+| 📡 Radar free catalog     |    —    |      —      |   🔭 next   |
+| ⚖️ Quota-aware scheduling |    —    |      —      |   🔭 next   |
+| 📊 Quota telemetry        |    —    |      —      |   🔭 next   |
+
+**→ [Roadmap](ROADMAP.md) — riding the rail to `v3.9.0 LTS`**
+
+</div>
+
+<br/>
+
 ## 🧩 Available
 
 [![npm version](https://img.shields.io/npm/v/omniroute?color=cb3837&logo=npm)](https://www.npmjs.com/package/omniroute)
@@ -81,7 +100,7 @@
   <tr>
     <td align="right"><b>⚙️ Features</b></td>
     <td align="center"><a href="#-combos--the-flagship">🎯 Combos</a></td>
-    <td align="center"><a href="#-291-ai-providers--90-free">🌐 Providers</a></td>
+    <td align="center"><a href="#-338-ai-providers--90-free">🌐 Providers</a></td>
     <td align="center"><a href="#-full-cli--a2a--mcp">🔌 CLI &amp; MCP</a></td>
   </tr>
   <tr>
@@ -190,7 +209,7 @@ curl http://localhost:20128/v1/chat/completions \
 
 </div>
 
-<img src="./docs/diagrams/promise-pillars.svg" width="100%" alt="The Promise — One endpoint. 291 providers. Never stop building — OmniRoute picks the cheapest one that works. Six pillars: Never hit limits (auto-fallback across 291 providers in milliseconds, zero downtime) · Save up to 95% tokens (RTK + Caveman stacked compression cuts 15–95%, ~89% avg on tool-heavy sessions) · $0 to start (90+ free tiers, 40+ free forever — no card needed) · Every tool works (33 coding agents through one config) · One endpoint (OpenAI ↔ Claude ↔ Gemini ↔ Responses API at /v1) · Production-grade (circuit breakers, TLS stealth, MCP 105 tools, A2A, memory, guardrails, evals — 25,000+ tests)."/>
+<img src="./docs/diagrams/promise-pillars.svg" width="100%" alt="The Promise — One endpoint. 338 providers. Never stop building — OmniRoute picks the cheapest one that works. Six pillars: Never hit limits (auto-fallback across 338 providers in milliseconds, zero downtime) · Save up to 95% tokens (RTK + Caveman stacked compression cuts 15–95%, ~89% avg on tool-heavy sessions) · $0 to start (90+ free tiers, 40+ free forever — no card needed) · Every tool works (33 coding agents through one config) · One endpoint (OpenAI ↔ Claude ↔ Gemini ↔ Responses API at /v1) · Production-grade (circuit breakers, TLS stealth, MCP 105 tools, A2A, memory, guardrails, evals — 25,000+ tests)."/>
 
 <br/>
 <br/>
@@ -409,7 +428,7 @@ All **19** strategies — mix & match per combo step:
   <tr>
     <td align="center">17</td>
     <td nowrap><code>auto</code></td>
-    <td>12-factor live scoring across every connection 🤖</td>
+    <td>14-factor live scoring across every connection 🤖</td>
   </tr>
   <tr>
     <td align="center">18</td>
@@ -423,7 +442,7 @@ All **19** strategies — mix & match per combo step:
   </tr>
 </table>
 
-<sub>The Auto-Combo engine scores every candidate on **12 factors** (health, quota, cost, latency, success rate, freshness…) — see [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md).</sub>
+<sub>The Auto-Combo engine scores every candidate on **14 factors** (health, quota, cost, latency, success rate, freshness…) — see [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md).</sub>
 
 ##
 
@@ -441,7 +460,7 @@ All **19** strategies — mix & match per combo step:
 
 </div>
 
-<img src="./docs/diagrams/comparison-table.svg" width="100%" alt="What sets OmniRoute apart — comparison table vs 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute: 291 providers, 90+ free providers built-in, 19 routing strategies, 12-engine token compression, built-in MCP server with 105 tools, A2A agent protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, Desktop/Termux/PWA, 43 i18n UI locales, 100% MIT self-hosted. OmniRoute is the only one with the full set; competitors show a mix of checks, partials and crosses. Verified from each project&apos;s docs."/>
+<img src="./docs/diagrams/comparison-table.svg" width="100%" alt="What sets OmniRoute apart — comparison table vs 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute: 338 providers, 90+ free providers built-in, 19 routing strategies, 12-engine token compression, built-in MCP server with 105 tools, A2A agent protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, Desktop/Termux/PWA, 43 i18n UI locales, 100% MIT self-hosted. OmniRoute is the only one with the full set; competitors show a mix of checks, partials and crosses. Verified from each project&apos;s docs."/>
 
 <sub>📊 Full methodology &amp; per-feature detail vs 9router, OpenRouter, CLIProxyAPI &amp; LiteLLM → [`docs/comparison/OMNIROUTE_VS_ALTERNATIVES.md`](docs/comparison/OMNIROUTE_VS_ALTERNATIVES.md)</sub>
 
@@ -499,8 +518,11 @@ Pix copia-e-cola:
 
 </div>
 
-> Recent highlights from **v3.8.20 → v3.8.49**. Full history in [`CHANGELOG.md`](CHANGELOG.md).
+> Recent highlights from **v3.8.20 → v3.8.50**. Full history in [`CHANGELOG.md`](CHANGELOG.md).
 
+- **🎛️ OmniConductor** — inbound A2A delegation to your agent fleet, Conductor skills on the Agent Card, and a dashboard panel with Faro push-to-talk voice chat. → [A2A Server](docs/frameworks/A2A-SERVER.md)
+- **🛂 Adaptive admission & overload protection** — heavyweight chat requests queue instead of 503ing, with atomic RPM rolling leases per connection. → [Resilience Guide](docs/architecture/RESILIENCE_GUIDE.md)
+- **🗂️ Canonical `/v1/models` ordering** — one contiguous provider-grouped block per provider (combos pinned first), stable across every catalog source. → [API Reference](docs/reference/API_REFERENCE.md)
 - **🗜️ Compression hardening** — default-on inflation guard, Caveman packs for DE / FR / JA + Chinese (wényán), RTK filters for Gradle & .NET. → [Compression](docs/compression/COMPRESSION_ENGINES.md)
 - **💸 Honest flat-rate cost** — subscription / coding-plan providers read **$0** in cost analytics; budget, quota & routing keep estimating. → [API Reference](docs/reference/API_REFERENCE.md)
 - **⚖️ Quota-Share routing** — split a shared account's quota fairly across pooled keys, work-conserving so idle slices are lent out. → [Resilience Guide](docs/architecture/RESILIENCE_GUIDE.md)
@@ -515,7 +537,7 @@ Pix copia-e-cola:
 - **🖼️ New endpoints** — `/v1/ocr` (Mistral OCR) and `/v1/audio/translations` (Whisper-style) round out the media surface. → [API Reference](docs/reference/API_REFERENCE.md)
 - **🎨 Image / video / audio generation** — one API for media: xAI Grok Imagine & Novita AI video, ComfyUI, Freepik, Adobe Firefly, Microsoft Designer, Google Imagen, Segmind, EdgeTTS. → [API Reference](docs/reference/API_REFERENCE.md)
 - **🌍 Deployment & ops** — reverse-proxy `basePath`, browser-language auto-detect, per-key device tracking, root-less MITM trust, zh-TW localization. → [Environment](docs/reference/ENVIRONMENT.md)
-- **🤝 More providers & agents** — Cursor Cloud Agent, Grok Build (xAI) with browser + OAuth login, Ollama first-class card, Claude Opus 5 & Sonnet 5, Kimi official partnership (Code/Web/Moonshot), Zed, Requesty, SenseNova, Yuanbao, Agnes AI… and a refreshed **291-provider catalog**. → [Providers](docs/reference/PROVIDER_REFERENCE.md)
+- **🤝 More providers & agents** — Cursor Cloud Agent, Grok Build (xAI) with browser + OAuth login, Ollama first-class card, Claude Opus 5 & Sonnet 5, Kimi official partnership (Code/Web/Moonshot), Zed, Requesty, SenseNova, Yuanbao, Agnes AI… and a refreshed **338-provider catalog**. → [Providers](docs/reference/PROVIDER_REFERENCE.md)
 - **📡 Routing transparency** — every response carries an `X-OmniRoute-Decision` header naming the strategy/provider/latency that served it, a new `cache-optimized` combo strategy + Auto-Combo `cacheAffinity` factor route repeat requests back to the connection holding the cached prefix, and a read-only `/v1/auto-combo/{channel}/candidates` endpoint exposes an `auto/*` channel's live candidate pool. → [Auto-Combo](docs/routing/AUTO-COMBO.md)
 - **⚡ Local performance & infra** — one-click local Redis, Cloudflare Workers / Deno Deploy relay deployers, Bifrost & Mux as supervised embedded services. → [Embedded Services](docs/frameworks/EMBEDDED-SERVICES.md)
 
@@ -576,11 +598,11 @@ Pix copia-e-cola:
 
 <div align="center">
 
-## 🌐 291 AI Providers — 90+ Free
+## 🌐 338 AI Providers — 90+ Free
 
 </div>
 
-> The most complete catalog of any open-source router: **291 providers**, **90+ with a free tier**, **40+ free forever**.
+> The most complete catalog of any open-source router: **338 providers**, **90+ with a free tier**, **40+ free forever**.
 
 <div align="center">
 
@@ -844,7 +866,7 @@ npm install -g omniroute
 omniroute
 ```
 
-> 💡 See `npm warn ERESOLVE` or peer-dep warnings? [They're harmless](docs/getting-started/TROUBLESHOOTING.md#npm-install-warnings-eresolve--peer--deprecated).
+> 💡 See `npm warn ERESOLVE` or peer-dep warnings? [They're harmless](docs/guides/TROUBLESHOOTING.md#npm-install-warnings-eresolve--peer--deprecated).
 
 Dashboard at `http://localhost:20128` · API at `http://localhost:20128/v1`.
 
@@ -896,7 +918,7 @@ docker run -d --name omniroute --restart unless-stopped --stop-timeout 40 \
 > `diegosouzapw/omniroute:next-web` follow the current default `release/v*`
 > branch. These mutable tags are intended only for testing unreleased fixes and
 > are **not supported for production**. See
-> [Docker Release Channels](docs/guides/DOCKER_RELEASE_CHANNELS.md).
+> [Docker Release Channels](docs/guides/DOCKER_GUIDE.md#release-channels).
 
 **🛠️ From source**
 
@@ -1038,7 +1060,7 @@ same process on one port, so there is no separate CLI-only package today.
   <tr><td nowrap><b>Runtime</b></td><td>Node.js 22.x / 24.x LTS — <code>&gt;=22.22.2 &lt;23 || &gt;=24.0.0 &lt;27</code></td></tr>
   <tr><td nowrap><b>Language</b></td><td>TypeScript 6.0 — <b>100% TypeScript</b> across <code>src/</code> and <code>open-sse/</code> (zero <code>any</code> in core since v2.0)</td></tr>
   <tr><td nowrap><b>Framework</b></td><td>Next.js 16 + React 19 + Tailwind CSS 4</td></tr>
-  <tr><td nowrap><b>Database</b></td><td>better-sqlite3 (SQLite, WAL journaling) + LowDB (JSON legacy) — 95 domain modules, 110 migrations</td></tr>
+  <tr><td nowrap><b>Database</b></td><td>better-sqlite3 (SQLite, WAL journaling) + LowDB (JSON legacy) — 95 domain modules, 144 migrations</td></tr>
   <tr><td nowrap><b>Memory</b></td><td>SQLite FTS5 full-text + int8-quantized vector embeddings, typed decay</td></tr>
   <tr><td nowrap><b>Schemas</b></td><td>Zod 4 — MCP tool I/O validation + API contracts</td></tr>
   <tr><td nowrap><b>Protocols</b></td><td>MCP (stdio / HTTP / SSE) + A2A v0.3 (JSON-RPC 2.0 + SSE)</td></tr>
@@ -1099,9 +1121,9 @@ same process on one port, so there is no separate CLI-only package today.
   <tr><td nowrap><b><a href="docs/compression/COMPRESSION_RULES_FORMAT.md">Compression Rules Format</a></b></td><td>JSON rule-pack schemas for Caveman and RTK filters</td></tr>
   <tr><td nowrap><b><a href="docs/compression/COMPRESSION_LANGUAGE_PACKS.md">Compression Language Packs</a></b></td><td>Language detection and Caveman rule-pack authoring</td></tr>
   <tr><td nowrap><b><a href="docs/architecture/RESILIENCE_GUIDE.md">Resilience Guide</a></b></td><td>Circuit breakers, cooldowns, queue, anti-thundering herd, TLS spoofing</td></tr>
-  <tr><td nowrap><b><a href="docs/routing/AUTO-COMBO.md">Auto-Combo Engine</a></b></td><td>12-factor scoring, mode packs, self-healing</td></tr>
+  <tr><td nowrap><b><a href="docs/routing/AUTO-COMBO.md">Auto-Combo Engine</a></b></td><td>14-factor scoring, mode packs, self-healing</td></tr>
   <tr><td nowrap><b><a href="docs/ops/PROXY_GUIDE.md">Proxy Guide</a></b></td><td>3-level proxy system, 1proxy marketplace, registry CRUD</td></tr>
-  <tr><td nowrap><b><a href="docs/reference/FREE_TIERS.md">Free Tiers</a></b></td><td>25+ free API providers consolidated directory</td></tr>
+  <tr><td nowrap><b><a href="docs/reference/FREE_TIERS.md">Free Tiers</a></b></td><td>90+ free providers consolidated directory (42 documented token pools / 495 models)</td></tr>
   <tr><td nowrap><b><a href="docs/guides/FEATURES.md">Features Gallery</a></b></td><td>Visual dashboard tour with screenshots</td></tr>
   <tr><td nowrap><b><a href="docs/architecture/CODEBASE_DOCUMENTATION.md">Codebase Documentation</a></b></td><td>Beginner-friendly codebase walkthrough</td></tr>
 </table>
@@ -1112,7 +1134,7 @@ same process on one port, so there is no separate CLI-only package today.
   <tr><th align="left">Document</th><th align="left">Description</th></tr>
   <tr><td nowrap><b><a href="docs/reference/API_REFERENCE.md">API Reference</a></b></td><td>All endpoints with examples</td></tr>
   <tr><td nowrap><b><a href="docs/openapi.yaml">OpenAPI Spec</a></b></td><td>OpenAPI 3.0 specification</td></tr>
-  <tr><td nowrap><b><a href="open-sse/mcp-server/README.md">MCP Server</a></b></td><td>104 MCP tools, IDE configs, Python/TS/Go clients</td></tr>
+  <tr><td nowrap><b><a href="open-sse/mcp-server/README.md">MCP Server</a></b></td><td>105 MCP tools, IDE configs, Python/TS/Go clients</td></tr>
   <tr><td nowrap><b><a href="docs/frameworks/MCP-SERVER.md">MCP Server Guide</a></b></td><td>MCP installation, transports, and tool reference</td></tr>
   <tr><td nowrap><b><a href="src/lib/a2a/README.md">A2A Server</a></b></td><td>JSON-RPC 2.0 protocol, skills, streaming, task mgmt</td></tr>
   <tr><td nowrap><b><a href="docs/frameworks/A2A-SERVER.md">A2A Server Guide</a></b></td><td>A2A agent card, tasks, skills, and streaming</td></tr>
@@ -1126,7 +1148,7 @@ same process on one port, so there is no separate CLI-only package today.
   <tr><td nowrap><b><a href="docs/ops/BRANCHING_MODEL.md">Branching & Release Model</a></b></td><td>Where PRs target (<code>release/*</code>), what <code>main</code> and tags mean</td></tr>
   <tr><td nowrap><b><a href="CHANGELOG.md">Changelog</a></b></td><td>Full per-version release history</td></tr>
   <tr><td nowrap><b><a href="SECURITY.md">Security Policy</a></b></td><td>Vulnerability reporting and security practices</td></tr>
-  <tr><td nowrap><b><a href="docs/guides/I18N.md">i18n Guide</a></b></td><td>40+ language support, translation workflow, RTL</td></tr>
+  <tr><td nowrap><b><a href="docs/guides/I18N.md">i18n Guide</a></b></td><td>43-language support, translation workflow, RTL</td></tr>
   <tr><td nowrap><b><a href="docs/ops/RELEASE_CHECKLIST.md">Release Checklist</a></b></td><td>Pre-release validation steps</td></tr>
   <tr><td nowrap><b><a href="docs/ops/COVERAGE_PLAN.md">Coverage Plan</a></b></td><td>Test coverage strategy and 25,000+ test suite</td></tr>
 </table>
@@ -1269,7 +1291,7 @@ A heartfelt thank-you to the people who fund OmniRoute out of their own pocket
 
 <div align="center">
 
-## 👥 500+ Contributors
+## 👥 320+ Contributors
 
 </div>
 

ROADMAP.md

@@ -7,7 +7,7 @@ lastUpdated: 2026-08-06
 # OmniRoute Roadmap
 
 > Version-gated, not date-gated: each milestone ships when its quality gates pass.
-> Current line: **v3.8.x** (this branch). Last updated: 2026-07-23.
+> Current line: **v3.8.x** (this branch). Last updated: 2026-08-06.
 
 OmniRoute is heading from a monolithic router to a **modular AI platform**: a lightweight
 core engine, a typed SDK, and everything else as installable modules and plugins. The path

_references/_sistemas_cli/01-relatorio-pesquisa-clis-omniroute.md

@@ -1,296 +0,0 @@
-# Relatorio de pesquisa: repositorios de CLI integraveis com OmniRoute
-
-> **Status final (2026-08-03):** este documento preserva o inventário inicial. A pesquisa foi concluída para `104/104` casos. Para resultados por projeto, use `04-tracker-integracoes-clis.md`; para o fechamento executivo e a estratégia de publicação, use `06-relatorio-final-104-clis-e-estrategia-prs.md`.
-
-**Data da pesquisa:** 2026-08-01  
-**Escopo:** agentes de codigo de terminal, CLIs de LLM, runtimes de agentes e harnesses que possam consumir um endpoint HTTP compativel com OpenAI, Anthropic ou Gemini, ou que possam ser adaptados por provider/plugin/ACP/MITM.  
-**Fonte local principal:** `_tasks/hands-off/2026-08-01_release-v3.8.50_v3.8.50_sess-e1846bc2/handoff.md`  
-**Fontes externas principais:** GitHub Search/API, READMEs dos repositorios e a lista publica `bradAGI/awesome-cli-coding-agents` (atualizada em 2026-07-29).
-
-## 1. Resumo executivo
-
-O OmniRoute ja possui uma integracao funcional com o jcode e um catalogo local de ferramentas CLI. O proximo ganho de maior valor e transformar o OmniRoute em um endpoint reconhecido pelos principais agentes de terminal, priorizando configuracao nativa e PR upstream quando o projeto aceitar contribuicoes.
-
-A pesquisa encontrou:
-
-- **33 entradas de ferramentas no registro local `CLI_TOOLS`**, contando o registro extraido de Grok Build em `src/shared/constants/cliToolsGrokBuild.ts`, incluindo Claude Code, Codex CLI, Cline, Kilo, Continue, OpenCode, Aider, jcode, Smelt, Pi, Crush, Goose, Open Interpreter, OpenClaw, Hermes Agent, Letta CLI e outros.
-- **Mais de 90 projetos publicos** no inventario externo consultado, entre agentes de codigo, CLIs generalistas, forks, runtimes e orquestradores.
-- **Candidatos com evidencia forte de endpoint customizavel:** Gemini CLI, Claw Code, Plandex, MiMo Code, Trae Agent, Kimi CLI, Every Code, Open Codex, VT Code, OpenHands CLI, gptme, Nanocoder, RA.Aid, CoreCoder, Grok CLI, Gitlawb Zero, DeepSeek Reasonix, KlaatCode, CodeMini, DvalinCode, Coro Code, Mini-Kode, Late CLI, Agentty, Aizen, Minacode, YottaCode, aichat, ShellGPT, Mistral Vibe, OpenSquilla, Kode CLI e outros.
-- **Candidatos que exigem pesquisa confirmatoria:** projetos com README generico, configuracao recente, repositorio ambiguo, binario fechado ou sem evidencia textual suficiente de `base_url`/provider.
-- **Candidatos que podem ser integrados por outros caminhos:** ACP, MCP, wrapper/launcher, provider adapter, proxy MITM ou apenas documentacao; eles nao devem ser classificados automaticamente como OpenAI-compatible.
-
-Conclusao: devemos pesquisar e tentar todos os candidatos tecnicamente viaveis, mas separar claramente `suporte no catalogo OmniRoute`, `configuracao generica`, `adaptacao upstream publicada` e `PR/issue aceita`. O tracker acompanha essas dimensoes separadamente.
-
-## 2. Metodo e limites
-
-### 2.1 Como a busca foi feita
-
-1. Leitura integral do handoff do caso jcode para capturar o padrao de integracao, validacao, publicacao e as restricoes de worktree.
-2. Inspecao do catalogo local em `src/shared/constants/cliTools.ts`, da documentacao de CLI e do fluxo de setup em `docs/guides/CLI-INTEGRATIONS.md`.
-3. Consulta do GitHub Search/API para resolver o repositorio canonico de cada nome, evitando homonimos.
-4. Leitura de README/raw quando disponivel, procurando sinais como `base_url`, `baseURL`, `OPENAI_BASE_URL`, `OPENAI_API_BASE`, `LLM_BASE_URL`, `provider`, `gateway`, `model provider`, `Anthropic` e `Gemini`.
-5. Consulta da lista `https://github.com/bradAGI/awesome-cli-coding-agents`, que serve como descoberta ampla, nao como prova de compatibilidade.
-6. Classificacao por adocao, manutencao, licenca, evidencia de endpoint, maturidade, potencial de PR e utilidade para o ecossistema OmniRoute.
-
-### 2.2 O que ainda nao foi afirmado
-
-- Nao foi feita implementacao ou abertura de PR/issue para os candidatos abaixo; o unico caso publicado nesta sessao anterior e o jcode.
-- A presenca da palavra `provider` no README nao prova que uma URL arbitraria funciona em runtime.
-- Estrelas e datas sao snapshots aproximados obtidos em 2026-08-01 e podem mudar.
-- Repositorios fechados ou com EULA entram no inventario para avaliacao de configuracao, mas nao implicam possibilidade de fork ou PR.
-- Cada task de integracao precisa repetir a pesquisa no upstream antes de editar codigo.
-
-## 3. Baseline do OmniRoute
-
-### 3.1 Superficie que o OmniRoute oferece
-
-- Endpoint OpenAI em `/v1`.
-- Superficie Anthropic na raiz, usada por clientes que esperam `/v1/messages` a partir do `ANTHROPIC_BASE_URL`.
-- Superficie Gemini em `/v1beta`.
-- Catalogo de modelos consultavel pelos comandos de setup quando o cliente suporta descoberta.
-- Chave via `OMNIROUTE_API_KEY` ou chave selecionada no dashboard.
-- Traducao entre formatos, streaming SSE, tool calling, fallback, combos, custos e politicas de autenticacao.
-- Modos de consumo: configuracao de ambiente, arquivo nativo do cliente, provider customizado, ACP/MCP e MITM.
-
-### 3.2 Catalogo local ja registrado
-
-Fonte: `src/shared/constants/cliTools.ts` e `src/shared/constants/cliToolsGrokBuild.ts`.
-
-**Codigo/CLI:** Claude Code, OpenAI Codex CLI, Factory Droid, OpenClaw, Cursor, Cline, Kilo Code, Continue, Antigravity, GitHub Copilot CLI, OpenCode, Kiro, Qwen Code, Aider, ForgeCode, Cursor Agent CLI, Roo Code, jcode, DeepSeek TUI, CodeWhale, Smelt, Pi, Crush.
-
-**Agentes:** Hermes, Hermes Agent, Goose, Open Interpreter, Oh My Pi, Letta CLI, Warp AI, Agent Deck.
-
-Os documentos do catalogo tambem mantem um backlog MITM para ferramentas sem base URL, como Windsurf, Amp, Amazon Q/Kiro CLI e Cowork. Esses casos devem permanecer separados de uma integracao direta.
-
-### 3.3 Caso jcode (referencia validada)
-
-- Upstream: `https://github.com/1jehuang/jcode`
-- Mecanismo: perfil OpenAI-compatible dirigido por metadados; nao foi criado um plugin de runtime.
-- Branch: `feat/omniroute-provider`
-- Commit: `ee4f904e6`
-- PR no fork: `https://github.com/diegosouzapw/jcode/pull/1`
-- Issue no upstream: `https://github.com/1jehuang/jcode/issues/704`
-- Diff: 6 arquivos, `+56/-3`.
-- Validacao: `cargo check --workspace` limpo; 205 testes passaram e uma falha foi preexistente/ambiental.
-- Estado: aguardando mantenedor; o upstream nao aceita PR de forks externos, por isso a issue e o artefato oficial.
-- Pendencia prometida: adicionar no README do OmniRoute a secao "Tools & repositories that work with OmniRoute".
-
-Licao: o trabalho deve comecar descobrindo o mecanismo real de providers do upstream. Nem todos os clientes precisam de mudanca no OmniRoute; alguns precisam somente de um perfil local, e outros exigirao um adaptador especifico.
-
-## 4. Candidatos prioritarios com evidencia concreta
-
-As evidencias abaixo sao sinais de README/configuracao observados na pesquisa inicial. A task individual deve abrir o arquivo exato, confirmar a versao atual e executar um smoke test.
-
-| Projeto | Repositorio | Evidencia inicial | Rota provavel |
-|---|---|---|---|
-| Gemini CLI | `google-gemini/gemini-cli` | `GOOGLE_GEMINI_BASE_URL` | configuracao direta; possivel PR/documentacao |
-| Claw Code | `ultraworkers/claw-code` | `OPENAI_BASE_URL`, provider compativel | configuracao direta ou provider |
-| Plandex | `plandex-ai/plandex` | providers customizados com `baseUrl` | provider/preset |
-| MiMo Code | `XiaomiMiMo/MiMo-Code` | `@ai-sdk/openai-compatible` e `baseURL` | provider customizado |
-| Trae Agent | `bytedance/trae-agent` | `model_providers` e `base_url` | provider/config |
-| Kimi CLI | `MoonshotAI/kimi-cli` | modos `openai_legacy`, `openai_responses`, `anthropic` e `base_url` | provider nativo/config |
-| Every Code | `just-every/code` | fork Codex com providers OpenAI/Claude/Gemini | perfil/provider |
-| Open Codex | `ymichael/open-codex` | multi-provider e OpenAI-compatible | fork/provider |
-| VT Code | `vinhnx/vtcode` | `custom_providers[].base_url`, failover | provider customizado |
-| OpenHands CLI | `OpenHands/OpenHands-CLI` | `LLM_BASE_URL` | configuracao direta |
-| gptme | `gptme/gptme` | `OPENAI_BASE_URL` e providers | configuracao direta |
-| Nanocoder | `Nano-Collective/nanocoder` | qualquer API OpenAI-compatible | configuracao direta |
-| RA.Aid | `ai-christianson/RA.Aid` | `OPENAI_API_BASE` | configuracao direta |
-| CoreCoder | `he-yufeng/CoreCoder` | `OPENAI_BASE_URL` | configuracao direta |
-| Grok CLI | `superagent-ai/grok-cli` | `GROK_BASE_URL`/`baseURL` | configuracao direta |
-| Gitlawb Zero | `Gitlawb/zero` | provider `custom-openai-compatible`, `--base-url` | provider/flag |
-| DeepSeek Reasonix | `esengine/DeepSeek-Reasonix` | provider compativel e endpoint | confirmar configuracao |
-| KlaatCode | `KlaatAI/klaatcode` | `customModels` OpenAI-compatible | configuracao JSON |
-| CodeMini CLI | `havingautism/Codemini-CLI` | `gateway.base_url` | gateway/config |
-| Zot | `patriceckhart/zot` | `--base-url` e provider custom em `models.json` | flag/config |
-| Pool | `poolsideai/pool` | `POOLSIDE_STANDALONE_BASE_URL`; licenca proprietaria | configuracao, sem PR assumido |
-| Octomind | `Muvon/octomind` | `<PROVIDER>_API_URL`/`LOCAL_API_URL` | provider/env |
-| Coro Code | `Blushyes/coro-code` | `OPENAI_BASE_URL` | configuracao direta |
-| Mini-Kode | `minmaxflow/mini-kode` | `MINIKODE_BASE_URL` | configuracao direta |
-| Late CLI | `mlhher/late-cli` | `OPENAI_BASE_URL`/`api-url` | env/flag |
-| Agentty | `1ay1/agentty` | modelo agnostico e endpoints compativeis | confirmar arquivo de config |
-| Aizen | `aizen-stack/aizen` | CLI Rust OpenAI-compatible; `AIZEN_BASE_URL` | configuracao direta |
-| Clif-Code | `DLhugly/Clif-Code` | OpenRouter/OpenAI/Anthropic/Ollama | provider/config |
-| Minacode | `hit9/minacode` | provider e compatibilidade no README | confirmar URL |
-| YottaCode | `yottadynamics/yottacode` | modelo escolhido, gateway/provider | confirmar config |
-| aichat | `sigoden/aichat` | providers OpenAI/Claude/Gemini e compatibilidade | `models.yaml`/provider |
-| ShellGPT | `TheR1D/shell_gpt` | `API_BASE_URL` | env/config |
-| Mistral Vibe | `mistralai/mistral-vibe` | `base_url`, API base e provider | config/env |
-| OpenSquilla | `opensquilla/opensquilla` | 20+ providers e gateway | provider/config |
-| Kode CLI | `shareAI-lab/Kode-cli` | provider, endpoint e Anthropic/OpenAI/Gemini | config |
-| Crush | `charmbracelet/crush` | `base_url`, provider compativel | ja catalogado no OmniRoute; validar upstream |
-| Hermes Agent | `NousResearch/hermes-agent` | endpoint/gateway e 300+ modelos | ja catalogado; validar modo de endpoint |
-| OpenClaw | `openclaw/openclaw` | providers, gateway e endpoints | ja catalogado; validar configuracao atual |
-
-## 5. Inventario amplo localizado
-
-### 5.1 Agentes de terminal e coding CLIs
-
-Os projetos desta tabela foram encontrados na lista curada ou no GitHub Search. `Pesquisa` indica o proximo gate; nao significa que a integracao ja esta pronta.
-
-| Projeto | Repositorio | Licenca/sinal publico | Situacao inicial |
-|---|---|---|---|
-| OpenCode | `anomalyco/opencode` | multi-provider, 75+ providers | ja suportado; acompanhar provider/plugin |
-| Codex CLI | `openai/codex` | Apache-2.0, provider configuravel | ja suportado |
-| OpenHands principal | `All-Hands-AI/OpenHands` | OSS, CLI e web | pesquisar CLI e `LLM_BASE_URL` |
-| Pi | `badlogic/pi-mono` | harness multi-provider | ja suportado; confirmar repo atual |
-| Open Interpreter | `OpenInterpreter/open-interpreter` | Apache-2.0, `--api_base` | ja suportado |
-| Cline | `cline/cline` | Apache-2.0, base URL/gateway | ja suportado |
-| Goose | `aaif-goose/goose` | Apache-2.0, providers | ja suportado |
-| Aider | `Aider-AI/aider` | Apache-2.0, Anthropic/OpenAI | ja suportado |
-| Continue | `continuedev/continue` | Apache-2.0, multi-model | ja suportado |
-| Deep Agents Code | `langchain-ai/deepagents` | MIT, tool-calling LLM | pesquisar pacote `deepagents-code` |
-| Crush | `charmbracelet/crush` | provider/base URL | ja suportado |
-| Kilo Code | `Kilo-Org/kilocode` | MIT, providers | ja suportado |
-| Qwen Code | `QwenLM/qwen-code` | Apache-2.0, providers | ja suportado |
-| Roo Code | `RooCodeInc/Roo-Code` | Apache-2.0 | ja catalogado; validar CLI |
-| Grok Build | `xai-org/grok-build` | Apache-2.0, provider | ja suportado |
-| Oh My Pi | `can1357/oh-my-pi` | provider custom em YAML | ja suportado |
-| SWE-agent | `SWE-agent/SWE-agent` | MIT | pesquisar backend e base URL |
-| Smol Developer | `smol-ai/developer` | embeddable agent | adapter/SDK, nao necessariamente CLI |
-| Claude Engineer | `Doriandarko/claude-engineer` | CLI Claude | pesquisar provider |
-| Claurst | `Kuberwastaken/claurst` | GPL-3.0, provider | confirmar endpoint e politica de fork |
-| Free Code | `paoloanzn/free-code` | fork de Claude Code | pesquisar licenca e endpoint |
-| Codebuff | `CodebuffAI/codebuff` | multi-agent CLI | pesquisar provider |
-| ForgeCode | `antinomyhq/forge` | 300+ modelos | ja suportado |
-| OpenSquilla | `opensquilla/opensquilla` | Apache-2.0, gateway | candidato forte |
-| Kode CLI | `shareAI-lab/Kode-cli` | Apache-2.0, endpoint | candidato forte |
-| Devon | `entropy-research/Devon` | pair programmer TUI | pesquisar backend |
-| AutoCodeRover | `AutoCodeRoverSG/auto-code-rover` | agente de issues | pesquisar configuracao de modelos |
-| Letta Code | `letta-ai/letta-code` | Apache-2.0, model-agnostic | pesquisar API base |
-| CodeMachine CLI | `moazbuilds/CodeMachine-CLI` | multi-agent local | pesquisar provider |
-| Codel | `semanser/codel` | AGPL-3.0, Docker/web UI | confirmar servidor OpenAI e restricoes AGPL |
-| Agentless | `OpenAutoCoder/Agentless` | workflow sem loop persistente | pesquisar entrada de modelo |
-| Amazon Q Developer CLI | `aws/amazon-q-developer-cli` | Apache-2.0 | provavelmente auth/ecossistema AWS; pesquisar |
-| Neovate Code | `neovateai/neovate-code` | MIT, plugin/multi-provider | candidato forte |
-| Groq Code CLI | `build-with-groq/groq-code-cli` | multi-model | pesquisar endpoint |
-| Dexto | `truffle-ai/dexto` | CLI/web/API, subagentes | pesquisar provider |
-| claw-code-agent | `HarnessLab/claw-code-agent` | Python, sem dependencias | confirmar endpoint |
-| g3 | `dhanji/g3` | Rust, provider abstraction | confirmar licenca e URL |
-| Coro Code | `Blushyes/coro-code` | base URL/OpenAI | candidato |
-| Mini-Kode | `minmaxflow/mini-kode` | MIT, referencia educacional | candidato |
-| zot | `patriceckhart/zot` | MIT, TUI/JSON/RPC | candidato |
-| agentty | `1ay1/agentty` | MIT, ACP e multi-provider | candidato |
-| nori-cli | `tilework-tech/nori-cli` | multi-provider sobre Codex | pesquisar base URL |
-| cursor-agent clone | `civai-technologies/cursor-agent` | OpenAI/Claude/Ollama | pesquisar maturidade e licenca |
-| DvalinCode | `arthurpanhku/dvalincode` | MIT, OpenAI-compatible | candidato |
-| OpenHarness | `zhijiewong/openharness` | Apache-2.0, any LLM | candidato |
-| Octomind | `Muvon/octomind` | Apache-2.0, 13+ providers | candidato |
-| Codex Infinity | `lee101/codex-infinity` | fork Codex | pesquisar endpoint |
-| San | `genai-io/san` | Apache-2.0, provider-neutral | pesquisar endpoint |
-| Waveloom | `Menfre01/waveloom` | Apache-2.0, DeepSeek-focused | pesquisar provider |
-| picocode | `jondot/picocode` | Rust, multi-LLM | pesquisar provider |
-| QQCode | `qnguyen3/qqcode` | Rust, skills | pesquisar provider |
-| Keen Code | `mochow13/keen-code` | MIT, 9+ providers | pesquisar provider |
-| Smelt | `leonardcser/smelt` | MIT, OpenAI-compatible | ja suportado |
-| Grinta | `josephsenior/Grinta-Coding-Agent` | MIT, Python | pesquisar provider |
-| Zap | `zap-coding-agent/zap-coding-agent` | MIT, MCP, local/OpenAI | pesquisar endpoint |
-| Binharic | `CogitatorTech/binharic-cli` | multi-provider | pesquisar endpoint |
-| Darce | `AmerSarhan/darce-cli` | MIT, multi-model | pesquisar endpoint |
-| CLAII | `agencyswarm/CLAII` | multi-agent/MCP | pesquisar endpoint |
-
-### 5.2 Agentes generalistas e ecossistema OpenClaw
-
-Estes podem consumir OmniRoute como backend, mas a task deve confirmar se a interface de configuracao e realmente uma CLI de codigo ou apenas um gateway de agente.
-
-| Projeto | Repositorio | Possivel caminho |
-|---|---|---|
-| OpenClaw | `openclaw/openclaw` | provider/gateway; ja catalogado |
-| nanobot | `HKUDS/nanobot` | provider OpenAI-compatible |
-| ZeroClaw | `zeroclaw-labs/zeroclaw` | trait de provider |
-| NanoClaw | `gavrielc/nanoclaw` | Anthropic SDK; pesquisar base |
-| PicoClaw | `sipeed/picoclaw` | provider/config |
-| IronClaw | `nearai/ironclaw` | provider Rust |
-| NullClaw | `nullclaw/nullclaw` | 23+ providers |
-| Clawith | `dataelement/Clawith` | gateway/teams |
-| claw0 | `shareAI-lab/claw0` | tutorial/runtime; pesquisa de viabilidade |
-| Moltis | `moltis-org/moltis` | provider Rust |
-| GitClaw | `open-gitagent/gitclaw` | agente Git-native; pesquisar |
-| LionClaw | `moshthepitt/lionclaw` | CLI local; pesquisar |
-| Aizen | `aizen-stack/aizen` | OpenAI-compatible |
-| aichat | `sigoden/aichat` | provider/model YAML |
-| ShellGPT | `TheR1D/shell_gpt` | `API_BASE_URL` |
-| gptme | `gptme/gptme` | `OPENAI_BASE_URL` |
-
-### 5.3 Orquestradores, wrappers e ferramentas adjacentes
-
-Nao sao todos alvos de um provider OmniRoute. Devem ser avaliados para launcher, ACP, MCP, observabilidade ou configuracao de seus agentes filhos.
-
-| Projeto | Repositorio | Tipo de integracao a investigar |
-|---|---|---|
-| Agent Deck | `asheshgoplani/agent-deck` | config dos CLIs filhos; ja catalogado |
-| VibePod | `VibePod/vibepod-cli` | wrapper Docker e metricas |
-| zeroshot | `the-open-engine/zeroshot` | launcher/worktrees |
-| Fractal | `plasma-ai/fractal` | orquestrador de CLIs |
-| Bernstein | `chernistry/bernstein` | orquestrador/verificador |
-| Traycer | `traycerai/traycer` | CLI custom e agentes filhos |
-| h5i | `h5i-dev/h5i` | execucao paralela |
-| OMK | `dmae97/open-multi-agent-kit` | control plane/provider-neutral |
-| kodo | `ikamensh/kodo` | orquestrador |
-| ORCH | `oxgeneral/ORCH` | fila de tarefas |
-| LoopTroop | `LoopTroop-ai/LoopTroop` | orchestration sobre OpenCode |
-| Galley | `shinpr/galley` | worktree/PR handoff |
-| Relay | `jcast90/relay` | MCP/orquestracao |
-| sage | `youwangd/SageCLI` | runtime-agnostic |
-| 5dive | `5dive-ai/5dive` | agentes em servidor |
-| agx | `ramarlina/agx` | checkpoints e agentes |
-| claude-code-router | `musistudio/claude-code-router` | proxy/roteamento; possivel upstream consumidor |
-| cc-router | `finch-xu/cc-router` | proxy Anthropic multi-provider |
-| OneCLI | `onecli/onecli` | broker de credenciais, nao agente |
-| agent-browser | `vercel-labs/agent-browser` | ferramenta MCP/plugin |
-| OpenWork | `different-ai/openwork` | desktop sobre OpenCode |
-| Mistral Vibe | `mistralai/mistral-vibe` | provider/base URL |
-| Junie CLI | `junie.jetbrains.com` | fechado; configuracao BYOK a confirmar |
-| Pool | `poolsideai/pool` | binario/EULA; sem PR presumido |
-
-## 6. Evidencias tecnicas e mapeamento para OmniRoute
-
-### 6.1 Padroes de endpoint encontrados
-
-| Padrao observado | Exemplos | Acao OmniRoute |
-|---|---|---|
-| `OPENAI_BASE_URL`/`OPENAI_API_BASE` | Claw Code, RA.Aid, CoreCoder, Coro Code | fornecer root ou `/v1` conforme o cliente; testar append de path |
-| `base_url`/`baseURL` em provider | Plandex, MiMo Code, Trae Agent, VT Code, KlaatCode | gerar bloco de provider e modelo |
-| `LLM_BASE_URL` | OpenHands CLI | configurar surface OpenAI e validar streaming/tool calling |
-| `GOOGLE_GEMINI_BASE_URL` | Gemini CLI | usar superficie `/v1beta`/Gemini; confirmar formato esperado |
-| `GROK_BASE_URL` | Grok CLI | decidir se o cliente fala xAI ou OpenAI; testar traducoes |
-| `--base-url` | Gitlawb Zero, Zot, jcode | launcher ou perfil persistido |
-| `API_BASE_URL` | ShellGPT | config/env direta |
-| `<PROVIDER>_API_URL`/gateway | Octomind, Pool, OpenSquilla | provider selecionavel; testar cada preset |
-| ACP/MCP sem URL direta | Agentty, Kimi CLI, Goose, OpenCode | avaliar se OmniRoute deve ser provider ou backend ACP |
-| endpoint nao customizavel | Cursor desktop, Antigravity, Kiro, Windsurf, Amp | somente MITM/guide; nao prometer integracao direta |
-
-### 6.2 Superficies e riscos de protocolo
-
-- **`/v1` duplicado:** alguns clientes recebem a raiz e acrescentam `/v1/chat/completions`; outros exigem a URL final com `/v1`. Cada task deve registrar o resultado real.
-- **Chat Completions vs Responses:** forks do Codex e clientes modernos podem usar Responses; testar ambas quando o cliente permitir.
-- **Anthropic:** clientes que mandam `/v1/messages` esperam `ANTHROPIC_BASE_URL` sem `/v1` no valor. A traducao Anthropic do OmniRoute deve ser validada com streaming e tool use.
-- **Gemini:** Gemini CLI pode esperar uma base Gemini nativa, nao somente OpenAI-compatible; validar `generateContent`, streaming e headers.
-- **Tool calling:** o agente pode exigir nomes/ids de ferramenta estaveis, JSON estrito, `tool_choice` ou blocos de pensamento especificos.
-- **Descoberta de modelos:** `/v1/models` pode ser obrigatorio, opcional ou inexistente. O setup precisa aceitar `--model` fixo quando a descoberta nao for suportada.
-- **Autenticacao:** alguns projetos leem somente env, outros gravam tokens em arquivo/keyring e alguns usam OAuth proprietario. Nunca reutilizar credenciais de um upstream sem verificar escopo.
-- **Streaming e retry:** SSE, timeouts, abort signals e re-tentativas podem divergir do cliente. Validar uma chamada longa e uma falha de provider.
-- **Licenca:** GPL/AGPL, EULA e repositorios sem SPDX exigem decisao de distribuicao antes de enviar patch.
-
-## 7. Riscos de pesquisa e integracao
-
-1. **Homonomimos e clones:** usar sempre URL canonica, organizacao, release e README do repositorio correto.
-2. **Repositorios que mudam rapidamente:** congelar commit/versao no relatorio da task e repetir a consulta no dia da implementacao.
-3. **README divergente do codigo:** procurar schema, parser de config, testes e comando de execucao; README sozinho e evidencia Tier 1.
-4. **Clientes fechados:** registrar como `needs-mitm` ou `config-only`, nunca como PR upstream.
-5. **Forks com historia de origem controversa:** avaliar politica, licenca e aceite de contribuicoes antes de reproduzir componentes.
-6. **Segredos no ambiente:** limpar `OMNIROUTE_API_KEY` e chaves de teste quando a suite assume ambiente sem credencial, como ocorreu no jcode.
-7. **Mudancas no checkout:** usar worktree em `.claude/worktrees/` por projeto; nao editar o checkout compartilhado do OmniRoute nem usar `git stash`.
-
-## 8. Recomendacao
-
-Executar primeiro os lotes P0/P1 do documento de prioridade. Cada lote pode ter ate tres subagentes, um repositorio por worktree. O agente principal deve revisar a pesquisa, o smoke test e a licenca antes de permitir implementacao. O resultado de cada caso deve atualizar o tracker com commit, PR/issue, validacao e status upstream, sem preencher campos externos por suposicao.
-
-## 9. Referencias
-
-- OmniRoute CLI catalogo: `src/shared/constants/cliTools.ts`
-- OmniRoute CLI reference: `docs/reference/CLI-TOOLS.md`
-- OmniRoute setup guide: `docs/guides/CLI-INTEGRATIONS.md`
-- Handoff jcode: `_tasks/hands-off/2026-08-01_release-v3.8.50_v3.8.50_sess-e1846bc2/handoff.md`
-- Inventario curado: `https://github.com/bradAGI/awesome-cli-coding-agents`
-- GitHub Search API: `https://api.github.com/search/repositories`

_references/_sistemas_cli/02-prioridade-integracoes-clis.md

@@ -1,167 +0,0 @@
-# Prioridade de integracoes de CLIs com OmniRoute
-
-> **Status final (2026-08-03):** esta é a priorização inicial que orientou a execução. Todos os `104/104` casos já foram pesquisados. A classificação final está no tracker `04`; a estratégia revisada de contribuição está no relatório `06`.
-
-**Snapshot:** 2026-08-01  
-**Objetivo:** ordenar do melhor para o pior todos os projetos tecnicamente candidatos a consumir OmniRoute, sem remover projetos pequenos. A ordem e uma fila de pesquisa/execucao; ela nao e promessa de que todo upstream aceitara um PR.
-
-## Como ler a prioridade
-
-- **P0:** ja esta no catalogo OmniRoute ou tem evidencia muito forte de endpoint customizavel; executar/consolidar primeiro.
-- **P1:** forte candidato novo, com provider/base URL evidente e bom retorno para o ecossistema.
-- **P2:** tecnicamente promissor, mas requer confirmacao de protocolo, config, maturidade ou licenca.
-- **P3:** possivel via ACP/MCP/wrapper/launcher, ou com menor adocao; pesquisar depois dos P0-P2.
-- **P4:** cliente fechado, EULA, MITM ou pesquisa exploratoria; manter no inventario, mas nao bloquear os demais.
-
-Os fatores usados foram: evidencia de endpoint arbitrario, adocao/atividade, facilidade de teste, compatibilidade OpenAI/Anthropic/Gemini, maturidade, licenca, chance de PR upstream, valor para usuarios OmniRoute e risco de protocolo.
-
-## A. Catalogo OmniRoute ja existente
-
-Estas entradas ja aparecem no registro local. A prioridade aqui significa consolidar documentacao, smoke tests, detector/configurador e eventual upstream nominal; nao significa recriar uma integracao que ja existe.
-
-| Ordem | Projeto | Repositorio/documentacao | Estado local | Proximo foco |
-|---:|---|---|---|---|
-| A1 | Claude Code | `anthropics/claude-code` | catalogado; Anthropic base URL | manter compatibilidade Anthropic, streaming e tools |
-| A2 | Codex CLI | `openai/codex` | catalogado; OpenAI-compatible | Responses, profiles e `/v1` |
-| A3 | OpenCode | `anomalyco/opencode` | catalogado; provider | provider nativo/plugin e model discovery |
-| A4 | Cline | `cline/cline` | catalogado; base URL | validar CLI/extension e append de `/v1` |
-| A5 | Goose | `aaif-goose/goose` | catalogado; `OPENAI_HOST` | validar schema atual e ACP |
-| A6 | Aider | `Aider-AI/aider` | catalogado; `OPENAI_API_BASE` | LiteLLM path, tools e custo |
-| A7 | Continue | `continuedev/continue` | catalogado; provider OpenAI | CLI e config YAML atual |
-| A8 | Kilo Code | `Kilo-Org/kilocode` | catalogado; custom URL | CLI, extension e auth |
-| A9 | Roo Code | `RooCodeInc/Roo-Code` | catalogado; custom URL | CLI/headless e provider |
-| A10 | Qwen Code | `QwenLM/qwen-code` | catalogado; `modelProviders` | V4 schema, Responses e env |
-| A11 | Open Interpreter | `OpenInterpreter/open-interpreter` | catalogado; `--api_base` | streaming e tool execution |
-| A12 | OpenClaw | `openclaw/openclaw` | catalogado; gateway/provider | config atual e segurança |
-| A13 | Hermes Agent | `NousResearch/hermes-agent` | catalogado; provider/gateway | endpoint custom e modelos |
-| A14 | Hermes | `NousResearch/hermes-agent` | catalogado/dual entry | distinguir CLI e agente |
-| A15 | Oh My Pi | `can1357/oh-my-pi` | catalogado; YAML provider | auto-discovery e tool calling |
-| A16 | Pi | `badlogic/pi-mono` | catalogado; provider | confirmar repositorio/CLI atual |
-| A17 | Crush | `charmbracelet/crush` | catalogado; `base_url` | config TOML/JSON atual |
-| A18 | Smelt | `leonardcser/smelt` | catalogado; OpenAI-compatible | headless e subagents |
-| A19 | ForgeCode | `antinomyhq/forge` | catalogado; multi-provider | base URL e custom agents |
-| A20 | jcode | `1jehuang/jcode` | integrado e proposto upstream | aguardar issue #704; manter README OmniRoute |
-| A21 | DeepSeek TUI | `hunterbown/deepseek-tui` | catalogado legado | confirmar sucessor CodeWhale |
-| A22 | CodeWhale | `Hmbown/CodeWhale` | catalogado | config primaria e legado |
-| A23 | Grok Build | `xai-org/grok-build` | catalogado; `~/.grok/config.toml` | provider OmniRoute e modelos |
-| A24 | Cursor Agent CLI | `cursor.com/cli` | catalogado parcial | confirmar limites de endpoint |
-| A25 | Factory Droid | `Factory-AI/factory` | catalogado parcial | BYOK e endpoint suportado |
-| A26 | GitHub Copilot CLI | `github/copilot-cli` | catalogado | provider base URL atual |
-| A27 | Letta CLI | `letta-ai/letta-code` | catalogado | config pi-ai/local mode |
-| A28 | Warp AI | `warpdotdev/Warp` | catalogado parcial | somente BYOK/desktop |
-| A29 | Agent Deck | `asheshgoplani/agent-deck` | catalogado | agentes filhos e ACP |
-| A30 | Antigravity | produto Google | MITM backlog | nao tratar como endpoint direto |
-| A31 | Kiro AI | produto AWS | MITM backlog | auth/SSO e MITM |
-| A32 | Cursor desktop | produto Anysphere | cloud/MITM | manter separado do Cursor CLI |
-
-## B. Novos candidatos em ordem de execucao
-
-| Ordem | Prioridade | Projeto | Repositorio | Evidencia inicial | Rota esperada |
-|---:|:---:|---|---|---|---|
-| 1 | P0 | Gemini CLI | `google-gemini/gemini-cli` | `GOOGLE_GEMINI_BASE_URL` | config direta/Gemini |
-| 2 | P0 | Claw Code | `ultraworkers/claw-code` | `OPENAI_BASE_URL`, provider | OpenAI-compatible |
-| 3 | P0 | Plandex | `plandex-ai/plandex` | provider com `baseUrl` | preset/provider |
-| 4 | P0 | MiMo Code | `XiaomiMiMo/MiMo-Code` | `@ai-sdk/openai-compatible`, `baseURL` | provider |
-| 5 | P0 | Trae Agent | `bytedance/trae-agent` | `model_providers`, `base_url` | provider/config |
-| 6 | P0 | Kimi CLI | `MoonshotAI/kimi-cli` | OpenAI legacy/Responses/Anthropic, `base_url` | provider nativo |
-| 7 | P0 | Every Code | `just-every/code` | fork Codex, OpenAI/Claude/Gemini | profile/provider |
-| 8 | P0 | Open Codex | `ymichael/open-codex` | OpenAI/Gemini/OpenRouter/Ollama | profile/provider |
-| 9 | P0 | VT Code | `vinhnx/vtcode` | `custom_providers[].base_url` | provider/failover |
-| 10 | P0 | OpenHands CLI | `OpenHands/OpenHands-CLI` | `LLM_BASE_URL` | config direta |
-| 11 | P0 | gptme | `gptme/gptme` | `OPENAI_BASE_URL` | config direta |
-| 12 | P0 | Nanocoder | `Nano-Collective/nanocoder` | qualquer OpenAI-compatible | config direta |
-| 13 | P0 | RA.Aid | `ai-christianson/RA.Aid` | `OPENAI_API_BASE` | config direta |
-| 14 | P0 | CoreCoder | `he-yufeng/CoreCoder` | `OPENAI_BASE_URL` | config direta |
-| 15 | P1 | Grok CLI | `superagent-ai/grok-cli` | `GROK_BASE_URL`/`baseURL` | config direta |
-| 16 | P1 | Gitlawb Zero | `Gitlawb/zero` | `custom-openai-compatible`, `--base-url` | provider/flag |
-| 17 | P1 | DeepSeek Reasonix | `esengine/DeepSeek-Reasonix` | endpoint/provider compativel | provider |
-| 18 | P1 | KlaatCode | `KlaatAI/klaatcode` | `customModels` OpenAI-compatible | config |
-| 19 | P1 | CodeMini CLI | `havingautism/Codemini-CLI` | `gateway.base_url` | gateway |
-| 20 | P1 | Zot | `patriceckhart/zot` | `--base-url`, `models.json` | flag/config |
-| 21 | P1 | Octomind | `Muvon/octomind` | provider URL envs | provider/env |
-| 22 | P1 | DvalinCode | `arthurpanhku/dvalincode` | qualquer OpenAI-compatible | config direta |
-| 23 | P1 | Coro Code | `Blushyes/coro-code` | `OPENAI_BASE_URL` | env |
-| 24 | P1 | Mini-Kode | `minmaxflow/mini-kode` | `MINIKODE_BASE_URL` | env |
-| 25 | P1 | Late CLI | `mlhher/late-cli` | `OPENAI_BASE_URL`, `api-url` | env/flag |
-| 26 | P1 | Agentty | `1ay1/agentty` | provider-agnostic, ACP | config/ACP |
-| 27 | P1 | Aizen | `aizen-stack/aizen` | Rust OpenAI-compatible, `AIZEN_BASE_URL` | config |
-| 28 | P1 | Clif-Code | `DLhugly/Clif-Code` | OpenAI/Anthropic/Ollama | provider |
-| 29 | P1 | Minacode | `hit9/minacode` | provider/compatibilidade | confirmar URL |
-| 30 | P1 | YottaCode | `yottadynamics/yottacode` | modelo escolhido/gateway | provider |
-| 31 | P1 | aichat | `sigoden/aichat` | OpenAI/Claude/Gemini | models YAML |
-| 32 | P1 | ShellGPT | `TheR1D/shell_gpt` | `API_BASE_URL` | env |
-| 33 | P1 | Mistral Vibe | `mistralai/mistral-vibe` | `base_url`, API base | config |
-| 34 | P1 | OpenSquilla | `opensquilla/opensquilla` | gateway, 20+ providers | provider |
-| 35 | P1 | Kode CLI | `shareAI-lab/Kode-cli` | endpoint/Anthropic/OpenAI/Gemini | config |
-| 36 | P1 | Neovate Code | `neovateai/neovate-code` | plugin/multi-provider | plugin/provider |
-| 37 | P1 | Deep Agents Code | `langchain-ai/deepagents` | qualquer tool-calling LLM | provider SDK |
-| 38 | P1 | Kode fork/variants | `shareAI-lab/Kode-cli` | multi-provider | confirmar upstream |
-| 39 | P1 | OpenHands principal | `All-Hands-AI/OpenHands` | CLI/web; pesquisar LLM base | config/CLI |
-| 40 | P1 | SWE-agent | `SWE-agent/SWE-agent` | agente de issues | backend/provider |
-| 41 | P1 | AutoCodeRover | `AutoCodeRoverSG/auto-code-rover` | agente de patches | backend/provider |
-| 42 | P2 | Claurst | `Kuberwastaken/claurst` | provider/Anthropic | config; licenca GPL |
-| 43 | P2 | Codebuff | `CodebuffAI/codebuff` | multi-agent CLI | provider |
-| 44 | P2 | Devon | `entropy-research/Devon` | TUI pair programmer | backend |
-| 45 | P2 | Letta Code | `letta-ai/letta-code` | model-agnostic | provider |
-| 46 | P2 | CodeMachine CLI | `moazbuilds/CodeMachine-CLI` | multi-agent local | provider |
-| 47 | P2 | Groq Code CLI | `build-with-groq/groq-code-cli` | multi-model | endpoint |
-| 48 | P2 | Dexto | `truffle-ai/dexto` | CLI/web/API | provider |
-| 49 | P2 | claw-code-agent | `HarnessLab/claw-code-agent` | endpoint/gateway | provider |
-| 50 | P2 | g3 | `dhanji/g3` | Rust provider abstraction | provider |
-| 51 | P2 | San | `genai-io/san` | provider-neutral | provider |
-| 52 | P2 | Waveloom | `Menfre01/waveloom` | DeepSeek/provider | endpoint |
-| 53 | P2 | picocode | `jondot/picocode` | multi-LLM | config |
-| 54 | P2 | QQCode | `qnguyen3/qqcode` | skills, Rust | config |
-| 55 | P2 | Keen Code | `mochow13/keen-code` | 9+ providers | config |
-| 56 | P2 | Grinta | `josephsenior/Grinta-Coding-Agent` | provider-agnostic | config |
-| 57 | P2 | Zap | `zap-coding-agent/zap-coding-agent` | Claude/Gemini/OpenAI/LM Studio | provider |
-| 58 | P2 | Binharic | `CogitatorTech/binharic-cli` | multi-provider | config |
-| 59 | P2 | Darce | `AmerSarhan/darce-cli` | multi-model/streaming | config |
-| 60 | P2 | CLAII | `agencyswarm/CLAII` | multi-agent/MCP | provider |
-| 61 | P2 | nori-cli | `tilework-tech/nori-cli` | multi-provider sobre Codex | config |
-| 62 | P2 | cursor-agent clone | `civai-technologies/cursor-agent` | Claude/OpenAI/Ollama | provider |
-| 63 | P2 | Free Code | `paoloanzn/free-code` | fork Claude Code | licenca/config |
-| 64 | P2 | Claude Engineer | `Doriandarko/claude-engineer` | CLI Claude | provider |
-| 65 | P2 | Smol Developer | `smol-ai/developer` | agent embutivel | SDK/adaptador |
-| 66 | P2 | Agentless | `OpenAutoCoder/Agentless` | workflow sem loop | entrada de modelo |
-| 67 | P2 | Amazon Q Developer CLI | `aws/amazon-q-developer-cli` | CLI AWS | auth/provider |
-| 68 | P2 | nanobot | `HKUDS/nanobot` | OpenClaw rewrite | provider |
-| 69 | P2 | ZeroClaw | `zeroclaw-labs/zeroclaw` | providers pluggable | provider |
-| 70 | P2 | NanoClaw | `gavrielc/nanoclaw` | Anthropic SDK | base URL |
-| 71 | P2 | PicoClaw | `sipeed/picoclaw` | provider/config | provider |
-| 72 | P2 | IronClaw | `nearai/ironclaw` | provider Rust | provider |
-| 73 | P2 | NullClaw | `nullclaw/nullclaw` | 23+ providers | provider |
-| 74 | P2 | Moltis | `moltis-org/moltis` | Rust agent | provider |
-| 75 | P2 | GitClaw | `open-gitagent/gitclaw` | Git-native agent | provider |
-| 76 | P2 | LionClaw | `moshthepitt/lionclaw` | CLI local | provider |
-| 77 | P3 | VibePod | `VibePod/vibepod-cli` | wrapper Docker | launcher |
-| 78 | P3 | zeroshot | `the-open-engine/zeroshot` | worktrees/orchestration | launcher |
-| 79 | P3 | Fractal | `plasma-ai/fractal` | orquestra CLIs | launcher |
-| 80 | P3 | Bernstein | `chernistry/bernstein` | executa/verifica agentes | launcher |
-| 81 | P3 | Traycer | `traycerai/traycer` | agentes paralelos | launcher |
-| 82 | P3 | h5i | `h5i-dev/h5i` | sandbox e peer review | launcher |
-| 83 | P3 | OMK | `dmae97/open-multi-agent-kit` | control plane | ACP/MCP |
-| 84 | P3 | kodo | `ikamensh/kodo` | orquestrador | launcher |
-| 85 | P3 | ORCH | `oxgeneral/ORCH` | fila de tarefas | launcher |
-| 86 | P3 | LoopTroop | `LoopTroop-ai/LoopTroop` | orquestrador OpenCode | launcher |
-| 87 | P3 | Galley | `shinpr/galley` | worktree/PR | launcher |
-| 88 | P3 | Relay | `jcast90/relay` | MCP/orquestracao | MCP |
-| 89 | P3 | SageCLI | `youwangd/SageCLI` | runtime-agnostic | launcher/ACP |
-| 90 | P3 | 5dive | `5dive-ai/5dive` | agentes em servidor | launcher |
-| 91 | P3 | agx | `ramarlina/agx` | checkpoints | launcher |
-| 92 | P3 | claude-code-router | `musistudio/claude-code-router` | proxy multi-provider | integrar como consumidor/proxy |
-| 93 | P3 | cc-router | `finch-xu/cc-router` | proxy Anthropic | interoperabilidade |
-| 94 | P3 | OneCLI | `onecli/onecli` | broker de credenciais | seguranca/integ. adjacente |
-| 95 | P3 | agent-browser | `vercel-labs/agent-browser` | ferramenta para agentes | MCP/plugin |
-| 96 | P3 | OpenWork | `different-ai/openwork` | desktop sobre OpenCode | config do agente filho |
-| 97 | P4 | Pool | `poolsideai/pool` | `POOLSIDE_STANDALONE_BASE_URL`; EULA | config sem PR presumido |
-| 98 | P4 | Junie CLI | `junie.jetbrains.com` | fechado/EAP | BYOK/endpoint a confirmar |
-| 99 | P4 | Cursor desktop | `Anysphere` | cloud endpoint | MITM/guide |
-| 100 | P4 | Windsurf | produto Codeium | sem base URL geral | MITM |
-| 101 | P4 | Amp | `sourcegraph.com/amp` | fechado | MITM/sem PR |
-| 102 | P4 | Amazon Q/Kiro CLI | AWS | SSO/ecossistema AWS | MITM/adapter |
-| 103 | P4 | Cowork | produto Anthropic | endpoint opaco | MITM |
-
-## C. Regra de promocao/rebaixamento
-
-Um projeto sobe de prioridade quando a pesquisa individual confirma: configuracao documentada, teste local com OmniRoute, licenca permissiva e contribuicao aceita. Desce quando: a URL e fixa, o endpoint e somente SaaS, o README nao corresponde ao codigo, a autenticacao e inseparavel do provedor, ou a licenca/EULA impede redistribuicao. Nenhum projeto e marcado como impossivel sem registrar a evidencia no tracker.

_references/_sistemas_cli/03-plano-integracao-em-lotes.md

@@ -1,314 +0,0 @@
-# Plano executavel de integracao de CLIs
-
-> **Status final (2026-08-03):** a fase de pesquisa foi concluída em lotes de até três worktrees/agentes, cobrindo `104/104` casos. Este documento continua válido como processo operacional para implementação/publicação. Consulte `06-relatorio-final-104-clis-e-estrategia-prs.md` para o resultado final.
-
-**Data:** 2026-08-01  
-**Objetivo:** pesquisar, integrar, validar e publicar suporte ao OmniRoute em todos os projetos tecnicamente possiveis, mantendo uma fila que permite ate tres subagentes simultaneos.
-
-O ciclo especifico de preparacao, revisao, envio e acompanhamento das contribuicoes upstream esta
-em `05-plano-publicacao-prs-upstream.md`.
-
-## 1. Principios operacionais
-
-- Um repositorio por subagente e por worktree.
-- No maximo tres tasks de repositorios em execucao ao mesmo tempo.
-- Cada task pesquisa o upstream novamente antes de editar; o relatorio inicial e somente contexto.
-- O agente principal revisa licenca, arquitetura, smoke test e diff antes do proximo lote.
-- Nao usar checkout compartilhado para desenvolvimento e nao usar `git stash`/`git pop`.
-- Usar worktrees em `.claude/worktrees/` e branches especificas.
-- Nao inventar PR, issue, commit ou aceite de mantenedor.
-- Nao adicionar trailers ou rodapes de IA em commits/PRs.
-
-## 2. Fases obrigatorias por projeto
-
-### Fase 0 - Preparacao da task
-
-Criar uma task com nome do projeto, URL canonica, prioridade, evidencia inicial, estado no catalogo OmniRoute e objetivo de integrar. Definir a worktree e o agente responsavel.
-
-### Fase 1 - Pesquisa individual fresca
-
-O agente deve verificar no upstream atual:
-
-- arquitetura de providers e ponto de entrada do CLI;
-- arquivo/schema de configuracao e suporte a `base_url`, `baseURL`, `OPENAI_BASE_URL`, `OPENAI_API_BASE`, `LLM_BASE_URL` ou equivalente;
-- protocolo real (Chat Completions, Responses, Anthropic Messages, Gemini, ACP, MCP ou outro);
-- descoberta de modelos e necessidade de `/v1/models`;
-- autenticacao, keyring, OAuth e variaveis de ambiente;
-- streaming, tool calling, reasoning e limites conhecidos;
-- politica de contribuicao, licenca e se PR de fork externo e aceito;
-- atividade, releases, issues/PRs sobre providers customizados ou endpoints locais;
-- comandos de build, lint, teste e smoke test;
-- possibilidade de fork/PR, issue de proposta, documentacao ou apenas wrapper/MITM.
-
-Registrar commit/release pesquisado e links de evidencia.
-
-### Fase 2 - Gate de viabilidade
-
-Classificar exatamente um caminho inicial:
-
-`viable-direct` (somente configuracao), `viable-upstream` (mudanca no upstream), `viable-acp`, `viable-mcp`, `needs-wrapper`, `needs-mitm`, `config-only`, `blocked` ou `research-more`.
-
-Nao implementar antes de haver uma conclusao de viabilidade e uma razao verificavel.
-
-### Fase 3 - Baseline e TDD
-
-- Executar a suite recomendada pelo upstream antes das mudancas.
-- Registrar falhas preexistentes, dependencias ausentes e comandos exatos.
-- Limpar `OMNIROUTE_API_KEY` e demais credenciais quando os testes pressupuserem ambiente sem chaves.
-- Adicionar primeiro um teste de configuracao, endpoint e selecao de modelo que falhe sem a integracao.
-
-### Fase 4 - Implementacao minima
-
-Implementar apenas o necessario para o caso pesquisado:
-
-- perfil/preset `omniroute` ou provider custom;
-- base URL correta (raiz, `/v1` ou `/v1beta` conforme o cliente);
-- chave via ambiente ou mecanismo seguro do cliente;
-- modelo fixo ou descoberta de modelos;
-- selecao/login/report se o CLI tiver esses fluxos;
-- documentacao de uso e limites;
-- testes de config e chamada.
-
-Se o upstream nao aceitar mudanca, preparar wrapper/launcher ou documentacao local e registrar a limitacao.
-
-### Fase 5 - Validacao funcional
-
-Executar, conforme o protocolo:
-
-- build, lint, typecheck e testes do upstream;
-- smoke request com OmniRoute;
-- streaming SSE e encerramento por abort;
-- tool calling e JSON de argumentos;
-- `/v1/models` ou equivalente;
-- Chat Completions, Responses, Anthropic Messages e Gemini `generateContent` quando aplicavel;
-- fallback/erro, timeout, retry e modelo inexistente;
-- teste com chave limpa e teste com `OMNIROUTE_API_KEY` real fora dos logs.
-
-### Fase 6 - Publicacao upstream
-
-- Criar fork somente quando permitido e branch especifica.
-- Abrir PR upstream se contribuicoes externas forem aceitas.
-- Se PR externo for bloqueado, abrir issue com proposta, patch/referencia e smoke test.
-- Se o projeto for fechado/EULA, registrar config manual ou issue de produto; nao criar PR ficticio.
-- Atualizar o tracker com URL, commit, estado e resposta do mantenedor.
-
-### Fase 7 - Catalogo e integracao OmniRoute
-
-Quando houver valor para usuarios OmniRoute:
-
-- criar worktree propria do OmniRoute;
-- atualizar `src/shared/constants/cliTools.ts` ou `src/shared/constants/cliToolsGrokBuild.ts`;
-- atualizar detector em `src/lib/cli-helper/tool-detector.ts` se necessario;
-- adicionar gerador/configurador e rota de settings somente se o caso exigir;
-- adicionar testes do catalogo, detector, settings, `baseUrlSupport` e `/v1`;
-- atualizar `docs/reference/CLI-TOOLS.md`, `docs/guides/CLI-INTEGRATIONS.md` e README quando apropriado;
-- atualizar o tracker com a integracao local e evidencias.
-
-### Fase 8 - Fechamento
-
-Registrar commit, branch, PR/issue, testes, limitacoes, status do upstream, status do catalogo OmniRoute e proximo passo. O agente principal faz uma revisao final de seguranca, licenca e factualidade.
-
-## 3. Lotes de ate tres subagentes
-
-O lote e uma unidade operacional. A fila abaixo e ordenada pelo documento `02-prioridade-integracoes-clis.md`; cada linha representa uma task individual.
-
-### Lote 0 - consolidacao do caso de referencia
-
-- `CLI-000` - jcode - manter a issue #704, validar resposta do mantenedor e concluir a secao do README OmniRoute.
-
-### Lote P0.1
-
-- `CLI-001` - Gemini CLI - integrar provider/base URL Gemini.
-- `CLI-002` - Claw Code - integrar `OPENAI_BASE_URL`/provider OmniRoute.
-- `CLI-003` - Plandex - integrar provider custom com `baseUrl`.
-
-### Lote P0.2
-
-- `CLI-004` - MiMo Code - integrar provider OpenAI-compatible.
-- `CLI-005` - Trae Agent - integrar `model_providers` e `base_url`.
-- `CLI-006` - Kimi CLI - integrar modos OpenAI/Responses/Anthropic.
-
-### Lote P0.3
-
-- `CLI-007` - Every Code - integrar perfil derivado do Codex.
-- `CLI-008` - Open Codex - integrar provider multi-modelo.
-- `CLI-009` - VT Code - integrar `custom_providers` e failover.
-
-### Lote P0.4
-
-- `CLI-010` - OpenHands CLI - integrar `LLM_BASE_URL`.
-- `CLI-011` - gptme - integrar `OPENAI_BASE_URL`.
-- `CLI-012` - Nanocoder - integrar API OpenAI-compatible.
-
-### Lote P0.5
-
-- `CLI-013` - RA.Aid - integrar `OPENAI_API_BASE`.
-- `CLI-014` - CoreCoder - integrar `OPENAI_BASE_URL`.
-- `CLI-015` - Grok CLI - integrar `GROK_BASE_URL`.
-
-### Lote P1.1
-
-- `CLI-016` - Gitlawb Zero - integrar provider custom e `--base-url`.
-- `CLI-017` - DeepSeek Reasonix - confirmar e integrar endpoint.
-- `CLI-018` - KlaatCode - integrar `customModels`.
-
-### Lote P1.2
-
-- `CLI-019` - CodeMini CLI - integrar `gateway.base_url`.
-- `CLI-020` - Zot - integrar flag/config `--base-url`.
-- `CLI-021` - Octomind - integrar provider URL envs.
-
-### Lote P1.3
-
-- `CLI-022` - DvalinCode - integrar OpenAI-compatible.
-- `CLI-023` - Coro Code - integrar `OPENAI_BASE_URL`.
-- `CLI-024` - Mini-Kode - integrar `MINIKODE_BASE_URL`.
-
-### Lote P1.4
-
-- `CLI-025` - Late CLI - integrar `OPENAI_BASE_URL`/`api-url`.
-- `CLI-026` - Agentty - integrar provider e/ou ACP.
-- `CLI-027` - Aizen - integrar `AIZEN_BASE_URL`.
-
-### Lote P1.5
-
-- `CLI-028` - Clif-Code - integrar providers OpenAI/Anthropic/Ollama.
-- `CLI-029` - Minacode - confirmar provider e integrar URL.
-- `CLI-030` - YottaCode - integrar gateway/provider.
-
-### Lote P1.6
-
-- `CLI-031` - aichat - integrar models YAML/provider.
-- `CLI-032` - ShellGPT - integrar `API_BASE_URL`.
-- `CLI-033` - Mistral Vibe - integrar base URL/provider.
-
-### Lote P1.7
-
-- `CLI-034` - OpenSquilla - integrar gateway/provider.
-- `CLI-035` - Kode CLI - integrar endpoint multi-provider.
-- `CLI-036` - Neovate Code - integrar plugin/provider.
-
-### Lote P1.8
-
-- `CLI-037` - Deep Agents Code - integrar provider do pacote CLI.
-- `CLI-038` - OpenHands principal - integrar CLI/config.
-- `CLI-039` - SWE-agent - integrar backend/provider.
-
-### Lote P1.9
-
-- `CLI-040` - AutoCodeRover - integrar backend/provider.
-- `CLI-041` - Claurst - integrar provider, respeitando GPL.
-- `CLI-042` - Codebuff - integrar provider.
-
-### Lote P2.1
-
-- `CLI-043` - Devon - integrar backend.
-- `CLI-044` - Letta Code - integrar provider.
-- `CLI-045` - CodeMachine CLI - integrar provider.
-
-### Lote P2.2
-
-- `CLI-046` - Groq Code CLI - integrar endpoint.
-- `CLI-047` - Dexto - integrar provider.
-- `CLI-048` - claw-code-agent - integrar endpoint.
-
-### Lote P2.3
-
-- `CLI-049` - g3 - integrar provider Rust.
-- `CLI-050` - San - integrar provider-neutral.
-- `CLI-051` - Waveloom - integrar provider/endpoint.
-
-### Lote P2.4
-
-- `CLI-052` - picocode - integrar multi-LLM.
-- `CLI-053` - QQCode - integrar config.
-- `CLI-054` - Keen Code - integrar provider.
-
-### Lote P2.5
-
-- `CLI-055` - Grinta - integrar provider.
-- `CLI-056` - Zap - integrar Claude/Gemini/OpenAI.
-- `CLI-057` - Binharic - integrar multi-provider.
-
-### Lote P2.6
-
-- `CLI-058` - Darce - integrar multi-modelo.
-- `CLI-059` - CLAII - integrar provider/MCP.
-- `CLI-060` - nori-cli - integrar provider baseado em Codex.
-
-### Lote P2.7
-
-- `CLI-061` - cursor-agent clone - integrar provider.
-- `CLI-062` - Free Code - pesquisar licenca e integrar se viavel.
-- `CLI-063` - Claude Engineer - integrar provider.
-
-### Lote P2.8
-
-- `CLI-064` - Smol Developer - integrar SDK/adaptador.
-- `CLI-065` - Agentless - integrar entrada de modelo.
-- `CLI-066` - Amazon Q Developer CLI - pesquisar auth/provider.
-
-### Lote P2.9
-
-- `CLI-067` - nanobot - integrar provider OpenClaw-compatible.
-- `CLI-068` - ZeroClaw - integrar trait de provider.
-- `CLI-069` - NanoClaw - confirmar base Anthropic.
-
-### Lote P2.10
-
-- `CLI-070` - PicoClaw - integrar provider/config.
-- `CLI-071` - IronClaw - integrar provider Rust.
-- `CLI-072` - NullClaw - integrar provider.
-
-### Lote P2.11
-
-- `CLI-073` - Moltis - integrar provider Rust.
-- `CLI-074` - GitClaw - integrar provider Git-native.
-- `CLI-075` - LionClaw - integrar provider CLI.
-
-### Lote P3.1 - wrappers e orquestradores
-
-- `CLI-076` - VibePod; `CLI-077` - zeroshot; `CLI-078` - Fractal.
-
-### Lote P3.2
-
-- `CLI-079` - Bernstein; `CLI-080` - Traycer; `CLI-081` - h5i.
-
-### Lote P3.3
-
-- `CLI-082` - OMK; `CLI-083` - kodo; `CLI-084` - ORCH.
-
-### Lote P3.4
-
-- `CLI-085` - LoopTroop; `CLI-086` - Galley; `CLI-087` - Relay.
-
-### Lote P3.5
-
-- `CLI-088` - SageCLI; `CLI-089` - 5dive; `CLI-090` - agx.
-
-### Lote P3.6
-
-- `CLI-091` - claude-code-router; `CLI-092` - cc-router; `CLI-093` - OneCLI.
-
-### Lote P3.7
-
-- `CLI-094` - agent-browser; `CLI-095` - OpenWork; `CLI-096` - Agent Deck (revisao de agente filho).
-
-### Lote P4 - fechados/MITM
-
-- `CLI-097` - Pool; `CLI-098` - Junie CLI; `CLI-099` - Cursor desktop.
-- `CLI-100` - Windsurf; `CLI-101` - Amp; `CLI-102` - Amazon Q/Kiro CLI; `CLI-103` - Cowork.
-
-## 4. Criterio para iniciar o lote seguinte
-
-O lote seguinte pode iniciar quando os tres agentes do lote atual tiverem: pesquisa upstream anexada, gate de viabilidade preenchido, baseline registrado, resultado de smoke test ou bloqueio reproduzivel, e tracker atualizado. Uma falha de um agente nao deve paralisar os outros dois; o agente principal deve marcar `blocked` ou `research-more` com evidencia e seguir a fila.
-
-## 5. Entregaveis de cada task
-
-1. Nota de pesquisa fresca com commit/release e links.
-2. Classificacao de viabilidade.
-3. Diff minimo ou conclusao documentada de que nao ha diff necessario.
-4. Testes e comandos executados, incluindo falhas preexistentes.
-5. PR/issue upstream ou justificativa de config-only/MITM.
-6. Entrada no catalogo OmniRoute quando aplicavel.
-7. Atualizacao do tracker `04-tracker-integracoes-clis.md`.

_references/_sistemas_cli/04-tracker-integracoes-clis.md

@@ -1,144 +0,0 @@
-# Tracker de integracoes de CLIs com OmniRoute
-
-**Status final da pesquisa:** `104/104` concluídos (`100%`), `0` casos `not-started`. Este é o registro individual autoritativo. O relatório executivo está em `06-relatorio-final-104-clis-e-estrategia-prs.md`.
-
-**Snapshot inicial:** 2026-08-01
-**Legenda de status:** `not-started`, `researching`, `research-more`, `viable-direct`, `viable-upstream`, `viable-acp`, `viable-mcp`, `needs-wrapper`, `needs-mitm`, `blocked`, `implementing`, `validating`, `published-pr`, `published-issue`, `awaiting-maintainer`, `accepted`, `rejected`, `integrated`.
-
-Os campos externos (`branch`, `commit`, `PR`, `issue`) ficam como `—` ate haver evidencia real. “Catalogo OmniRoute” significa entrada local, nao necessariamente suporte upstream publicado.
-
-| ID | Prio | Projeto | Repositorio | Pesquisa | Tipo | Upstream | Branch | Commit | PR | Issue | Catalogo OmniRoute | Observacoes/proximo passo |
-|---|:---:|---|---|---|---|---|---|---|---|---|---|---|
-| CLI-000 | P0 | jcode | `1jehuang/jcode` | concluida | `viable-upstream` | `awaiting-maintainer` | `feat/omniroute-provider` | `ee4f904e6` | [fork PR](https://github.com/diegosouzapw/jcode/pull/1) | [upstream #704](https://github.com/1jehuang/jcode/issues/704) | integrated | acompanhar mantenedor e concluir secao do README |
-
-## Caso publicado: jcode
-
-| Campo | Valor |
-|---|---|
-| Projeto | jcode |
-| Repositorio | `https://github.com/1jehuang/jcode` |
-| Status geral | `awaiting-maintainer` |
-| Tipo | `viable-upstream`; perfil OpenAI-compatible dirigido por metadados |
-| Branch | `feat/omniroute-provider` |
-| Commit | `ee4f904e6` |
-| PR | `https://github.com/diegosouzapw/jcode/pull/1` (fork de referencia) |
-| Issue | `https://github.com/1jehuang/jcode/issues/704` |
-| Catalogo OmniRoute | `integrated` / entrada existente |
-| Validacao | `cargo check --workspace` limpo; 205 testes passaram; 1 falha preexistente/ambiental |
-| Diff | 6 arquivos, `+56/-3` |
-| Proximo passo | acompanhar issue #704 e criar secao de README do OmniRoute |
-
-## Tabela principal
-
-| ID | Prio | Projeto | Repositorio | Pesquisa | Tipo | Upstream | Branch | Commit | PR | Issue | Catalogo OmniRoute | Observacoes/proximo passo |
-|---|:---:|---|---|---|---|---|---|---|---|---|---|---|
-| CLI-001 | P0 | Gemini CLI | `google-gemini/gemini-cli` | concluida | `pr-generic` | `published-issue` | `fix/omniroute-gateway-auth` | `8138105c38cc1637fe9e8a9bd520eb835f1620e6` | — | [upstream #27550](https://github.com/google-gemini/gemini-cli/issues/27550#issuecomment-5152312278) | not-in-catalog | regression `AuthType.GATEWAY`; patch +26; auth 10/10, non-interactive 17/17, content generator 55/55, Gemini `/v1beta` stream/tools smoke verde; aguardar `help wanted` antes de terceira PR |
-| CLI-002 | P0 | Claw Code | `ultraworkers/claw-code` | concluida | `pr-docs` | `published-issue` | `docs/omniroute-setup` | `de857038b2f9ff9b319132e2241549e86215c351` | — | [upstream #3283](https://github.com/ultraworkers/claw-code/issues/3283) | not-in-catalog | generic OpenAI Chat Completions; docs +37; 1.415 testes, fmt, docs/release checks e clippy oficial verdes; fork bloqueado pelo GitHub, issue-first; smoke OmniRoute parcial/timeout; chave do smoke deve ser rotacionada |
-| CLI-003 | P0 | Plandex | `plandex-ai/plandex` | concluida | `pr-docs` | `published-pr` | `feat/omniroute-provider-docs` | `f8f0694bdf7d1cb6e65a1f1c5bc39f84921a4507` | [upstream #359](https://github.com/plandex-ai/plandex/pull/359) | — | not-in-catalog | custom provider OpenAI-compatible ja existia; docs com `/v1`, `OMNIROUTE_API_KEY`, Docker reachability e model mapping; Go indisponivel; Docusaurus build verde; acompanhar mantenedor |
-| CLI-004 | P0 | MiMo Code | `XiaomiMiMo/MiMo-Code` | concluida | `config-only` | not-applicable | `research/omniroute-mimo-code` | — | — | — | not-in-catalog | SHA `ce124cb`; provider customizado `@ai-sdk/openai-compatible` já suporta `baseURL`, `apiKey` e modelo; 116 testes focados + typecheck verdes; smoke CLI inconclusivo por travamento ambiental; sem PR artificial |
-| CLI-005 | P0 | Trae Agent | `bytedance/trae-agent` | concluida | `pr-docs` | `published-pr` | `research/omniroute-trae-agent` | `4801e48b69d7583300eb86ec5c69235506d7f205` | [upstream #449](https://github.com/bytedance/trae-agent/pull/449) | — | not-in-catalog | README +39; `provider: openai` + mapping `base_url=/v1`; `/v1/responses`, `/v1/models`, Bearer, tools e limitação sem streaming; 62 testes/17 skips, pre-commit e mocks verdes; CLA pendente |
-| CLI-006 | P0 | Kimi CLI | `MoonshotAI/kimi-cli` | concluida | `pr-docs` | `published-issue` | `research/omniroute-kimi-cli` | `a2f62bf6108a6954e798db992411aa06670e224f` | — | [upstream #2576](https://github.com/MoonshotAI/kimi-cli/issues/2576) | not-in-catalog | docs EN/ZH +63; `openai_legacy` `/v1`, chave via `OPENAI_API_KEY`, modelo manual; Responses/Anthropic alternativos; 47 testes e VitePress verdes; aguardar direção do mantenedor antes da PR |
-| CLI-007 | P0 | Every Code | `just-every/code` | concluida | `pr-docs` / `config-only` | `published-pr` | `feat/omniroute-integration` | `8fbc8dab5fb76bf05535055801af0c3ccfea6f3b` | [upstream #614](https://github.com/just-every/code/pull/614) | — | not-in-catalog | PR documental aberta e mergeable; release `v0.6.162`; `./build-fast.sh` baseline/pós-patch verdes; smoke mock Responses/SSE/tools verde; acompanhar CI/mantenedor |
-| CLI-008 | P0 | Open Codex | `ymichael/open-codex` | concluida | `pr-generic` / `issue-first` | `published-issue` | `feat/omniroute-integration` | `f25de99f991c0e4d9d6ae2811d307cdbff92f869` | — | [upstream #4](https://github.com/ymichael/open-codex/issues/4#issuecomment-5152804104) | not-in-catalog | patch genérico pronto localmente; issue-first por firewall de container e PR #19 fechada; 132 testes, typecheck/build/format verdes; lint bloqueado por ambiente; aguardar mantenedor antes de PR |
-| CLI-009 | P0 | VT Code | `vinhnx/vtcode` | concluida | `pr-docs` / `config-only` | `published-pr` | `feat/omniroute-integration` | `256682d10c72f3e6e145d852b6d9d53f5c471988` | [upstream #717](https://github.com/vinhnx/VTCode/pull/717) | — | not-in-catalog | PR documental aberta e mergeable; release `0.141.10`; custom provider `/v1`, Bearer, `auto`, discovery manual, streaming/tools; 10 testes config verdes; nextest/docs checks bloqueados por ambiente; acompanhar CI/mantenedor |
-| CLI-010 | P0 | OpenHands CLI | `OpenHands/OpenHands-CLI` | concluida | `config-only` | not-applicable | `feat/omniroute-openhands-cli-integration` | — | — | — | not-in-catalog | SHA `2df8a283`; `LLM_BASE_URL=/v1`, `LLM_API_KEY`, modelo obrigatório `openai/auto`, Chat Completions/SSE/tools; 63 testes focados e mock verdes; sem PR artificial |
-| CLI-011 | P0 | gptme | `gptme/gptme` | concluida | `config-only` | not-applicable | `feat/omniroute-gptme-integration` | — | — | — | not-in-catalog | SHA `7fe250529`; provider TOML nomeado, `/v1/chat/completions`, `/v1/models`, Bearer, streaming/tools; compileall verde, pytest bloqueado por deps; docs genericas ja cobrem |
-| CLI-012 | P0 | Nanocoder | `Nano-Collective/nanocoder` | concluida | `config-only` | not-applicable | `feat/omniroute-nanocoder-integration` | — | — | — | not-in-catalog | SHA `becae998`; `createOpenAICompatible`, `/v1/models`, streaming/native tools + XML/JSON fallback; types/format/lint/build verdes; suite ampla com falhas preexistentes; sem PR artificial |
-| CLI-013 | P0 | RA.Aid | `ai-christianson/RA.Aid` | concluida | `config-only` | not-applicable | `feat/omniroute-ra-aid-integration` | — | — | — | not-in-catalog | SHA `e71bb83`; provider `openai-compatible`, `/v1/chat/completions`, Bearer, modelo explicito/`auto`, function tools; 762 testes + 62 focados e smoke verdes; sem Responses/stream HTTP garantido; Aider exige config separada; sem PR artificial |
-| CLI-014 | P0 | CoreCoder | `he-yufeng/CoreCoder` | concluida | `pr-docs` / `config-only` | `published-pr` | `feat/omniroute-integration` | `f4d2851649e5dda20738c313a8a94337b24eeb9d` | [upstream #20](https://github.com/he-yufeng/CoreCoder/pull/20) | — | not-in-catalog | PR documental aberta, nao draft e mergeable; `/v1/chat/completions`, Bearer, `auto`, streaming/native tools; 86 testes, compileall, build, twine e smoke verdes; Ruff mantem 41 falhas preexistentes; acompanhar CI/mantenedor |
-| CLI-015 | P1 | Grok CLI | `superagent-ai/grok-cli` | concluida | `config-only` | not-applicable | `feat/omniroute-grok-cli-integration` | — | — | — | not-in-catalog | SHA `fb97af8`; `GROK_BASE_URL`/`--base-url`, Chat Completions/SSE, Bearer, `auto` e tools confirmados; 47/48 suites e 246 testes no gate isolado, 6 arquivos/39 testes focados verdes; Node não carrega `bun:sqlite`; Responses/search/STT/Batch/midia não garantidos; monitorar PRs #290/#349 |
-| CLI-016 | P1 | Gitlawb Zero | `Gitlawb/zero` | concluida | `config-only` | not-applicable | `feat/omniroute-gitlawb-zero-integration` | — | — | — | not-in-catalog | SHA `8e266797`; release `v0.6.0`; provider custom `/v1`, Bearer, `auto`, Chat/SSE/tools, usage e `/v1/models` confirmados; Go test/vet/fmt e smoke verdes; release build bloqueado por falta de espaco; politica exige issue aprovada; sem contribuicao nominal artificial |
-| CLI-017 | P1 | DeepSeek Reasonix | `esengine/DeepSeek-Reasonix` | concluida | `config-only` | not-applicable | `feat/omniroute-deepseek-reasonix-integration` | — | — | — | not-in-catalog | SHA `1c62489d`; release `v1.19.1`; `kind=openai`, `/v1/chat/completions`, Bearer, `auto`, SSE/tools, `/v1/models` e reasoning confirmados; suite completa, vet, fmt, build e smoke verdes apos remover env SSH do runner; sem PR/issue redundante |
-| CLI-018 | P1 | KlaatCode | `KlaatAI/klaatcode` | concluida | `config-only` | not-applicable | `feat/omniroute-klaatcode-integration` | — | — | — | not-in-catalog | SHA `0d20f24a`; release `V2.4.0`; `customModels` com `/v1`, Bearer, `auto`, Chat/SSE/tools confirmados; 316 testes, 33 fixtures e build verdes; typecheck local divergiu do CI verde; custom endpoint e apenas TUI; divergencia de metadata de licenca registrada; sem contribuicao nominal artificial |
-| CLI-019 | P1 | CodeMini CLI | `havingautism/Codemini-CLI` | concluida | `config-only` | not-applicable | `feat/omniroute-codemini-cli-integration` | — | — | — | not-in-catalog | SHA `a3764b21`; package `0.8.3`; gateway `/v1`, Bearer persistido, `auto`, Chat/SSE/usage/tools e tool round trip confirmados; `/models` e probe, nao picker; 122/123 testes, 10 focados e pack-imports verdes; sem PR nominal redundante |
-| CLI-020 | P1 | Zot | `patriceckhart/zot` | concluida | `config-only` | not-applicable | `feat/omniroute-zot-integration` | — | — | — | not-in-catalog | SHA `f3d8eb66`; release `v0.3.29`; custom provider `omniroute` em `models.json`, `/v1`, Bearer, `auto`, Chat/SSE/tools/reasoning opt-in e cache usage confirmados; `--base-url` e so override; PR #36 ja cita OmniRoute; race suite/build/vet/fmt verdes |
-| CLI-021 | P1 | Octomind | `Muvon/octomind` | concluida | `config-only` | not-applicable | `feat/omniroute-octomind-integration` | — | — | — | not-in-catalog | SHA `65ab1db1`; release `0.39.0`; provider `local:auto` usa endpoint completo `/v1/chat/completions`, Bearer opcional, Chat JSON buffered, tools/reasoning/usage; sem SSE/Responses/discovery; fmt/fetch e smokes com/sem auth verdes; suite ampla nao executada por disco/contencao |
-| CLI-022 | P1 | DvalinCode | `arthurpanhku/dvalincode` | concluida | `config-only` | not-applicable | `feat/omniroute-dvalincode-integration` | — | — | — | not-in-catalog | SHA `7d42664a`; release `v0.14.1`; provider OpenAI-compatible custom com `/v1`, Bearer via env, `auto`, Chat/SSE/usage/tools e tool round trip confirmados; `provider test` bloqueado por trusted presets; issues #109/#118/#135 ja cobrem melhorias genericas; sem PR nominal |
-| CLI-023 | P1 | Coro Code | `Blushyes/coro-code` | concluida | `config-only` | not-applicable | `feat/omniroute-coro-code-integration` | — | — | — | not-in-catalog | SHA `679c57af`; release `v0.0.8`; `OPENAI_BASE_URL=/v1`, Bearer, `auto`, Chat JSON e function tools/tool loop confirmados; streaming existe mas nao e usado pelo agente; sem Responses/discovery; `cargo check`/fmt bloqueados por drift preexistente; risco de LICENSE ausente; sem PR nominal |
-| CLI-024 | P1 | Mini-Kode | `minmaxflow/mini-kode` | concluida | `config-only` | not-applicable | `feat/omniroute-mini-kode-integration` | — | — | — | not-in-catalog | SHA `4e7f9767`; release/tag npm `0.2.3`; provider custom por `MINIKODE_BASE_URL=/v1`, Bearer, `auto`, Chat/SSE e tools/tool loop confirmados; sem Responses/discovery/reasoning dedicado; sem PR nominal redundante |
-| CLI-025 | P1 | Late CLI | `mlhher/late-cli` | concluida | `config-only` | not-applicable | `feat/omniroute-late-cli-integration` | — | — | — | not-in-catalog | SHA `26814e62`; release `v1.4.2`; `OPENAI_BASE_URL=/v1`, Bearer, `auto`, Chat/SSE/usage/reasoning_content/tools e tool round trip confirmados; probes `/props`/`/v1/models` nao sao picker; BSL 1.1/CLA; sem PR nominal |
-| CLI-026 | P1 | Agentty | `1ay1/agentty` | concluida | `config-only` | not-applicable | `feat/omniroute-agentty-integration` | — | — | — | not-in-catalog | SHA `e947b26c`; release `v0.2.10`; custom host `127.0.0.1:20128`, Bearer, Chat/SSE/tools e `/v1/models` confirmados; Responses/reasoning/tool round trip dinamico nao confirmados; MIT; sem PR nominal |
-| CLI-027 | P1 | Aizen | `aizen-stack/aizen` | concluida | `config-only` | not-applicable | `feat/omniroute-aizen-integration` | — | — | — | not-in-catalog | SHA `3d8ae0f6`; release `v0.5.4`; `AIZEN_BASE_URL=/v1`, Bearer, `auto`/modelo literal, Chat/SSE/reasoning_content e `/v1/models`; tools confirmadas estaticamente, sem smoke dinamico; PolyForm Noncommercial/CLA; sem PR nominal |
-| CLI-028 | P1 | Clif-Code | `DLhugly/Clif-Code` | concluida | `config-only` | not-applicable | `feat/omniroute-clif-code-integration` | — | — | — | not-in-catalog | SHA `282a787a`; release `v1.72.0`; `CLIFCODE_API_URL=/v1`, Bearer, `auto`, Chat/SSE/usage/tools e tool loop confirmados por fonte; smoke bloqueado por binario ausente; sem Responses/reasoning; licença proprietária conflitante com FSL declarada exige revisão jurídica; sem PR nominal |
-| CLI-029 | P1 | Minacode | `hit9/minacode` | concluida | `config-only` | not-applicable | `feat/omniroute-minacode-integration` | — | — | — | not-in-catalog | SHA `d4ea4a97`; release `v0.18.1`; TOML custom `/v1`, key obrigatória, `auto`, Chat/Responses/Anthropic, SSE/tools/reasoning/discovery confirmados; smoke de protocolo Chat+Responses+models e compileall verdes; CI remoto verde; sem PR nominal |
-| CLI-030 | P1 | YottaCode | `yottadynamics/yottacode` | concluida | `config-only` | not-applicable | `feat/omniroute-yottacode-integration` | — | — | — | not-in-catalog | SHA `039f61ce`; release `v0.3.1`; provider `openai-compatible`, `/v1`, Bearer, `/v1/models`, Chat/SSE/tools/reasoning parsing confirmados; smoke oficial com mock passou; Go 1.26 nao instalado e gates completos nao executados por espaco; sem PR nominal |
-| CLI-031 | P1 | aichat | `sigoden/aichat` | concluida | `config-only` | not-applicable | `feat/omniroute-aichat-integration` | — | — | — | not-in-catalog | SHA `82976d3`; package/release `v0.30.0`; provider `openai-compatible` com base `/v1`, Bearer opcional e modelo `auto`; Chat stream/JSON, reasoning e tool round-trip confirmados; Responses ausente (#1431); limites de tool SSE ja cobertos por #1454/#1495 e PR #1496; sem publicacao nominal |
-| CLI-032 | P1 | ShellGPT | `TheR1D/shell_gpt` | concluida | `config-only` | not-applicable | `feat/omniroute-shellgpt-integration` | — | — | — | not-in-catalog | SHA `a082bd53`; release `1.5.1`; `API_BASE_URL=/v1`, `OPENAI_API_KEY`, `DEFAULT_MODEL=auto` e `USE_LITELLM=false`; smoke real confirmou env e `.sgptrc`, Chat/SSE e Bearer; issue #718 nao reproduz no HEAD; CI baseline vermelho por temperatura default independente; sem publicacao nominal |
-| CLI-033 | P1 | Mistral Vibe | `mistralai/mistral-vibe` | concluida | `config-only` | not-applicable | `feat/omniroute-mistral-vibe-integration` | — | — | — | not-in-catalog | SHA/release `99a6efa9` / `v2.23.2`; `GenericBackend` custom com base `/v1`, Bearer, Chat/SSE, usage, tools e reasoning; smoke do binario oficial verde; #790 cobre somente discovery `/v1/models`; upstream nao aceita contribuicoes de codigo no momento; sem publicacao |
-| CLI-034 | P1 | OpenSquilla | `opensquilla/opensquilla` | concluida | `config-only` | not-applicable | `feat/omniroute-opensquilla-integration` | — | — | — | not-in-catalog | `custom` com `/v1`, Bearer opcional, Chat/SSE, tools, reasoning recebido, usage e `/v1/models`; smoke provider-level verde; monitorar issue #912 do probe custom; sem publicacao nominal |
-| CLI-035 | P1 | Kode CLI | `shareAI-lab/Kode-cli` | concluida | `config-only` | not-applicable | `feat/omniroute-kode-cli-integration` | — | — | — | not-in-catalog | `custom-openai` com `/v1`, discovery `/v1/models`, fallback manual, Bearer, Chat/SSE, tools/tool round-trip e persistencia; smoke runtime bloqueado por Bun/artefato ausente; CI baseline vermelho por formatacao; sem publicacao nominal |
-| CLI-036 | P1 | Neovate Code | `neovateai/neovate-code` | concluida | `config-only` | not-applicable | `feat/omniroute-neovate-code-integration` | — | — | — | not-in-catalog | provider JSON custom normalizado para OpenAI-compatible, `/v1`, Bearer, Chat/SSE, tools/tool round-trip; model catalog declarado (sem discovery); smoke do pacote publicado verde; sem publicacao nominal |
-| CLI-037 | P1 | Deep Agents Code | `langchain-ai/deepagents` | concluida | `config-only` | not-applicable | `feat/omniroute-deepagents-code-integration` | — | — | — | not-in-catalog | SHA `46ee772b4`; `deepagents-code==0.1.51`; provider `openai`, base OmniRoute `/v1`, model `openai:auto`; Responses e default, Chat usa `use_responses_api=false`; smoke de config verde, sem HTTP/runtime por deps e disco; #3973/#3287 ja cobrem os pontos genericos; sem publicacao nominal |
-| CLI-038 | P1 | OpenHands principal | `OpenHands/OpenHands` | concluida | `config-only` | not-applicable | `feat/omniroute-openhands-main-integration` | — | — | — | not-in-catalog | SHA `1708efc44`; Agent Canvas `1.8.0`; `openai/auto` + base `/v1` + API key + `api_mode=chat`; LiteLLM envia `model=auto`, Chat/SSE/tools estruturais; sem discovery generico `/v1/models`; PRs OmniRoute [#15189](https://github.com/OpenHands/OpenHands/pull/15189)/[#15211](https://github.com/OpenHands/OpenHands/pull/15211) fechadas sem merge; sem nova publicacao |
-| CLI-039 | P1 | SWE-agent | `SWE-agent/SWE-agent` | concluida | `config-only` | not-applicable | `feat/omniroute-swe-agent-integration` | — | — | — | not-in-catalog | SHA `3ea751c08`; release `v1.1.0`; LiteLLM com `openai/<model-id>`, `api_base=/v1` e chave por env; Chat/tools/tool round-trip e batch confirmados por fonte; reasoning parcial; smoke HTTP bloqueado por deps ausentes; sem publicacao nominal |
-| CLI-040 | P1 | AutoCodeRover | `AutoCodeRoverSG/auto-code-rover` | concluida | `pr-generic` | `validating` | `feat/omniroute-auto-code-rover-integration` | — | — | — | not-in-catalog | SHA `585d3e639`; patch local sem commit em 4 arquivos corrige `litellm-generic-openai/auto`, base `/v1`, precedencia da chave e pricing desconhecido; 9 testes focados com stubs, tracer source-only, compileall e diff-check verdes; sem HTTP real; licenca SONAR Source-Available exige gate juridico antes de publicar |
-| CLI-041 | P2 | Claurst | `Kuberwastaken/claurst` | concluida | `config-only` | not-applicable | `feat/omniroute-claurst-integration` | — | — | — | not-in-catalog | SHA `595b0ebe3`; `custom-openai` com settings persistidos, base `/v1`, `CUSTOM_OPENAI_API_KEY`, modelo `auto`, Chat/SSE/tools e `/v1/models`; CI upstream verde; sem build/smoke local e sem publicacao nominal; monitorar PR #365 sem duplicar |
-| CLI-042 | P2 | Codebuff | `CodebuffAI/codebuff` | concluida | `blocked` / `issue-first` | `blocked` | `feat/omniroute-codebuff-integration` | — | — | — | not-in-catalog | SHA `195b9bef6`; main nao expoe base/chave/provider custom na CLI/SDK; PR upstream existente [#693](https://github.com/CodebuffAI/codebuff/pull/693) cobre a lacuna, observada OPEN/CONFLICTING/DIRTY; nao criar patch concorrente; acompanhar #693 e validar apos merge/port |
-| CLI-043 | P2 | Devon | `entropy-research/Devon` | concluida | `pr-generic` | validating | `feat/omniroute-devon-integration` | — | — | [upstream #100](https://github.com/entropy-research/Devon/issues/100) | not-in-catalog | SHA `8f68f1d74`; diff local genérico em 5 arquivos, sem commit; reprodução literal DeepSeek/OpenRouter e resume corrigidos; 9 testes focados, compileall e diff-check verdes; Standards/Spec aprovados; aguardar autorização antes de fork/push/PR |
-| CLI-044 | P2 | Letta Code | `letta-ai/letta-code` | concluida | `config-only` | not-applicable | `feat/omniroute-letta-code-integration` | — | — | — | integrated | SHA `09aff1bb4`; já coberta pelo provider local `lmstudio` (`lmstudio_openai`), discovery `/api/v0/models`→`/v1/models`, Chat/SSE/tools; 8 testes OmniRoute verdes; sem PR nominal |
-| CLI-045 | P2 | CodeMachine CLI | `moazbuilds/CodeMachine-CLI` | concluida | `config-only` | not-applicable | `feat/omniroute-codemachine-cli-integration` | — | — | — | not-in-catalog | SHA `572def63e`; integração indireta por OpenCode custom `@ai-sdk/openai-compatible`, base `/v1`, chave por env e `omniroute/auto`; provider/model reconhecidos no smoke de config; alternativa Claude Code; sem PR nominal |
-| CLI-046 | P2 | Groq Code CLI | `build-with-groq/groq-code-cli` | concluida | `pr-generic` | `awaiting-maintainer` | `feat/omniroute-groq-code-cli-integration` | — | — | — | not-in-catalog | SHA `a303eb4be`; `groq-sdk@0.27.0` fixa `/openai/v1/chat/completions`, logo não há config-only para OmniRoute; mock confirmou path/Bearer; PR existente [#7](https://github.com/build-with-groq/groq-code-cli/pull/7) é a duplicata natural, mas precisa distinguir Groq-compatible de OpenAI-compatible; 17 testes oficiais + 5 testes de contexto, build e mock verdes; clone limpo, sem patch/publicação |
-| CLI-047 | P2 | Dexto | `truffle-ai/dexto` | concluida | `config-only` | `not-applicable` | `feat/omniroute-dexto-integration` | — | — | — | not-in-catalog | SHA `4108a9c73`; provider `openai-compatible` nativo exige `baseURL`, aceita modelo arbitrário, Bearer opcional, Chat/SSE/tools e reasoning effort; receita `/v1` + `auto`; 175 testes focados e builds llm/core verdes; TS2741 em chatgpt-oauth é baseline; ELv2; sem PR/issue nominal |
-| CLI-048 | P2 | claw-code-agent | `HarnessLab/claw-code-agent` | concluida | `config-only` | `not-applicable` | `feat/omniroute-claw-code-agent-integration` | — | — | — | not-in-catalog | SHA `167571da8`; `OPENAI_BASE_URL=http://127.0.0.1:20128/v1`, Bearer, model manual/`auto`, Chat/SSE/tools/usage confirmados; smoke `MOCK_SMOKE_OK`, 80 testes focados; sem discovery/Responses API; licença não identificada (`license: null`); sem PR/issue |
-| CLI-049 | P2 | g3 | `dhanji/g3` | concluida | `pr-generic` | `validating` | `feat/omniroute-g3-integration` | — | — | [upstream #70](https://github.com/dhanji/g3/issues/70) | not-in-catalog | SHA `0ddb052d2`; diff local provider-neutral em `provider_registration.rs`, 1 arquivo `+25/-1`, corrige registro `custom`→`custom.default`; `cargo check -p g3-config`, 6 testes config e diff-check verdes; teste focal escrito mas build bloqueado em `x11.pc`; manifesto declara MIT sem arquivo LICENSE; Standards/Spec centrais aprovados; sem publicação |
-| CLI-050 | P2 | San | `genai-io/san` | concluida | `config-only` | `not-applicable` | `feat/omniroute-san-integration` | — | — | — | not-in-catalog | SHA `e45ec0ef7`; Apache-2.0/release v1.22.1; provider Custom com base `/v1`, Bearer, `/models`, Chat/SSE/tools/tool result e reasoning best-effort; smoke HTTP de dois turnos e gates Go focados verdes; sem provider nominal ou publicação |
-| CLI-051 | P2 | Waveloom | `Menfre01/waveloom` | concluida | `config-only` | `not-applicable` | `feat/omniroute-waveloom-integration` | — | — | — | not-in-catalog | SHA `293d5cd11`; Apache-2.0/release v0.5.1; adapter OpenAI com `/v1`, Bearer, `/models`, SSE, 14 tools, tool-result round-trip e sessões; smoke do binário oficial verde e CI remoto do HEAD verde; reasoning/cache avançados não são projetados; sem publicação |
-| CLI-052 | P2 | picocode | `jondot/picocode` | concluida | `config-only` | `not-applicable` | `feat/omniroute-picocode-integration` | — | — | — | not-in-catalog | SHA `064a2a6ea`; MIT/release v0.6.0; Rig 0.28 lê `OPENAI_BASE_URL` e usa Responses `/v1/responses`; smoke confirmou Bearer, `auto`, 11 tools e function_call_output; 7 testes/doc-tests verdes; fmt/clippy só baseline; sem PR/issue |
-| CLI-053 | P2 | QQCode | `qnguyen3/qqcode` | concluida | `config-only` | `not-applicable` | `feat/omniroute-qqcode-integration` | — | — | — | not-in-catalog | SHA `be6a96ce7`; Apache-2.0/release v1.2.0; provider arbitrário + `GENERIC`/OpenAI com base `/v1`; smoke confirmou JSON/SSE, Bearer, extra_body, reasoning e tool-result; backend 20/20, ACP 13+1 skip, observer 11/11, compileall/helps verdes; sem PR/issue |
-| CLI-054 | P2 | Keen Code | `mochow13/keen-code` | concluida | `config-only` | `not-applicable` | `feat/omniroute-keen-code-integration` | — | — | — | not-in-catalog | SHA `ee2eaf0f4`; MIT/release v0.40.0; receita manual `openai-compatible` + `/v1` + Bearer + model arbitrário; smoke oficial confirmou Chat/SSE, tools/tool-result, usage e reasoning replay; provider oculto apenas no picker; CI remoto verde; sem PR/issue |
-| CLI-055 | P2 | Grinta | `josephsenior/Grinta-Coding-Agent` | concluida | `config-only` | `not-applicable` | `feat/omniroute-grinta-integration` | — | — | — | not-in-catalog | SHA `df7437524`; provider OpenAI-compatible com `LLM_API_KEY`, model `auto`, base `/v1`; smoke Chat/SSE/tools/tool-result/reasoning/usage/cache verde; 183 testes focados, compileall e Ruff verdes; sem PR/issue nominal |
-| CLI-056 | P2 | Zap | `zap-coding-agent/zap-coding-agent` | concluida | `config-only` | `not-applicable` | `feat/omniroute-zap-integration` | — | — | — | not-in-catalog | SHA `f0203f872`; provider arbitrário `kind=openai`, base `/v1`, Bearer, discovery `/models`, Chat JSON/SSE, tools/tool-result, reasoning e usage confirmados; cargo check + 16 testes/gates focados verdes; issue #2 confirma arquitetura; sem PR nominal |
-| CLI-057 | P2 | Binharic | `CogitatorTech/binharic-cli` | concluida | `pr-generic` | `validating` | `feat/omniroute-binharic-integration` | — | — | — | not-in-catalog | SHA `52ccca70b`; patch sem commit em `provider.ts` + teste: aplica `baseURL` ao OpenAI/Anthropic e usa Chat Completions para base customizada; RED→GREEN, 14 focal, 88 arquivos/774 testes, typecheck/build e smoke wire verdes; lint upstream bloqueado; sem publicação |
-| CLI-058 | P2 | Darce | `AmerSarhan/darce-cli` | concluida | `config-only` | `not-applicable` | `feat/omniroute-darce-integration` | — | — | — | not-in-catalog | SHA `1b90c379a`; MIT declarada no package/npm sem arquivo LICENSE; `DARCE_API_BASE` raiz sem `/v1`, `DARCE_API_KEY`, `DARCE_MODEL=auto`; smoke PTY do binário confirmou 2 Chat/SSE, 7 tools, tool-result e Bearer; 106 testes/build verdes; sem MCP/ACP/A2A; sem PR/issue |
-| CLI-059 | P2 | CLAII | `agencyswarm/CLAII` | concluida | `pr-generic` | `blocked` | `feat/omniroute-claii-integration` | — | — | — | not-in-catalog | SHA `89d42311b`; patch sem commit em README/config/providers/test: `CLAII_API_KEY`, `CLAII_BASE_URL` origem sem `/v1beta`, model runtime e reject explícito; 4 wire/loop + 10 calculator + pip install + smoke CLI verdes; unittest discover falha só baseline `calculator`/`pkg`; sem MCP/ACP/A2A; **All Rights Reserved**, não publicar sem autorização jurídica |
-| CLI-060 | P2 | nori-cli | `tilework-tech/nori-cli` | concluida | `config-only` | `not-applicable` | `feat/omniroute-nori-cli-integration` | — | — | — | not-in-catalog | SHA `829ecf3fd`; Apache-2.0/v0.24.0; Nori custom ACP → OpenCode `opencode-ai@1.18.11` → OmniRoute `/v1`; MCP separado por `/api/mcp/stream` ou stdio; 5 testes focados, cargo build nori e smoke ACP Nori→OpenCode verdes; sem patch/publicação |
-| CLI-061 | P2 | cursor-agent clone | `civai-technologies/cursor-agent` | concluida | `config-only` | `not-applicable` | `feat/omniroute-cursor-agent-clone-integration` | — | — | — | not-in-catalog | SHA `d21a8f3d4`; MIT/v0.1.39; SDK OpenAI usa base `/v1`, Anthropic usa raiz; smokes de 2 turnos/tools verdes; factory rejeita `auto` puro; 23 testes, mypy/build verdes; sem patch/publicação |
-| CLI-062 | P2 | Free Code | `freecodexyz/free-code` | concluida | `config-only` | `blocked` | `feat/omniroute-free-code-integration` | — | — | [upstream #20](https://github.com/freecodexyz/free-code/issues/20) | not-in-catalog | SHA `6b25ab68b`; URL antiga `paoloanzn/free-code` redireciona; base Anthropic raiz, `model=auto`, stream/tools/MCP; build verde; sem LICENSE/campo license e código atribuído à Anthropic, não publicar |
-| CLI-063 | P2 | Claude Engineer | `Doriandarko/claude-engineer` | concluida | `config-only` / `pr-generic` | `blocked` | `feat/omniroute-claude-engineer-integration` | — | [upstream #250](https://github.com/Doriandarko/claude-engineer/pull/250) | [upstream #116](https://github.com/Doriandarko/claude-engineer/issues/116) | not-in-catalog | SHA `0a9e4b309`; v3 funciona por base Anthropic raiz com modelo fixo; #250 já adiciona `ANTHROPIC_MODEL`; arquivo LICENSE ausente apesar de declaração MIT; sem patch concorrente/publicação |
-| CLI-064 | P2 | Smol Developer | `smol-ai/developer` | concluida | `config-only` | `not-applicable` | `feat/omniroute-smol-developer-integration` | — | — | — | not-in-catalog | SHA `a6747d1a6`; `OPENAI_API_BASE=/v1`, `auto`, 3 Chat calls, SSE/function calling e Agent Protocol validados; gates de runtime verdes, build metadata preexistente; sem patch/publicação |
-| CLI-065 | P2 | Agentless | `OpenAutoCoder/Agentless` | concluida | `config-only` | `not-applicable` | `feat/omniroute-agentless-integration` | — | — | — | not-in-catalog | SHA `5ce5888b9`; OpenAI chat + embeddings funcionam com bases distintas; Anthropic normal/cache histórico validados; DeepSeek fixa host; pre-commit/compileall verdes; sem patch/publicação |
-| CLI-066 | P2 | Amazon Q Developer CLI | `aws/amazon-q-developer-cli` | concluida | `viable-mcp` / `needs-wrapper` | `not-applicable` | `feat/omniroute-amazon-q-developer-cli-integration` | — | — | — | not-in-catalog | SHA `15cc8f3cd`; modelo usa AWS JSON/EventStream Bearer/SigV4 e não `/v1`; MCP stdio imediato, HTTP legado com ressalva; upstream issue-first/manutenção crítica; sem patch/publicação |
-| CLI-067 | P2 | nanobot | `HKUDS/nanobot` | concluida | `config-only` | `not-applicable` | `feat/omniroute-nanobot-integration` | — | — | — | not-in-catalog | HEAD `44b7e1bf4`; provider dinâmico OpenAI-compatible com base `/api/v1` e modelo `omniroute/auto`; Chat/SSE/tools/reasoning/usage/images/discovery e retry validados; 424 testes + Ruff; sem PR nominal |
-| CLI-068 | P2 | ZeroClaw | `zeroclaw-labs/zeroclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-zeroclaw-integration` | — | — | — | not-in-catalog | HEAD `4770420ab`; `custom.omniroute`, base `/v1`, Bearer, `auto`, Chat/Responses e tools nativas opt-in; 1.173 unit + 1 integração, fmt/config/smoke verdes; sem PR nominal |
-| CLI-069 | P2 | NanoClaw | `gavrielc/nanoclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-nanoclaw-integration` | — | — | — | not-in-catalog | HEAD `dfac7e0af`; provider Claude existente aponta para raiz Anthropic OmniRoute e OneCLI guarda a chave; baseline e 49 testes OmniRoute verdes; Codex #3155/#1984 e OpenCode #2985 ficam como follow-ups; sem PR |
-| CLI-070 | P2 | PicoClaw | `sipeed/picoclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-picoclaw-integration` | — | — | — | not-in-catalog | HEAD `49183d7`, `/api/v1`, `openai/auto` → `auto`; Chat/SSE/tools/usage/images/discovery; Go ausente, testes locais não executados; issue router #3298; sem publicação |
-| CLI-071 | P2 | IronClaw | `nearai/ironclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-ironclaw-integration` | — | — | — | not-in-catalog | HEAD `4b71aaae`; `openai_compatible` `/api/v1`, Chat/SSE/tools/images/discovery; 889+5 testes e fmt verdes; reasoning #3673; sem publicação |
-| CLI-072 | P2 | NullClaw | `nullclaw/nullclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-nullclaw-integration` | — | — | — | not-in-catalog | HEAD `d8a802fd`; custom `/api/v1`, Chat/Responses/Anthropic, tools/streaming/usage/images; Zig ausente, CI run 30788444193 verde; sem publicação |
-| CLI-073 | P2 | Moltis | `moltis-org/moltis` | concluida | `config-only` | `not-applicable` | `feat/omniroute-moltis-integration` | — | — | — | not-in-catalog | HEAD `678d407`; `custom-omniroute`, `/api/v1`, `auto`, Chat/SSE/tools/reasoning/usage/images; 401 testes + fmt verdes; MCP/ACP separados; sem publicação |
-| CLI-074 | P2 | GitClaw | `open-gitagent/gitclaw` | concluida | `config-only` | `not-applicable` | `feat/omniroute-gitclaw-integration` | — | — | — | not-in-catalog | GitAgent HEAD `d3e25d7`; base `/api/v1`, `omniroute:auto`, Chat/SSE/tools/images; build + 65 testes + smoke verdes; reasoning=false no descriptor; sem publicação |
-| CLI-075 | P2 | LionClaw | `moshthepitt/lionclaw` | concluida | `patch-required` / `issue-first` | `awaiting-maintainer` | `feat/omniroute-lionclaw-integration` | — | — | — | not-in-catalog | HEAD `cb59b23d`; Codex app-server não projeta config.toml/secret para runtime confinado; patch seguro necessário, alinhado à #157; gates locais bloqueados por uv/podman; CI verde; sem publicação |
-| CLI-076 | P3 | VibePod | `VibePod/vibepod-cli` | concluida | `config-only` | `not-applicable` | `feat/omniroute-vibepod-integration` | — | — | — | not-in-catalog | Claude Code via `/api`, container usa `host.docker.internal`; Codex não injeta chave; compileall verde, pytest bloqueado por typer; sem publicação |
-| CLI-077 | P3 | zeroshot | `the-open-engine/zeroshot` | concluida | `config-only` | `not-applicable` | `feat/omniroute-zeroshot-integration` | — | — | — | not-in-catalog | Gateway OpenAI `/api/v1`, `auto`, tools fail-closed; 22 testes + build verdes; sem streaming JSON/reasoning/MCP no gateway; sem publicação |
-| CLI-078 | P3 | Fractal | `plasma-ai/fractal` | concluida | `config-only` / `needs-wrapper` | `awaiting-maintainer` | `feat/omniroute-fractal-integration` | — | — | — | not-in-catalog | Codex Responses por node `CODEX_HOME`; caveat tmux quente não encaminha `OMNIROUTE_API_KEY`; fix genérico recomendado, sem PR |
-| CLI-079 | P3 | Bernstein | `chernistry/bernstein` | concluida | `config-only` | `not-applicable` | `feat/omniroute-bernstein-integration` | — | — | — | not-in-catalog | Canonical `sipyourdrink-ltd/bernstein`; openai_agents `/api/v1`, auto, api_key_env allowlisted; testes bloqueados por openai ausente; sem publicação |
-| CLI-080 | P3 | Traycer | `traycerai/traycer` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-traycer-integration` | — | — | — | not-in-catalog | Harness OpenCode + provider `@ai-sdk/openai-compatible`, `/api/v1`, `omniroute/auto`; host central fechado; sem publicação |
-| CLI-081 | P3 | h5i | `h5i-dev/h5i` | concluida | `patch-required` | `awaiting-maintainer` | `feat/omniroute-h5i-integration` | — | — | — | not-in-catalog | Auth proxy/egress Codex fixos em OpenAI anulam base custom; patch seguro/policy-pinned necessário; CI externa verde; sem publicação |
-| CLI-082 | P3 | OMK | `dmae97/open-multi-agent-kit` | concluida | `viable-mcp` | `not-applicable` | `feat/omniroute-omk-integration` | — | — | — | not-in-catalog | pesquisa concluída neste lote; controle multiagente, MCP é caminho primário; sem provider nominal |
-| CLI-083 | P3 | kodo | `ikamensh/kodo` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-kodo-integration` | — | — | — | not-in-catalog | pesquisa concluída neste lote; orquestrador/agent child, propagar env/base/model ao agente filho |
-| CLI-084 | P3 | ORCH | `oxgeneral/ORCH` | concluida | `needs-wrapper` | `awaiting-maintainer` | `feat/omniroute-orch-integration` | — | — | — | not-in-catalog | pesquisa concluída neste lote; fila/controle sem provider LLM direto, wrapper/adaptador necessário |
-| CLI-085 | P3 | LoopTroop | `LoopTroop-ai/LoopTroop` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-looptroop-integration` | — | — | — | not-in-catalog | HEAD `cbfc81c5`; OpenCode recebe provider `@ai-sdk/openai-compatible`, `/api/v1`, `omniroute/auto`; 16 testes verdes; sem publicação |
-| CLI-086 | P3 | Galley | `shinpr/galley` | concluida | `patch-required` | `awaiting-maintainer` | `feat/omniroute-galley-integration` | — | — | — | not-in-catalog | HEAD `6bcc593d`; registry/transports fechados, requer transport OpenAI-compatible para executor e supervisor; Go ausente; sem publicação |
-| CLI-087 | P3 | Relay | `jcast90/relay` | concluida | `config-only` | `not-applicable` | `feat/omniroute-relay-integration` | — | — | — | not-in-catalog | HEAD `7bd5a2f6`; provider profile Codex com `OPENAI_BASE_URL`, key ref e modelo; smoke Responses obrigatório; MCP separado; sem publicação |
-| CLI-088 | P3 | SageCLI | `youwangd/SageCLI` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-sagecli-integration` | — | — | — | not-in-catalog | HEAD `c167712d`; Codex runtime, base/key configuradas fora do Sage; env plaintext caveat; 45 testes verdes; sem publicação |
-| CLI-089 | P3 | 5dive | `5dive-ai/5dive` | concluida | `patch-required` | `awaiting-maintainer` | `feat/omniroute-5dive-integration` | — | — | — | not-in-catalog | HEAD `b64b6dac`; provider/base maps fechados; patch OpenAI-compatible genérico; 50 testes focados verdes; sem publicação |
-| CLI-090 | P3 | agx | `ramarlina/agx` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-agx-integration` | — | — | — | not-in-catalog | HEAD `e674cec1`; Codex herda base/key/model; smoke Responses e governança `--full-auto`; Jest ausente; sem publicação |
-| CLI-091 | P3 | claude-code-router | `musistudio/claude-code-router` | concluida | `config-only` | `not-applicable` | `feat/omniroute-claude-code-router-integration` | — | — | — | not-in-catalog | HEAD `bc8a8e62`; provider custom OpenAI/Anthropic/Gemini, Chat/Responses; smoke por protocolo; sem publicação |
-| CLI-092 | P3 | cc-router | `finch-xu/cc-router` | concluida | `config-only` | `not-applicable` | `feat/omniroute-cc-router-integration` | — | — | — | not-in-catalog | HEAD `c4c7579`; custom Responses/Chat com base/path/header, SSE/tools/reasoning; cargo bloqueado por glib; sem publicação |
-| CLI-093 | P3 | OneCLI | `onecli/onecli` | concluida | `config-only` | `not-applicable` | `feat/omniroute-onecli-integration` | — | — | — | not-in-catalog | HEAD `84ccaf74`; MITM credential gateway, generic host injection; MCP separado; sem publicação |
-| CLI-094 | P3 | agent-browser | `vercel-labs/agent-browser` | concluida | `config-only` | `not-applicable` | `feat/omniroute-agent-browser-integration` | — | — | — | not-in-catalog | HEAD `01c1147d`; chat usa gateway Chat/SSE/tools com env key/model; base precisa validar sufixo `/v1` para não duplicar path; cargo test exit 0; sem publicação |
-| CLI-095 | P3 | OpenWork | `different-ai/openwork` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-openwork-integration` | — | — | — | not-in-catalog | HEAD `ecb7a5f0`; OpenCode custom provider `/api/v1`, auth gerenciada; sem testes/deps; sem publicação |
-| CLI-096 | P3 | Agent Deck review | `asheshgoplani/agent-deck` | concluida | `config-only` indireto | `not-applicable` | `feat/omniroute-agent-deck-review` | — | — | — | integrated | HEAD `46300807`; env/model propagados a Codex/OpenCode; Go ausente; sem publicação |
-| CLI-097 | P4 | Pool | `poolsideai/pool` | concluida | `config-only` | `not-applicable` | `feat/omniroute-pool-integration` | — | — | — | not-in-catalog | HEAD `a6fe0ca1`; `pool exec --api-url` OpenAI-compatible, sandbox required, MCP/ACP separado; EULA; sem publicação |
-| CLI-098 | P4 | Junie CLI | `junie.jetbrains.com` | concluida | `config-only` | `not-applicable` | `feat/omniroute-junie-integration` | — | — | — | not-in-catalog | HEAD `d2701be6`; custom profile OpenAICompletion/Responses com baseUrl full e env ref; runtime proprietário/EAP; sem publicação |
-| CLI-099 | P4 | Cursor desktop | Anysphere | concluida | `config-only` limitado | `awaiting-maintainer` | `feat/omniroute-cursor-desktop-integration` | — | — | — | integrated | disclosure-only; BYO key/chat panel; Composer/Tab nativos; privado/MITM proibido; sem publicação |
-| CLI-100 | P4 | Windsurf | Codeium | concluida | `blocked-closed` / MCP-only | `awaiting-maintainer` | `feat/omniroute-windsurf-integration` | — | — | — | not-in-catalog | sem upstream/base custom; BYOK Anthropic específico; MCP separado; MITM proibido; sem publicação |
-| CLI-101 | P4 | Amp | Sourcegraph | concluida | `config-only` parcial / Enterprise-gated | `awaiting-maintainer` | `feat/omniroute-amp-integration` | — | — | — | not-in-catalog | CLI fechada/Amp Server; confirmar provider custom com suporte; MCP viável; sem publicação |
-| CLI-102 | P4 | Amazon Q/Kiro CLI | AWS | concluida | `patch-required` legado / `blocked-closed` Kiro | `awaiting-maintainer` | `feat/omniroute-amazon-q-integration` | — | — | — | integrated | Q usa AWS EventStream/SigV4; Kiro fechado sem base custom; MCP-only seguro; sem publicação |
-| CLI-103 | P4 | Cowork | Anthropic | concluida | `blocked-closed` / MCP-only | `not-applicable` | — | — | — | — | not-in-catalog | inferência gerida pela Anthropic sem BYOK/base custom; Custom Connector MCP remoto; MITM proibido; sem publicação |
-
-## Como atualizar
-
-Ao terminar uma fase, alterar somente os campos comprovados e deixar os demais como `—`. Para uma integracao concluida, registrar: versao/commit pesquisado, mecanismo, arquivos modificados, testes, branch, commit, URL de PR/issue e resposta do mantenedor. Se o caso for apenas configuracao, registrar o comando/config real e marcar `config-only` ou `viable-direct`, sem criar uma PR artificial.
-
-Antes de publicar uma contribuicao, aplicar o gate e o checklist de
-`05-plano-publicacao-prs-upstream.md`.

_references/_sistemas_cli/05-plano-publicacao-prs-upstream.md

@@ -1,659 +0,0 @@
-# Plano de publicacao de integracoes OmniRoute nos repositorios upstream
-
-> **Status da campanha de pesquisa:** `104/104` casos concluídos. Este plano continua sendo o procedimento de execução e publicação. A matriz final, inclusive os casos em que PR é inadequada ou impossível, está em `06-relatorio-final-104-clis-e-estrategia-prs.md`.
-
-**Data:** 2026-08-01
-**Escopo:** transformar a fila `CLI-000` a `CLI-103` em contribuicoes upstream verificadas,
-publicando PR, issue, guia de configuracao, adaptador ou conclusao de bloqueio conforme o mecanismo
-real de cada projeto.
-**Documentos-base:** `01-relatorio-pesquisa-clis-omniroute.md`,
-`02-prioridade-integracoes-clis.md`, `03-plano-integracao-em-lotes.md` e
-`04-tracker-integracoes-clis.md`.
-
-## 1. Resultado esperado
-
-Para cada repositorio pesquisado, a campanha deve produzir exatamente um resultado principal:
-
-1. **PR upstream de integracao nominal:** adiciona provider/preset `omniroute`, configuracao,
-   documentacao e testes quando isso combina com a arquitetura do projeto.
-2. **PR upstream de compatibilidade generica:** melhora suporte a endpoint customizado sem acoplar
-   o projeto ao nome OmniRoute, acompanhado de documentacao comprovando o uso com OmniRoute.
-3. **PR somente de documentacao:** registra uma configuracao funcional quando o codigo ja suporta
-   OmniRoute e o upstream aceita guias de terceiros.
-4. **Issue-first:** solicita decisao de arquitetura ou permissao antes do patch quando a politica do
-   repositorio, o desenho de providers ou o tamanho da mudanca exigirem alinhamento.
-5. **Configuracao sem PR:** documenta no OmniRoute um fluxo que ja funciona e para o qual uma mudanca
-   upstream seria redundante ou rejeitada pela politica do projeto.
-6. **Adaptador ACP/MCP/wrapper:** contribui no ponto de extensao correto quando o projeto nao consome
-   diretamente APIs de modelos.
-7. **MITM, produto fechado ou bloqueado:** registra evidencia e nao fabrica uma contribuicao que o
-   upstream nao pode receber.
-
-O objetivo e tentar integrar todos os casos tecnicamente possiveis. O objetivo nao e abrir uma PR em
-todo repositorio independentemente da arquitetura, licenca ou politica de contribuicao.
-
-## 2. Regras da campanha
-
-- Trabalhar em lotes de no maximo tres repositorios, com um subagente por repositorio.
-- Usar uma worktree isolada por repositorio dentro de `.claude/worktrees/`.
-- Nao editar implementacoes no checkout compartilhado.
-- Nao usar `git stash` ou `git pop`.
-- Fazer pesquisa fresca no commit atual do upstream antes de criar branch ou editar arquivos.
-- Ler `README`, `CONTRIBUTING`, templates de issue/PR, `SECURITY`, licenca e instrucoes locais de
-  agentes antes da implementacao.
-- Procurar issues e PRs abertas/fechadas sobre custom provider, base URL, OpenAI-compatible,
-  Anthropic-compatible, Gemini endpoint, proxy, gateway e OmniRoute antes de propor uma mudanca.
-- Registrar a base pesquisada por commit SHA ou release. Nao usar apenas `main` como evidencia.
-- Executar baseline antes da mudanca e distinguir falhas preexistentes de regressao.
-- Nunca expor `OMNIROUTE_API_KEY` ou qualquer outra credencial em comandos publicados, fixtures,
-  logs, commits, screenshots, PRs ou issues.
-- Nao inserir trailers, assinaturas ou rodapes de IA em commits, PRs ou issues.
-- Nao afirmar que uma integracao funciona sem um teste reproduzivel ou uma limitacao explicitamente
-  registrada.
-- Nao inventar fork, branch, commit, PR, issue, CI ou resposta de mantenedor.
-- Atualizar `04-tracker-integracoes-clis.md` ao concluir cada fase material.
-
-## 3. Unidade de trabalho por repositorio
-
-Cada item `CLI-NNN` deve possuir uma task individual. A task e o pacote de contexto entregue ao
-subagente e o registro que permite retomar o trabalho sem repetir ou perder evidencias.
-
-### 3.1 Cabecalho obrigatorio da task
-
-```md
-# CLI-NNN - <projeto> - integracao OmniRoute upstream
-
-- Repositorio canonico: <URL>
-- Prioridade/lote: <P0-P4 / lote>
-- Estado no catalogo OmniRoute: <integrated/not-in-catalog/parcial>
-- Evidencia inicial: <resumo vindo do relatorio; ainda nao confirmado>
-- Worktree: <caminho isolado>
-- Branch planejada: <definir somente depois de ler as regras upstream>
-- Commit/release pesquisado: —
-- Responsavel: <agente>
-- Estado: researching
-```
-
-### 3.2 Pesquisa obrigatoria dentro da task
-
-O subagente deve responder, com links e caminhos de codigo:
-
-1. Qual e o repositorio canonico, commit/release atual, licenca e nivel de atividade?
-2. Contribuicoes de forks externos sao aceitas? Ha CLA, DCO, sign-off ou issue previa obrigatoria?
-3. Qual e a arquitetura de providers e qual e o menor ponto de extensao?
-4. O cliente usa Chat Completions, Responses, Anthropic Messages, Gemini, ACP, MCP ou protocolo
-   proprietario?
-5. A base URL esperada e raiz, `/v1`, `/v1beta` ou uma URL completa por operacao?
-6. O cliente acrescenta algum sufixo automaticamente? Pode duplicar `/v1` ou `/v1beta`?
-7. Como a autenticacao e resolvida: variavel de ambiente, arquivo, keyring, OAuth ou header custom?
-8. Como os modelos sao definidos ou descobertos? O cliente chama um endpoint de modelos?
-9. Streaming, tool calling, reasoning, imagens e cancelamento funcionam pelo caminho escolhido?
-10. Ja existe issue, PR, discussao ou documentacao para endpoints customizados ou OmniRoute?
-11. Quais comandos oficiais executam install, format, lint, typecheck, build e testes?
-12. Qual contribuicao agrega valor real: codigo nominal, compatibilidade generica, docs, issue,
-    wrapper, MCP/ACP, somente configuracao ou nenhum patch?
-
-### 3.3 Gate de contribuicao
-
-Antes de editar, preencher uma decisao:
-
-| Decisao | Quando usar | Saida esperada |
-|---|---|---|
-| `pr-provider` | O upstream possui catalogo/presets de providers | Provider/preset OmniRoute, docs e testes |
-| `pr-generic` | Falta uma capacidade generica necessaria, como base URL customizavel | Patch generico, docs e teste com OmniRoute |
-| `pr-docs` | O codigo ja funciona e o upstream aceita guias de integracao | Guia minimo e validado |
-| `issue-first` | Mudanca arquitetural, politica incerta ou mantenedor exige proposta | Issue com evidencia e desenho do patch |
-| `config-only` | Tudo funciona por configuracao e um PR seria redundante | Guia no OmniRoute e smoke test |
-| `adapter-acp` | ACP e o ponto real de integracao | Adaptador/registro ACP e testes |
-| `adapter-mcp` | MCP e o ponto real de integracao | Config/servidor MCP e testes |
-| `wrapper` | O projeto apenas lanca outro agente | Wrapper/env forwarding e teste do filho |
-| `needs-mitm` | Endpoint fechado ou fixo | Pesquisa/guia MITM separado; sem PR artificial |
-| `blocked` | Licenca, politica, build ou protocolo impedem progresso | Evidencia reproduzivel e proximo desbloqueio |
-
-O gate deve incluir a alternativa rejeitada. Exemplo: `pr-provider` escolhido porque o repositorio
-mantem presets nomeados; `pr-docs` rejeitado porque a configuracao exigiria cinco campos internos e
-nao seria uma experiencia suportada.
-
-## 4. Ciclo completo da PR
-
-### Fase PR-0 - Preparar o contexto
-
-- Reservar o item no tracker e marcar pesquisa em andamento.
-- Confirmar que nenhum outro agente esta trabalhando no mesmo repositorio.
-- Resolver o repositorio canonico, fork existente e permissao de contribuicao.
-- Criar a task individual com a evidencia inicial marcada como hipotese.
-- Criar a worktree isolada somente depois de confirmar o upstream correto.
-
-### Fase PR-1 - Pesquisar upstream e contribuicoes existentes
-
-- Ler integralmente as regras do repositorio aplicaveis aos arquivos que podem mudar.
-- Mapear provider registry, configuracao, transporte HTTP, auth, modelo, streaming e ferramentas.
-- Pesquisar issues/PRs por termos de compatibilidade e pelo nome OmniRoute.
-- Registrar commit/release, caminhos e links de evidencia na task.
-- Escolher o gate de contribuicao da secao 3.3.
-
-### Fase PR-2 - Baseline reproduzivel
-
-- Instalar dependencias de acordo com o upstream.
-- Rodar format check, lint, typecheck/build e testes relevantes antes do patch.
-- Rodar um smoke test do caminho existente, mesmo que ele falhe por falta da integracao.
-- Limpar chaves do ambiente nos testes que validem o comportamento sem credenciais.
-- Registrar comando, codigo de saida, testes aprovados e falhas preexistentes.
-- Se o projeto nao puder ser construido, tentar o ambiente documentado e registrar o bloqueio; nao
-  declarar regressao nem compatibilidade com base apenas na leitura do README.
-
-### Fase PR-3 - Desenhar o menor patch aceitavel
-
-A ordem de preferencia e:
-
-1. Reusar a abstracao de provider ja existente.
-2. Adicionar metadados/preset antes de criar codigo especial.
-3. Reusar cliente OpenAI/Anthropic/Gemini ja presente.
-4. Adicionar capacidade generica quando ela beneficiar outros gateways e for coerente com o projeto.
-5. Criar executor/adapter dedicado somente quando o protocolo realmente divergir.
-
-O patch normalmente deve cobrir:
-
-- identificador e nome de exibicao `omniroute`, se presets nomeados forem aceitos;
-- base URL correta e sem dupla concatenacao de versao;
-- chave obtida de ambiente ou storage seguro;
-- configuracao/descoberta de modelo;
-- headers estritamente necessarios;
-- streaming e tool calling preservados;
-- mensagens de erro sem expor segredo;
-- documentacao curta e executavel;
-- testes unitarios/integracao alinhados ao padrao upstream.
-
-Nao adicionar telemetria, dependencia, fluxo de login ou codigo de rede novo quando o provider
-generico existente ja resolve o caso.
-
-### Fase PR-4 - Implementar com teste primeiro
-
-- Criar teste que demonstre a ausencia do preset, config ou comportamento requerido.
-- Confirmar a falha pelo motivo esperado.
-- Implementar o menor patch.
-- Fazer o teste passar e executar testes adjacentes.
-- Refatorar apenas o necessario para manter o padrao do upstream.
-- Formatar somente os arquivos tocados, salvo exigencia contraria do repositorio.
-
-Para PR somente de documentacao, substituir o teste vermelho por uma validacao real dos comandos e
-do arquivo de configuracao documentado. Nao sintetizar exemplos que nao foram executados.
-
-### Fase PR-5 - Validar contra OmniRoute
-
-Escolher a matriz compativel com o cliente:
-
-| Superficie | Base inicial esperada | Validacoes minimas |
-|---|---|---|
-| OpenAI Chat Completions | confirmar se o cliente espera raiz ou `/v1` | chamada simples, stream, tool call, erro de modelo |
-| OpenAI Responses | confirmar regra de concatenacao do cliente | resposta simples, stream/eventos, tool call |
-| Anthropic Messages | normalmente base antes de `/v1/messages`; confirmar no codigo | mensagem, stream, tools, headers de versao |
-| Gemini | normalmente base antes das operacoes `v1beta`; confirmar no codigo | generateContent, streamGenerateContent, tools |
-| ACP | endpoint/transport definido pelo protocolo | discovery, sessao, request e cancelamento |
-| MCP | stdio, SSE ou Streamable HTTP conforme suporte | inicializacao, listagem e invocacao de ferramenta |
-
-Registrar no resultado quais linhas da matriz foram executadas, omitidas ou bloqueadas. Um smoke
-test simples nao deve ser apresentado como prova de tool calling ou streaming.
-
-### Fase PR-6 - Revisar o diff antes de publicar
-
-O agente responsavel faz uma auto-revisao e o agente principal verifica:
-
-- aderencia a `CONTRIBUTING` e instrucoes locais;
-- escopo minimo e ausencia de refactor oportunista;
-- testes cobrindo config, URL, auth sem segredo e modelo;
-- documentacao consistente com o codigo executado;
-- ausencia de arquivos gerados, caches, logs ou credenciais;
-- licenca e atribuicao preservadas;
-- branch baseada no upstream atual;
-- commits pequenos e com mensagem no estilo do projeto;
-- ausencia de trailers ou texto de IA;
-- `git diff --check` e gates oficiais limpos, ou falhas preexistentes documentadas.
-
-Uma PR nao deve ser publicada enquanto houver alteracao sem explicacao, teste essencial faltando ou
-duvida material sobre a politica do upstream.
-
-### Fase PR-7 - Preparar a publicacao
-
-- Confirmar fork e remotes sem sobrescrever branches existentes.
-- Atualizar a branch sobre o ponto exigido pelo upstream usando operacao nao destrutiva.
-- Enviar a branch ao fork somente depois da revisao.
-- Criar PR contra a branch correta do repositorio canonico.
-- Se a contribuicao externa estiver bloqueada, abrir issue-first e anexar o commit/patch de
-  referencia somente quando isso for permitido.
-- Registrar URLs reais no tracker imediatamente apos a publicacao.
-
-Convencoes de branch sugeridas, sujeitas ao padrao de cada upstream:
-
-- `feat/omniroute-provider` para provider/preset nominal;
-- `feat/custom-base-url` para capacidade generica;
-- `docs/omniroute-setup` para documentacao validada;
-- `fix/custom-endpoint-versioning` para correcao de raiz versus `/v1`/`/v1beta`.
-
-### Fase PR-8 - Corpo da PR
-
-Usar o template oficial do repositorio quando existir. Na ausencia de template, adaptar:
-
-```md
-## Why
-
-Explain the user problem and the existing extension point. Avoid marketing claims.
-
-## What changed
-
-- Add or enable the smallest provider/configuration path required.
-- Document the verified setup.
-- Cover URL, authentication and model selection behavior with tests.
-
-## Verification
-
-- `<official upstream command>`
-- `<focused test command>`
-- `<sanitized OmniRoute smoke test and result>`
-
-## Compatibility notes
-
-- API surface: `<Chat Completions/Responses/Anthropic/Gemini/ACP/MCP>`
-- Base URL rule: `<root, /v1, /v1beta or full operation URL>`
-- Streaming: `<verified/not applicable/not verified>`
-- Tool calling: `<verified/not applicable/not verified>`
-
-## Scope
-
-No unrelated refactors or credential changes.
-```
-
-O titulo deve descrever a mudanca, nao a campanha. Exemplos de formato, sujeitos ao estilo do
-upstream: `Add OmniRoute provider preset`, `Support configurable OpenAI-compatible base URLs` ou
-`Document OmniRoute as a custom endpoint`.
-
-### Fase PR-9 - Issue-first ou fallback
-
-Quando uma PR direta nao for apropriada, a issue deve conter:
-
-- problema reproduzivel e publico afetado;
-- ponto de extensao encontrado no codigo;
-- proposta minima;
-- compatibilidade esperada e protocolo;
-- evidencia de teste ou prototipo;
-- pergunta objetiva ao mantenedor;
-- link para patch de referencia apenas se permitido.
-
-Nao abrir simultaneamente issue e PR sem necessidade. Se o template exigir issue previa, esperar a
-decisao ou seguir a politica declarada.
-
-### Fase PR-10 - Acompanhar ate a decisao
-
-Depois da publicacao:
-
-- observar CI e checks obrigatorios;
-- responder perguntas tecnicas com evidencia;
-- corrigir somente o escopo da contribuicao ou pedidos claros do mantenedor;
-- reexecutar testes depois de cada mudanca;
-- registrar novos commits, revisoes e estado no tracker;
-- marcar `accepted` somente depois de merge/aceite comprovado;
-- marcar `rejected` com o motivo fornecido pelo upstream;
-- se a PR ficar inativa, registrar `awaiting-maintainer`, sem declarar abandono prematuramente;
-- manter o guia/catalogo OmniRoute coerente com o estado real do upstream.
-
-O acompanhamento pode usar a skill `babysit` individualmente para uma PR aberta. Como essa skill
-acompanha uma unica PR, nunca agrupar tres PRs em uma mesma execucao dela.
-
-### Fase PR-11 - Fechar a task
-
-Uma task individual termina com:
-
-- pesquisa fresca e gate registrados;
-- diff, configuracao ou bloqueio documentado;
-- baseline e validacao final comparados;
-- branch/commit reais, quando criados;
-- PR/issue reais, quando publicados;
-- status no catalogo OmniRoute;
-- limitacoes e proximo passo;
-- linha correspondente no tracker atualizada.
-
-## 5. Estrategia de paralelizacao
-
-### 5.1 Papeis por lote
-
-- **Subagente A:** primeiro repositorio do lote; dono exclusivo da worktree e do diff upstream.
-- **Subagente B:** segundo repositorio do lote; dono exclusivo da worktree e do diff upstream.
-- **Subagente C:** terceiro repositorio do lote; dono exclusivo da worktree e do diff upstream.
-- **Agente principal:** coordena o tracker, revisa gates/diffs, impede duplicacao e autoriza a
-  publicacao depois das evidencias.
-
-Todos os agentes devem ser avisados de que nao estao sozinhos no workspace e nao podem reverter ou
-sobrescrever mudancas de outros agentes.
-
-### 5.2 Barreira do lote
-
-O lote seguinte pode comecar quando os tres itens atuais tiverem, no minimo:
-
-1. commit/release upstream pesquisado;
-2. gate de contribuicao definido;
-3. baseline registrado;
-4. patch validado, configuracao comprovada ou bloqueio reproduzivel;
-5. decisao de publicacao tomada;
-6. tracker atualizado.
-
-A espera por resposta de mantenedor nao bloqueia o lote seguinte. Depois de uma PR/issue publicada,
-o item passa para acompanhamento e libera o slot de implementacao.
-
-### 5.3 Limite de trabalho em progresso
-
-- No maximo tres pesquisas/implementacoes ativas.
-- Publicacoes aguardando mantenedor nao contam como slot de implementacao, mas ficam no tracker.
-- No maximo uma task ativa por repositorio, inclusive forks ou variantes do mesmo upstream.
-- Se dois itens resolverem o mesmo repositorio, consolidar a pesquisa e decidir se ha uma ou duas
-  contribuicoes antes de abrir branches.
-
-## 6. Fila de publicacao
-
-A ordem detalhada continua sendo a do `03-plano-integracao-em-lotes.md`. Esta secao define o objetivo
-de publicacao de cada onda; a pesquisa individual pode promover, rebaixar ou mudar o tipo de
-contribuicao.
-
-### Onda 0 - referencia e infraestrutura da campanha
-
-- `CLI-000` jcode: acompanhar issue upstream e PR de referencia; concluir a secao prometida no
-  README do OmniRoute.
-- Preparar o modelo de task individual e aplicar o mesmo tracker a todos os novos repositorios.
-
-### Onda 1 - P0.1 a P0.5
-
-- `CLI-001` Gemini CLI: confirmar se o endpoint Gemini customizado pede apenas docs/config ou um
-  preset nominal.
-- `CLI-002` Claw Code: confirmar provider OpenAI-compatible e propor preset/docs minimos.
-- `CLI-003` Plandex: confirmar o registro de providers customizados e propor provider/preset.
-- `CLI-004` MiMo Code: confirmar o adapter OpenAI-compatible e propor configuracao/provider.
-- `CLI-005` Trae Agent: confirmar `model_providers` e propor entrada OmniRoute/documentacao.
-- `CLI-006` Kimi CLI: escolher uma superficie suportada e evitar um patch que misture tres
-  protocolos sem testes.
-- `CLI-007` Every Code: reutilizar a arquitetura herdada do Codex quando ainda aplicavel.
-- `CLI-008` Open Codex: confirmar upstream canonico e propor provider multi-modelo.
-- `CLI-009` VT Code: validar provider customizado, modelo e failover.
-- `CLI-010` OpenHands CLI: verificar se `LLM_BASE_URL` torna o caso docs/config-only.
-- `CLI-011` gptme: verificar se `OPENAI_BASE_URL` torna o caso docs/config-only.
-- `CLI-012` Nanocoder: confirmar compatibilidade de tool calling e decidir preset versus docs.
-- `CLI-013` RA.Aid: verificar se `OPENAI_API_BASE` torna o caso docs/config-only.
-- `CLI-014` CoreCoder: verificar se `OPENAI_BASE_URL` torna o caso docs/config-only.
-- `CLI-015` Grok CLI: confirmar se o endpoint e genericamente configuravel ou preso ao protocolo
-  Grok antes de propor patch.
-
-### Onda 2 - P1.1 a P1.9
-
-- `CLI-016` Gitlawb Zero: provider custom/flag; preferir docs ou preset pequeno.
-- `CLI-017` DeepSeek Reasonix: confirmar repositorio, atividade e endpoint antes de qualquer PR.
-- `CLI-018` KlaatCode: integrar via `customModels` ou preset se o catalogo aceitar nomes.
-- `CLI-019` CodeMini CLI: validar `gateway.base_url` e sua regra de versao.
-- `CLI-020` Zot: validar `--base-url` e `models.json`; docs-first se ja suficiente.
-- `CLI-021` Octomind: confirmar variaveis de URL por provider e propor configuracao minima.
-- `CLI-022` DvalinCode: confirmar o cliente OpenAI-compatible e testes disponiveis.
-- `CLI-023` Coro Code: confirmar `OPENAI_BASE_URL`; docs-first se nao houver lacuna de codigo.
-- `CLI-024` Mini-Kode: confirmar `MINIKODE_BASE_URL`; docs-first se nao houver lacuna de codigo.
-- `CLI-025` Late CLI: testar ambiente e flag `api-url`; corrigir precedencia apenas se necessario.
-- `CLI-026` Agentty: escolher entre provider direto e ACP conforme a arquitetura atual.
-- `CLI-027` Aizen: validar `AIZEN_BASE_URL` e propor docs/preset.
-- `CLI-028` Clif-Code: selecionar um unico protocolo principal para a primeira contribuicao.
-- `CLI-029` Minacode: pesquisa confirmatoria antes de definir o tipo de PR.
-- `CLI-030` YottaCode: confirmar gateway/provider e selecao de modelo.
-- `CLI-031` aichat: integrar via configuracao de modelos ou provider nominal, conforme a politica.
-- `CLI-032` ShellGPT: validar `API_BASE_URL` e decidir docs/config-only.
-- `CLI-033` Mistral Vibe: confirmar base URL customizada e separar suporte generico de marca.
-- `CLI-034` OpenSquilla: localizar o registro de gateways e propor provider/preset.
-- `CLI-035` Kode CLI: escolher OpenAI, Anthropic ou Gemini com base na implementacao mais nativa.
-- `CLI-036` Neovate Code: preferir plugin/provider oficial ao patch no core, se existir.
-- `CLI-037` Deep Agents Code: contribuir no pacote CLI/provider correto, nao apenas no SDK generico.
-- `CLI-038` OpenHands principal: evitar duplicar `CLI-010`; consolidar se ambos apontarem para o
-  mesmo mecanismo e upstream.
-- `CLI-039` SWE-agent: confirmar backend de modelos e interface publica suportada.
-- `CLI-040` AutoCodeRover: confirmar backend e propor config/provider minimo.
-- `CLI-041` Claurst: revisar GPL e politica antes de redistribuir qualquer adaptacao.
-- `CLI-042` Codebuff: confirmar se o provider e extensivel e se contribuicoes externas sao aceitas.
-
-### Onda 3 - P2.1 a P2.11
-
-- `CLI-043` Devon, `CLI-044` Letta Code e `CLI-045` CodeMachine CLI: pesquisar backend real;
-  revisar a entrada local ja existente de Letta antes de nova PR.
-- `CLI-046` Groq Code CLI, `CLI-047` Dexto e `CLI-048` claw-code-agent: confirmar endpoints,
-  protocolos e maturidade antes do patch.
-- `CLI-049` g3, `CLI-050` San e `CLI-051` Waveloom: localizar a abstracao de provider e preferir
-  implementacao generica.
-- `CLI-052` picocode, `CLI-053` QQCode e `CLI-054` Keen Code: validar configuracao multi-modelo e
-  documentar o caminho minimo.
-- `CLI-055` Grinta, `CLI-056` Zap e `CLI-057` Binharic: escolher o provider compativel com melhor
-  cobertura de streaming/tools.
-- `CLI-058` Darce, `CLI-059` CLAII e `CLI-060` nori-cli: separar integracao de modelo de MCP e de
-  codigo herdado do Codex.
-
-Resultado P2.6:
-
-- `CLI-058` Darce: `config-only`, sem PR necessária; usar `DARCE_API_BASE` na raiz e `DARCE_MODEL`.
-- `CLI-059` CLAII: patch genérico local validado, mas publicação bloqueada pela declaração upstream
-  `All Rights Reserved`/ausência de licença OSS; só reconsiderar com autorização jurídica explícita.
-- `CLI-060` nori-cli: `config-only` via agente ACP customizado OpenCode; não alterar backend Codex;
-  MCP deve ser configurado uma vez, em Nori ou OpenCode, para evitar duplicação de tools.
-- `CLI-061` cursor-agent clone, `CLI-062` Free Code e `CLI-063` Claude Engineer: revisar origem,
-  licenca e politica do fork antes de publicar.
-
-Lote P2.7 reservado em 2026-08-02, na branch-base local `release/v3.8.50` em
-`35405be6020696a7c66158ea7a25f06d61ff88ff`. Os três upstreams foram clonados em worktrees
-separadas, indexados e delegados. Nenhuma publicação está autorizada; patches só podem surgir após
-prova RED→GREEN e permanecem sem commit até revisão central.
-
-Resultado P2.7:
-
-- `CLI-061` cursor-agent clone: `config-only`; OpenAI usa base com `/v1`, Anthropic usa raiz sem
-  `/v1`; tools/tool-result foram comprovados nos dois protocolos. O factory rejeita `auto` puro,
-  mas isso não impede uso com modelos reconhecíveis ou classes diretas. Sem PR.
-- `CLI-062` Free Code: `config-only` com `ANTHROPIC_BASE_URL` na raiz e `model=auto`; stream,
-  tools/tool-result e MCP nativo foram comprovados. O repo canônico agora é `freecodexyz/free-code`,
-  mas não há licença e o README atribui o código à Anthropic; publicação bloqueada.
-- `CLI-063` Claude Engineer: endpoint/chave funcionam como `config-only` com modelo fixo. A lacuna
-  de `ANTHROPIC_MODEL` já está coberta pela PR #250; não criar patch concorrente. Arquivo de licença
-  segue ausente apesar da issue #116, portanto publicação permanece bloqueada.
-- `CLI-064` Smol Developer, `CLI-065` Agentless e `CLI-066` Amazon Q Developer CLI: decidir entre
-  SDK/adaptador, config de modelo ou bloqueio por autenticacao.
-
-Lote P2.8 iniciado em 2026-08-02 na branch-base local `release/v3.8.50`, SHA
-`35405be6020696a7c66158ea7a25f06d61ff88ff`, com clones limpos e separados. Smol Developer será
-testado primeiro como integração do SDK OpenAI legado; Agentless será avaliado por backend
-OpenAI/Anthropic/DeepSeek; Amazon Q Developer CLI será tratado como protocolo AWS próprio, com MCP
-avaliado separadamente. Não criar adaptador grande para Amazon Q nem qualquer publicação antes de
-issue-first/coordenação exigida por `CONTRIBUTING.md`. Estado inicial: nenhum commit, fork, push,
-PR, issue ou Discussion.
-
-Resultado P2.8:
-
-- `CLI-064` Smol Developer: `config-only`; `OPENAI_API_BASE` com `/v1` e `model=auto` passaram no
-  CLI, biblioteca e Agent Protocol histórico. Não há lacuna provider-specific e a PR #134 já cobre
-  uma expansão LiteLLM. Sem publicação.
-- `CLI-065` Agentless: `config-only` pelo backend OpenAI, incluindo embeddings. Anthropic normal
-  também funciona; cache/tools exige SDK histórico e DeepSeek possui host fixo, mas essas melhorias
-  não são necessárias para integrar o projeto e propostas LiteLLM anteriores foram fechadas. Sem
-  publicação.
-- `CLI-066` Amazon Q Developer CLI: MCP stdio é a integração direta; o backend de modelo fala AWS
-  JSON/EventStream e precisa de wrapper/backend novo. O upstream está em manutenção crítica e exige
-  issue-first; não preparar PR nominal ou adaptador surpresa. Sem publicação.
-
-Estado final P2.8: commits `0`, pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`.
-Próxima fila: P2.9 (`CLI-067` nanobot, `CLI-068` ZeroClaw, `CLI-069` NanoClaw), usando no máximo
-três worktrees/agentes e repetindo a pesquisa individual antes de qualquer patch.
-
-Lote P2.9 iniciado em 2026-08-03 sobre a branch-base local `release/v3.8.50`, SHA
-`84b1e5e12f238269e698f400766230f985f4a07b`. O checkout principal já continha uma alteração do
-operador em `CLAUDE.md`, preservada fora do escopo. As worktrees foram recriadas e os upstreams
-foram clonados nos HEADs `44b7e1bf4` (nanobot), `4770420ab` (ZeroClaw) e `dfac7e0af` (NanoClaw).
-Os três índices Codebase Memory moderate estão ready, sem skipped, e a pesquisa foi delegada a um
-agente por repositório. Nenhuma publicação está autorizada; o estado inicial continua: commits `0`,
-pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`.
-
-- `CLI-067` nanobot, `CLI-068` ZeroClaw e `CLI-069` NanoClaw: validar providers OpenClaw/Anthropic
-  e evitar assumir que todos aceitam a mesma base URL.
-
-Resultado P2.9:
-
-- `CLI-067` nanobot: `config-only` pelo provider dinâmico OpenAI-compatible. A base correta inclui
-  `/api/v1`; `omniroute/auto` seleciona o provider custom e envia `auto` no wire. Chat, SSE, tools,
-  reasoning, usage, imagens, discovery e retry foram validados. Sem publicação upstream.
-- `CLI-068` ZeroClaw: `config-only` pela família `custom`, com `uri=/v1`, modelo `auto`, wire Chat e
-  `native_tools=true`. Responses é opt-in. Suite de provider, config, fmt e smoke HTTP passaram.
-  Sem provider nominal ou publicação upstream.
-- `CLI-069` NanoClaw: `config-only` pelo provider Claude existente, apontando a raiz Anthropic do
-  OmniRoute sem `/v1/messages` e usando OneCLI para a credencial. Codex e OpenCode têm bloqueios
-  upstream reproduzidos (#3155/#1984/#2985) e ficam fora do caminho de produção atual.
-
-Estado final P2.9: commits `0`, pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`.
-Progresso da pesquisa: `70/104` (`67,3%`); pendentes: `34/104` (`32,7%`). Próxima fila: P2.10
-(`CLI-070` PicoClaw, `CLI-071` IronClaw, `CLI-072` NullClaw).
-- `CLI-070` PicoClaw, `CLI-071` IronClaw e `CLI-072` NullClaw: localizar traits/registries e propor
-  um provider pequeno com testes.
-- `CLI-073` Moltis, `CLI-074` GitClaw e `CLI-075` LionClaw: confirmar atividade, provider e comandos
-  de validacao antes da publicacao.
-
-### Onda 4 - P3, integracoes indiretas
-
-- `CLI-076`, `CLI-077`, `CLI-078`, `CLI-079`, `CLI-080` e `CLI-081`: pesquisar forwarding de
-  ambiente/configuracao para os agentes filhos;
-  publicar wrapper ou docs somente quando houver um ponto de extensao real.
-- `CLI-082`, `CLI-083`, `CLI-084`, `CLI-085`, `CLI-086`, `CLI-087`, `CLI-088`, `CLI-089` e
-  `CLI-090`: escolher ACP, MCP, launcher ou integracao do agente filho; nao apresentar uma
-  integracao de orquestrador como provider de modelo.
-- `CLI-091` e `CLI-092`: tratar como interoperabilidade entre proxies; documentar loops, headers,
-  auth e riscos antes de propor codigo.
-- `CLI-093` e `CLI-094`: integrar como broker/ferramenta MCP somente se isso estiver no escopo dos
-  projetos.
-- `CLI-095` e `CLI-096`: configurar o agente filho e revisar a entrada existente de Agent Deck.
-
-### Onda 5 - P4, fechados, EULA e MITM
-
-- `CLI-097` Pool: confirmar o que a EULA permite; priorizar configuracao local e nao presumir PR.
-- `CLI-098` Junie CLI: pesquisar canal oficial de feedback; sem repositorio publico confirmado, nao
-  existe fila de PR.
-- `CLI-099` Cursor desktop, `CLI-100` Windsurf, `CLI-101` Amp, `CLI-102` Amazon Q/Kiro CLI e
-  `CLI-103` Cowork: tratar como MITM, configuracao de produto ou pedido oficial de feature. So mover
-  para PR se um repositorio publico e uma politica de contribuicao forem comprovados.
-
-## 7. Prompt operacional para cada subagente
-
-O agente principal deve adaptar e enviar este prompt para cada item:
-
-```text
-Voce e responsavel exclusivamente por CLI-NNN - <projeto> no repositorio <URL>.
-Voce nao esta sozinho no workspace: nao reverta, sobrescreva ou reorganize mudancas de outros
-agentes. Trabalhe somente na worktree isolada atribuida dentro de .claude/worktrees/ e nunca use
-git stash/pop.
-
-Primeiro pesquise o upstream atual. Leia README, CONTRIBUTING, licenca, templates e instrucoes locais.
-Registre commit/release, arquitetura de providers, config/base URL, protocolo, auth, modelos,
-streaming, tool calling, issues/PRs existentes e comandos oficiais de build/test. A evidencia inicial
-do relatorio e uma hipotese, nao uma conclusao.
-
-Antes de editar, classifique o caso como pr-provider, pr-generic, pr-docs, issue-first, config-only,
-adapter-acp, adapter-mcp, wrapper, needs-mitm ou blocked, com justificativa. Execute o baseline e
-registre falhas preexistentes. Se houver patch, trabalhe com teste primeiro e implemente somente a
-menor integracao coerente com o upstream. Confirme raiz versus /v1 versus /v1beta, autenticacao,
-modelo, streaming e tool calling conforme aplicavel.
-
-Nao publique nada antes da revisao do agente principal. Entregue: pesquisa com links/caminhos,
-gate, baseline, diff, testes, smoke test sanitizado, riscos, branch/commit local se criados e a
-atualizacao proposta para 04-tracker-integracoes-clis.md. Nao invente dados e nao exponha chaves.
-```
-
-## 8. Checklist de autorizacao para enviar uma PR
-
-O agente principal somente autoriza a publicacao quando todas as respostas forem `sim` ou houver
-uma excecao registrada:
-
-- [ ] O repositorio canonico e a branch-alvo foram confirmados.
-- [ ] A politica aceita o tipo de contribuicao planejado.
-- [ ] Issues/PRs duplicadas foram pesquisadas.
-- [ ] O commit/release de base esta registrado.
-- [ ] O gate de contribuicao esta justificado.
-- [ ] O baseline foi executado e falhas preexistentes estao separadas.
-- [ ] O patch e o menor necessario e segue a arquitetura upstream.
-- [ ] A base URL e sua regra de versao foram verificadas no codigo e em runtime.
-- [ ] Auth/modelos foram testados sem vazar segredo.
-- [ ] Streaming/tool calling foram testados ou marcados explicitamente como nao aplicaveis.
-- [ ] Testes, lint, format, typecheck/build relevantes foram executados.
-- [ ] A documentacao foi executada e corresponde ao codigo.
-- [ ] O diff nao contem caches, builds, logs, credenciais ou refactors sem relacao.
-- [ ] O titulo e o corpo seguem o template upstream e nao contêm marketing ou texto de IA.
-- [ ] O tracker esta pronto para receber branch, commit e URL reais.
-
-## 9. Campos adicionais recomendados no tracker
-
-O tracker atual deve continuar como fonte principal. Durante a execucao, registrar nas observacoes ou
-em uma nota individual:
-
-- commit/release pesquisado;
-- decisao `pr-provider`, `pr-generic`, `pr-docs`, `issue-first`, `config-only`, adapter, wrapper,
-  MITM ou bloqueio;
-- protocolo e regra da base URL;
-- comandos de baseline e resultado;
-- comandos finais e resultado;
-- smoke tests realizados;
-- arquivos modificados;
-- fork, branch e commit;
-- PR/issue e estado de CI/review;
-- limitacoes e proximo passo.
-
-Campos ainda nao comprovados permanecem `—`.
-
-## 10. Inicio recomendado
-
-O primeiro ciclo de publicacao deve usar o lote P0.1:
-
-1. `CLI-001` - Gemini CLI (`google-gemini/gemini-cli`)
-2. `CLI-002` - Claw Code (`ultraworkers/claw-code`)
-3. `CLI-003` - Plandex (`plandex-ai/plandex`)
-
-Os tres subagentes fazem pesquisa fresca e implementacao em paralelo, mas nenhuma PR e enviada antes
-da revisao individual do agente principal. Ao publicar ou concluir config-only/bloqueio, atualizar o
-tracker e liberar os mesmos tres slots para o lote P0.2.
-
-## Lote P2.10 iniciado em 2026-08-03
-
-Base local: `release/v3.8.50` em `84b1e5e12f238269e698f400766230f985f4a07b`. Worktrees isoladas e um agente por upstream foram criadas para `CLI-070` PicoClaw, `CLI-071` IronClaw e `CLI-072` NullClaw. Nenhuma publicação está autorizada; os agentes devem pesquisar o HEAD atual, provar `config-only` ou RED→GREEN e registrar governança, gates, smoke e estado limpo.
-
-Resultado P2.10:
-
-- `CLI-070` PicoClaw: `config-only`, `openai/auto` com base `/api/v1`; Chat/SSE/tools/usage/images/discovery. Go ausente impediu execução local; monitorar #3298, sem PR.
-- `CLI-071` IronClaw: `config-only`, `openai_compatible` com `/api/v1` e `auto`; 889 testes do crate LLM, 5 de resolução e fmt passaram. Sem PR; reasoning proprietário segue limitado por #3673.
-- `CLI-072` NullClaw: `config-only`, provider custom com Chat Completions recomendado e Responses/Anthropic como alternativas. Zig ausente; CI do mesmo HEAD verde. Sem PR.
-
-Estado final P2.10: commits `0`, pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`.
-Pesquisa acumulada: `73/104` (`70,2%`); pendentes: `31/104` (`29,8%`). Próxima fila: P2.11 (`CLI-073` Moltis, `CLI-074` GitClaw, `CLI-075` LionClaw).
-
-Resultado P3.1:
-
-- `CLI-076` VibePod: `config-only` pelo agente Claude Code com raiz Anthropic `/api`; wrapper injeta env no container. Codex sem chave automática permanece não comprovado.
-- `CLI-077` zeroshot: `config-only` pelo gateway OpenAI `/api/v1`; 22 testes focados verdes; limitações de streaming JSON, reasoning e MCP registradas.
-- `CLI-078` Fractal: `config-only` por Codex Responses em `CODEX_HOME` por node; servidores tmux quentes podem perder `OMNIROUTE_API_KEY`, recomendando fix genérico upstream.
-
-Estado final P3.1: commits `0`, pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`. Pesquisa acumulada: `79/104` (`76,0%`); pendentes: `25/104` (`24,0%`).
-
-Resultado P3.2: Bernstein `config-only` por openai_agents; Traycer `config-only` indireto pelo harness OpenCode; h5i `patch-required` porque auth proxy/egress são fixados em OpenAI. Nenhuma publicação externa. Pesquisa acumulada `82/104` (`78,8%`), pendentes `22/104` (`21,2%`).
-
-Resultado P2.11:
-
-- `CLI-073` Moltis: `config-only`, provider `custom-omniroute`, `/api/v1`, `auto`, Chat/SSE/tools e capacidades multimodais. 401 testes e fmt passaram. Sem publicação.
-- `CLI-074` GitClaw/GitAgent: `config-only`, loader OpenAI-compatible com `GITAGENT_MODEL_BASE_URL`, `OPENAI_API_KEY` e `omniroute:auto`. Build, 65 testes e smoke passaram. Sem publicação.
-- `CLI-075` LionClaw: `patch-required`/`issue-first`. O runtime Codex confinado não recebe `config.toml`/provider secret; preparar proposta genérica alinhada à [#157](https://github.com/moshthepitt/lionclaw/issues/157), sem PR até revisão do mantenedor.
-
-Estado final P2.11: commits `0`, pushes `0`, forks `0`, PRs `0`, issues `0`, Discussions `0`. Pesquisa acumulada: `76/104` (`73,1%`); pendentes: `28/104` (`26,9%`).
-Resultado P3.3: OMK `viable-mcp`; kodo `config-only` indireto; ORCH `needs-wrapper`. Pesquisa acumulada `85/104` (`81,7%`), pendentes `19/104` (`18,3%`). Nenhuma publicação externa.
-
-Resultado P3.4: LoopTroop `config-only` indireto via provider OpenCode; Galley `patch-required` por não possuir transport OpenAI-compatible configurável; Relay `config-only` via provider profile/Codex, condicionado a smoke da Responses API e controles sobre ferramentas nativas. Nenhuma publicação externa. Pesquisa acumulada `88/104` (`84,6%`), pendentes `16/104` (`15,4%`).
-
-Resultado P3.5: SageCLI `config-only` indireto via Codex, com caveat de env plaintext; 5dive `patch-required` por mapas fechados de provider/base; agx `config-only` indireto via Codex e com gates de Responses/sandbox. Pesquisa acumulada `91/104` (`87,5%`), pendentes `13/104` (`12,5%`). Nenhuma publicação externa.
-
-Resultado P3.6: claude-code-router, cc-router e OneCLI são config-only; os dois primeiros oferecem endpoints custom OpenAI-compatible e OneCLI injeta credenciais por proxy MITM. Pesquisa acumulada `94/104` (`90,4%`), pendentes `10/104` (`9,6%`). Nenhuma publicação externa.
-
-Resultado P3.7: agent-browser `config-only` direto por Chat Completions; OpenWork `config-only` via OpenCode custom; Agent Deck `config-only` via CLIs filhos. Pesquisa acumulada `97/104` (`93,3%`), pendentes `7/104` (`6,7%`). Nenhuma publicação externa.
-
-Resultado P4.1: Pool e Junie são `config-only` OpenAI-compatible; Cursor é `config-only` limitado ao BYO chat panel, sem MITM/protocolo privado. Pesquisa acumulada `100/104` (`96,2%`), pendentes `4/104` (`3,8%`). Nenhuma publicação externa.
-
-Resultado P4.2: Windsurf está bloqueado para inferência e permite apenas MCP; Amp depende de confirmação Enterprise; Amazon Q legado requer patch substancial e Kiro atual é MCP-only seguro. Pesquisa acumulada `103/104` (`99,0%`), pendente `1/104` (`1,0%`). Nenhuma publicação externa.
-
-Resultado P4.3: Cowork não permite substituir oficialmente a inferência; Custom Connector MCP remoto é o único caminho suportado e permanece separado do modelo. Pesquisa concluída `104/104` (`100%`), pendentes `0/104` (`0%`). Nenhuma publicação externa nesta fase de pesquisa.

_references/_sistemas_cli/06-relatorio-final-104-clis-e-estrategia-prs.md

@@ -1,131 +0,0 @@
-# Relatório final — campanha de 104 integrações CLI OmniRoute
-
-**Data de fechamento:** 2026-08-03  
-**Escopo:** `CLI-000` a `CLI-103`  
-**Resultado:** `104/104` pesquisados (`100%`), `0` pendentes de pesquisa.
-
-## Como consultar o resultado individual
-
-O documento autoritativo, com uma linha para cada caso, é o [tracker completo](./04-tracker-integracoes-clis.md). Ele contém para cada ID:
-
-- prioridade;
-- projeto e repositório;
-- classificação de integração;
-- estado de contribuição upstream;
-- branch e commit quando existentes;
-- URL de PR e/ou issue quando publicados;
-- estado no catálogo OmniRoute;
-- observações, limitações, testes e próximo passo.
-
-Além do tracker, existem fichas técnicas individuais em `_tasks/cli-integrations/`. A cobertura foi auditada e agora há uma ficha para cada ID `CLI-000`–`CLI-103`; o caso `CLI-000` jcode foi adicionado como ficha de referência nesta revisão.
-
-## Resumo quantitativo
-
-| Grupo operacional | Quantidade | Tratamento |
-|---|---:|---|
-| Configuração direta ou indireta | 76 | Documentar receita, validar smoke e só abrir PR se houver melhoria upstream real |
-| Contribuição upstream (PR/issue/docs/patch) | 17 | Preparar diff mínimo, validar, revisar e publicar conforme política do repositório |
-| Patch obrigatório | 4 | Implementar genericamente, com RED→GREEN/TDD e revisão do mantenedor |
-| Bloqueados/fechados | 4 | Registrar bloqueio; usar apenas MCP ou canal oficial, sem MITM |
-| MCP/wrapper/ACP como caminho principal | 2 | Integrar a camada de ferramentas/orquestração, sem falsificar provider de inferência |
-| Outros casos híbridos | 1 | Seguir a combinação específica descrita no tracker |
-
-Os números são derivados do campo `Tipo` do tracker; categorias podem se sobrepor em casos híbridos. Atualmente há **7 PRs reais** e **9 issues reais** registrados no tracker, além de cinco entradas locais marcadas como integradas ao catálogo OmniRoute. Nenhum link foi inventado para os 97 casos sem publicação externa.
-
-## O que foi feito na campanha
-
-1. Inventário inicial e busca extensa de CLIs, runtimes, harnesses e control-planes.
-2. Priorização P0–P4 considerando compatibilidade de protocolo, adoção, licença, maturidade e risco.
-3. Pesquisa fresca, uma a uma, em worktrees isoladas, em lotes de no máximo três agentes.
-4. Uso de Codebase Memory para índices upstream e verificação de cobertura; faixas parciais foram lidas diretamente quando aplicável.
-5. Classificação por configuração, patch, PR documental, issue-first, MCP, wrapper ou bloqueio.
-6. Registro de comandos, base URL, autenticação, modelos, streaming, tools, reasoning, imagens, MCP/ACP/A2A, testes e limitações.
-7. Consolidação de cada lote com commit separado no OmniRoute e no repositório `_tasks`.
-8. Atualização final do tracker, plano de integração, plano de publicação e handoff.
-9. Nenhuma credencial real, publicação externa ou técnica de interceptação não autorizada foi utilizada.
-
-## Estratégia para abrir PRs em 100% dos casos
-
-“Abrir PR para 100%” deve ser interpretado como **dar um destino upstream apropriado a 100% dos casos**, e não criar 104 PRs artificiais. Há quatro trilhas:
-
-### Trilha A — PR de código ou documentação
-
-Aplicar aos casos `viable-upstream`, `pr-generic`, `pr-docs`, `patch-required` e híbridos que tenham superfície pública e política de contribuição compatível.
-
-Processo por caso:
-
-1. Reconfirmar HEAD, licença, branch default, política de contribuição e duplicatas.
-2. Criar worktree/branch baseada na versão local vigente.
-3. Executar baseline upstream e registrar falhas preexistentes.
-4. Escrever teste RED que demonstre a lacuna.
-5. Implementar o menor patch genérico possível — preferir `openai-compatible`, `base_url` ou provider abstrato a um provider nominal OmniRoute.
-6. Executar GREEN: testes focados, suite upstream, lint, format, typecheck/build e smoke com fake server ou OmniRoute local usando placeholder.
-7. Revisar segurança: nenhuma chave em argv, logs, fixtures, URL ou artefato; erros sanitizados; streaming/tools/cancelamento cobertos.
-8. Abrir PR somente se contribuições externas forem aceitas. O corpo deve explicar problema, solução genérica, compatibilidade, testes, limitações e não conter marketing/texto de IA.
-9. Se o repositório bloquear fork/PR ou pedir discussão prévia, abrir issue de proposta com o mesmo patch/reprodução, sem enviar PR prematuramente.
-10. Atualizar tracker com branch, commit, URL, CI, revisão e resposta do mantenedor; acompanhar até `accepted`, `merged`, `rejected` ou `awaiting-maintainer`.
-
-### Trilha B — Issue-first, discussão ou suporte ao mantenedor
-
-Aplicar quando a arquitetura é adequada, mas há bloqueio de governança, firewall, CLA, fork fechado, dúvida de protocolo ou necessidade de decisão do autor. A issue deve conter:
-
-- caso de uso OmniRoute;
-- configuração atualmente possível;
-- lacuna reproduzível;
-- proposta genérica;
-- impacto de segurança;
-- testes/fake server;
-- disposição para enviar PR após aprovação.
-
-Não abrir uma PR paralela enquanto a política exigir issue-first.
-
-### Trilha C — Config-only documentado
-
-Aplicar aos casos em que o upstream já suporta a integração e uma mudança de código seria redundante. O entregável é:
-
-- ficha individual;
-- receita validada;
-- smoke test e limitações;
-- eventual documentação externa/local do OmniRoute;
-- issue somente se houver pedido de documentação ou descoberta de bug real.
-
-Não criar provider nominal ou PR apenas para adicionar a palavra “OmniRoute”.
-
-### Trilha D — MCP, wrapper ou bloqueio seguro
-
-Aplicar a control-planes, produtos fechados e CLIs sem rota de inferência substituível. O resultado pode ser:
-
-- MCP remoto/stdio do OmniRoute;
-- wrapper local claramente identificado como wrapper;
-- solicitação oficial de custom provider;
-- registro de bloqueio e gate legal/ToS.
-
-Nunca mascarar OmniRoute como Claude/Codex, falsificar executável, interceptar TLS ou reutilizar tokens privados para fabricar uma PR upstream.
-
-## Ordem recomendada de execução
-
-1. **Primeiro:** PRs e issues já preparadas ou com alto retorno e baixo risco — jcode, Gemini CLI, Claw Code, Plandex, Trae Agent, Every Code, VT Code e CoreCoder.
-2. **Segundo:** patches genéricos com boa superfície OSS — AutoCodeRover, Galley, 5dive e demais casos `pr-generic`/`patch-required`.
-3. **Terceiro:** issues aguardando decisão — Open Codex, Kimi CLI, Devon, g3, Free Code, Claude Engineer e casos com `awaiting-maintainer`.
-4. **Quarto:** documentação e receitas config-only agrupadas por ecossistema — OpenCode, Codex, LiteLLM, AI SDK, OpenAI-compatible e Anthropic-compatible.
-5. **Quinto:** MCP/plugins para produtos fechados — Windsurf, Amp, Kiro, Cowork e Cursor, sempre pela superfície oficial.
-
-Cada rodada deve manter no máximo três agentes ativos. O agente principal revisa o resultado do trio antes de liberar o próximo.
-
-## Critério de encerramento por caso
-
-Um caso só pode ser marcado como finalizado quando possui: pesquisa, classificação, evidência de protocolo, baseline ou limitação reproduzível, receita/patch/bloqueio, validação proporcional, estado de publicação e próximo passo. Para produtos fechados, `blocked-closed` ou `MCP-only` é um resultado válido e preferível a uma PR não autorizada.
-
-## Estado de publicação atual
-
-Os únicos links de publicação comprovados devem continuar sendo os registrados no tracker. O fato de existir uma branch local de pesquisa não significa que exista PR upstream. A matriz de verdade é:
-
-- PR/issue preenchida: publicação real;
-- campo `—`: nenhuma publicação externa comprovada;
-- `not-applicable`: configuração ou bloqueio sem contribuição upstream;
-- `awaiting-maintainer`: contato feito, aguardando decisão;
-- `published-pr`/`published-issue`: URL real presente no tracker.
-
-## Próxima fase
-
-A pesquisa está encerrada. A próxima fase é execução controlada da Trilha A/B/C/D, começando pelos casos com maior retorno e menor risco, com revisão central antes de qualquer push, PR, issue ou contato externo.

docs/DEVIN_CLAUDE_BRIDGE_PROGRESS.md

@@ -1,115 +0,0 @@
-# Devin Claude Bridge Progress
-
-Updated: 2026-07-28
-
-## Baseline
-
-- Fork version: `3.8.49`.
-- Starting branch: `release/v3.8.49`.
-- Starting commit: `ed7db3ee5f89a144b2d931d8605534522f83de30`.
-- Fixed runtime artifacts: Node `26.0.0`, Claude Code `2.1.220`, Devin CLI `3000.2.17`.
-- Existing `devin-cli` remains unchanged; the new path is the separate
-  `devin-cli-agentic` provider.
-
-## Implemented architecture
-
-- Claude Code runs only inside the non-root bridge container with its own empty config
-  volume and local OmniRoute base URL.
-- `devin-cli-agentic` preserves Anthropic messages, tool schemas, `tool_use`, and
-  `tool_result`, then calls the official Devin CLI over ACP stdio.
-- The executor starts `devin acp --agent-type summarizer`. This is the only fixed official
-  ACP role in the pinned CLI that has no Devin-owned tools.
-- The request is framed as an execution trace. Devin can return one strict client tool
-  envelope; Claude Code executes that tool locally.
-- Internal ACP `tool_call` events, unsupported blocks, invalid schemas, narrative actions,
-  timeouts, cancellation, and process failure all fail closed.
-- Provider and network policy prevent combo/auto/Anthropic fallback.
-
-## Offline proof
-
-- Focused serializer, parser, executor, ACP lifecycle, wire-format, environment, and audit
-  tests pass (39/39).
-- The contract suite covers Anthropic JSON/SSE, `tool_use`, `tool_result` continuation,
-  fragmented ACP frames, stderr, early exit, timeout, cancellation, and fail-closed provider
-  loss.
-- The production bridge image builds with the pinned CLIs.
-- Real Claude Code offline E2E loads `CLAUDE.md`, the project skill and slash command, fires
-  hooks, executes local tools over multiple turns, observes a failed test, repairs the file,
-  reruns the test, and completes.
-- The isolation verifier proves non-root/read-only execution, isolated mounts and config,
-  blocked Anthropic/Claude access, no host credential mounts, local-only inference, and no
-  fallback.
-
-Evidence is generated under `.sandbox/evidence` and ignored by Git.
-
-## Regression status
-
-- `typecheck:core`, focused ESLint, Prettier, shell/Node syntax, and the complete documentation
-  accuracy suite pass.
-- The broad `npm run check` is not reported as passed: after its lint phase, the repository
-  test runner remained alive while an existing `ioredis` client repeatedly retried an
-  unavailable local Redis endpoint after `quota-redis-store.test.ts`. The bridge-focused
-  suites, production image build, offline E2E, isolation proof, and live gate do not use that
-  Redis service and all pass.
-
-## Live Devin proof
-
-Passed with the official in-container login and discovered model
-`swe-1-7-lightning`. The terminal live run completed all three scenarios:
-
-1. Claude Code loaded the fixture instructions, issued client-owned `Read` calls, and
-   returned a correct defect analysis.
-2. Claude Code issued a real `Edit` changing subtraction to addition, then a client-owned
-   `Bash` call running `npm test`; the test reported one pass and zero failures.
-3. Claude Code initialization listed `bridge-check` and `bridge-proof`, read the corrected
-   source and test, executed another client-owned `npm test`, and completed successfully.
-
-The live evidence validator parses stream JSON and requires successful tool results. It does
-not accept a textual claim that a tool ran. It also rejects terminal summaries that report a
-blocker, incomplete work, or required next steps.
-
-The final live gate reported:
-
-```text
-PASS: validated Claude evidence for LIVE_ANALYSIS_COMPLETE
-PASS: validated Claude evidence for LIVE_FIX_COMPLETE
-PASS: validated Claude evidence for BRIDGE_E2E_COMPLETE
-PASS: three live Devin-backed Claude Code scenarios completed
-PASS: live model swe-1-7-lightning was discovered and validated by three scenarios
-```
-
-The same gate validated the network audit: only the Devin guard path was used, no internal
-Devin tool event was accepted, and the Claude egress audit remained empty.
-
-## Investigation conclusion
-
-The initial default-agent hypothesis failed because ACP permission modes do not turn the
-default Devin agent into a raw inference backend. Even `ask` mode can emit Devin-owned
-`tool_call` events. A discovered `allowed-tools: []` agent configuration was not consumed by
-`devin acp` in CLI `3000.2.17`.
-
-The working adaptation uses the official `summarizer` agent because it is structurally
-no-tools. Its fixed summarization behavior can produce intermediate prose, so the bridge
-frames requests as execution traces, detects future-action narration, performs at most one
-strict repair, and otherwise fails. Live validation also exposed transient ACP timeouts;
-the harness now spaces independent scenarios rather than weakening routing or retrying into
-another provider.
-
-## Safety record
-
-No host Claude executable, configuration, login, OAuth token, Keychain, or Anthropic API was
-used. The dedicated Docker volumes remain role-separated. No credential value is written to
-the repository or evidence output.
-
-During the early baseline, a focused test without isolated `DATA_DIR` initialized the
-repository's normal OmniRoute database at `/Users/lucasisrael/.omniroute/storage.sqlite`.
-It was not rolled back or touched again. Every bridge command now pins database and temporary
-paths under the worktree's `.sandbox` directory.
-
-## Remaining limits
-
-- The no-tools backend has a summarizer system role rather than a neutral generation role.
-- One client tool call per response is supported; parallel tool calls are rejected.
-- ACP processes are per-turn and stateless.
-- Live Devin availability can still produce explicit `502`/`504` failures.
-- Images and unadvertised vision/effort/large-context capabilities remain unsupported.

docs/INCIDENT_RESPONSE.md

@@ -1,200 +0,0 @@
----
-title: "Incident Response Runbook — OmniRoute (2026-06-18)"
-version: 3.8.50
-lastUpdated: 2026-08-06
----
-
-# Incident Response Runbook — OmniRoute (2026-06-18)
-
-**Status**: Authoritative. The 71-pillar audit (L61) references this doc
-for the `Obs > 2.00` gate.
-**Owner**: observability-circle (lead: security-circle lead).
-**SLOs**: see `docs/PERF_BUDGETS.md` § 1 (top-level SLOs) and
-`ops/slos.yaml` (machine-readable form, generated by the Bifrost team).
-**Disclosure policy**: see `SECURITY.md` (vulnerability disclosure only,
-separate flow).
-
-This runbook is the operational playbook for **non-security** incidents:
-outages, latency regressions, error-budget burn, and provider-side
-failures. Vulnerability disclosure stays on `SECURITY.md`; do not route
-those through this runbook.
-
----
-
-## 1. Severity ladder
-
-| Sev | Definition | Examples | Page on | Resolve by |
-|---|---|---|---|---|
-| **SEV-1** | User-visible outage; > 50 % of requests failing or > 2x SLO breach for 5 min. | Cluster down; auth layer broken; 5xx flood. | On-call P0 (immediate) | 4 h |
-| **SEV-2** | Significant degradation; 1.5–2x SLO breach for 15 min, or single-tenant impact. | Single provider down; p95 > 1.5x budget; rate-limit runaway. | On-call P1 (15 min) | 24 h |
-| **SEV-3** | Latent bug or near-miss; no current user impact but error budget at risk. | Memory leak trending up; circuit breaker tripping on one provider. | Slack `#omniroute-ops` (next standup) | 7 d |
-| **SEV-4** | Cosmetic / informational. | Log line noise; non-binding UI glitch. | Next weekly review | Next refactor cycle |
-
-**Burn-rate escalation** (per `docs/PERF_BUDGETS.md` § 1): 6x for 5 min
-is SEV-1; 2x for 1 h is SEV-2; sustained < 1x for 7 d demotes to SEV-3.
-
----
-
-## 2. Detection sources
-
-| Source | Signal | Routing |
-|---|---|---|
-| Prometheus (`/metrics`) | Counter deltas (5xx, latency) | Alertmanager → PagerDuty |
-| Grafana SLO dashboards | SLO burn-rate panels | Slack `#omniroute-ops` |
-| Uptime probe (`/api/health/ping`) | 3 consecutive failures from 3 regions | Alertmanager → PagerDuty |
-| Dependabot | New CVE in dependency | GitHub issue + Slack `#security` |
-| User report (support@) | Manual triage | Slack `#omniroute-triage` |
-| Error budget burn alert | `slo_burn_rate > threshold` | Alertmanager |
-
-Prometheus and Alertmanager are configured in the deploy repo (see
-`docs/operations/DEPLOY.md` once published; currently inline in
-`docker-compose.prod.yml`).
-
----
-
-## 3. First-15-minutes checklist
-
-When paged, the on-call engineer runs this checklist verbatim. **Do
-not** skip steps; each is timed.
-
-1. **0:00** — Acknowledge the page in PagerDuty. Stops the escalation
-   timer and notifies the secondary.
-2. **0:02** — Open the [SLO dashboard][dash] and the [incident
-   channel][chan] (`#inc-YYYY-MM-DD-slug`). Post a single-line ack
-   with the alert name and the time.
-3. **0:05** — Classify severity per § 1. If SEV-1 or SEV-2, declare
-   the incident in the channel and tag `@incident-commander`.
-4. **0:08** — Capture the alert payload, the most recent deploy SHA,
-   and the top 5 slow / erroring endpoints. Post to the channel.
-5. **0:12** — Decide: **mitigate first, root-cause later**. Choose
-   one of:
-   - **Roll back** to the last green deploy (`bin/rollback.sh vX.Y.Z`).
-   - **Failover** to the healthy replicas (Caddy LB removes the bad
-     replica automatically; verify with `curl /api/health/ping`).
-   - **Disable** the broken connection(s) via `PUT /api/providers/{connectionId}`
-     with body `{ "isActive": false }` (per-connection toggle, safe by
-     default; repeat per key/account — see § 4.1).
-6. **0:15** — Post the chosen mitigation in the channel. If the page
-   is still firing after 5 more minutes, escalate to the secondary.
-
-[chan]: TBD — set to your team's incident-chat channel (e.g. a Discord/Slack `#inc-*` channel); not provisioned by this repo.
-[dash]: TBD — set to your Grafana/observability dashboard URL; not provisioned by this repo.
-
----
-
-## 4. Mitigation runbooks (per failure mode)
-
-### 4.1 Provider outage (single provider down)
-
-1. `PUT /api/providers/{connectionId}` with body `{ "isActive": false }` —
-   deactivates that connection; combo routing and account selection skip it
-   on the next request (`src/app/api/providers/[id]/route.ts`). There is no
-   single whole-provider kill switch — if the provider has more than one
-   key/account, repeat per connection, or let the automatic provider circuit
-   breaker trip on its own (`src/shared/utils/circuitBreaker.ts`,
-   `domain_circuit_breakers` table; see `docs/architecture/RESILIENCE_GUIDE.md`).
-2. Verify p95 returns to budget within 5 min.
-3. If all connections for a model are down, apply the same `isActive: false`
-   toggle to every connection offering that model — there is no separate
-   per-model disable endpoint. Combo routing's automatic Model Lockout
-   (`open-sse/services/accountFallback.ts`; see
-   `docs/architecture/RESILIENCE_GUIDE.md`) also skips a model that keeps
-   erroring, without manual action.
-4. Update the status page (if one is configured — see § 5) with a banner if
-   the outage exceeds 15 min.
-
-### 4.2 Cluster-wide latency regression
-
-1. Check the most recent deploy (`/api/monitoring/health` returns `appVersion`).
-2. If p95 doubled vs the 7-day baseline, **roll back** to the prior
-   SHA via `bin/rollback.sh`.
-3. If the regression is provider-side, see § 4.1.
-
-### 4.3 Auth layer broken (5xx on /v1/responses for all keys)
-
-1. Check the authz-inventory endpoint:
-   `curl https://api.omniroute.dev/api/settings/authz-inventory | jq`.
-   It returns a route-tier inventory (`tiers`, `bypassEnabled`,
-   `bypassPrefixes`, `spawnCapablePrefixes`, `cors` — see
-   `src/app/api/settings/authz-inventory/route.ts`); there is no
-   `policies_active` field. A non-200 response, or a `tiers` array that
-   fails to populate, means the settings/DB layer the auth pipeline reads
-   from is down — not just a single bad key.
-2. If the endpoint itself errors or returns malformed data, restore the
-   settings store from the last good backup (`bin/restore-policies.sh <sha>`).
-3. If the endpoint is healthy but requests still 5xx for every key, verify
-   `JWT_SECRET` / `API_KEY_SECRET` are set and unchanged for this deploy,
-   and that `isValidApiKey` (`src/sse/services/auth.ts`) can reach the DB.
-4. Roll back if the cause is unclear.
-
-### 4.4 Data-layer incident (sqlite corruption, audit log gap)
-
-1. **Stop the cluster** (`docker compose -f docker-compose.prod.yml
-   stop`) — preventing further writes is more important than uptime.
-2. Snapshot the data volume (`bin/snapshot-data.sh`).
-3. Open a SEV-1; this is data-loss territory. Page the data-team.
-4. Restore from the last verified backup (see `docs/BACKUP.md` once
-   published; currently the runbook is `bin/restore-data.sh <sha>`).
-
-### 4.5 Security incident (vulnerability disclosure)
-
-**Stop.** This is the `SECURITY.md` path, not this runbook. Page the
-security on-call (`@security-team`); do not post details to
-`#omniroute-ops`.
-
----
-
-## 5. Communication
-
-| Audience | Channel | Cadence | Owner |
-|---|---|---|---|
-| Engineering | `#inc-YYYY-MM-DD-slug` | Real-time | Incident commander |
-| Status page | TBD — not provisioned by this repo | Every 30 min during SEV-1/2 | On-call |
-| Customers (email) | TBD — set your announcement list/address | At SEV-1 start + resolution | Comms lead |
-| Upstream providers | Direct contact | At SEV-1 start | Vendor mgmt |
-| Postmortem | `docs/postmortem/YYYY-MM-DD-slug.md` | Within 5 business days | Incident commander |
-
-Postmortem template is at `docs/postmortem/TEMPLATE.md` (forthcoming; no
-dedicated ADR covers it yet — once written, register it in
-`docs/architecture/cluster-decisions.md` following this repo's 71-pillar/ADR
-numbering convention, e.g. ADR-041 there).
-
----
-
-## 6. On-call rotation
-
-| Role | Primary | Secondary | Rotation |
-|---|---|---|---|
-| Engineering on-call | security-circle lead | @open-sse | Weekly, Mon 09:00 PDT |
-| Security on-call | @security-team | — | Weekly |
-| Data on-call | @db-team | — | Weekly |
-| Comms lead | @comms | — | As needed |
-
-**Handoff**: every Monday 09:00 PDT, the outgoing on-call posts a
-written handoff to the incoming in `#omniroute-ops-handoff` covering:
-open SEV-3/4 items, scheduled maintenance windows, and any
-in-flight mitigations.
-
----
-
-## 7. Postmortem expectations
-
-- **Blameless**. People did the best they could with the information
-  they had. Focus on systems, signals, and decision points.
-- **Within 5 business days** of resolution. File via
-  `gh issue create --label postmortem --label SEV-1` (or `--label SEV-2`).
-- **Action items** must be assigned, dated, and tracked in
-  `docs/TECH_DEBT.md` (P0 < 30 d, P1 < 90 d per that doc's SLA).
-- **Mandatory attendees**: incident commander, on-call, any engineer
-  who touched the mitigation, and one person who was *not* involved
-  (fresh-eyes review).
-
----
-
-## 8. Review log
-
-| Date | Reviewer | Change |
-|---|---|---|
-| 2026-06-18 | security-circle lead | Initial runbook; severity ladder + 15-min checklist + 4.1–4.5 mitigation runbooks. Closes 71-pillar audit L61 (1/3 → 2/3). |
-| 2026-07-18 | observability-circle | Corrected § 4.1/4.3 to the real provider-disable (`PUT /api/providers/{connectionId}`) and authz-inventory (`tiers`/`bypassEnabled`/`cors`, no `policies_active`) mechanisms; removed foreign branding and the nonexistent ADR-024/029 references. |
-| 2026-07-18 (planned) | observability-circle | Wire on-call rotation into PagerDuty schedule; add the postmortem template. |

docs/PERF_BUDGETS.md

@@ -1,233 +0,0 @@
----
-title: "Performance Budgets — OmniRoute (2026-06-18)"
-version: 3.8.50
-lastUpdated: 2026-08-06
----
-
-# Performance Budgets — OmniRoute (2026-06-18)
-
-**Status**: Authoritative. SLO targets that the 71-pillar audit (L13)
-references for the `Perf > 2.00` gate.
-**Methodology**: per-endpoint p50/p95/p99 latency budgets, plus a
-top-level availability SLO. Budgets are derived from the 3-replica
-Caddy + Redis topology (commit `038439fa7`); adjust on infra change.
-**Enforcement**: none yet. § 6 sketches a `benches/perf-gate.k6.js` k6
-script that would assert the SLOs below, but it is a design reference,
-not a committed file — no `bench/` or `benches/` directory exists in
-this repo today. This doc is a target-setting reference only until a
-CI gate is built as follow-up work.
-**Re-evaluation cadence**: quarterly, or on any major infra change.
-
----
-
-## 1. Top-level SLOs
-
-| SLO | Target | Window | Page on breach |
-|---|---|---|---|
-| **Availability** (2xx or 4xx for /v1/* and /api/settings/*) | 99.9% | rolling 30 days | on-call P2 |
-| **Error budget burn rate** (1xx normalized rate) | < 2x for 1h, < 6x for 5m | 1h / 5m windows | on-call P1 |
-| **Aggregate p95 latency** (all /v1/*) | ≤ 1.5 s | rolling 5 min | on-call P2 |
-| **Aggregate p99 latency** (all /v1/*) | ≤ 4.0 s | rolling 5 min | on-call P2 |
-
-**Error budget**: 30-day window = 43.2 minutes of unavailability at
-99.9%. Burn rate > 2x is P2; > 6x is P1.
-
----
-
-## 2. Per-endpoint latency budgets
-
-All budgets measured **server-side** (Next.js Route Handler entry to
-response start, or last byte for streaming). Stream endpoints are
-measured to time-of-first-byte (TTFB) since the body is incremental.
-
-### 2.1 Inference endpoints (the hot path)
-
-| Endpoint | Method | p50 | p95 | p99 | Notes |
-|---|---|---|---|---|---|
-| `/v1/responses` (non-stream) | POST | 800 ms | 1.8 s | 3.5 s | Includes translator + provider roundtrip |
-| `/v1/responses` (stream) | POST (TTFB) | 350 ms | 900 ms | 1.8 s | TTFB only; total duration unbounded |
-| `/v1/relay/chat/completions` (non-stream) | POST | 1.0 s | 2.2 s | 4.0 s | Includes per-(token,IP) rate-limit check |
-| `/v1/relay/chat/completions` (stream) | POST (TTFB) | 400 ms | 1.0 s | 2.0 s | |
-| `/v1/embeddings` | POST | 300 ms | 700 ms | 1.4 s | Pure provider roundtrip; cheap |
-| `/v1/rerank` | POST | 600 ms | 1.4 s | 2.8 s | |
-| `/v1/moderations` | POST | 250 ms | 600 ms | 1.2 s | Lightweight classification |
-| `/v1/audio/speech` | POST | 1.2 s | 3.0 s | 6.0 s | Audio synthesis is slow; budget reflects that |
-| `/v1/audio/transcriptions` | POST | 2.0 s | 5.0 s | 10.0 s | STT is bounded by audio duration + model size |
-| `/v1/images/generations` | POST | 4.0 s | 8.0 s | 15.0 s | Image gen is async-bound by provider |
-| `/v1/videos/generations` | POST (TTFB) | 600 ms | 1.5 s | 3.0 s | Async; client polls `/v1/videos/{id}` |
-| `/v1/music/generations` | POST | 3.0 s | 6.0 s | 12.0 s | |
-
-### 2.2 Files + batches
-
-| Endpoint | Method | p50 | p95 | p99 | Notes |
-|---|---|---|---|---|---|
-| `/v1/files` (GET) | GET | 80 ms | 200 ms | 400 ms | Cached list |
-| `/v1/files` (POST upload) | POST | 500 ms | 1.2 s | 2.5 s | 25 MB cap; multipart parse |
-| `/v1/files/{id}` (GET) | GET | 60 ms | 150 ms | 300 ms | |
-| `/v1/files/{id}` (DELETE) | DELETE | 80 ms | 200 ms | 400 ms | |
-| `/v1/files/{id}/content` (download) | GET | 100 ms | 300 ms | 600 ms | + per-MB throughput |
-| `/v1/batches` (GET) | GET | 150 ms | 400 ms | 800 ms | |
-| `/v1/batches` (POST create) | POST | 200 ms | 500 ms | 1.0 s | Validates input file then enqueues |
-| `/v1/batches/{id}` (GET) | GET | 100 ms | 300 ms | 600 ms | |
-| `/v1/batches/{id}` (DELETE) | DELETE | 100 ms | 300 ms | 600 ms | |
-| `/v1/batches/delete-completed` (POST) | POST | 400 ms | 1.0 s | 2.0 s | Mass delete; n rows |
-
-### 2.3 Agents
-
-| Endpoint | Method | p50 | p95 | p99 | Notes |
-|---|---|---|---|---|---|
-| `/v1/agents/health` | GET | 1.5 s | 4.5 s | 5.0 s | 5s per-provider timeout cap; expect 3-provider total |
-| `/v1/agents/credentials` | GET | 100 ms | 250 ms | 500 ms | Metadata only; values never returned |
-| `/v1/agents/tasks` (GET list) | GET | 150 ms | 400 ms | 800 ms | |
-| `/v1/agents/tasks` (POST create) | POST | 250 ms | 600 ms | 1.2 s | Just enqueues; doesn't run agent |
-| `/v1/agents/tasks/{id}` (GET) | GET | 100 ms | 300 ms | 600 ms | |
-| `/v1/agents/tasks/{id}` (DELETE) | DELETE | 150 ms | 400 ms | 800 ms | |
-
-### 2.4 Combos / me / providers
-
-| Endpoint | Method | p50 | p95 | p99 |
-|---|---|---|---|---|
-| `/v1/combos` | GET | 80 ms | 200 ms | 400 ms |
-| `/v1/me/status` | GET | 60 ms | 150 ms | 300 ms |
-| `/v1/providers/{provider}/models` | GET | 100 ms | 250 ms | 500 ms |
-
-### 2.5 Web / search
-
-| Endpoint | Method | p50 | p95 | p99 | Notes |
-|---|---|---|---|---|---|
-| `/v1/web/fetch` | POST | 1.5 s | 4.0 s | 8.0 s | 10s timeout cap; recurse depth 3 |
-| `/v1/search` | POST | 800 ms | 2.0 s | 4.0 s | Provider search latency varies |
-
-### 2.6 VSCode-CLI shim (token-scoped)
-
-These are the legacy passthrough paths. Budgets are tighter because
-they're called frequently by the VSCode-CLI extension in tight loops.
-
-| Endpoint | Method | p50 | p95 | p99 |
-|---|---|---|---|---|
-| `/v1/vscode/{token}/v1/chat/completions` | POST | 700 ms | 1.6 s | 3.0 s |
-| `/v1/vscode/{token}/v1/models` | GET | 60 ms | 150 ms | 300 ms |
-| `/v1/vscode/{token}/combos` | GET | 80 ms | 200 ms | 400 ms |
-| `/v1/vscode/{token}/chat/completions` (legacy) | POST | 700 ms | 1.6 s | 3.0 s |
-| `/v1/vscode/{token}/models` (legacy) | GET | 60 ms | 150 ms | 300 ms |
-| `/v1/vscode/{token}/responses` | POST | 800 ms | 1.8 s | 3.5 s |
-
-### 2.7 Management / settings
-
-Management endpoints are operator-only and not part of the hot path.
-Budgets are set conservatively; breaches don't page on-call but do
-flag in the weekly perf review.
-
-| Endpoint group | p50 | p95 | p99 |
-|---|---|---|---|
-| `/api/settings/*` (GET) | 100 ms | 300 ms | 600 ms |
-| `/api/settings/*` (POST/PATCH/DELETE) | 200 ms | 500 ms | 1.0 s |
-| `/api/keys/*` (CRUD) | 150 ms | 400 ms | 800 ms |
-| `/api/quota/*` (CRUD) | 150 ms | 400 ms | 800 ms |
-| `/api/monitoring/health` (heavy) | 500 ms | 1.5 s | 3.0 s |
-
-### 2.8 Public probes
-
-| Endpoint | Method | p50 | p95 | p99 |
-|---|---|---|---|---|
-| `/api/health/ping` | GET | 5 ms | 20 ms | 50 ms |
-| `/api/monitoring/health` | GET | 5 ms | 20 ms | 50 ms |
-| `/api/docs` | GET | 20 ms | 80 ms | 200 ms (HTML shell, no provider call) |
-
----
-
-## 3. Throughput targets
-
-| Tier | Per-replica RPS | Cluster RPS (3 replicas) | Notes |
-|---|---|---|---|
-| Inference (non-stream) | 50 RPS | 150 RPS | Bounded by provider quota + translator CPU |
-| Inference (stream) | 25 concurrent streams | 75 streams | Bounded by Node event-loop + memory |
-| Embeddings | 200 RPS | 600 RPS | Cheap |
-| Files (upload) | 10 RPS | 30 RPS | Multipart parse + DB write |
-| Files (download) | 100 RPS | 300 RPS | Static-content via Next.js |
-| Combos / me / providers | 500 RPS | 1,500 RPS | Cached |
-| WebSocket | 100 concurrent connections | 300 | Per-IP cap 5 |
-
-**Cluster ceiling** (all endpoints combined, sustained): ~1,000 RPS
-before p95 latency begins to climb. Scale horizontally beyond that
-by adding replicas; the Caddy LB is stateless.
-
----
-
-## 4. Resource budgets
-
-| Resource | Per-replica cap | Notes |
-|---|---|---|
-| RSS memory | 1.5 GB | Spikes during audio/video gen; expect brief 2 GB |
-| Event-loop lag (p99) | 50 ms | Alert via `clinic doctor` regression |
-| Heap retained | 800 MB | Old-gen GC tuning in `node --max-old-space-size` |
-| File descriptors | 2,000 | `ulimit -n 4096` recommended at host |
-| DB connections (sql.js) | 1 per replica | sql.js is in-process; no pool needed |
-| Redis connections | 20 per replica | Pooled; idle reaped at 5 min |
-
----
-
-## 5. Cold-start budget
-
-Next.js App Router cold-start on a fresh container:
-
-| Phase | Budget |
-|---|---|
-| Container start → HTTP listening | ≤ 800 ms |
-| First request TTFB (warm) | ≤ 200 ms |
-| Translator registry bootstrap | ≤ 500 ms (one-time, first /v1/responses) |
-
-**Measurement script**: `bin/cold-start-bench.sh` (already in the repo
-since v3.8.36; `bin/` is the canonical scripts dir).
-
----
-
-## 6. Regression gate (k6 reference, not yet implemented)
-
-The sketch below shows how a future `benches/perf-gate.k6.js` script
-would assert the SLOs above. Nothing in this section is committed or
-wired into CI today — it is a design reference for follow-up work, not
-a running gate.
-
-```javascript
-// benches/perf-gate.k6.js — pseudo-code; not yet committed
-import http from 'k6/http';
-import { check, Trend } from 'k6';
-
-const responsesTTFB = new Trend('v1_responses_ttfb', true);
-
-export const options = {
-  scenarios: {
-    smoke: {
-      executor: 'constant-vus',
-      vus: 10,
-      duration: '1m',
-    },
-  },
-  thresholds: {
-    'http_req_duration{endpoint:v1_responses}': ['p(95)<1800', 'p(99)<3500'],
-    'http_req_failed': ['rate<0.01'],
-    'v1_responses_ttfb': ['p(95)<900'],
-  },
-};
-
-export default function () {
-  const res = http.post(`${__ENV.BASE_URL}/api/v1/responses`, JSON.stringify({
-    model: 'gpt-4o-mini',
-    input: 'ping',
-  }), { headers: { 'Authorization': `Bearer ${__ENV.API_KEY}` }});
-  check(res, { 'status is 200': (r) => r.status === 200 });
-  responsesTTFB.add(res.timings.waiting);
-}
-```
-
----
-
-## 7. Review log
-
-| Date | Reviewer | Change |
-|---|---|---|
-| 2026-06-18 | security-circle lead | Initial per-endpoint budgets derived from 3-replica Caddy + Redis topology |
-| 2026-07-18 | observability-circle | Clarified this doc ships zero enforcement today (no `bench/`/`benches/` dir, no CI gate) and fixed the stale "not yet committed" claim about `bin/cold-start-bench.sh` (present since v3.8.36). |
-| 2026-07-18 (planned) | observability-circle | Wire `benches/perf-gate.k6.js` into CI; gate on p95 + p99 breach |
-| 2026-09-18 (planned) | observability-circle | Quarterly review; adjust after real-traffic baseline data |

docs/README.md

@@ -8,7 +8,7 @@ lastUpdated: 2026-06-28
 
 Navigable index of the OmniRoute documentation set. Topics are grouped by intent so you can find what you need quickly.
 
-> Looking for the project overview, install steps, or release notes? See the root [README.md](../README.md), [CHANGELOG.md](../CHANGELOG.md), and [CONTRIBUTING.md](../CONTRIBUTING.md).
+> Looking for the project overview, install steps, or release notes? See the root [README.md](../README.md), [ROADMAP.md](../ROADMAP.md), [CHANGELOG.md](../CHANGELOG.md), and [CONTRIBUTING.md](../CONTRIBUTING.md).
 
 ---
 
@@ -22,7 +22,7 @@ Simple guides for using OmniRoute — no technical background needed.
 - [AUTO-COMBO-GUIDE.md](getting-started/AUTO-COMBO-GUIDE.md) — let OmniRoute pick the best AI for you.
 - [PROVIDERS-GUIDE.md](getting-started/PROVIDERS-GUIDE.md) — how to connect AI providers.
 - [FREE-TIERS-GUIDE.md](getting-started/FREE-TIERS-GUIDE.md) — get free AI with no credit card.
-- [TROUBLESHOOTING.md](getting-started/TROUBLESHOOTING.md) — fix common issues.
+- [WEB-COOKIE-GUIDE.md](getting-started/WEB-COOKIE-GUIDE.md) — web cookie providers (session-credential setup).
 
 ### guides/
 
@@ -42,6 +42,8 @@ Simple guides for using OmniRoute — no technical background needed.
 - [CLAUDE-CODE-CONFIGURATION.md](guides/CLAUDE-CODE-CONFIGURATION.md) — Claude Code CLI with OmniRoute.
 - [CODEX-CLI-CONFIGURATION.md](guides/CODEX-CLI-CONFIGURATION.md) — Codex CLI with OmniRoute.
 - [KIRO_SETUP.md](guides/KIRO_SETUP.md) — Kiro setup.
+- [ANTIGRAVITY-ONBOARDING.md](guides/ANTIGRAVITY-ONBOARDING.md) — Antigravity (Google One AI) onboarding.
+- [MANAGEMENT-AUTH.md](guides/MANAGEMENT-AUTH.md) — management authentication.
 - [I18N.md](guides/I18N.md) — translation and locale workflow.
 - [TROUBLESHOOTING.md](guides/TROUBLESHOOTING.md) — detailed troubleshooting reference.
 - [UNINSTALL.md](guides/UNINSTALL.md) — clean removal steps.
@@ -64,6 +66,10 @@ How the system is put together — read these to understand the runtime, code la
 - [QUALITY_GATES.md](architecture/QUALITY_GATES.md) — quality-gate scripts and CI jobs inventory.
 - [MONITORING_SECTIONS.md](architecture/MONITORING_SECTIONS.md) — monitoring/costs dashboard navigation.
 - [cluster-decisions.md](architecture/cluster-decisions.md) — optional sidecar/cluster profile decisions.
+- [DESIGN_SYSTEM.md](architecture/DESIGN_SYSTEM.md) — design system & visual identity.
+- [ROUTER_BACKENDS.md](architecture/ROUTER_BACKENDS.md) — router backends & embedded services architecture contract (ADR).
+- [admission-lanes.md](architecture/admission-lanes.md) — the two admission-lane systems and what gates each.
+- [persistence-backend-boundary.md](architecture/persistence-backend-boundary.md) — pluggable persistence boundary (ADR).
 
 ## reference/
 
@@ -77,6 +83,9 @@ Lookup material — API surface, environment variables, CLI flags, provider cata
 - [FEATURE_FLAGS.md](reference/FEATURE_FLAGS.md) — feature flags and their defaults.
 - [CLI-TOOLS.md](reference/CLI-TOOLS.md) — bundled CLI commands.
 - [FREE_TIERS.md](reference/FREE_TIERS.md) — free-tier LLM provider directory.
+- [FREE_PROXIES_API.md](reference/FREE_PROXIES_API.md) — free proxies API.
+- [RELAY_BACKEND_STRATEGY.md](reference/RELAY_BACKEND_STRATEGY.md) — relay backend strategy.
+- [RELAY_TROUBLESHOOTING.md](reference/RELAY_TROUBLESHOOTING.md) — relay troubleshooting.
 
 ## frameworks/
 
@@ -97,6 +106,7 @@ Pluggable subsystems exposed to clients, agents, and operators.
 - [EMBEDDED-SERVICES.md](frameworks/EMBEDDED-SERVICES.md) — embedded sidecar services (9Router, CLIProxyAPI).
 - [NOTION_CONTEXT.md](frameworks/NOTION_CONTEXT.md) — Notion context source.
 - [OBSIDIAN_CONTEXT.md](frameworks/OBSIDIAN_CONTEXT.md) — Obsidian context source.
+- [LOCAL_CORPUS_CONTEXT.md](frameworks/LOCAL_CORPUS_CONTEXT.md) — local corpus context source (approved directory exposed to MCP).
 - [OPENCODE.md](frameworks/OPENCODE.md) — OpenCode integration.
 - [OPEN_SSE_ARCHITECTURE.md](frameworks/OPEN_SSE_ARCHITECTURE.md) — open-sse streaming engine internals.
 - [PLAYGROUND_STUDIO.md](frameworks/PLAYGROUND_STUDIO.md) — Playground Studio UI.
@@ -111,9 +121,10 @@ Pluggable subsystems exposed to clients, agents, and operators.
 
 Combo routing, scoring, and replay.
 
-- [AUTO-COMBO.md](routing/AUTO-COMBO.md) — Auto-Combo (multi-factor scoring, 17 strategies).
+- [AUTO-COMBO.md](routing/AUTO-COMBO.md) — Auto-Combo (multi-factor scoring, 19 strategies).
 - [QUOTA_SHARE.md](routing/QUOTA_SHARE.md) — quota sharing engine.
 - [REASONING_REPLAY.md](routing/REASONING_REPLAY.md) — reasoning replay cache.
+- [REASONING_ROUTING.md](routing/REASONING_ROUTING.md) — reasoning routing rules (effort/budget rule engine).
 
 ## security/
 
@@ -127,6 +138,9 @@ Guardrails, compliance, stealth, and the mandatory patterns for handling public
 - [ROUTE_GUARD_TIERS.md](security/ROUTE_GUARD_TIERS.md) — route-guard classification tiers.
 - [CLI_TOKEN.md](security/CLI_TOKEN.md) — CLI machine-ID token (HMAC + legacy SHA-256) auth.
 - [EGRESS_POLICY.md](security/EGRESS_POLICY.md) — egress IP family (IPv4/IPv6) policy.
+- [BAN_DETECTION.md](security/BAN_DETECTION.md) — account-ban / banned-keyword detection.
+- [AGENTROUTER_WAF.md](security/AGENTROUTER_WAF.md) — agentrouter.org WAF.
+- [CORS.md](security/CORS.md) — CORS configuration & security.
 - [MITM-TPROXY-DECRYPT.md](security/MITM-TPROXY-DECRYPT.md) — transparent MITM decrypt.
 - [SUPPLY_CHAIN.md](security/SUPPLY_CHAIN.md) — supply-chain gates (SLSA, SBOM, Trivy, osv-scanner, Scorecard).
 - [SOCKET_DEV_FINDINGS.md](security/SOCKET_DEV_FINDINGS.md) — supply-chain finding attestations.
@@ -148,8 +162,11 @@ Prompt compression engines, rules, and language packs.
 Provider-specific integration guides.
 
 - [CLAUDE_WEB.md](providers/CLAUDE_WEB.md) — Claude Web (cookie-auth) provider.
+- [CHATGPT_WEB.md](providers/CHATGPT_WEB.md) — ChatGPT Web (Plus/Pro + Codex) providers.
+- [ALIBABA-QWEN-PROVIDER-FAMILIES.md](providers/ALIBABA-QWEN-PROVIDER-FAMILIES.md) — Alibaba and Qwen provider families.
 - [AGENTROUTER.md](providers/AGENTROUTER.md) — AgentRouter setup.
 - [ZED-DOCKER.md](providers/ZED-DOCKER.md) — Zed IDE integration under Docker.
+- [CURSOR-DOCKER.md](providers/CURSOR-DOCKER.md) — Cursor model listing under Docker.
 
 ## comparison/
 
@@ -161,11 +178,17 @@ Release, deployment, proxies, tunnels, coverage, database, monitoring.
 
 - [RELEASE_CHECKLIST.md](ops/RELEASE_CHECKLIST.md) — release flow checklist.
 - [RELEASE_GREEN.md](ops/RELEASE_GREEN.md) — keeping the PR queue and release branch green.
+- [BRANCHING_MODEL.md](ops/BRANCHING_MODEL.md) — branching & release model.
+- [MERGE_TRAIN.md](ops/MERGE_TRAIN.md) — merge queue & manual merge-train runbook.
+- [HOMOLOGATION.md](ops/HOMOLOGATION.md) — homologation suite (`npm run homolog`).
 - [QUALITY_GATE_PLAYBOOK.md](ops/QUALITY_GATE_PLAYBOOK.md) — quality-gate playbook.
+- [RUNNER_BOX.md](ops/RUNNER_BOX.md) — self-hosted runner box operations.
 - [BRANCH_PROTECTION_MAIN.md](ops/BRANCH_PROTECTION_MAIN.md) — `main` branch protection.
+- [CONTRIBUTION_GOLDEN_PATH.md](ops/CONTRIBUTION_GOLDEN_PATH.md) — contribution golden path (focused checks per change type).
 - [COVERAGE_PLAN.md](ops/COVERAGE_PLAN.md) — test coverage plan.
 - [DATABASE_GUIDE.md](ops/DATABASE_GUIDE.md) — DB schema and operations.
 - [SQLITE_RUNTIME.md](ops/SQLITE_RUNTIME.md) — SQLite driver resolution chain.
+- [REDIS_PRODUCTION_CONFIG.md](ops/REDIS_PRODUCTION_CONFIG.md) — Redis production configuration.
 - [MONITORING_GUIDE.md](ops/MONITORING_GUIDE.md) — monitoring & observability.
 - [FLY_IO_DEPLOYMENT_GUIDE.md](ops/FLY_IO_DEPLOYMENT_GUIDE.md) — Fly.io deployment.
 - [VM_DEPLOYMENT_GUIDE.md](ops/VM_DEPLOYMENT_GUIDE.md) — generic VM deployment.

docs/architecture/ARCHITECTURE.md

@@ -17,7 +17,7 @@ It provides a single OpenAI-compatible endpoint (`/v1/*`) and routes traffic acr
 
 Core capabilities:
 
-- OpenAI-compatible API surface for CLI/tools (271 providers, 89 executors)
+- OpenAI-compatible API surface for CLI/tools (338 providers, 101 executors)
 - Request/response translation across provider formats
 - Model combo fallback (multi-model sequence)
 - Structured combo steps (`provider + model + connection`) with runtime ordering by `compositeTiers`
@@ -365,7 +365,7 @@ relying on a static combo definition. It powers the `auto/*` model prefix family
 
 Key capabilities:
 
-- **17 routing strategies** (priority, weighted, fill-first, round-robin, P2C, random,
+- **19 routing strategies** (priority, weighted, fill-first, round-robin, P2C, random,
   least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random,
   **auto**, lkgp, context-optimized, context-relay, **fusion**, plus a fallback path) —
   auto is the headline addition in v3.8.0; `fusion` (panel fan-out + judge synthesis,

docs/architecture/CODEBASE_DOCUMENTATION.md

@@ -452,12 +452,12 @@ open-sse/
 ├── types.d.ts
 ├── config/                 Provider registries, header profiles, identity, …
 ├── handlers/               Request handlers (chat, embeddings, audio, image, …)
-├── executors/              89 provider-specific HTTP executors
+├── executors/              101 provider-specific HTTP executors
 ├── translator/             Format conversion (OpenAI ↔ Claude ↔ Gemini ↔ Cursor ↔ Kiro)
 ├── transformer/            Responses API ↔ Chat Completions stream transformer
 ├── services/               80+ service modules (combos, fallback, quotas, identity, …)
 ├── utils/                  Streaming helpers, TLS client, AWS SigV4, proxy fetch, …
-└── mcp-server/             MCP server (3 transports, 32 scopes, 99 tools)
+└── mcp-server/             MCP server (3 transports, 31 scopes, 105 tools)
 ```
 
 ### 4.1 `open-sse/handlers/`
@@ -482,7 +482,7 @@ open-sse/
 
 ### 4.2 `open-sse/executors/`
 
-84 provider executors, each extending `BaseExecutor` (`base.ts`):
+101 provider executors, each extending `BaseExecutor` (`base.ts`):
 
 `antigravity`, `azure-openai`, `blackbox-web`, `chatgpt-web`, `cliproxyapi`,
 `cloudflare-ai`, `codex`, `commandCode`, `cursor`, `default`, `devin-cli`,
@@ -491,7 +491,7 @@ open-sse/
 (shared identity helper) and `index.ts` (registry).
 
 > Note: providers not listed here are served by `default.ts` using the generic
-> OpenAI-compatible executor. The full provider catalog (268 entries) lives in
+> OpenAI-compatible executor. The full provider catalog (338 providers) lives in
 > `src/shared/constants/providers.ts`.
 
 ### 4.3 `open-sse/translator/`
@@ -524,7 +524,7 @@ Highlights (full list under `open-sse/services/`):
 
 | Concern              | Files                                                                                                                                                                                                                                             |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Combo routing        | `combo.ts` (17 strategies), `comboConfig.ts`, `comboMetrics.ts`, `comboManifestMetrics.ts`, `comboAgentMiddleware.ts`                                                                                                                             |
+| Combo routing        | `combo.ts` (19 strategies), `comboConfig.ts`, `comboMetrics.ts`, `comboManifestMetrics.ts`, `comboAgentMiddleware.ts`                                                                                                                             |
 | Auto Combo engine    | `autoCombo/` — `engine.ts`, `scoring.ts`, `taskFitness.ts`, `virtualFactory.ts`, `modePacks.ts`, `autoPrefix.ts`, `persistence.ts`, `providerDiversity.ts`, `providerRegistryAccessor.ts`, `routerStrategy.ts`, `selfHealing.ts`, `index.ts`      |
 | Resilience           | `accountFallback.ts` (cooldown + lockout), `errorClassifier.ts`, `emergencyFallback.ts`, `rateLimitManager.ts`, `rateLimitSemaphore.ts`, `accountSemaphore.ts`, `accountSelector.ts`                                                              |
 | Quotas               | `quotaMonitor.ts`, `quotaPreflight.ts`, `bailianQuotaFetcher.ts`, `codexQuotaFetcher.ts`, `deepseekQuotaFetcher.ts`, `openrouterQuotaFetcher.ts`, `openrouterFreeWindow.ts`, `crofUsageFetcher.ts`, `antigravityCredits.ts`                       |
@@ -544,7 +544,7 @@ Highlights (full list under `open-sse/services/`):
   5 compression tools, 3 memory tools, 4 skills tools, plus advanced tools added
   through `advancedTools.ts`).
 - **3 transports**: stdio, HTTP Streamable, SSE.
-- **13 scopes** declared in `src/shared/constants/mcpScopes.ts`.
+- **31 scopes** declared in `src/shared/constants/mcpScopes.ts`.
 - Audit table: `mcp_tool_audit` (populated by `audit.ts`).
 - Files: `server.ts`, `index.ts`, `httpTransport.ts`, `audit.ts`, `scopeEnforcement.ts`,
   `runtimeHeartbeat.ts`, `descriptionCompressor.ts`, `schemas/{tools, a2a, audit, index}.ts`,

docs/architecture/MONITORING_SECTIONS.md

@@ -142,5 +142,5 @@ Namespaces added by Group B:
 | `sidebar.costsOverview` | Costs overview item                                            |
 | `activity.*`            | All Activity page strings (title, verbs, filters, empty state) |
 
-Source-of-truth locales: `pt-BR` and `en`. All other 39 locales fall back to
+Source-of-truth locales: `pt-BR` and `en`. All other 41 locales fall back to
 English via the `next-intl` fallback mechanism (configured in `src/i18n/config.ts`).

docs/architecture/QUALITY_GATES.md

@@ -9,7 +9,9 @@ It describes each gate, what it validates, which CI job it runs in, whether it u
 a ratchet baseline or a pass/fail policy, and whether it blocks the build or is advisory.
 
 For a short summary and the allowlist policy, see the "Quality Gates & Ratchets" section
-in `CLAUDE.md`.
+in `CLAUDE.md`. For the critical assessment, maturity classification, and tool-agnostic
+replication plan of the same system, see the
+[Quality Gate Playbook](../ops/QUALITY_GATE_PLAYBOOK.md).
 
 ---
 
@@ -205,7 +207,7 @@ Runs after `build`. Blocks merge on failure.
 
 | Suite            | Validates                                               | Blocking                                                                                                      |
 | ---------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| `test:vitest`    | MCP server (94 tools), autoCombo, cache — vitest runner | Yes                                                                                                           |
+| `test:vitest`    | MCP server (105 tools), autoCombo, cache — vitest runner | Yes                                                                                                           |
 | `test:vitest:ui` | UI component tests — vitest runner                      | **Blocking** — pre-existing failures are explicitly excluded in `vitest.config.ts`; new failures fail the job |
 
 ### Nightly workflows (scheduled, advisory)

docs/architecture/REPOSITORY_MAP.md

@@ -182,7 +182,7 @@ src/
 | `compliance/`                            | Audit log + provider audit — see `docs/security/COMPLIANCE.md`                                                                                                                                                                                                                                                          |
 | `compression/`                           | Compression engine glue (engines live in `open-sse/services/compression/`)                                                                                                                                                                                                                                              |
 | `config/`                                | Runtime config helpers                                                                                                                                                                                                                                                                                                  |
-| `db/`                                    | 95+ domain DB modules + 110+ migrations (always go through here for SQLite)                                                                                                                                                                                                                                             |
+| `db/`                                    | 95+ domain DB modules + 144 migrations (always go through here for SQLite)                                                                                                                                                                                                                                             |
 | `quota/`                                 | Quota Sharing Engine: `dimensions.ts` (types/Zod), `types.ts` (QuotaStore interface), `sqliteQuotaStore.ts`, `redisQuotaStore.ts`, `storeFactory.ts`, `fairShare.ts`, `burnRate.ts`, `planResolver.ts`, `planRegistry.ts`, `saturationSignals.ts`, `enforce.ts`, `spendRecorder.ts` — see `docs/routing/QUOTA_SHARE.md` |
 | `radar/`                                 | Radar free-model catalog client: `feedSchema.ts`, `pinnedKeys.ts`, `verify.ts`, `sync.ts`, `applyFeed.ts`, `index.ts` (`getRadarCatalog()`) — see `docs/frameworks/RADAR.md`                                                                                                                                            |
 | `display/`                               | UI formatting helpers (cost, latency, etc.)                                                                                                                                                                                                                                                                             |
@@ -209,7 +209,7 @@ src/
 | `cacheLayer.ts`, `idempotencyLayer.ts`   | Request caching + idempotency                                                                                                                                                                                                                                                                                           |
 | (~30 more top-level files)               | Specialized helpers (logEnv, modelsDevSync, piiSanitizer, etc.)                                                                                                                                                                                                                                                         |
 
-### `src/db/` — Database (94 modules + 106 migrations)
+### `src/db/` — Database (117 modules + 144 migrations)
 
 | Subdir                    | Purpose                                                                                                                                                                    |
 | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -244,9 +244,9 @@ src/
 
 | Module                           | Purpose                                                                |
 | -------------------------------- | ---------------------------------------------------------------------- |
-| `constants/providers.ts`         | **236 providers** with Zod validation (source of truth)                |
+| `constants/providers.ts`         | **338 providers** with Zod validation (source of truth)                |
 | `constants/cliTools.ts`          | External CLI tool registry                                             |
-| `constants/routingStrategies.ts` | **17 routing strategies** with priorities                              |
+| `constants/routingStrategies.ts` | **19 routing strategies** with priorities                              |
 | `constants/publicApiRoutes.ts`   | Routes that require Bearer (vs management) auth                        |
 | `constants/upstreamHeaders.ts`   | Header denylist for upstream requests                                  |
 | `validation/schemas.ts`          | ~80 Zod schemas (single source of truth for API contracts)             |
@@ -270,7 +270,7 @@ open-sse/
 ├── translator/          # Format converters (9 request, 9 response, 9 helpers)
 ├── transformer/         # Responses API ↔ Chat Completions (TransformStream)
 ├── services/            # ~80+ service modules (combo, accountFallback, autoCombo, reasoningCache, claude code/chatgpt stealth, modelDeprecation, taskAwareRouter, workflowFSM, etc.)
-├── mcp-server/          # MCP server (99 tools, 3 transports, 32 scopes)
+├── mcp-server/          # MCP server (105 tools, 3 transports, 31 scopes)
 ├── config/              # Provider/model registries, header config, model aliases
 ├── utils/               # TLS client, proxy fetch/dispatcher, network helpers
 ├── index.ts             # Workspace entry
@@ -398,16 +398,16 @@ open-sse/
 | `COVERAGE_PLAN.md`          | Coverage goals and current state                                                      |
 | `FREE_TIERS.md`             | Curated free-tier providers (48+ free + 11 OAuth)                                     |
 | `CLI-TOOLS.md`              | External CLI integrations + Internal OmniRoute CLI                                    |
-| `I18N.md`                   | i18n architecture, adding a language, 30 locales                                      |
+| `I18N.md`                   | i18n architecture, adding a language, 43 locales                                      |
 | `UNINSTALL.md`              | Clean uninstall steps                                                                 |
-| `PROVIDER_REFERENCE.md`     | **Auto-generated** catalog of 236 providers (regen: `npm run gen:provider-reference`) |
+| `PROVIDER_REFERENCE.md`     | **Auto-generated** catalog of 338 providers (regen: `npm run gen:provider-reference`) |
 
 ### Subsystem deep-dives
 
 | Doc                        | Purpose                                                             |
 | -------------------------- | ------------------------------------------------------------------- |
-| `MCP-SERVER.md`            | MCP server: 99 tools, 3 transports, 32 scopes, REST endpoints       |
-| `A2A-SERVER.md`            | A2A v0.3: JSON-RPC, 5 skills, REST helpers, agent card              |
+| `MCP-SERVER.md`            | MCP server: 105 tools, 3 transports, 31 scopes, REST endpoints       |
+| `A2A-SERVER.md`            | A2A v0.3: JSON-RPC, 6 skills, REST helpers, agent card              |
 | `AGENT_PROTOCOLS_GUIDE.md` | Unified guide: A2A vs ACP vs Cloud Agents                           |
 | `CLOUD_AGENT.md`           | Codex Cloud / Devin / Jules orchestration                           |
 | `SKILLS.md`                | Skills framework (built-in + marketplace + SkillsSH + sandbox)      |

docs/architecture/meta.json

@@ -6,6 +6,12 @@
     "CODEBASE_DOCUMENTATION",
     "REPOSITORY_MAP",
     "RESILIENCE_GUIDE",
-    "QUALITY_GATES"
+    "QUALITY_GATES",
+    "DESIGN_SYSTEM",
+    "MONITORING_SECTIONS",
+    "ROUTER_BACKENDS",
+    "admission-lanes",
+    "cluster-decisions",
+    "persistence-backend-boundary"
   ]
 }

docs/architecture/mysql-conformance-semantics.md

@@ -1,916 +0,0 @@
----
-title: "MySQL conformance semantics and failure-mode matrix"
-status: proposed-test-specification
-lastUpdated: 2026-07-30
----
-
-# MySQL conformance semantics and failure-mode matrix
-
-- **Tracking issue:** [#8075](https://github.com/diegosouzapw/OmniRoute/issues/8075)
-- **Governing proposal:** [Pluggable persistence boundary](persistence-backend-boundary.md)
-- **Measured baseline:** [SQLite coupling inventory](sqlite-coupling-inventory.md)
-- **Target:** MySQL 8.0 with InnoDB
-- **Runtime impact:** None. This document adds no driver, dependency, configuration, schema,
-  migration, or support claim.
-
-## 1. Purpose and normative language
-
-The persistence-boundary ADR requires conformance tests to compare observable behavior, not only
-repository method signatures. This document turns the MySQL/InnoDB differences that can change
-OmniRoute behavior into an implementation-ready specification. It provides:
-
-- a required server and session profile;
-- evidence from the current SQLite implementation;
-- minimal SQL probes that reviewers can reproduce independently;
-- a backend-neutral error and retry taxonomy;
-- normative decisions that a repository contract must make;
-- executable acceptance specifications for a future shared conformance harness;
-- a focused acceptance profile for combo definitions and model-to-combo mappings.
-
-The terms **MUST**, **MUST NOT**, **SHOULD**, and **MAY** are normative. A proposed MySQL adapter is
-not conformant merely because its SQL succeeds. It is conformant only when the same repository
-fixture produces the same domain result, durable state, atomicity, ordering, and classified failure
-as the SQLite implementation.
-
-## 2. Scope and non-goals
-
-### 2.1 In scope
-
-This specification covers portable durable-state behavior for:
-
-- create, read, update, delete, and missing-row results;
-- uniqueness, collation, case and accent sensitivity, and `NULL`;
-- stable ordering and pagination;
-- no-op writes and affected-row reporting;
-- insert, identity-preserving upsert, and replacement;
-- IDs, JSON, exact numerics, and timestamps;
-- transactions, deadlocks, lock waits, disconnects, and retry boundaries;
-- foreign keys and atomic related-record changes;
-- migration ownership, implicit DDL commits, recovery, and readiness.
-
-### 2.2 Out of scope
-
-This specification does not:
-
-- approve PostgreSQL or MySQL runtime support;
-- select a Node.js MySQL driver or pool;
-- define a public environment variable or configuration UI;
-- define final TypeScript repository interfaces;
-- add physical MySQL schema or migration files;
-- make SQLite maintenance, FTS5, `sqlite-vec`, backup files, or WAL portable;
-- replace domain-specific acceptance criteria;
-- permit runtime work while the governing ADR remains unapproved.
-
-## 3. Evidence from the current repository
-
-The current implementation establishes behavior that a portable contract must either preserve or
-explicitly revise. These are source-backed observations, not proposed MySQL schema.
-
-### 3.1 Combo identity and lookup
-
-`src/lib/db/migrations/001_initial_schema.sql` defines `combos.id` as the primary key and
-`combos.name` as unique. `src/lib/db/combos.ts` currently:
-
-- generates UUIDs in the application;
-- generates timestamps with `new Date().toISOString()`;
-- performs exact name lookup first;
-- provides a separate `COLLATE NOCASE` fallback lookup;
-- lists by `sort_order ASC, name COLLATE NOCASE ASC`;
-- treats an update of a missing ID as `null`;
-- treats deletion of a missing ID as `false`;
-- updates the JSON payload and deduplicated columns together;
-- reorders all selected rows in one SQLite transaction.
-
-Those choices imply that a future MySQL slice does not need database-generated numeric IDs for
-combos, but it must still define Unicode collation, complete tie-breakers, update/delete results, and
-reorder concurrency.
-
-### 3.2 Model-to-combo mapping behavior
-
-`src/lib/db/migrations/010_model_combo_mappings.sql` defines a foreign key from
-`model_combo_mappings.combo_id` to `combos.id` with `ON DELETE CASCADE`.
-`src/lib/db/modelComboMappings.ts` currently:
-
-- generates mapping UUIDs and ISO timestamps in the application;
-- lists by `priority DESC, created_at ASC`;
-- returns a separate total count for paginated results;
-- maps integer `0`/`1` values to booleans;
-- treats a missing update as `null` and a missing delete as `false`;
-- resolves the first enabled matching pattern;
-- skips malformed combo JSON rather than failing resolution.
-
-The current list and resolution order lacks a unique final tie-breaker. The MySQL implementation
-MUST NOT preserve that accidental nondeterminism. Before portability is claimed, the contract must
-add `id ASC` (or another unique stable key) after `created_at ASC` and the SQLite implementation
-must adopt the same order.
-
-### 3.3 Existing SQLite-specific signals
-
-The measured SQLite coupling inventory records widespread use of synchronous prepared statements,
-`INSERT OR REPLACE`, `lastInsertRowid`, SQLite transactions, and SQLite lifecycle operations. A
-future adapter must not translate those tokens mechanically. In particular:
-
-- `INSERT OR REPLACE` is delete-then-insert conflict handling, not an update;
-- `changes` is a driver result, not a portable domain result;
-- `COLLATE NOCASE` is not equivalent to a modern MySQL Unicode collation;
-- SQLite numbered migration SQL is not reusable as MySQL migration SQL.
-
-## 4. Required MySQL deployment and session profile
-
-A conformance run MUST fail during backend initialization if the effective profile is outside the
-supported envelope. Silently inheriting server defaults would make behavior depend on an operator's
-installation history.
-
-| Property                 | Required profile                                                                   | Verification                                                                         | Failure class         |
-| ------------------------ | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | --------------------- |
-| Server family            | Oracle MySQL 8.0.x until another family passes the same suite                      | `SELECT VERSION()` and server metadata                                               | `unsupported`         |
-| Storage engine           | `InnoDB` for every portable table                                                  | `information_schema.tables`                                                          | `schema_incompatible` |
-| Character set            | `utf8mb4` for schema, tables, and portable text columns                            | `information_schema.schemata`, `tables`, and `columns`                               | `schema_incompatible` |
-| Identity collation       | Explicit per identity column; never inherited                                      | `information_schema.columns.collation_name`                                          | `schema_incompatible` |
-| SQL mode                 | Strict mode and the engine-substitution guard; adapter records the effective value | `SELECT @@SESSION.sql_mode`                                                          | `unsupported`         |
-| Transaction isolation    | Explicitly selected and verified by the backend                                    | `SELECT @@SESSION.transaction_isolation`                                             | `unsupported`         |
-| Session time zone        | UTC                                                                                | `SELECT @@SESSION.time_zone`                                                         | `unsupported`         |
-| Autocommit               | Known pool default; repository transactions set boundaries explicitly              | `SELECT @@SESSION.autocommit`                                                        | `unsupported`         |
-| Connection character set | `utf8mb4`                                                                          | `SELECT @@character_set_client, @@character_set_connection, @@character_set_results` | `unsupported`         |
-| Found-rows behavior      | One fixed pool setting, but repository results remain independent of it            | Driver/pool configuration plus conformance probe                                     | `unsupported`         |
-| Foreign-key checks       | Enabled for normal runtime and conformance tests                                   | `SELECT @@SESSION.foreign_key_checks`                                                | `unsupported`         |
-| InnoDB page size         | Recorded before validating indexed key lengths                                     | `SELECT @@innodb_page_size`                                                          | `schema_incompatible` |
-
-The backend readiness report SHOULD expose the verified profile without credentials. It MUST NOT
-log connection strings or secrets.
-
-### 4.1 Initialization probe
-
-The adapter acceptance suite should run an equivalent of the following read-only probe on a newly
-leased connection:
-
-```sql
-SELECT
-  VERSION() AS server_version,
-  @@SESSION.sql_mode AS sql_mode,
-  @@SESSION.transaction_isolation AS transaction_isolation,
-  @@SESSION.time_zone AS time_zone,
-  @@SESSION.autocommit AS autocommit,
-  @@SESSION.foreign_key_checks AS foreign_key_checks,
-  @@character_set_client AS character_set_client,
-  @@character_set_connection AS character_set_connection,
-  @@character_set_results AS character_set_results,
-  @@innodb_page_size AS innodb_page_size;
-```
-
-A pool MUST apply and verify session settings on every newly created physical connection. Applying
-settings only to the first connection is insufficient.
-
-## 5. Normative semantic matrix
-
-### 5.0 Observable SQLite/MySQL difference summary
-
-This table is the review index for the detailed rules below. It distinguishes current or common
-backend behavior from the portable result the repository must expose. The MySQL column describes
-InnoDB under the verified session profile; it must not be read as permission to inherit an
-unverified server default.
-
-| Concern                | SQLite-shaped behavior                                                                                                                   | MySQL/InnoDB behavior                                                                                                                      | Required repository contract                                                                                                       |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
-| Text identity          | Binary comparison by default; current code opts into ASCII-oriented `NOCASE` for selected reads and sorts                                | Equality, uniqueness, and sort order follow the selected column/expression collation                                                       | Declare byte-exact identity separately from named insensitive lookup and display order                                             |
-| Nullable unique key    | Multiple SQL `NULL` values can pass a plain unique constraint                                                                            | Multiple SQL `NULL` values can pass a plain unique index                                                                                   | Enforce any "one logical null" invariant atomically outside a plain unique key                                                     |
-| Unordered/tied results | No total order without a complete `ORDER BY`                                                                                             | No total order without a complete `ORDER BY`                                                                                               | Define `NULL` position and a unique final tie-breaker for every portable list                                                      |
-| No-op update           | Driver change count reflects SQLite's statement behavior                                                                                 | Changed-row count differs from matched-row mode for identical assignments                                                                  | Return domain outcomes independently of raw affected-row counts                                                                    |
-| Conflict write         | `INSERT OR REPLACE` can delete then insert                                                                                               | Duplicate-key upsert updates one selected conflict                                                                                         | Classify every operation as insert-only, identity-preserving upsert, or replacement                                                |
-| Generated identity     | SQLite row IDs and driver-local last-insert state are connection-bound                                                                   | Generated IDs and last-insert state are connection-bound                                                                                   | Retrieve identity in the insert operation/lease and use stable idempotency identity on retry                                       |
-| JSON                   | Existing combo payloads are text and malformed legacy text can be observed                                                               | Native `JSON` validates and normalizes its representation                                                                                  | Choose text or typed JSON deliberately and compare the declared domain representation                                              |
-| Exact values/time      | Current modules commonly serialize JavaScript values and ISO UTC text                                                                    | Driver conversion can lose large integers/decimals; temporal types depend on type and session zone                                         | Fix exact representations, UTC policy, and precision across backends                                                               |
-| Concurrency/isolation  | Deferred transactions and a database-wide single-writer model shape conflicts; read visibility depends on transaction mode and WAL state | InnoDB defaults to `REPEATABLE READ`, uses MVCC snapshots for consistent reads, and permits concurrent writers on different locked records | Select and verify isolation, then test domain-visible reads, conflicts, and retry boundaries rather than relying on either default |
-| DDL/migrations         | SQLite migration sequences can be wrapped according to SQLite transaction rules                                                          | DDL commonly commits implicitly; one atomic DDL statement does not make a multi-step migration atomic                                      | Use distributed ownership, durable phase checkpoints, postcondition inspection, and readiness gating                               |
-
-### 5.1 Text identity, collation, and uniqueness
-
-MySQL equality and unique indexes use the effective collation of the indexed expression. A `_ci`
-collation is case-insensitive; an `_ai` collation is also accent-insensitive. SQLite's default text
-comparison and `COLLATE NOCASE` do not provide an equivalent Unicode contract.
-
-| Concern          | SQLite-shaped risk                                       | Required portable decision                                                  | MySQL implementation rule                                                           |
-| ---------------- | -------------------------------------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
-| IDs              | Text IDs can inherit an unintended collation             | IDs are byte-exact and case-sensitive                                       | Use an explicit binary collation or binary representation                           |
-| Combo names      | Exact lookup and insensitive fallback are separate today | Exact lookup remains exact; insensitive lookup is a named operation         | Exact and insensitive queries use explicit, different collations or normalized keys |
-| Unique names     | A server default can collapse case or accents            | The domain declares whether case/accent variants conflict                   | Unique index uses the declared collation, never the database default                |
-| Pattern text     | Pattern matching occurs in application code              | Stored pattern bytes round-trip unchanged                                   | Store with an explicit case-sensitive collation                                     |
-| User-facing sort | SQLite `NOCASE` order is not portable Unicode order      | List order is defined by a normalized sort key or explicit collation policy | Schema and query use the selected policy and a unique tie-breaker                   |
-
-Minimum probe:
-
-```sql
-CREATE TEMPORARY TABLE conformance_text (
-  id VARCHAR(64) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin PRIMARY KEY,
-  name VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_0900_ai_ci UNIQUE
-) ENGINE=InnoDB;
-
-INSERT INTO conformance_text (id, name) VALUES ('A', 'Résumé');
--- The next statement conflicts under utf8mb4_0900_ai_ci.
-INSERT INTO conformance_text (id, name) VALUES ('a', 'resume');
-```
-
-The harness MUST repeat the probe for the exact collation selected by the eventual schema; the
-example collation above is evidence, not an approval for combo names.
-
-### 5.2 `NULL`, missing rows, and nullable unique keys
-
-MySQL unique indexes permit multiple `NULL` values. SQLite does likewise for unique columns.
-However, neither behavior implements a domain invariant such as "only one active row may have no
-owner."
-
-Repository contracts MUST distinguish:
-
-- no row found;
-- a row found with a nullable field set to SQL `NULL`;
-- a JSON document containing JSON `null`;
-- a missing JSON member.
-
-Minimum probe:
-
-```sql
-CREATE TEMPORARY TABLE conformance_null (
-  id VARCHAR(64) PRIMARY KEY,
-  optional_key VARCHAR(64) NULL,
-  UNIQUE KEY uq_optional_key (optional_key)
-) ENGINE=InnoDB;
-
-INSERT INTO conformance_null VALUES ('one', NULL), ('two', NULL);
-SELECT COUNT(*) AS row_count FROM conformance_null;
--- Expected: 2.
-```
-
-If a domain allows at most one logical `NULL`, it MUST use an explicit atomic invariant rather than
-rely on a plain unique index.
-
-### 5.3 Ordering, ties, and pagination
-
-Without `ORDER BY`, result order is undefined. With a non-unique `ORDER BY`, tied rows still have an
-undefined relative order. Offset pagination can therefore duplicate or omit records if the complete
-order is not stable.
-
-Every portable list MUST specify:
-
-1. every user-visible sort expression;
-2. the position of `NULL` values;
-3. a unique final tie-breaker;
-4. the cursor comparison tuple, if cursor pagination is used;
-5. the snapshot/concurrency expectation across pages.
-
-For the proposed combo/mapping slice:
-
-```sql
--- Combo list contract candidate.
-ORDER BY sort_order ASC, normalized_name ASC, id ASC
-
--- Mapping list and resolution contract candidate.
-ORDER BY priority DESC, created_at ASC, id ASC
-```
-
-The exact `normalized_name` representation remains a contract decision. It MUST NOT be implemented
-by relying on an unspecified database default.
-
-For nullable values, use an explicit sort key rather than a backend default:
-
-```sql
-ORDER BY nullable_column IS NULL ASC, nullable_column ASC, id ASC
-```
-
-### 5.4 Update, no-op, delete, and affected rows
-
-MySQL `UPDATE` reports rows actually changed by default. With the C API found-rows connection flag,
-it reports rows matched. `INSERT ... ON DUPLICATE KEY UPDATE` reports 1 for insert, 2 for an actual
-update, and 0 for an update to identical values; the found-rows flag changes the last value to 1.
-These numbers MUST NOT become repository semantics.
-
-| Repository outcome | Required meaning                                       | Forbidden implementation shortcut             |
-| ------------------ | ------------------------------------------------------ | --------------------------------------------- |
-| `updated`          | Target existed and the operation's postcondition holds | `affectedRows > 0` alone                      |
-| `unchanged`        | Target existed and already satisfied the postcondition | Treating 0 changed rows as missing            |
-| `not_found`        | Target identity did not exist                          | Treating every 0 count as unchanged           |
-| `conflict`         | Compare/update version or invariant failed             | Returning generic `false`                     |
-| delete `true`      | A row existed and was deleted                          | Assuming a successful statement deleted a row |
-| delete `false`     | No row existed                                         | Throwing a backend-specific error             |
-
-Minimum probe, run once with each supported connection mode:
-
-```sql
-CREATE TEMPORARY TABLE conformance_update (
-  id VARCHAR(64) PRIMARY KEY,
-  value_text VARCHAR(64) NOT NULL,
-  version_no BIGINT NOT NULL
-) ENGINE=InnoDB;
-
-INSERT INTO conformance_update VALUES ('row', 'same', 1);
-UPDATE conformance_update SET value_text = 'same' WHERE id = 'row';
-UPDATE conformance_update SET value_text = 'changed' WHERE id = 'row';
-UPDATE conformance_update SET value_text = 'missing' WHERE id = 'missing';
-```
-
-The harness asserts repository results and final rows, not raw driver counts. A versioned
-compare/update SHOULD use a predicate such as `WHERE id = ? AND version_no = ?`, then distinguish a
-missing identity from a stale version according to the domain contract.
-
-### 5.5 Insert, upsert, and replacement
-
-SQLite `INSERT OR REPLACE` deletes rows that conflict with a unique or primary key before inserting
-the new row. MySQL `INSERT ... ON DUPLICATE KEY UPDATE` updates one conflicting row. The two forms
-differ in foreign-key cascades, triggers, omitted columns, IDs, timestamps, and affected-row counts.
-
-Every write method MUST be classified as exactly one of:
-
-1. **insert-only:** duplicate identity returns `unique_violation`;
-2. **identity-preserving upsert:** duplicate identity updates an explicit allowlist of mutable fields;
-3. **replacement:** old identity is deleted and a new row is inserted, with cascade effects included
-   in the contract.
-
-A generic helper MUST NOT choose among these behaviors based on SQL convenience.
-
-Minimum difference probe. This uses ordinary InnoDB tables because MySQL temporary tables cannot
-serve as the parent/child foreign-key fixture. Run it in an isolated conformance schema; cleanup is
-included so the probe is repeatable:
-
-```sql
-DROP TABLE IF EXISTS conformance_child;
-DROP TABLE IF EXISTS conformance_parent;
-
-CREATE TABLE conformance_parent (
-  id VARCHAR(64) PRIMARY KEY,
-  immutable_value VARCHAR(64) NOT NULL,
-  mutable_value VARCHAR(64) NOT NULL
-) ENGINE=InnoDB;
-
-CREATE TABLE conformance_child (
-  id VARCHAR(64) PRIMARY KEY,
-  parent_id VARCHAR(64) NOT NULL,
-  CONSTRAINT fk_conformance_child_parent
-    FOREIGN KEY (parent_id) REFERENCES conformance_parent(id) ON DELETE CASCADE
-) ENGINE=InnoDB;
-
-INSERT INTO conformance_parent VALUES ('p', 'keep', 'old');
-INSERT INTO conformance_child VALUES ('c', 'p');
-INSERT INTO conformance_parent (id, immutable_value, mutable_value)
-VALUES ('p', 'replacement', 'new')
-ON DUPLICATE KEY UPDATE mutable_value = VALUES(mutable_value);
-
-SELECT immutable_value, mutable_value FROM conformance_parent WHERE id = 'p';
-SELECT COUNT(*) AS child_count FROM conformance_child WHERE parent_id = 'p';
--- Expected: immutable_value='keep', mutable_value='new', child_count=1.
-
-DROP TABLE conformance_child;
-DROP TABLE conformance_parent;
-```
-
-The `VALUES(mutable_value)` form is used here because the target remains MySQL 8.0 as a family and
-no minimum 8.0 patch release has been approved. It is deprecated in later MySQL 8.0 releases, so an
-adapter that establishes a newer minimum MAY use the supported row-alias form instead. The harness
-asserts identity-preserving behavior, not either SQL spelling.
-
-Tables with multiple unique indexes require special care because a duplicate can select an
-unexpected conflicting row. Portable upsert schema SHOULD have one unambiguous conflict identity.
-
-### 5.6 Unicode and index-size constraints
-
-`utf8mb4` uses up to four bytes per character. InnoDB's maximum index key is 3072 bytes for common
-`DYNAMIC` or `COMPRESSED` row formats with a 16 KiB page, and is lower for smaller page sizes or
-legacy row formats. A prefix unique index is not equivalent to full-value uniqueness.
-
-Schema acceptance MUST:
-
-- set bounded lengths for all indexed identity strings;
-- calculate the worst-case byte length of every composite index;
-- verify the actual page size and row format;
-- reject a prefix unique index for a full-identity contract;
-- test maximum-length non-ASCII values before migration is accepted;
-- classify an incompatible definition as `schema_incompatible`, not `unique_violation`.
-
-Example boundary probe for a 16 KiB/DYNAMIC profile:
-
-```sql
-CREATE TEMPORARY TABLE conformance_index (
-  value_text VARCHAR(768) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
-  UNIQUE KEY uq_value_text (value_text)
-) ENGINE=InnoDB ROW_FORMAT=DYNAMIC;
-```
-
-The exact accepted length MUST be derived from all key parts and the verified deployment profile;
-this example is deliberately near a physical boundary and is not a proposed production column.
-
-### 5.7 IDs and connection-local state
-
-The current combo and mapping modules generate UUIDs in the application. A MySQL implementation
-SHOULD preserve this strategy for those domains.
-
-If another domain uses a database-generated incrementing ID, the adapter MUST observe these rules:
-
-- ID retrieval is part of the same driver operation and physical connection as the insert;
-- callers never issue a later connection-level `LAST_INSERT_ID()` query;
-- multi-row inserts define whether one ID or all IDs are returned;
-- an error or rollback makes a previously observed `LAST_INSERT_ID()` unsuitable as proof of commit;
-- retries use a stable domain idempotency key;
-- upsert defines whether it returns an existing or newly generated identity.
-
-MySQL documents `LAST_INSERT_ID()` as per-connection state and leaves it undefined after some errors
-or error-driven rollbacks. Pool leases are therefore part of correctness, not merely performance.
-
-### 5.8 JSON representation
-
-Current combo data is JSON text, and malformed JSON is observable: combo reads can skip malformed
-rows and mapping resolution skips malformed combo payloads. Switching the MySQL column directly to
-native `JSON` would reject malformed rows at write/import time and normalize duplicate keys,
-whitespace, and key order.
-
-Before choosing `LONGTEXT` or `JSON`, the combo contract MUST decide:
-
-- whether malformed stored payloads remain representable for compatibility tests;
-- whether equality is structural or byte-for-byte;
-- whether duplicate object keys are rejected before persistence;
-- whether serialization order is stable and application-owned;
-- which fields are duplicated into typed columns and which representation is authoritative.
-
-For the first slice, an identity-preserving migration SHOULD keep application serialization as the
-domain boundary. If native `JSON` is selected, imports MUST parse and validate before writing, and
-tests MUST compare parsed domain values rather than raw JSON text.
-
-Minimum normalization probe:
-
-```sql
-CREATE TEMPORARY TABLE conformance_json (id VARCHAR(64) PRIMARY KEY, payload JSON) ENGINE=InnoDB;
-INSERT INTO conformance_json VALUES ('j', '{"b": 2, "a": 1, "a": 3}');
-SELECT payload FROM conformance_json WHERE id = 'j';
--- The value is normalized; original whitespace/key duplication is not preserved.
-```
-
-### 5.9 Exact numerics and timestamps
-
-| Type        | Risk                                                  | Required contract                                                       |
-| ----------- | ----------------------------------------------------- | ----------------------------------------------------------------------- |
-| `BIGINT`    | Values can exceed JavaScript's safe integer range     | Return a string or validated bigint representation across every backend |
-| `DECIMAL`   | Driver options may return strings or lossy numbers    | Fix precision/scale and use an exact domain representation              |
-| `TIMESTAMP` | Session time zone conversion and fractional precision | Force UTC session time zone and specify fractional precision            |
-| `DATETIME`  | No intrinsic time zone                                | Use only for explicitly zone-free civil time                            |
-| ISO text    | Lexical ordering depends on one canonical format      | Validate UTC suffix and exact precision before persistence              |
-
-Combo and mapping timestamps are currently application-generated ISO strings. The first slice SHOULD
-preserve their exact domain format rather than introducing server-generated local time.
-
-### 5.10 Transaction isolation and observable concurrency
-
-MySQL InnoDB uses `REPEATABLE READ` as its default isolation level. Within an explicit transaction,
-its consistent non-locking reads normally establish and reuse an MVCC snapshot, while locking reads
-and writes inspect and lock current index records or ranges. SQLite instead combines snapshot/read
-transaction behavior with a database-wide single-writer model; transaction mode and WAL state affect
-when a writer is admitted and when a read transaction can be upgraded. These mechanisms are not
-interchangeable even when a simple CRUD fixture produces the same final row.
-
-The backend profile MUST select and verify an isolation level rather than silently accept either
-backend's default. The repository contract MUST then define observable results for each atomic
-operation. It MUST NOT promise the implementation mechanism itself, such as gap locks or a
-SQLite-wide writer lock.
-
-| Scenario                          | SQLite-shaped risk                                                                      | InnoDB `REPEATABLE READ` risk                                                                              | Required conformance decision                                                                              |
-| --------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
-| Two reads in one transaction      | Snapshot timing depends on when the read transaction begins and the active journal mode | Consistent reads normally reuse the transaction's first established read view                              | State whether the operation requires one stable snapshot or deliberately performs a current read           |
-| Range read plus concurrent insert | A concurrent writer may be serialized by SQLite's writer admission rules                | A plain consistent read can retain its snapshot; a locking range read can lock index gaps                  | Define whether a later read sees the insert and whether the operation requires a locking predicate         |
-| Read-modify-write                 | Single-writer serialization can mask an unsafe application sequence                     | Concurrent transactions can read the same value and later contend or overwrite without a version predicate | Require compare/update, a locking read, or another explicit invariant; never rely on backend serialization |
-| Writers touching different rows   | SQLite still admits only one writer at a time                                           | InnoDB can execute both until their record/range locks conflict                                            | Do not infer portable throughput or lock order; assert only atomic effects and classified conflicts        |
-| Pagination across transactions    | Separate page reads can observe different committed states                              | Separate autocommit reads get separate views; one transaction may retain one view                          | Declare snapshot pagination or documented live pagination and test that policy                             |
-| Retry after conflict              | Busy/locked outcomes and transaction upgrade failures are SQLite-shaped                 | Deadlocks and lock timeouts have different rollback scopes                                                 | Normalize the error, discard the failed context, and retry the complete idempotent operation only          |
-
-Minimum two-connection visibility probe for the selected MySQL profile:
-
-```text
-Connection A                                      Connection B
-SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
-START TRANSACTION;
-SELECT value_no FROM conformance_isolation
-  WHERE id = 1;  -- establishes read view: 0
-                                                  START TRANSACTION;
-                                                  UPDATE conformance_isolation
-                                                    SET value_no = 1 WHERE id = 1;
-                                                  COMMIT;
-SELECT value_no FROM conformance_isolation
-  WHERE id = 1;  -- same consistent-read view: 0
-COMMIT;
-SELECT value_no FROM conformance_isolation
-  WHERE id = 1;  -- new transaction/view: 1
-```
-
-The shared harness MUST NOT assert that every backend reproduces this internal sequence. It must use
-it to prove that the chosen repository operation either requests a stable snapshot explicitly or
-avoids depending on repeat-read visibility. If an operation uses a current/locking read, that choice
-and its conflict behavior need a separate test.
-
-## 6. Transactions, failures, and retry policy
-
-### 6.1 Transaction states
-
-The backend contract should expose only opaque transaction contexts, but its implementation must
-maintain the following lifecycle:
-
-```text
-idle
-  -> active
-      -> committed
-      -> rolled_back
-      -> failed_statement -> rolled_back
-      -> failed_transaction -> rolled_back
-      -> outcome_unknown -> reconciled | escalated
-```
-
-A context in `committed`, `rolled_back`, `failed_transaction`, or `outcome_unknown` MUST reject new
-repository work. A context with a failed statement SHOULD be explicitly rolled back before its
-connection returns to the pool, even when MySQL would technically permit more statements.
-
-### 6.2 Error classification matrix
-
-Numeric codes and SQLSTATE values below are MySQL 8.0 server signals. A Node.js driver can also
-produce transport-specific codes; those MUST be normalized without leaking raw messages to callers.
-
-| Condition                      | MySQL signal                           | Rollback scope                                    | Portable class           | Retry policy                                                   |
-| ------------------------------ | -------------------------------------- | ------------------------------------------------- | ------------------------ | -------------------------------------------------------------- |
-| Duplicate key                  | `1062`, SQLSTATE `23000`               | Statement                                         | `unique_violation`       | No, unless contract defines idempotent create                  |
-| Missing referenced parent      | `1452`, SQLSTATE `23000`               | Statement                                         | `foreign_key_violation`  | No                                                             |
-| Parent still referenced        | `1451`, SQLSTATE `23000`               | Statement                                         | `foreign_key_violation`  | No                                                             |
-| Deadlock victim                | `1213`, SQLSTATE `40001`               | Entire transaction                                | `transaction_conflict`   | Retry whole atomic operation                                   |
-| Lock wait timeout              | `1205`, SQLSTATE `HY000`               | Statement by default; server option can change it | `lock_timeout`           | Roll back explicitly, then retry whole operation if idempotent |
-| Invalid JSON text              | `3140`, SQLSTATE `22032`               | Statement                                         | `invalid_data`           | No                                                             |
-| Data too long                  | `1406`, SQLSTATE `22001`               | Statement                                         | `invalid_data`           | No                                                             |
-| Check constraint               | `3819`, SQLSTATE `HY000`               | Statement                                         | `constraint_violation`   | No                                                             |
-| Server gone before request     | Driver/server transport signal         | No operation or unknown                           | `unavailable`            | Retry only if operation definitely was not sent                |
-| Connection lost during request | Driver transport signal                | Unknown                                           | `outcome_unknown`        | Reconcile by idempotency key; do not blind retry               |
-| Pool acquisition timeout       | Driver/pool signal                     | None                                              | `unavailable`            | Bounded retry outside transaction                              |
-| Unsupported profile            | Initialization probe mismatch          | None                                              | `unsupported`            | No; fail readiness                                             |
-| Migration lock timeout         | Named-lock acquisition returns timeout | None                                              | `migration_lock_timeout` | Wait/back off according to startup policy                      |
-| Migration lock error           | Named-lock acquisition returns error   | None                                              | `migration_lock_failed`  | No blind retry; inspect connection state                       |
-
-The adapter MUST classify by structured code and SQLSTATE where available, never by localized message
-text. Public HTTP/SSE/MCP responses must still pass through the repository's existing sanitized error
-helpers.
-
-### 6.3 Retry rules
-
-A retryable classification does not automatically make an operation safe to retry.
-
-A retry loop MUST:
-
-1. own the entire repository atomic operation;
-2. discard the failed transaction context;
-3. acquire a valid connection and begin a new transaction;
-4. preserve a stable operation or entity identity;
-5. use bounded attempts with jitter;
-6. stop on non-retryable classifications;
-7. reconcile `outcome_unknown` before issuing another write;
-8. emit structured diagnostics without credentials or raw SQL values.
-
-MySQL explicitly recommends retrying the entire transaction after a deadlock. A lock wait timeout
-rolls back only the current statement by default, so explicit rollback is required to make the retry
-boundary independent of server configuration.
-
-### 6.4 Reproducible two-connection deadlock probe
-
-Use two physical connections, not two logical operations that might share one pool connection:
-
-```sql
-CREATE TABLE conformance_deadlock (
-  id INT PRIMARY KEY,
-  value_no INT NOT NULL
-) ENGINE=InnoDB;
-INSERT INTO conformance_deadlock VALUES (1, 0), (2, 0);
-```
-
-```text
-Connection A                         Connection B
-START TRANSACTION;                   START TRANSACTION;
-UPDATE ... WHERE id = 1;             UPDATE ... WHERE id = 2;
-UPDATE ... WHERE id = 2;             UPDATE ... WHERE id = 1;
-```
-
-Exactly one transaction should become the deadlock victim. The harness asserts that the victim is
-classified as retryable, its whole transaction is retried with a new context, both logical updates
-occur once, and no partial result remains.
-
-## 7. Migration ownership and DDL recovery
-
-### 7.1 Why a normal transaction is insufficient
-
-MySQL DDL statements commonly commit the current transaction implicitly before execution and often
-afterward. Atomic DDL protects one supported DDL statement; it does not make a sequence of DDL,
-data backfill, and schema-history updates one user transaction.
-
-A MySQL migration runner therefore MUST model a migration as recoverable phases:
-
-```text
-lock acquired
-  -> current schema inspected
-  -> intent/checkpoint recorded
-  -> DDL phase applied and verified
-  -> data phase applied in bounded transactions
-  -> postconditions verified
-  -> logical milestone recorded
-  -> readiness allowed
-  -> lock released
-```
-
-A process crash at any arrow must have a deterministic resume or stop condition.
-
-### 7.2 Ownership alternatives
-
-| Option                          | Strengths                                                                | Failure modes                                                                             | Decision                                                               |
-| ------------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| Process-local mutex             | Simple and useful for one process                                        | Does not coordinate replicas                                                              | Rejected for external-backend migration ownership                      |
-| Row lock held in a transaction  | Uses normal InnoDB locking                                               | DDL implicit commit releases transaction ownership                                        | Rejected as the sole DDL migration lock                                |
-| Lease row with owner and expiry | Survives pooled connections and can support takeover                     | Requires clock/expiry/fencing design; stale owner may continue                            | Candidate for scheduled jobs, not first migration mechanism            |
-| MySQL named lock                | Server-wide, exclusive, tied to physical session, released on disconnect | Must pin one connection; not transaction-scoped; one-server scope; undefined waiter order | Recommended first MySQL migration mutex, combined with durable history |
-| External coordinator            | Can coordinate across database topologies                                | Adds an operational dependency outside the database contract                              | Deferred unless deployment topology requires it                        |
-
-### 7.3 Recommended first mechanism
-
-For a single writable MySQL primary, the migration runner SHOULD:
-
-1. lease and pin one physical connection;
-2. acquire one application-and-database-specific named lock of at most 64 characters;
-3. distinguish acquired (`1`), timeout (`0`), and error (`NULL`);
-4. inspect a durable migration-history table after acquiring the lock;
-5. execute idempotent physical phases with explicit postcondition checks;
-6. record completion only after all postconditions pass;
-7. release the named lock explicitly in `finally`;
-8. close/discard the pinned connection if release cannot be confirmed.
-
-Named locks are released when the session ends, not on commit or rollback. They are server-wide on one
-`mysqld`; topology and failover behavior must be validated before active-active support is advertised.
-A durable history/checkpoint table remains necessary because lock ownership alone says nothing about
-partially completed DDL.
-
-### 7.4 Migration failure matrix
-
-| Injection point                 | Required durable evidence                     | Restart behavior                    | Readiness                                     |
-| ------------------------------- | --------------------------------------------- | ----------------------------------- | --------------------------------------------- |
-| Before lock                     | No intent                                     | Retry lock acquisition              | Not ready while required migration is pending |
-| After lock, before intent       | No schema change                              | Reinspect and restart               | Not ready                                     |
-| After DDL, before checkpoint    | Schema postcondition reveals DDL applied      | Mark/continue only after validation | Not ready                                     |
-| During data backfill            | Bounded checkpoint identifies completed range | Resume from verified checkpoint     | Not ready                                     |
-| After data, before milestone    | Postconditions prove completion               | Record milestone idempotently       | Not ready until recorded                      |
-| After milestone, before release | History proves complete                       | New owner verifies and proceeds     | Ready if all required milestones pass         |
-
-## 8. SQLite-to-MySQL migration validation
-
-An offline migration tool is required before database switching can be advertised. For each migrated
-domain it MUST provide a dry run and a post-import report.
-
-### 8.1 Preflight
-
-- verify supported SQLite and MySQL schema milestones;
-- validate every source JSON payload according to the chosen target representation;
-- detect names that collide under the target collation;
-- validate UTF-8 and maximum indexed byte lengths;
-- detect orphaned foreign keys even if the source connection had checks disabled;
-- validate timestamps and numeric ranges;
-- count source rows by table and logical domain;
-- refuse to mutate either database during dry run.
-
-### 8.2 Import
-
-- preserve application-generated IDs;
-- use deterministic batches and checkpoints;
-- import parents before children;
-- do not use replacement semantics to hide conflicts;
-- classify every rejected row with a stable reason;
-- keep encrypted credential ciphertext opaque and never log it;
-- stop on an unclassified difference.
-
-### 8.3 Postconditions
-
-- row counts match for every migrated table;
-- identity sets match exactly;
-- foreign-key orphan counts are zero;
-- canonical domain digests match for JSON-backed records;
-- list ordering and mapping resolution produce the same results;
-- a second dry run reports no pending changes;
-- SQLite remains unchanged and available for operator rollback until cutover is accepted.
-
-## 9. Backend-neutral conformance catalog
-
-Each test below runs the same repository fixture against SQLite and MySQL. MySQL-specific probes may
-assert error metadata internally, but the shared assertion compares only domain results and durable
-state.
-
-### 9.1 Core CRUD and representation
-
-| Test name                                     | Fixture/action                                                    | Required assertion                                     |
-| --------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------ |
-| `create_round_trips_domain_values`            | Create Unicode, nullable, JSON, and timestamp fields              | Parsed domain object equals normalized input           |
-| `find_missing_distinguishes_absent_from_null` | Read an absent ID and a present nullable row                      | Results are distinct                                   |
-| `update_missing_returns_not_found`            | Update an absent ID                                               | Stable `not_found` result                              |
-| `delete_is_idempotent_as_declared`            | Delete the same ID twice                                          | First and second results match the repository contract |
-| `json_round_trips_structurally`               | Write equivalent JSON with different whitespace/order             | Parsed values are equal; raw text is not asserted      |
-| `timestamp_round_trips_in_utc`                | Change MySQL session default before leasing a verified connection | Domain serialization remains canonical UTC             |
-| `decimal_round_trips_without_float_loss`      | Write precision/scale boundaries                                  | Exact representation is unchanged                      |
-| `large_integer_does_not_cross_number_lossily` | Write beyond JavaScript safe integer range                        | String/bigint domain representation is exact           |
-
-### 9.2 Identity and collation
-
-| Test name                                      | Fixture/action                                             | Required assertion                                         |
-| ---------------------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------- |
-| `id_is_byte_exact`                             | Create IDs differing only by case                          | Both remain distinct if the ID contract is binary          |
-| `exact_name_lookup_is_case_sensitive`          | Store `MASTER-LIGHT`, query exact lowercase                | Exact lookup misses                                        |
-| `insensitive_name_lookup_uses_declared_policy` | Query the same row through the named insensitive operation | One deterministic row is returned                          |
-| `unique_name_case_policy_is_explicit`          | Insert case variants                                       | Result matches the selected name policy on both backends   |
-| `unique_name_accent_policy_is_explicit`        | Insert accent variants                                     | Result matches the selected policy                         |
-| `unique_violation_is_classified`               | Concurrently create one identity                           | One wins; loser is `unique_violation` without backend text |
-| `nullable_unique_policy_is_explicit`           | Insert two `NULL` logical keys                             | Result matches domain rule, not accidental index behavior  |
-
-### 9.3 Ordering and pagination
-
-| Test name                                           | Fixture/action                                 | Required assertion                                     |
-| --------------------------------------------------- | ---------------------------------------------- | ------------------------------------------------------ |
-| `list_uses_unique_final_tiebreaker`                 | Insert rows with identical primary sort values | Repeated list order is identical and ID-ordered        |
-| `pagination_has_no_gaps_or_duplicates`              | Traverse small pages across tied rows          | Union equals full ID set; page intersections are empty |
-| `nullable_sort_position_is_fixed`                   | Mix `NULL` and non-`NULL` values               | `NULL` appears at the contract-defined end             |
-| `cursor_predicate_matches_sort_tuple`               | Page forward through mixed sort keys           | Every row appears exactly once in declared order       |
-| `concurrent_insert_pagination_behavior_is_declared` | Insert between page reads                      | Result matches snapshot or documented live-page policy |
-
-### 9.4 Writes and affected rows
-
-| Test name                                   | Fixture/action                             | Required assertion                                 |
-| ------------------------------------------- | ------------------------------------------ | -------------------------------------------------- |
-| `same_value_update_is_not_missing`          | Update an existing row to identical values | `unchanged` or declared success, never `not_found` |
-| `same_value_result_ignores_found_rows_mode` | Run fixture with both connection modes     | Domain result is identical                         |
-| `compare_update_detects_stale_version`      | Two writers use one old version            | One succeeds; one returns `conflict`               |
-| `batch_count_uses_contract_definition`      | Mix changed and unchanged matches          | Count means the same thing on both backends        |
-| `upsert_preserves_identity_and_children`    | Upsert parent with a child row             | ID, immutable fields, and child survive            |
-| `insert_only_never_silently_updates`        | Repeat insert-only identity                | Second call is `unique_violation`                  |
-
-### 9.5 Transactions, isolation, and failure injection
-
-| Test name                                       | Fixture/action                                                    | Required assertion                                                     |
-| ----------------------------------------------- | ----------------------------------------------------------------- | ---------------------------------------------------------------------- |
-| `related_changes_commit_atomically`             | Update parent and children                                        | All postconditions commit together                                     |
-| `related_changes_roll_back_atomically`          | Inject a child constraint failure                                 | All tables equal pre-operation state                                   |
-| `stable_snapshot_behavior_is_declared`          | Read, commit a concurrent update, then read in the same operation | Result follows the operation's declared snapshot/current-read policy   |
-| `range_insert_visibility_is_declared`           | Read a range while another transaction inserts a matching row     | Later visibility matches the declared snapshot/live policy             |
-| `read_modify_write_prevents_lost_update`        | Two transactions read one version and attempt distinct updates    | One declared winner; loser conflicts/retries without overwriting       |
-| `independent_writers_preserve_atomic_effects`   | Two transactions update different identities concurrently         | Both logical effects commit; no contract depends on backend lock order |
-| `deadlock_retries_whole_operation`              | Two physical connections lock in opposite order                   | One victim; final logical effect occurs once                           |
-| `lock_timeout_discards_context`                 | Hold a row lock past timeout                                      | Explicit rollback; old context rejects work                            |
-| `duplicate_and_foreign_key_errors_are_distinct` | Trigger each constraint                                           | Stable distinct classes                                                |
-| `disconnect_before_send_is_unavailable`         | Fail connection before dispatch                                   | Safe bounded retry is permitted                                        |
-| `disconnect_during_commit_is_outcome_unknown`   | Drop connection at commit boundary                                | No blind retry; reconciliation is required                             |
-| `retry_uses_stable_operation_identity`          | Fail first attempt after durable write                            | At most one logical effect exists                                      |
-
-### 9.6 Migration and readiness
-
-| Test name                               | Fixture/action                              | Required assertion                                 |
-| --------------------------------------- | ------------------------------------------- | -------------------------------------------------- |
-| `only_one_instance_owns_migration`      | Two backend instances acquire one name      | Exactly one executes migration phases              |
-| `lock_timeout_is_not_reported_as_ready` | Hold migration lock from another connection | Startup waits/fails with classified state          |
-| `disconnect_releases_named_lock`        | Terminate owner connection                  | Another instance can acquire and reinspect         |
-| `ddl_checkpoint_recovers_after_crash`   | Stop after DDL before history update        | Restart detects postcondition and continues safely |
-| `backfill_resumes_without_duplication`  | Stop between deterministic batches          | Completed rows are neither skipped nor duplicated  |
-| `partial_migration_blocks_readiness`    | Leave required milestone incomplete         | Health may be alive; readiness is false            |
-| `completed_history_is_idempotent`       | Start against fully migrated schema         | No DDL/data mutation occurs                        |
-
-## 10. First-slice acceptance profile: combos and model mappings
-
-This section specializes the general catalog for the candidate first slice discussed in #8075 and
-implemented experimentally in Draft PR #8757. It does not approve that runtime PR.
-
-### 10.1 Contract decisions required before adapter code
-
-| Decision              | Current evidence                                       | Required resolution                                                                         |
-| --------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
-| Combo ID              | Application UUID                                       | Preserve as byte-exact text/binary identity                                                 |
-| Combo name uniqueness | SQLite unique name; exact and insensitive reads differ | Select explicit uniqueness collation independently from insensitive fallback                |
-| Combo list            | `sort_order`, then `name NOCASE`                       | Add `id` as final tie-breaker and define Unicode name order                                 |
-| Next sort order       | `MAX(sort_order) + 1`                                  | Replace race-prone read-then-insert with an atomic allocation or retryable unique invariant |
-| Reorder               | One SQLite transaction updates all parseable rows      | Define concurrent reorder serialization and all-or-nothing behavior                         |
-| Corrupt combo JSON    | Reads/resolution skip malformed payloads               | Decide whether MySQL schema can represent malformed legacy rows during migration            |
-| Mapping order         | `priority DESC, created_at ASC`                        | Add `id ASC` final tie-breaker                                                              |
-| Mapping delete        | Boolean from affected rows                             | Preserve `true` then `false` behavior independent of found-rows mode                        |
-| Combo delete          | Foreign key cascade removes mappings                   | Preserve one-operation atomic cascade                                                       |
-| Timestamps            | Application ISO strings                                | Preserve canonical UTC text or define an exact typed conversion                             |
-
-### 10.2 Required combo fixtures
-
-The shared fixture MUST include:
-
-- combo names `Alpha`, `alpha`, `Résumé`, and `resume` to exercise selected collation policy;
-- three combos with the same requested `sortOrder` to exercise the unique final order;
-- one missing ID for update and delete results;
-- one payload with explicit JSON `null` and one with a missing member;
-- one intentionally malformed legacy payload if compatibility requires it;
-- mappings with identical `priority` and `createdAt` but different IDs;
-- enabled, disabled, inactive-target, and corrupt-target mappings;
-- one combo with at least two dependent mappings for cascade verification.
-
-### 10.3 Required combo assertions
-
-A MySQL implementation cannot claim the first slice complete until the shared harness proves:
-
-1. application UUIDs and ISO timestamps round-trip unchanged;
-2. exact and insensitive combo-name lookups remain distinct operations;
-3. uniqueness follows the approved name policy, not server defaults;
-4. combo and mapping lists have a total deterministic order;
-5. every offset page is a contiguous slice of that order;
-6. update of a missing combo/mapping returns `null`;
-7. first delete returns `true`, repeated delete returns `false`;
-8. reorder filters unknown/duplicate requested IDs exactly as the accepted contract specifies;
-9. reorder either commits every intended row or none;
-10. mapping resolution uses the deterministic order and skips disabled, inactive, and malformed targets;
-11. deleting a combo atomically removes all dependent mappings;
-12. errors are classified without raw MySQL messages;
-13. SQLite starts without loading a MySQL dependency;
-14. no external-backend support is advertised by the presence of this slice alone.
-
-### 10.4 Concurrency probes specific to the slice
-
-#### Concurrent combo creation
-
-Two connections create different UUIDs with the same contract-equivalent name. Exactly one succeeds;
-the other receives `unique_violation`. If case/accent variants are allowed by the approved policy,
-both succeed and exact lookup returns the correct identity.
-
-#### Concurrent sort allocation
-
-Two connections create combos without an explicit sort order. The final values MUST follow the
-contract without duplicates caused by both transactions reading the same `MAX(sort_order)`. The
-implementation may serialize allocation, use a separate sequence, or retry a protected invariant;
-the contract must not require one specific SQL mechanism.
-
-#### Concurrent reorder
-
-Two connections reorder the same set in opposite orders. The accepted outcome MUST be one complete
-order or the other, never a mixed sequence or mismatched JSON/column `sortOrder`. The loser may wait,
-return conflict, or retry according to the approved contract.
-
-#### Delete versus mapping creation
-
-One connection deletes a combo while another creates a mapping to it. The final state MUST be either
-an existing combo with a valid mapping or no combo and no mapping. An orphan mapping is forbidden.
-
-## 11. Implementation gate checklist
-
-A MySQL adapter PR for any domain MUST NOT start until reviewers can answer all applicable items:
-
-- [ ] Identity, case, accent, and collation semantics are explicit.
-- [ ] Every list has a complete order, `NULL` position, and unique tie-breaker.
-- [ ] Missing, unchanged, conflict, and delete results are distinguishable.
-- [ ] Every write is classified as insert-only, identity-preserving upsert, or replacement.
-- [ ] ID generation and idempotency ownership are explicit.
-- [ ] JSON and temporal representations are selected with migration compatibility in mind.
-- [ ] Error codes map to the backend-neutral taxonomy.
-- [ ] Retry ownership and maximum scope are explicit.
-- [ ] Migration mutex, durable checkpoints, and readiness rules are approved.
-- [ ] SQLite and MySQL fixtures run through one behavior harness.
-- [ ] Offline migration preflight and postconditions exist before cutover is advertised.
-- [ ] SQLite remains the zero-configuration default and clean startup path.
-
-## 12. Reference sources
-
-### 12.1 OmniRoute sources
-
-- `docs/architecture/persistence-backend-boundary.md`
-- `docs/architecture/sqlite-coupling-inventory.md`
-- `src/lib/db/combos.ts`
-- `src/lib/db/modelComboMappings.ts`
-- `src/lib/db/migrations/001_initial_schema.sql`
-- `src/lib/db/migrations/010_model_combo_mappings.sql`
-- `src/lib/db/migrations/020_combo_sort_order.sql`
-
-### 12.2 MySQL 8.0 reference manual
-
-- [Character sets and collations](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/charset.html)
-- [CREATE TABLE](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/create-table.html)
-- [UPDATE](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/update.html)
-- [INSERT ... ON DUPLICATE KEY UPDATE](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/insert-on-duplicate.html)
-- [Information functions](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/information-functions.html)
-- [The JSON data type](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/json.html)
-- [InnoDB transaction isolation](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/innodb-transaction-isolation-levels.html)
-- [InnoDB error handling](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/innodb-error-handling.html)
-- [Handling deadlocks](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/innodb-deadlocks-handling.html)
-- [Statements that cause an implicit commit](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/implicit-commit.html)
-- [Locking functions](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/locking-functions.html)
-- [InnoDB limits](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/innodb-limits.html)
-
-### 12.3 SQLite references
-
-- [ON CONFLICT](https://sqlite.org/lang_conflict.html)
-- [`NULL` handling](https://sqlite.org/nulls.html)
-- [Transactions](https://sqlite.org/lang_transaction.html)
-- [SELECT and ordering](https://sqlite.org/lang_select.html#orderby)
-
-## 13. Open decisions
-
-This specification deliberately leaves the following decisions to the accepted first-slice design:
-
-1. the exact collation and normalization policy for combo names;
-2. the typed or text representation of combo JSON in MySQL;
-3. the repository result type for an existing same-value update;
-4. the isolation level selected by the backend profile;
-5. the concurrency mechanism for sort-order allocation and reorder;
-6. the physical MySQL migration schema and durable checkpoint format;
-7. the exact retry budget and backoff policy;
-8. the topology boundary within which a MySQL named migration lock is sufficient.
-
-These are not adapter implementation details. Each changes observable behavior or operational
-correctness and therefore requires explicit review before runtime support proceeds.

docs/architecture/sqlite-coupling-inventory.md

@@ -1,226 +0,0 @@
----
-title: "SQLite coupling inventory"
-status: measured-snapshot
-lastUpdated: 2026-07-23
----
-
-# SQLite coupling inventory
-
-- **Tracking issue:** [#8075](https://github.com/diegosouzapw/OmniRoute/issues/8075)
-- **Snapshot revision:** `9a3b605f3420ae3ab08bd93d6443034f03a1bcbc`
-- **Scanned-corpus SHA-256:** `72334620a7a18a42bcede1643fb2fdf95da6eae9ffa66a891ae14ed633ad43f6`
-- **Purpose:** Measure the current persistence cut lines before proposing repository interfaces
-- **Runtime impact:** None; this document and its audit script do not change database behavior
-
-## How to reproduce
-
-From the repository root:
-
-```bash
-node scripts/check/audit-sqlite-coupling.mjs
-node scripts/check/audit-sqlite-coupling.mjs --json
-node --test scripts/check/audit-sqlite-coupling.test.mjs
-```
-
-The script reads tracked files from Git, scans non-test source under `src/`, `open-sse/`,
-`electron/`, and `bin/`, and scans migration SQL under `src/lib/db/migrations/`. It excludes the
-top-level test tree, co-located test directories, test/spec source files, and paths outside those
-configured source roots (including documentation and scripts).
-
-The script refuses to run if tracked files in those source roots differ from `HEAD`. It reports
-both the audit-tool revision and a SHA-256 over the ordered path/content corpus. The snapshot above
-was taken from the listed source revision; this PR changes only excluded documentation and script
-paths, so rerunning from the clean PR branch produces the same corpus digest.
-
-This is a **lexical inventory**, not a TypeScript or SQL semantic analysis:
-
-- counts are occurrences of defined patterns, not counts of distinct SQL statements;
-- adapter-call and direct-singleton patterns mask comments and literal contents first;
-- template-literal contents, including embedded expressions, are excluded from those code-syntax
-  counts;
-- the lightweight masker is not a JavaScript parser, so unusual regular-expression literal syntax
-  can still require manual review;
-- comments and string literals can contribute to dialect-signal counts, which intentionally search
-  raw text for embedded SQL;
-- a `.prepare()` match outside `src/lib/db/` is a review lead, not proof that the call should move;
-- calls hidden behind a differently named wrapper may not be counted;
-- file counts are deduplicated, while occurrence counts are not.
-
-The JSON output includes every matching path so reviewers can inspect or reclassify individual
-results rather than trusting totals alone.
-
-## Snapshot scope
-
-At the recorded revision, the script scanned:
-
-- 3,830 tracked non-test source files;
-- 129 migration SQL files.
-
-The source-file count is intentionally broad because the goal is to find persistence coupling that
-has escaped the nominal database directory, including CLI and proxy/runtime code.
-
-## Boundary signals
-
-| Signal                                                                           | Files | Occurrences |
-| -------------------------------------------------------------------------------- | ----: | ----------: |
-| Direct `getDbInstance()` call syntax outside comments/literals and `src/lib/db/` |    45 |         150 |
-| `localDb` import consumers                                                       |   211 |           — |
-| `SqliteAdapter` type consumers outside comments/literals and `src/lib/db/`       |     3 |           — |
-
-The `localDb` barrel already gives many callers a domain-function seam, but
-`src/lib/localDb.ts` remains a re-export layer rather than a backend contract. The 45 direct
-singleton consumers are the clearest first review set because they bypass that logical seam and
-hold an adapter-shaped handle directly.
-
-The three non-test source files outside `src/lib/db/` that mention the `SqliteAdapter` type in code
-syntax are:
-
-- `src/app/api/db-backups/import/route.ts`;
-- `src/lib/compliance/index.ts`;
-- `src/lib/compliance/noLog.ts`.
-
-These are not equivalent migration tasks. Backup import is capability-specific; compliance
-persistence may be portable domain state. The future boundary should classify them rather than
-moving all three mechanically.
-
-## Adapter-shaped call syntax
-
-| Signal            | Occurrences | Files | Outside `src/lib/db/` occurrences | Outside files |
-| ----------------- | ----------: | ----: | --------------------------------: | ------------: |
-| `.prepare()`      |       1,219 |   163 |                               252 |            52 |
-| `.transaction()`  |          62 |    40 |                                12 |            10 |
-| `.immediate()`    |           3 |     3 |                                 0 |             0 |
-| `.pragma()`       |          39 |    11 |                                 6 |             4 |
-| `.backup()`       |           6 |     5 |                                 3 |             3 |
-| `.checkpoint()`   |           0 |     0 |                                 0 |             0 |
-| `lastInsertRowid` |          15 |     7 |                                 1 |             1 |
-
-This table shows why `SqliteAdapter` is a SQLite runtime compatibility layer rather than a portable
-backend abstraction. Its synchronous statement and transaction shape is widely used, and some of
-that shape is visible outside the nominal database layer.
-
-The top direct `getDbInstance()` consumers outside `src/lib/db/` at this revision are:
-
-| File                                               | Occurrences |
-| -------------------------------------------------- | ----------: |
-| `src/lib/proxySubscription/subscriptionService.ts` |          12 |
-| `src/lib/semanticCache.ts`                         |          10 |
-| `src/lib/usage/callLogs.ts`                        |           9 |
-| `src/lib/cloudAgent/db.ts`                         |           8 |
-| `src/lib/memory/store.ts`                          |           8 |
-| `src/lib/memory/vectorStore.ts`                    |           8 |
-| `src/lib/modelsDevSync.ts`                         |           8 |
-| `src/lib/gamification/badges.ts`                   |           5 |
-| `src/lib/memory/retrieval.ts`                      |           5 |
-| `src/lib/pricingSync.ts`                           |           5 |
-| `src/lib/skills/registry.ts`                       |           5 |
-| `src/lib/usage/usageHistory.ts`                    |           5 |
-
-The list spans control-plane configuration, usage/audit data, cache, memory/vector search, skills,
-gamification, and CLI/provider support. A single generic SQL adapter would preserve this spread;
-domain repositories provide a way to reduce it slice by slice.
-
-## SQLite dialect and lifecycle signals
-
-| Signal                | Occurrences | Files |
-| --------------------- | ----------: | ----: |
-| `PRAGMA` text         |          97 |    41 |
-| `sqlite_master`       |          14 |    11 |
-| `BEGIN IMMEDIATE`     |           2 |     2 |
-| `INSERT OR REPLACE`   |          83 |    45 |
-| `AUTOINCREMENT`       |          34 |    24 |
-| `datetime('now')`     |         171 |    68 |
-| `VACUUM`              |          39 |    10 |
-| `wal_checkpoint`      |          13 |     7 |
-| `fts5`                |          43 |     8 |
-| `vec0`                |           7 |     1 |
-| `last_insert_rowid()` |           1 |     1 |
-
-These values are text signals and include comments where present. They are useful for locating
-portability work, not for estimating implementation effort by multiplication.
-
-Verified high-coupling areas include:
-
-- `src/lib/db/core.ts`: singleton lifecycle, SQLite file paths, WAL checkpoint, recovery, schema,
-  compaction, and backup creation;
-- `src/lib/db/migrationRunner.ts`: numbered SQL migration execution, `sqlite_master`,
-  `PRAGMA table_info`, transaction behavior, and optional FTS5 handling;
-- `src/lib/db/optimizationSettings.ts`: page/cache settings, auto-vacuum, WAL transitions, and
-  `VACUUM`;
-- `src/lib/db/backup.ts`: database backup and restore lifecycle;
-- `src/lib/db/schemaColumns.ts`: SQLite schema introspection and compatibility columns;
-- `src/lib/memory/vectorStore.ts` and `src/lib/memory/retrieval.ts`: `vec0` and FTS5 behavior;
-- `src/lib/db/adapters/`: compatibility implementations for the supported SQLite runtimes.
-
-These areas should not be forced through a lowest-common-denominator repository interface. They
-need explicit SQLite capabilities or separate backend implementations.
-
-## Migration coupling
-
-The snapshot contains 129 tracked migration SQL files. `src/lib/db/migrationRunner.ts` does more
-than execute ordered files: it owns migration discovery, version history, duplicate-version safety,
-schema probes, FTS5 capability checks, pre-migration safety, and SQLite transaction execution.
-
-Consequently:
-
-- another SQL dialect cannot safely reuse the migration files unchanged;
-- external backends need their own migration implementation and schema history;
-- logical migration milestones may be shared, but physical SQL and capability probes remain
-  backend-specific;
-- multi-replica operation requires migration ownership or locking before an external backend is
-  considered ready.
-
-## Recommended cut lines
-
-### 1. Keep SQLite runtime compatibility intact
-
-Do not replace `SqliteAdapter` or the driver cascade in the first repository PR. Keep file recovery,
-WAL, backup, optimization, FTS5, and vector behavior behind the current SQLite implementation.
-
-### 2. Start with direct singleton consumers
-
-Use the 45-file direct-consumer list as the initial review queue. Classify each file as:
-
-- portable domain state;
-- backend-specific maintenance or search;
-- process-local or rebuildable state;
-- legacy access that should call an existing domain module.
-
-Classification must precede interface design. A path appearing in the inventory is not, by itself,
-a mandate to create a repository.
-
-### 3. Prove repositories with SQLite first
-
-For one bounded domain:
-
-1. define behavior-oriented repository operations;
-2. adapt current SQLite queries behind that repository;
-3. run behavior and transaction conformance tests against SQLite;
-4. migrate callers without changing the default runtime;
-5. only then implement the same repository for an external backend.
-
-### 4. Separate portable control-plane state from capability-specific data
-
-Provider connections, API keys, combos, and routing configuration are candidates for the first
-portable slice, subject to maintainer approval and a table-ownership review. Memory vector search,
-SQLite file backup/recovery, and database optimization are poor first slices because their behavior
-is deliberately SQLite-specific.
-
-### 5. Treat usage, quota, affinity, and audit as a later coordination slice
-
-These domains have concurrency and volume semantics beyond CRUD. Their repository contracts should
-be designed together with multi-replica transaction, lease, retention, and failure-mode tests rather
-than copied mechanically from current SQL.
-
-## What this inventory does not decide
-
-This inventory does not:
-
-- approve PostgreSQL or MySQL support;
-- define repository TypeScript interfaces;
-- choose the first table or domain to migrate;
-- claim every lexical match is a defect;
-- claim the current module boundaries are ineffective;
-- change SQLite, migrations, backup, search, or runtime behavior.
-
-Its purpose is to make the next design discussion evidence-based and reproducible.

docs/combo-context-requirements.md

@@ -1,273 +0,0 @@
----
-title: "Combo Context Requirements Feature"
-version: 3.8.50
-lastUpdated: 2026-08-06
----
-
-# Combo Context Requirements Feature
-
-## Overview
-
-The Context Requirements feature allows combo configurations to filter and sort targets based on their context window size. This is useful for use cases requiring large context windows like:
-
-- Long document processing (100k+ tokens)
-- Large codebase analysis
-- Extensive conversation histories
-- Multi-file code reviews
-
-## Configuration
-
-### Schema
-
-Add `contextRequirements` to your combo's runtime config:
-
-```json
-{
-  "contextRequirements": {
-    "minContextWindow": 128000,
-    "preferLargeContext": true,
-    "contextFilterMode": "strict"
-  }
-}
-```
-
-### Fields
-
-#### `minContextWindow` (optional)
-
-- **Type**: `number` (0 to 10,000,000)
-- **Default**: `undefined` (no filtering)
-- **Description**: Filters out models with context windows below this threshold
-
-**Examples**:
-
-- `32000` - Filter out models with <32K context
-- `128000` - Require 128K+ context (GPT-4 Turbo, Claude 3)
-- `200000` - Require 200K+ context (Claude 3 Opus)
-- `1000000` - Require 1M+ context (Gemini 1.5 Pro)
-
-#### `preferLargeContext` (optional)
-
-- **Type**: `boolean`
-- **Default**: `false`
-- **Description**: When `true`, sorts remaining targets by context size (descending). Large context models are tried first.
-
-#### `contextFilterMode` (optional)
-
-- **Type**: `"strict"` | `"lenient"`
-- **Default**: `"lenient"`
-- **Description**: How to handle models with unknown context window limits
-  - `"strict"`: Excludes models with unknown context limits when a known-good target remains; fail-opens to unknowns if the pool would otherwise be empty (#8786)
-  - `"lenient"`: Includes models with unknown context limits
-
-## Behavior
-
-### Filtering Pipeline
-
-Context requirements are applied after `filterTargetsByRequestCompatibility()`:
-
-1. **Request compatibility filtering** - Removes models incompatible with request (tools, vision, structured output)
-2. **Context requirements filtering** - Applies `minContextWindow` and `contextFilterMode`
-3. **Context-based sorting** - If `preferLargeContext` is true, sorts by context size descending
-
-### Filter Mode Logic
-
-When `minContextWindow` is set:
-
-**Lenient mode** (default):
-
-- ✅ Includes models with context >= minContextWindow
-- ✅ Includes models with unknown context limits
-- ❌ Excludes models with context < minContextWindow
-
-**Strict mode**:
-
-- ✅ Includes models with context >= minContextWindow
-- ❌ Excludes models with unknown context limits (when at least one known-good target remains)
-- ❌ Excludes models with context < minContextWindow
-- ⚠️ **Fail-open (#8786)**: if strict filtering would empty the pool and at least one
-  unknown-context target exists, those unknowns are restored instead of returning
-  `404 Combo has no executable targets`. Known-too-small targets are never resurrected.
-  When the pool is still empty (every known target is below `minContextWindow`), the
-  API returns `terminalReason: "context_requirements_exhausted"` with a recovery hint.
-
-### Sorting Logic
-
-When `preferLargeContext` is true:
-
-- Models are sorted by context window size (descending)
-- Unknown context models sort to the end
-- Original strategy order is used as a tiebreaker
-
-## Use Cases
-
-### Example 1: Long Document Processing
-
-```json
-{
-  "name": "Document Analysis",
-  "strategy": "fusion",
-  "config": {
-    "contextRequirements": {
-      "minContextWindow": 128000,
-      "preferLargeContext": true,
-      "contextFilterMode": "strict"
-    }
-  }
-}
-```
-
-This configuration:
-
-- Requires 128K+ context window
-- Prefers larger context models (Gemini 1.5 Pro > Claude 3 Opus > GPT-4 Turbo)
-- Excludes models with unknown context limits
-
-### Example 2: Large Codebase Analysis
-
-```json
-{
-  "name": "Code Review",
-  "strategy": "auto",
-  "config": {
-    "contextRequirements": {
-      "minContextWindow": 200000,
-      "preferLargeContext": true,
-      "contextFilterMode": "lenient"
-    }
-  }
-}
-```
-
-This configuration:
-
-- Requires 200K+ context window
-- Prefers larger context models
-- Includes models with unknown limits (lenient)
-
-### Example 3: Prefer Large Context Without Strict Requirements
-
-```json
-{
-  "name": "Flexible Chat",
-  "strategy": "weighted",
-  "config": {
-    "contextRequirements": {
-      "preferLargeContext": true
-    }
-  }
-}
-```
-
-This configuration:
-
-- No minimum requirement (all models eligible)
-- Sorts by context size (largest first)
-- Useful when large context is preferred but not required
-
-## API Response
-
-When context requirements filter targets, the combo logger outputs:
-
-```
-[COMBO] Context requirements: filtered 10 → 3 targets (minContextWindow: 128000, mode: strict)
-[COMBO] Context requirements: kept models gemini-1.5-pro, claude-3-opus-20240229, gpt-4-turbo
-[COMBO] Context requirements: sorted by context size (descending): gemini-1.5-pro(1000000), claude-3-opus-20240229(200000), gpt-4-turbo(128000)
-```
-
-## Implementation Details
-
-### Backend Module
-
-`open-sse/services/combo/contextRequirements.ts`:
-
-- `applyContextRequirements()` - Main filtering function
-- `getTargetContextWindow()` - Context lookup helper
-- Uses `getModelContextLimit()` from `modelCapabilities.ts`
-
-### Integration Point
-
-`open-sse/services/combo.ts` line 1187:
-
-```typescript
-orderedTargets = filterTargetsByRequestCompatibility(orderedTargets, body, log);
-orderedTargets = applyContextRequirements(orderedTargets, config.contextRequirements, log);
-```
-
-### Schema Definition
-
-`src/shared/validation/schemas/combo.ts`:
-
-```typescript
-contextRequirements: z
-  .object({
-    minContextWindow: z.coerce.number().int().min(0).max(10_000_000).optional(),
-    preferLargeContext: z.boolean().optional(),
-    contextFilterMode: z.enum(["strict", "lenient"]).optional(),
-  })
-  .strict()
-  .optional(),
-```
-
-## Testing
-
-### Run Tests
-
-```bash
-# Unit tests (schema + logic)
-npm test tests/unit/combo-context-requirements.test.ts
-
-# Integration tests (end-to-end)
-npm test tests/unit/combo/context-requirements-integration.test.ts
-```
-
-### Test Coverage
-
-- Schema validation: 6 tests
-- Filtering logic: 6 tests
-- Integration: 5 tests
-- **Total**: 17/17 passing ✅
-
-## Troubleshooting
-
-### All targets filtered out
-
-**Problem**: All targets removed, combo returns "no compatible models"
-
-**Solutions**:
-
-1. Lower `minContextWindow` threshold
-2. Switch to `"lenient"` mode to include unknown context models
-3. Remove `minContextWindow` and use only `preferLargeContext`
-
-### Unknown context models excluded
-
-**Problem**: Custom/new models excluded even though they have large context
-
-**Solutions**:
-
-1. Switch to `"lenient"` mode (default)
-2. Add model context limit to `modelCapabilities.ts`
-3. Remove context filtering and rely on strategy order
-
-### Sorting not applied
-
-**Problem**: `preferLargeContext` doesn't change order
-
-**Check**:
-
-1. Verify `preferLargeContext: true` in config
-2. Check if all targets have unknown context (all sort equal)
-3. Verify multiple targets remain after filtering
-
-## Related
-
-- [Auto-Combo Routing Strategies](./routing/AUTO-COMBO.md)
-- [Resilience Guide](./architecture/RESILIENCE_GUIDE.md)
-
-## Version History
-
-- **v3.8.47**: Initial implementation
-  - Added `contextRequirements` config
-  - Created backend filtering module
-  - Full test coverage (no dedicated dashboard UI yet — configure via combo JSON)

docs/compression/meta.json

@@ -6,6 +6,7 @@
     "RTK_COMPRESSION",
     "COMPRESSION_LANGUAGE_PACKS",
     "COMPRESSION_RULES_FORMAT",
+    "CONTEXT_EDITING",
     "EXTENDING_COMPRESSION"
   ]
 }

docs/diagrams/cli-terminal.svg

@@ -1,4 +1,4 @@
-<svg viewBox="0 0 1200 350" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Animated terminal demoing the OmniRoute CLI: omniroute providers list (278 providers registered, anthropic, codex, glm, kimi shown active), omniroute combo list (always-on priority, cost-saver, fusion-panel, context-relay) and omniroute health (healthy, 18412 requests in 24h, p95 412ms, circuit breakers 24 closed, 1 half-open, 0 open), cycling over the 80+ command surface: providers, oauth, keys, combo, nodes, models, cache, compression, cost, usage, quota, health, resilience, telemetry, logs, audit, mcp, a2a, cloud, memory, skills, eval, doctor, repl, tunnel, backup, sync, webhooks, policy, pricing, translator, simulate and more.">
+<svg viewBox="0 0 1200 350" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Animated terminal demoing the OmniRoute CLI: omniroute providers list (338 providers registered, anthropic, codex, glm, kimi shown active), omniroute combo list (always-on priority, cost-saver, fusion-panel, context-relay) and omniroute health (healthy, 18412 requests in 24h, p95 412ms, circuit breakers 24 closed, 1 half-open, 0 open), cycling over the 80+ command surface: providers, oauth, keys, combo, nodes, models, cache, compression, cost, usage, quota, health, resilience, telemetry, logs, audit, mcp, a2a, cloud, memory, skills, eval, doctor, repl, tunnel, backup, sync, webhooks, policy, pricing, translator, simulate and more.">
 <desc>Compact animated terminal cycling three real OmniRoute CLI commands with a typewriter effect and a scrolling subcommand ticker; the first frame shows the completed providers-list screen.</desc>
 <defs><clipPath id="tickerClip"><rect x="12" y="304" width="1176" height="40"/></clipPath><clipPath id="tw0"><rect x="64" y="46" height="26" width="0"><animate attributeName="width" calcMode="discrete" values="0;31;61;92;122;153;184;214;245;245" keyTimes="0;0.012;0.018;0.024;0.030;0.036;0.042;0.048;0.054;1" dur="18s" repeatCount="indefinite"/></rect></clipPath><clipPath id="tw1"><rect x="64" y="46" height="26" width="0"><animate attributeName="width" calcMode="discrete" values="0;26;51;76;102;128;153;178;204;204" keyTimes="0;0.345;0.351;0.357;0.363;0.369;0.375;0.381;0.387;1" dur="18s" repeatCount="indefinite"/></rect></clipPath><clipPath id="tw2"><rect x="64" y="46" height="26" width="0"><animate attributeName="width" calcMode="discrete" values="0;20;41;61;82;102;122;143;163;163" keyTimes="0;0.678;0.684;0.690;0.696;0.702;0.708;0.714;0.720;1" dur="18s" repeatCount="indefinite"/></rect></clipPath></defs>
 <rect width="1200" height="350" fill="#0d1117"/>
@@ -6,7 +6,7 @@
 <path d="M 0 34 L 1200 34" stroke="#ffffff" stroke-opacity="0.08" stroke-width="1"/>
 <circle cx="24" cy="17" r="6" fill="#ff5f56"/><circle cx="46" cy="17" r="6" fill="#ffbd2e"/><circle cx="68" cy="17" r="6" fill="#27c93f"/>
 <text x="600" y="22" text-anchor="middle" font-family="Consolas, 'Courier New', monospace" font-size="13" fill="#71717a">omniroute &#8212; 80+ commands</text>
-<g font-family="Consolas, 'Courier New', monospace" font-size="17"><animate attributeName="opacity" values="1;0;0" keyTimes="0;0.006;1" dur="18s" repeatCount="indefinite"/><text x="64" y="66" fill="#F7F6FC">omniroute providers list</text><text x="40" y="100" font-weight="700" fill="#38bdf8">OmniRoute Providers</text><text x="40" y="128" fill="#a1a1aa">1f3a9c2e&#160;&#160;anthropic&#160;&#160;&#160;Claude Max 20x&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="154" fill="#a1a1aa">8c2d5b1a&#160;&#160;codex&#160;&#160;&#160;&#160;&#160;&#160;&#160;Codex Pro (team)&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="180" fill="#a1a1aa">f4e0a97b&#160;&#160;glm&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;GLM Coding Plan&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="206" fill="#a1a1aa">03bd6e5f&#160;&#160;kimi&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Kimi K2 free&#160;&#160;&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="232" fill="#71717a">&#8230; 264 more providers</text></g><g opacity="1" font-family="Consolas, 'Courier New', monospace" font-size="17">
+<g font-family="Consolas, 'Courier New', monospace" font-size="17"><animate attributeName="opacity" values="1;0;0" keyTimes="0;0.006;1" dur="18s" repeatCount="indefinite"/><text x="64" y="66" fill="#F7F6FC">omniroute providers list</text><text x="40" y="100" font-weight="700" fill="#38bdf8">OmniRoute Providers</text><text x="40" y="128" fill="#a1a1aa">1f3a9c2e&#160;&#160;anthropic&#160;&#160;&#160;Claude Max 20x&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="154" fill="#a1a1aa">8c2d5b1a&#160;&#160;codex&#160;&#160;&#160;&#160;&#160;&#160;&#160;Codex Pro (team)&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="180" fill="#a1a1aa">f4e0a97b&#160;&#160;glm&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;GLM Coding Plan&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="206" fill="#a1a1aa">03bd6e5f&#160;&#160;kimi&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Kimi K2 free&#160;&#160;&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="232" fill="#71717a">&#8230; 334 more providers</text></g><g opacity="1" font-family="Consolas, 'Courier New', monospace" font-size="17">
 <animate attributeName="opacity" values="1;1;0;0" keyTimes="0;0.315;0.33;1" dur="18s" repeatCount="indefinite"/>
 <text x="40" y="66" fill="#22c55e">$</text>
 <g clip-path="url(#tw0)"><text x="64" y="66" fill="#F7F6FC">omniroute providers list</text></g>
@@ -14,7 +14,7 @@
   <animate attributeName="x" calcMode="discrete" values="64;95;125;156;186;217;248;278;309;309" keyTimes="0.000;0.012;0.018;0.024;0.030;0.036;0.042;0.048;0.054;1" dur="18s" repeatCount="indefinite"/>
   <animate attributeName="opacity" values="0;0;1;0.2;1;0.2;1;0;0" keyTimes="0;0.011;0.012;0.022;0.032;0.042;0.052;0.074;1" dur="18s" repeatCount="indefinite"/>
 </rect>
-<text x="40" y="100" font-weight="700" fill="#38bdf8" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.045;0.047" dur="18s" repeatCount="indefinite"/>OmniRoute Providers</text><text x="40" y="128" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.053;0.055" dur="18s" repeatCount="indefinite"/>1f3a9c2e&#160;&#160;anthropic&#160;&#160;&#160;Claude Max 20x&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="154" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.061;0.063" dur="18s" repeatCount="indefinite"/>8c2d5b1a&#160;&#160;codex&#160;&#160;&#160;&#160;&#160;&#160;&#160;Codex Pro (team)&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="180" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.069;0.07100000000000001" dur="18s" repeatCount="indefinite"/>f4e0a97b&#160;&#160;glm&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;GLM Coding Plan&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="206" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.077;0.079" dur="18s" repeatCount="indefinite"/>03bd6e5f&#160;&#160;kimi&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Kimi K2 free&#160;&#160;&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="232" fill="#71717a" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.085;0.08700000000000001" dur="18s" repeatCount="indefinite"/>&#8230; 264 more providers</text>
+<text x="40" y="100" font-weight="700" fill="#38bdf8" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.045;0.047" dur="18s" repeatCount="indefinite"/>OmniRoute Providers</text><text x="40" y="128" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.053;0.055" dur="18s" repeatCount="indefinite"/>1f3a9c2e&#160;&#160;anthropic&#160;&#160;&#160;Claude Max 20x&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="154" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.061;0.063" dur="18s" repeatCount="indefinite"/>8c2d5b1a&#160;&#160;codex&#160;&#160;&#160;&#160;&#160;&#160;&#160;Codex Pro (team)&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="180" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.069;0.07100000000000001" dur="18s" repeatCount="indefinite"/>f4e0a97b&#160;&#160;glm&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;GLM Coding Plan&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="206" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.077;0.079" dur="18s" repeatCount="indefinite"/>03bd6e5f&#160;&#160;kimi&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;Kimi K2 free&#160;&#160;&#160;&#160;&#160;&#160;<tspan fill='#22c55e'>active</tspan></text><text x="40" y="232" fill="#71717a" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.085;0.08700000000000001" dur="18s" repeatCount="indefinite"/>&#8230; 334 more providers</text>
 </g><g opacity="0" font-family="Consolas, 'Courier New', monospace" font-size="17">
 <animate attributeName="opacity" values="0;0;1;1;0;0" keyTimes="0;0.333;0.34500000000000003;0.648;0.663;1" dur="18s" repeatCount="indefinite"/>
 <text x="40" y="66" fill="#22c55e">$</text>
@@ -32,7 +32,7 @@
   <animate attributeName="x" calcMode="discrete" values="64;84;105;125;146;166;186;207;227;227" keyTimes="0;0.678;0.684;0.690;0.696;0.702;0.708;0.714;0.720;1" dur="18s" repeatCount="indefinite"/>
   <animate attributeName="opacity" values="0;0;1;0.2;1;0.2;1;0;0" keyTimes="0;0.677;0.678;0.688;0.698;0.708;0.718;0.74;1" dur="18s" repeatCount="indefinite"/>
 </rect>
-<text x="40" y="100" font-weight="700" fill="#38bdf8" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.711;0.713" dur="18s" repeatCount="indefinite"/>OmniRoute Health</text><text x="40" y="128" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.719;0.721" dur="18s" repeatCount="indefinite"/>&#160;&#160;Status: <tspan fill='#22c55e'>healthy</tspan>&#160;&#160;&#160;Uptime: 4d 12h 33m</text><text x="40" y="154" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.727;0.729" dur="18s" repeatCount="indefinite"/>&#160;&#160;Requests (24h): 18,412&#160;&#160;&#160;p95: 412ms</text><text x="40" y="180" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.735;0.737" dur="18s" repeatCount="indefinite"/>&#160;&#160;Breakers: <tspan fill='#22c55e'>&#9679; 24 closed</tspan>&#160;&#160;<tspan fill='#f59e0b'>&#9682; 1 half-open</tspan>&#160;&#160;<tspan fill='#ef4444'>&#9675; 0 open</tspan></text><text x="40" y="206" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.743;0.745" dur="18s" repeatCount="indefinite"/>&#160;&#160;Providers: 278 registered&#160;&#160;&#160;90+ free tiers</text><text x="40" y="232" fill="#71717a" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.751;0.753" dur="18s" repeatCount="indefinite"/>&#8230; live: /dashboard &#183; omniroute status</text>
+<text x="40" y="100" font-weight="700" fill="#38bdf8" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.711;0.713" dur="18s" repeatCount="indefinite"/>OmniRoute Health</text><text x="40" y="128" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.719;0.721" dur="18s" repeatCount="indefinite"/>&#160;&#160;Status: <tspan fill='#22c55e'>healthy</tspan>&#160;&#160;&#160;Uptime: 4d 12h 33m</text><text x="40" y="154" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.727;0.729" dur="18s" repeatCount="indefinite"/>&#160;&#160;Requests (24h): 18,412&#160;&#160;&#160;p95: 412ms</text><text x="40" y="180" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.735;0.737" dur="18s" repeatCount="indefinite"/>&#160;&#160;Breakers: <tspan fill='#22c55e'>&#9679; 24 closed</tspan>&#160;&#160;<tspan fill='#f59e0b'>&#9682; 1 half-open</tspan>&#160;&#160;<tspan fill='#ef4444'>&#9675; 0 open</tspan></text><text x="40" y="206" fill="#a1a1aa" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.743;0.745" dur="18s" repeatCount="indefinite"/>&#160;&#160;Providers: 338 registered&#160;&#160;&#160;90+ free tiers</text><text x="40" y="232" fill="#71717a" opacity="0"><animate attributeName="opacity" calcMode="discrete" values="0;0;1" keyTimes="0;0.751;0.753" dur="18s" repeatCount="indefinite"/>&#8230; live: /dashboard &#183; omniroute status</text>
 </g>
 <path d="M 0 300 L 1200 300" stroke="#ffffff" stroke-opacity="0.08" stroke-width="1"/>
 <g clip-path="url(#tickerClip)"><g font-family="Consolas, 'Courier New', monospace" font-size="14" fill="#71717a">

docs/diagrams/comparison-table.svg

@@ -1,4 +1,4 @@
-<svg viewBox="0 0 1200 780" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Comparison table: OmniRoute versus 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute is the only one with the full set: 290 providers, 90+ free providers built-in, 19 routing strategies, 12-engine token compression, a built-in MCP server with 104 tools, A2A protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, desktop/Termux/PWA, 43 UI locales and 100% MIT self-hosted. 9router has free providers, RTK compression and translation but no MCP, A2A, memory, guardrails, cloud agents or stealth. OpenRouter is a hosted SaaS with 400+ models, guardrails and a hosted MCP but is not self-hosted and lacks A2A, memory, cloud agents and stealth. CLIProxyAPI is a light OAuth proxy with two routing strategies. LiteLLM has 100+ providers, A2A and extensive guardrails but no memory, compression, free tier, stealth or cloud agents.">
+<svg viewBox="0 0 1200 780" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="Comparison table: OmniRoute versus 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute is the only one with the full set: 338 providers, 90+ free providers built-in, 19 routing strategies, 12-engine token compression, a built-in MCP server with 105 tools, A2A protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, desktop/Termux/PWA, 43 UI locales and 100% MIT self-hosted. 9router has free providers, RTK compression and translation but no MCP, A2A, memory, guardrails, cloud agents or stealth. OpenRouter is a hosted SaaS with 400+ models, guardrails and a hosted MCP but is not self-hosted and lacks A2A, memory, cloud agents and stealth. CLIProxyAPI is a light OAuth proxy with two routing strategies. LiteLLM has 100+ providers, A2A and extensive guardrails but no memory, compression, free tier, stealth or cloud agents.">
   <desc>Static-header comparison table where each capability row fades in top to bottom; the OmniRoute column is highlighted and shows a check or a leading value in every row, while competitors show a mix of checks, partials and crosses.</desc>
   <defs>
     <pattern id="gC" width="32" height="32" patternUnits="userSpaceOnUse"><path d="M 32 0 L 0 0 0 32" fill="none" stroke="#ffffff" stroke-opacity="0.05" stroke-width="1"/></pattern>
@@ -23,7 +23,7 @@
   <g font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif">
     <g opacity="0"><animate attributeName="opacity" values="0;1" dur="0.4s" begin="0.15s" fill="freeze"/>
       <text x="44" y="196" font-size="14.5" fill="#c9d1d9">Providers</text>
-      <text x="440" y="196" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="15" font-weight="800" fill="#7ee787">290</text>
+      <text x="440" y="196" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="15" font-weight="800" fill="#7ee787">338</text>
       <text x="604" y="196" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="13.5" font-weight="600" fill="#8b949e">40+</text>
       <text x="760" y="196" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="13.5" font-weight="600" fill="#8b949e">400+*</text>
       <text x="916" y="196" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="13.5" font-weight="600" fill="#8b949e">~5</text>
@@ -57,7 +57,7 @@
     </g>
     <g opacity="0"><animate attributeName="opacity" values="0;1" dur="0.4s" begin="0.51s" fill="freeze"/>
       <text x="44" y="364" font-size="14.5" fill="#c9d1d9">Built-in MCP server (own tools)</text>
-      <text x="440" y="364" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="15" font-weight="800" fill="#7ee787">104</text>
+      <text x="440" y="364" text-anchor="middle" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="15" font-weight="800" fill="#7ee787">105</text>
       <use href="#no" x="604" y="359"/>
       <use href="#mid" x="760" y="359"/>
       <use href="#no" x="916" y="359"/>

docs/diagrams/free-tier-budget.svg

@@ -1,4 +1,4 @@
-<svg viewBox="0 0 1200 842" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="OmniRoute free-tier budget: about 1.53 billion free tokens per month steady, up to about 2.15 billion in your first month with signup credits, aggregated from the documented free tiers of 43 provider pools and 460+ models behind one endpoint, live on /dashboard/free-tiers. Honest pool-deduped math: each shared free pool is counted once — counting every rate limit 24/7 would read about 10B, which we don't publish; 15 providers carry a ToS flag so you decide. Budget bar of the 19 countable free pools with per-model breakdown: Mistral Large 3 1B, GPT-4o mini 150M, Gemini 2.5 Flash 60M, GLM 4.7 30M, Llama 3.3 70B 30M, Grok-3 24M, DeepSeek V4 Pro 20M, GPT-4.1 18M, Llama 4 Scout 15M, GPT-4o 7M, MiniMax-M2.7 6M, Arcee Trinity 5M, and more. First month adds one-time signup credits of about 626M (vertex 300M, agentrouter 200M, predibase 25M, together 25M, glm-cn 20M, doubao 15M, ai21 10M, longcat 10M, deepseek 5M, hyperbolic 5M, nscale 5M). Plus the un-countable: permanently-free no-token-cap providers (SiliconFlow, Z.AI GLM-Flash, Kilo, OpenCode Zen, baidu and more) and a $10 OpenRouter top-up unlocking +24M per month, surfaced separately so they never inflate the headline. Live used/remaining and per-model breakdown on the dashboard.">
+<svg viewBox="0 0 1200 842" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="OmniRoute free-tier budget: about 1.51 billion free tokens per month steady, up to about 2.13 billion in your first month with signup credits, aggregated from the documented free tiers of 42 provider pools and 495 models behind one endpoint, live on /dashboard/free-tiers. Honest pool-deduped math: each shared free pool is counted once — counting every rate limit 24/7 would read about 10B, which we don't publish; 15 providers carry a ToS flag so you decide. Budget bar of the 19 countable free pools with per-model breakdown: Mistral Large 3 1B, GPT-4o mini 150M, Gemini 2.5 Flash 60M, GLM 4.7 30M, Llama 3.3 70B 30M, Grok-3 24M, DeepSeek V4 Pro 20M, GPT-4.1 18M, Llama 4 Scout 15M, GPT-4o 7M, MiniMax-M2.7 6M, Arcee Trinity 5M, and more. First month adds one-time signup credits of about 626M (vertex 300M, agentrouter 200M, predibase 25M, together 25M, glm-cn 20M, doubao 15M, ai21 10M, longcat 10M, deepseek 5M, hyperbolic 5M, nscale 5M). Plus the un-countable: permanently-free no-token-cap providers (SiliconFlow, Z.AI GLM-Flash, Kilo, OpenCode Zen, baidu and more) and a $10 OpenRouter top-up unlocking +24M per month, surfaced separately so they never inflate the headline. Live used/remaining and per-model breakdown on the dashboard.">
   <defs>
     <pattern id="gridPaperF" width="32" height="32" patternUnits="userSpaceOnUse">
       <path d="M 32 0 L 0 0 0 32" fill="none" stroke="#ffffff" stroke-opacity="0.06" stroke-width="1"/>
@@ -60,10 +60,10 @@
       <animate attributeName="opacity" values="0;1;1;0" dur="2.4s" begin="1.6s" repeatCount="indefinite"/>
     </circle>
   </g>
-  <text x="60" y="228" font-family="Consolas, 'Courier New', monospace" font-size="104" font-weight="800" fill="url(#gradBrandF)">~1.53B</text>
+  <text x="60" y="228" font-family="Consolas, 'Courier New', monospace" font-size="104" font-weight="800" fill="url(#gradBrandF)">~1.51B</text>
   <text x="62" y="266" font-family="Consolas, 'Courier New', monospace" font-size="15" letter-spacing="3" font-weight="700" fill="#a1a1aa">FREE TOKENS / MONTH &#183; <tspan fill="#22c55e">STEADY</tspan></text>
-  <text x="62" y="298" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="16" fill="#F7F6FC">up to <tspan font-weight="800" fill="#22c55e">~2.15B</tspan> in your first month &#8212; signup credits</text>
-  <text x="62" y="326" font-family="Consolas, 'Courier New', monospace" font-size="12" fill="#71717a">documented free tiers &#183; <tspan fill="#8b5cf6">43 provider pools</tspan> &#183; <tspan fill="#8b5cf6">460+ models</tspan> &#183; one endpoint</text>
+  <text x="62" y="298" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="16" fill="#F7F6FC">up to <tspan font-weight="800" fill="#22c55e">~2.13B</tspan> in your first month &#8212; signup credits</text>
+  <text x="62" y="326" font-family="Consolas, 'Courier New', monospace" font-size="12" fill="#71717a">documented free tiers &#183; <tspan fill="#8b5cf6">42 provider pools</tspan> &#183; <tspan fill="#8b5cf6">495 models</tspan> &#183; one endpoint</text>
 
   <!-- ═══ Panel · The honest math ═══ -->
   <rect x="680" y="84" width="460" height="216" rx="14" fill="#161b22" stroke="#ffffff" stroke-opacity="0.08" stroke-width="1"/>
@@ -74,7 +74,7 @@
   </line>
   <text x="836" y="156" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#a1a1aa">every rate limit &#183; 24/7</text>
   <text x="836" y="176" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#ef4444" opacity="0.85">we don't publish that</text>
-  <text x="704" y="240" font-family="Consolas, 'Courier New', monospace" font-size="34" font-weight="800" fill="#22c55e">~1.53B</text>
+  <text x="704" y="240" font-family="Consolas, 'Courier New', monospace" font-size="34" font-weight="800" fill="#22c55e">~1.51B</text>
   <text x="836" y="224" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#a1a1aa">each shared free pool</text>
   <text x="836" y="244" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#22c55e">counted once &#10003;</text>
   <text x="704" y="280" font-family="Consolas, 'Courier New', monospace" font-size="12" fill="#f59e0b"><tspan font-weight="800">15 providers</tspan> ToS-flagged <tspan fill="#71717a">&#8212; we flag it &#183; you decide</tspan></text>

docs/diagrams/promise-pillars.svg

@@ -1,4 +1,4 @@
-<svg viewBox="0 0 1200 540" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="The OmniRoute promise: one endpoint, 290 providers — never stop building, OmniRoute picks the cheapest one that works. Six pillars. Never hit limits: auto-fallback across 290 providers in milliseconds, quota out means the next provider takes over with zero downtime. Save up to 95 percent of tokens: RTK plus Caveman stacked compression cuts 15 to 95 percent of eligible tokens, about 89 percent average on tool-heavy sessions. Zero dollars to start: 90+ providers with a free tier, 40+ free forever — Qoder, Pollinations, Cloudflare, SiliconFlow — no card needed. Every tool works: 33 coding agents including Claude Code, Codex, Cursor, Cline, Copilot and Antigravity through one config. One endpoint: OpenAI, Claude, Gemini and Responses API translation — point any tool at /v1 and it just works. Production-grade: circuit breakers, TLS stealth, MCP with 104 tools, A2A, memory, guardrails, evals — 25,000+ tests.">
+<svg viewBox="0 0 1200 540" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="The OmniRoute promise: one endpoint, 338 providers — never stop building, OmniRoute picks the cheapest one that works. Six pillars. Never hit limits: auto-fallback across 338 providers in milliseconds, quota out means the next provider takes over with zero downtime. Save up to 95 percent of tokens: RTK plus Caveman stacked compression cuts 15 to 95 percent of eligible tokens, about 89 percent average on tool-heavy sessions. Zero dollars to start: 90+ providers with a free tier, 40+ free forever — Qoder, Pollinations, Cloudflare, SiliconFlow — no card needed. Every tool works: 33 coding agents including Claude Code, Codex, Cursor, Cline, Copilot and Antigravity through one config. One endpoint: OpenAI, Claude, Gemini and Responses API translation — point any tool at /v1 and it just works. Production-grade: circuit breakers, TLS stealth, MCP with 105 tools, A2A, memory, guardrails, evals — 25,000+ tests.">
   <desc>Animated promise card: six pillar tiles fade in in reading order, then a soft colored border highlight sweeps from tile to tile in a continuous cycle.</desc>
   <defs>
     <pattern id="gridPaperP" width="32" height="32" patternUnits="userSpaceOnUse">
@@ -21,7 +21,7 @@
     <line x1="150" y1="53" x2="1160" y2="53" stroke="#232b38" stroke-width="1.5"/>
   </g>
   <g>
-    <text x="40" y="100" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="23" font-weight="600" fill="#c9d1d9">One endpoint. <tspan fill="#a78bfa" font-weight="800">290 providers.</tspan> Never stop building — OmniRoute picks <tspan fill="#7ee787" font-weight="700">the cheapest one that works</tspan>.</text>
+    <text x="40" y="100" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="23" font-weight="600" fill="#c9d1d9">One endpoint. <tspan fill="#a78bfa" font-weight="800">338 providers.</tspan> Never stop building — OmniRoute picks <tspan fill="#7ee787" font-weight="700">the cheapest one that works</tspan>.</text>
   </g>
 
   <g font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif">
@@ -38,7 +38,7 @@
         <line x1="3.9" y1="3.9" x2="18.1" y2="18.1"/>
       </g>
       <text x="102" y="170" font-size="18" font-weight="800" fill="#74b9ff">Never hit limits</text>
-      <text x="66" y="204" font-size="13.5" fill="#a1a1aa">Auto-fallback across 290 providers in</text>
+      <text x="66" y="204" font-size="13.5" fill="#a1a1aa">Auto-fallback across 338 providers in</text>
       <text x="66" y="226" font-size="13.5" fill="#a1a1aa">milliseconds. Quota out? The next provider</text>
       <text x="66" y="248" font-size="13.5" fill="#a1a1aa">takes over — zero downtime.</text>
     </g>
@@ -125,7 +125,7 @@
         <path d="M 7,11 L 10,14 L 15.4,8.2"/>
       </g>
       <text x="862" y="354" font-size="18" font-weight="800" fill="#7ee787">Production-grade</text>
-      <text x="826" y="388" font-size="13.5" fill="#a1a1aa">Circuit breakers, TLS stealth, MCP (104</text>
+      <text x="826" y="388" font-size="13.5" fill="#a1a1aa">Circuit breakers, TLS stealth, MCP (105</text>
       <text x="826" y="410" font-size="13.5" fill="#a1a1aa">tools), A2A, memory, guardrails, evals —</text>
       <text x="826" y="432" font-size="13.5" fill="#a1a1aa">25,000+ tests.</text>
     </g>

docs/diagrams/readme-hero.svg

@@ -1,4 +1,4 @@
-<svg viewBox="0 0 1200 548" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="OmniRoute hero: Never stop coding. Every AI tool to 290 providers — 90+ free — through one endpoint. Claude Code, Codex, Cursor, Cline, Copilot and Antigravity into free Claude, GPT and Gemini with auto-fallback. RTK + Caveman stacked compression saves 15 to 95 percent of tokens — about 89 percent average on tool-heavy sessions — so you never hit limits. Stats: 290 AI providers, 90+ free tiers, about 1.53B free tokens per month, 15 to 95 percent token savings, 19 routing strategies, zero dollars to start.">
+<svg viewBox="0 0 1200 548" xmlns="http://www.w3.org/2000/svg" role="img" aria-label="OmniRoute hero: Never stop coding. Every AI tool to 338 providers — 90+ free — through one endpoint. Claude Code, Codex, Cursor, Cline, Copilot and Antigravity into free Claude, GPT and Gemini with auto-fallback. RTK + Caveman stacked compression saves 15 to 95 percent of tokens — about 89 percent average on tool-heavy sessions — so you never hit limits. Stats: 338 AI providers, 90+ free tiers, about 1.51B free tokens per month, 15 to 95 percent token savings, 19 routing strategies, zero dollars to start.">
   <desc>Animated hero card: a pulse travels the divider line and a compression bar demo repeatedly shrinks a prompt by up to 95 percent; all headline content is static and readable on the first frame.</desc>
   <defs>
     <pattern id="gridPaperH" width="32" height="32" patternUnits="userSpaceOnUse">
@@ -28,7 +28,7 @@
   <text x="48" y="138" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="60" font-weight="800" fill="#e9edf3">Never stop coding<tspan fill="#a855f7">.</tspan></text>
 
   <!-- subheadline -->
-  <text x="48" y="184" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="25" font-weight="600" fill="#c9d1d9">Every AI tool → <tspan fill="#a78bfa" font-weight="800">290 providers</tspan> — <tspan fill="#7ee787" font-weight="800">90+ free</tspan> — through one endpoint.</text>
+  <text x="48" y="184" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="25" font-weight="600" fill="#c9d1d9">Every AI tool → <tspan fill="#a78bfa" font-weight="800">338 providers</tspan> — <tspan fill="#7ee787" font-weight="800">90+ free</tspan> — through one endpoint.</text>
 
   <!-- plug line -->
   <text x="48" y="222" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="16.5" fill="#a1a1aa">Claude Code · Codex · Cursor · Cline · Copilot · Antigravity&#160;&#160;→&#160;&#160;<tspan fill="#7ee787" font-weight="700">FREE</tspan> Claude / GPT / Gemini · auto-fallback</text>
@@ -66,13 +66,13 @@
   <!-- stat chips -->
   <g font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" text-anchor="middle">
     <rect x="48" y="448" width="172" height="52" rx="12" fill="#161b22" stroke="#6c5ce7" stroke-opacity="0.55" stroke-width="1.5"/>
-    <text x="134" y="471" font-size="17" font-weight="800" fill="#a78bfa">290</text>
+    <text x="134" y="471" font-size="17" font-weight="800" fill="#a78bfa">338</text>
     <text x="134" y="490" font-size="11" fill="#a1a1aa">AI PROVIDERS</text>
     <rect x="234" y="448" width="172" height="52" rx="12" fill="#161b22" stroke="#22c55e" stroke-opacity="0.55" stroke-width="1.5"/>
     <text x="320" y="471" font-size="17" font-weight="800" fill="#7ee787">90+</text>
     <text x="320" y="490" font-size="11" fill="#a1a1aa">FREE TIERS</text>
     <rect x="420" y="448" width="172" height="52" rx="12" fill="#161b22" stroke="#22c55e" stroke-opacity="0.55" stroke-width="1.5"/>
-    <text x="506" y="471" font-size="17" font-weight="800" fill="#7ee787">~1.53B</text>
+    <text x="506" y="471" font-size="17" font-weight="800" fill="#7ee787">~1.51B</text>
     <text x="506" y="490" font-size="11" fill="#a1a1aa">FREE TOKENS / MO</text>
     <rect x="606" y="448" width="172" height="52" rx="12" fill="#161b22" stroke="#e17055" stroke-opacity="0.55" stroke-width="1.5"/>
     <text x="692" y="471" font-size="17" font-weight="800" fill="#e17055">15–95%</text>

docs/diagrams/tier-cascade.svg

@@ -89,7 +89,7 @@
     </circle>
   </g>
   <text x="364" y="216" font-family="Inter, 'Segoe UI', Arial, Helvetica, system-ui, sans-serif" font-size="20" font-weight="800" fill="url(#gradBrand)">OmniRoute — Smart Router</text>
-  <text x="364" y="243" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#a1a1aa"><tspan fill="#8b5cf6">RTK + Caveman compression</tspan> · <tspan fill="#8b5cf6">18 routing strategies</tspan></text>
+  <text x="364" y="243" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#a1a1aa"><tspan fill="#8b5cf6">RTK + Caveman compression</tspan> · <tspan fill="#8b5cf6">19 routing strategies</tspan></text>
   <text x="364" y="264" font-family="Consolas, 'Courier New', monospace" font-size="11.5" fill="#a1a1aa">Circuit breakers · TLS stealth · MCP · A2A · Guardrails</text>
 
   <!-- fan-out topology (always visible) -->

docs/frameworks/ACP.md

@@ -543,7 +543,7 @@ const agents = detectInstalledAgents();
 ## What's Next?
 
 - **[API Reference](../reference/API_REFERENCE.md)** — REST API endpoints
-- **[Provider Reference](../reference/PROVIDER_REFERENCE.md)** — All 226 providers
+- **[Provider Reference](../reference/PROVIDER_REFERENCE.md)** — All 338 providers
 - **[MCP Server](./MCP-SERVER.md)** — Model Context Protocol integration
 - **[A2A Server](./A2A-SERVER.md)** — Agent-to-Agent protocol
 - **[Cloud Agent](./CLOUD_AGENT.md)** — Cloud-based agents

docs/frameworks/AGENTBRIDGE.md

@@ -22,7 +22,7 @@ When an IDE agent (e.g., GitHub Copilot, Cursor, Claude Code) makes an API call,
 
 This means you can:
 
-- **Reroute any agent to any provider**: Copilot talking to OpenAI? Redirect it to Anthropic Claude, Gemini, or any of OmniRoute's 226+ providers.
+- **Reroute any agent to any provider**: Copilot talking to OpenAI? Redirect it to Anthropic Claude, Gemini, or any of OmniRoute's 338 providers.
 - **Apply model mappings**: `gemini-3-flash` → `claude-sonnet-4.7` transparently at the handler level.
 - **Observe all agent traffic**: every intercepted request is published to the [Traffic Inspector](./TRAFFIC_INSPECTOR.md).
 - **Apply OmniRoute resilience**: combo routing, circuit breakers, fallbacks, and cost tracking work for IDE agent traffic too.

docs/frameworks/AGENT_PROTOCOLS_GUIDE.md

@@ -183,7 +183,7 @@ Both have "long-running tasks" but at different layers:
 curl http://localhost:20128/.well-known/agent.json
 ```
 
-Returns the Agent Card with all 5 skills, transports, and version.
+Returns the Agent Card with all 6 skills, transports, and version.
 
 ### Call OmniRoute as an A2A agent
 

docs/frameworks/MCP-SERVER.md

@@ -6,7 +6,7 @@ lastUpdated: 2026-06-28
 
 # OmniRoute MCP Server Documentation
 
-> Model Context Protocol server with 104 tools across routing, cache, compression, memory, skills, proxy, pool, and context source operations.
+> Model Context Protocol server with 105 tools across routing, cache, compression, memory, skills, proxy, pool, and context source operations.
 >
 > Source of truth: `open-sse/mcp-server/server.ts` computes **104 unique tools** with `countUniqueMcpTools()`: 42 canonical definitions (including the six CCR lifecycle tools and the agent-skills trio), plus memory (3), skills (4), GitHub skills (3), pool (6), gamification (8), plugins (8), Notion (6), Obsidian (22), and two RTK-only compression tools.
 
@@ -369,7 +369,7 @@ MCP tool, prompt, and resource registries can compress descriptions at registrat
 
 Description compression shrinks each tool's metadata; **tool-cardinality reduction** goes one step further by reducing _how many_ tools are announced at all. Advertising fewer tools in the `tools/list` manifest cuts the per-request token cost the client's model pays for the tool catalog ("layer 5" compression). The implementation is a pure, stateless filter in `open-sse/mcp-server/toolCardinality.ts` (`reduceToolManifest`), wired into the registration loop in `createMcpServer()` (`open-sse/mcp-server/server.ts`).
 
-**Opt-in, off by default.** The filter only runs when at least one of two environment variables is set; with neither set, all 104 tools are announced unchanged.
+**Opt-in, off by default.** The filter only runs when at least one of two environment variables is set; with neither set, all 105 tools are announced unchanged.
 
 | Variable         | Mode                                                                                    |
 | :--------------- | :-------------------------------------------------------------------------------------- |

docs/frameworks/MEMORY.md

@@ -888,3 +888,228 @@ To leave it off, simply keep `autoSummarize` at its default (`false`).
 0 3 * * * curl -X POST http://localhost:20128/api/memory/summarize \
   -H "Authorization: Bearer $OMNIROUTE_KEY"
 ```
+
+---
+
+## MemoryBackend Provider Pattern
+
+> **Source of truth:** `src/lib/memory/backend.ts`, `src/lib/memory/genericBackend.ts`, `src/lib/memory/manager.ts`
+> **Tests:** `src/lib/memory/__tests__/generic-backend.test.ts`
+
+The MemoryBackend provider pattern introduces a **pluggable backend abstraction layer** over the existing memory engine. Instead of being tied to a single storage implementation, the memory system now supports multiple backends (SQLite, Obsidian, Notion, custom HTTP backends) with configurable primary/fallback routing.
+
+### Architecture
+
+```
+┌──────────────────────────────────────────────────────────┐
+│                    API Routes                             │
+│            (src/app/api/memory/route.ts)                  │
+└──────────────────────┬───────────────────────────────────┘
+                       │
+┌──────────────────────▼───────────────────────────────────┐
+│                   MemoryManager                           │
+│           Singleton orchestrator (manager.ts)             │
+│                                                          │
+│  Primary ──► Backend A  (e.g. SQLite)                    │
+│  Fallback ─► Backend B  (e.g. Obsidian)                  │
+│             Backend C  (e.g. Notion via GenericBackend)   │
+└──────────────────────┬───────────────────────────────────┘
+                       │
+        ┌──────────────┼──────────────┐
+        ▼              ▼              ▼
+┌────────────┐ ┌────────────┐ ┌──────────────────┐
+│ SQLite     │ │ Obsidian   │ │ GenericMemory    │
+│ Backend    │ │ Backend    │ │ Backend (HTTP)   │
+└────────────┘ └────────────┘ └──────────────────┘
+```
+
+#### Core Interface (`backend.ts`)
+
+Every backend must implement the `MemoryBackend` interface:
+
+```typescript
+interface MemoryBackend {
+  readonly id: string;
+  readonly displayName: string;
+
+  // CRUD
+  create(input: CreateMemoryInput): Promise<Memory>;
+  get(id: string): Promise<Memory | null>;
+  update(id: string, updates: Partial<...>): Promise<boolean>;
+  delete(id: string): Promise<boolean>;
+  list(filter: MemoryFilter): Promise<{ data: Memory[]; total: number; byType: Record<string, number> }>;
+
+  // Search
+  search(config: SearchConfig): Promise<Memory[]>;
+
+  // Health
+  health(): Promise<HealthCheckResult>;
+
+  // Lifecycle (optional)
+  initialize?(): Promise<void>;
+  shutdown?(): Promise<void>;
+}
+```
+
+#### MemoryManager (`manager.ts`)
+
+Singleton orchestrator that:
+
+- **Registers** backends via `register(backend)` — called at boot from `index.ts`
+- **Configures** primary + fallback via `configure(primary, fallbacks)`
+- **Routes** CRUD/search to the primary, with fallback chain on failure
+- **Health checks** all backends periodically
+
+**Fallback behavior:**
+
+| Operation | Primary              | Fallbacks               |
+| --------- | -------------------- | ----------------------- |
+| `create`  | ✅ Primary only      | ❌                      |
+| `get`     | ✅ Try primary first | ✅ Fallback if null     |
+| `update`  | ✅ Primary only      | ✅ Fire-and-forget sync |
+| `delete`  | ✅ Primary only      | ✅ Fire-and-forget sync |
+| `list`    | ✅ Primary only      | ❌                      |
+| `search`  | ✅ Primary first     | ✅ Fallback on error    |
+
+#### GenericMemoryBackend (`genericBackend.ts`)
+
+A generic HTTP connector that adapts any REST API into a MemoryBackend. Useful for:
+
+- **Notion** — connect via Notion API
+- **Obsidian** — connect via Obsidian Local REST API
+- **Custom backends** — any service that exposes a RESTful memory API
+
+**Configuration:**
+
+```typescript
+interface GenericBackendConfig {
+  baseUrl: string;           // Base URL of the backend API
+  apiKey?: string;           // Bearer token for auth
+  headers?: Record<string, string>;  // Custom HTTP headers
+  timeout?: number;          // Request timeout (default: 30000ms)
+  backendType?: string;      // For logging
+
+  // Endpoint overrides (defaults use REST conventions)
+  endpoints?: {
+    search?: string;   // default: "/memories/search"
+    create?: string;   // default: "/memories"
+    list?: string;     // default: "/memories"
+    get?: string;      // default: "/memories/{id}"
+    update?: string;   // default: "/memories/{id}"
+    delete?: string;   // default: "/memories/{id}"
+    health?: string;   // default: "/health"
+  };
+
+  // Query parameter name mappings
+  queryParams?: {
+    query?/apiKeyId?/limit?/offset?/strategy?/maxTokens?/type?/sessionId?/orderBy?/orderDir?/options?
+  };
+
+  // Path parameter name mappings
+  pathParams?: {
+    id?/memoryId?
+  };
+}
+```
+
+**Known backends** are pre-configured in `KNOWN_BACKENDS`:
+
+```typescript
+createKnownBackend("obsidian"); // → GenericMemoryBackend pointed at localhost:27123
+createKnownBackend("notion"); // → GenericMemoryBackend pointed at api.notion.com/v1
+```
+
+#### Built-in Backends
+
+##### SQLiteBackend (`sqliteBackend.ts`)
+
+The default primary backend. Wraps the existing SQLite-based memory store using `src/lib/memory/store.ts`. Automatically registered at boot.
+
+```typescript
+import { sqliteBackend } from "./sqliteBackend";
+memoryManager.register(sqliteBackend);
+```
+
+##### ObsidianBackend (`obsidianBackend.ts`)
+
+Wraps the existing Obsidian integration (`src/lib/memory/obsidianBackend.ts`). Connects to an Obsidian vault via the Obsidian Local REST API.
+
+### Settings
+
+Memory backend settings are stored in the app settings table and managed via `src/lib/memory/settings.ts`:
+
+| Setting           | Env/Config Key           | Default    | Description                  |
+| ----------------- | ------------------------ | ---------- | ---------------------------- |
+| Primary backend   | `memoryPrimaryBackend`   | `"sqlite"` | ID of the primary backend    |
+| Fallback backends | `memoryFallbackBackends` | `[]`       | Ordered fallback backend IDs |
+| Backend configs   | `memoryBackendConfigs`   | `{}`       | Per-backend config overrides |
+
+Settings are normalized via `normalizeMemorySettings()` and cached at `getMemorySettings()`.
+
+### Initialization Flow
+
+```
+App bootstrap
+  → index.ts imports (side-effect): registers SQLiteBackend
+  → initMemoryBackends() called from app lifecycle:
+      1. Load settings (getMemorySettings)
+      2. Configure primary + fallback
+      3. Initialize all backends (health check)
+      4. Ready for requests
+```
+
+### Adding a New Backend
+
+1. **Implement `MemoryBackend`** interface in `src/lib/memory/<name>Backend.ts`
+2. **Export** from `src/lib/memory/index.ts`
+3. **Register** with `memoryManager.register(yourBackend)` at boot
+4. **Configure** via settings: set `memoryPrimaryBackend` to your backend ID
+5. **Test** with `src/lib/memory/__tests__/generic-backend.test.ts` as reference
+
+#### Example: Brain Backend
+
+```typescript
+import { createGenericMemoryBackend } from "./genericBackend";
+
+const brainBackend = createGenericMemoryBackend("brain", "BK-Brain", {
+  baseUrl: process.env.BRAIN_API_URL || "http://localhost:9099",
+  apiKey: process.env.BRAIN_API_KEY,
+  endpoints: {
+    search: "/api/memory/search",
+    create: "/api/memory",
+    health: "/api/health",
+  },
+});
+
+memoryManager.register(brainBackend);
+```
+
+### Verification
+
+#### Unit tests
+
+```bash
+npx vitest run src/lib/memory/__tests__/generic-backend.test.ts --reporter=verbose
+```
+
+Expected output: **26 tests, all passing** covering:
+
+- Constructor (2)
+- Health check (4) — success, failure 500, network error, latency
+- Initialize (2) — success, failure
+- Create (2) — default endpoint, custom endpoint
+- Get (4) — success, 404 → null, non-404 throw, custom path params
+- Update (2) — success, 404 → false
+- Delete (2) — success, 404 → false
+- List (2) — query params, custom param names
+- Search (3) — query params, custom endpoint, options serialization
+- Auth headers (2) — Bearer token, custom headers
+- Factory (1)
+
+#### Type check
+
+```bash
+npm run typecheck:core
+```
+
+Expected: **0 errors**.

docs/frameworks/MEMORY_BACKEND.md

@@ -1,228 +0,0 @@
----
-title: "MemoryBackend Provider Pattern"
-version: 3.8.49
-lastUpdated: 2026-07-28
----
-
-# MemoryBackend Provider Pattern
-
-> **Source of truth:** `src/lib/memory/backend.ts`, `src/lib/memory/genericBackend.ts`, `src/lib/memory/manager.ts`
-> **Tests:** `src/lib/memory/__tests__/generic-backend.test.ts`
-
-The MemoryBackend provider pattern introduces a **pluggable backend abstraction layer** over the existing memory engine. Instead of being tied to a single storage implementation, the memory system now supports multiple backends (SQLite, Obsidian, Notion, custom HTTP backends) with configurable primary/fallback routing.
-
-## Architecture
-
-```
-┌──────────────────────────────────────────────────────────┐
-│                    API Routes                             │
-│            (src/app/api/memory/route.ts)                  │
-└──────────────────────┬───────────────────────────────────┘
-                       │
-┌──────────────────────▼───────────────────────────────────┐
-│                   MemoryManager                           │
-│           Singleton orchestrator (manager.ts)             │
-│                                                          │
-│  Primary ──► Backend A  (e.g. SQLite)                    │
-│  Fallback ─► Backend B  (e.g. Obsidian)                  │
-│             Backend C  (e.g. Notion via GenericBackend)   │
-└──────────────────────┬───────────────────────────────────┘
-                       │
-        ┌──────────────┼──────────────┐
-        ▼              ▼              ▼
-┌────────────┐ ┌────────────┐ ┌──────────────────┐
-│ SQLite     │ │ Obsidian   │ │ GenericMemory    │
-│ Backend    │ │ Backend    │ │ Backend (HTTP)   │
-└────────────┘ └────────────┘ └──────────────────┘
-```
-
-### Core Interface (`backend.ts`)
-
-Every backend must implement the `MemoryBackend` interface:
-
-```typescript
-interface MemoryBackend {
-  readonly id: string;
-  readonly displayName: string;
-
-  // CRUD
-  create(input: CreateMemoryInput): Promise<Memory>;
-  get(id: string): Promise<Memory | null>;
-  update(id: string, updates: Partial<...>): Promise<boolean>;
-  delete(id: string): Promise<boolean>;
-  list(filter: MemoryFilter): Promise<{ data: Memory[]; total: number; byType: Record<string, number> }>;
-
-  // Search
-  search(config: SearchConfig): Promise<Memory[]>;
-
-  // Health
-  health(): Promise<HealthCheckResult>;
-
-  // Lifecycle (optional)
-  initialize?(): Promise<void>;
-  shutdown?(): Promise<void>;
-}
-```
-
-### MemoryManager (`manager.ts`)
-
-Singleton orchestrator that:
-
-- **Registers** backends via `register(backend)` — called at boot from `index.ts`
-- **Configures** primary + fallback via `configure(primary, fallbacks)`
-- **Routes** CRUD/search to the primary, with fallback chain on failure
-- **Health checks** all backends periodically
-
-**Fallback behavior:**
-
-| Operation | Primary              | Fallbacks               |
-| --------- | -------------------- | ----------------------- |
-| `create`  | ✅ Primary only      | ❌                      |
-| `get`     | ✅ Try primary first | ✅ Fallback if null     |
-| `update`  | ✅ Primary only      | ✅ Fire-and-forget sync |
-| `delete`  | ✅ Primary only      | ✅ Fire-and-forget sync |
-| `list`    | ✅ Primary only      | ❌                      |
-| `search`  | ✅ Primary first     | ✅ Fallback on error    |
-
-### GenericMemoryBackend (`genericBackend.ts`)
-
-A generic HTTP connector that adapts any REST API into a MemoryBackend. Useful for:
-
-- **Notion** — connect via Notion API
-- **Obsidian** — connect via Obsidian Local REST API
-- **Custom backends** — any service that exposes a RESTful memory API
-
-**Configuration:**
-
-```typescript
-interface GenericBackendConfig {
-  baseUrl: string;           // Base URL of the backend API
-  apiKey?: string;           // Bearer token for auth
-  headers?: Record<string, string>;  // Custom HTTP headers
-  timeout?: number;          // Request timeout (default: 30000ms)
-  backendType?: string;      // For logging
-
-  // Endpoint overrides (defaults use REST conventions)
-  endpoints?: {
-    search?: string;   // default: "/memories/search"
-    create?: string;   // default: "/memories"
-    list?: string;     // default: "/memories"
-    get?: string;      // default: "/memories/{id}"
-    update?: string;   // default: "/memories/{id}"
-    delete?: string;   // default: "/memories/{id}"
-    health?: string;   // default: "/health"
-  };
-
-  // Query parameter name mappings
-  queryParams?: {
-    query?/apiKeyId?/limit?/offset?/strategy?/maxTokens?/type?/sessionId?/orderBy?/orderDir?/options?
-  };
-
-  // Path parameter name mappings
-  pathParams?: {
-    id?/memoryId?
-  };
-}
-```
-
-**Known backends** are pre-configured in `KNOWN_BACKENDS`:
-
-```typescript
-createKnownBackend("obsidian"); // → GenericMemoryBackend pointed at localhost:27123
-createKnownBackend("notion"); // → GenericMemoryBackend pointed at api.notion.com/v1
-```
-
-### Built-in Backends
-
-#### SQLiteBackend (`sqliteBackend.ts`)
-
-The default primary backend. Wraps the existing SQLite-based memory store using `src/lib/memory/store.ts`. Automatically registered at boot.
-
-```typescript
-import { sqliteBackend } from "./sqliteBackend";
-memoryManager.register(sqliteBackend);
-```
-
-#### ObsidianBackend (`obsidianBackend.ts`)
-
-Wraps the existing Obsidian integration (`src/lib/memory/obsidianBackend.ts`). Connects to an Obsidian vault via the Obsidian Local REST API.
-
-## Settings
-
-Memory backend settings are stored in the app settings table and managed via `src/lib/memory/settings.ts`:
-
-| Setting           | Env/Config Key           | Default    | Description                  |
-| ----------------- | ------------------------ | ---------- | ---------------------------- |
-| Primary backend   | `memoryPrimaryBackend`   | `"sqlite"` | ID of the primary backend    |
-| Fallback backends | `memoryFallbackBackends` | `[]`       | Ordered fallback backend IDs |
-| Backend configs   | `memoryBackendConfigs`   | `{}`       | Per-backend config overrides |
-
-Settings are normalized via `normalizeMemorySettings()` and cached at `getMemorySettings()`.
-
-## Initialization Flow
-
-```
-App bootstrap
-  → index.ts imports (side-effect): registers SQLiteBackend
-  → initMemoryBackends() called from app lifecycle:
-      1. Load settings (getMemorySettings)
-      2. Configure primary + fallback
-      3. Initialize all backends (health check)
-      4. Ready for requests
-```
-
-## Adding a New Backend
-
-1. **Implement `MemoryBackend`** interface in `src/lib/memory/<name>Backend.ts`
-2. **Export** from `src/lib/memory/index.ts`
-3. **Register** with `memoryManager.register(yourBackend)` at boot
-4. **Configure** via settings: set `memoryPrimaryBackend` to your backend ID
-5. **Test** with `src/lib/memory/__tests__/generic-backend.test.ts` as reference
-
-### Example: Brain Backend
-
-```typescript
-import { createGenericMemoryBackend } from "./genericBackend";
-
-const brainBackend = createGenericMemoryBackend("brain", "BK-Brain", {
-  baseUrl: process.env.BRAIN_API_URL || "http://localhost:9099",
-  apiKey: process.env.BRAIN_API_KEY,
-  endpoints: {
-    search: "/api/memory/search",
-    create: "/api/memory",
-    health: "/api/health",
-  },
-});
-
-memoryManager.register(brainBackend);
-```
-
-## Verification
-
-### Unit tests
-
-```bash
-npx vitest run src/lib/memory/__tests__/generic-backend.test.ts --reporter=verbose
-```
-
-Expected output: **26 tests, all passing** covering:
-
-- Constructor (2)
-- Health check (4) — success, failure 500, network error, latency
-- Initialize (2) — success, failure
-- Create (2) — default endpoint, custom endpoint
-- Get (4) — success, 404 → null, non-404 throw, custom path params
-- Update (2) — success, 404 → false
-- Delete (2) — success, 404 → false
-- List (2) — query params, custom param names
-- Search (3) — query params, custom endpoint, options serialization
-- Auth headers (2) — Bearer token, custom headers
-- Factory (1)
-
-### Type check
-
-```bash
-npm run typecheck:core
-```
-
-Expected: **0 errors**.

docs/frameworks/OPEN_SSE_ARCHITECTURE.md

@@ -228,7 +228,7 @@ export async function handleComboChat(body, comboId): Promise<ChatResult> {
 }
 ```
 
-Supports **17 routing strategies** (see `src/shared/constants/routingStrategies.ts`):
+Supports **19 routing strategies** (see `src/shared/constants/routingStrategies.ts`):
 
 | Strategy            | Behavior                                                                  |
 | ------------------- | ------------------------------------------------------------------------- |
@@ -252,7 +252,7 @@ Supports **17 routing strategies** (see `src/shared/constants/routingStrategies.
 
 ### base.ts (1170 LOC)
 
-The **abstract executor** that all 67 executors extend. It contains:
+The **abstract executor** that all 101 executors extend. It contains:
 
 - `buildUrl()` — default URL construction (subclasses override for custom)
 - `buildHeaders()` — default headers (auth, content-type)
@@ -368,7 +368,7 @@ const result = await executor.execute({
 });
 ````
 
-The factory is generated from `config/providerRegistry.ts` which lists all 212+ providers and their executor class.
+The factory is generated from `config/providerRegistry.ts` which lists all 338 providers and their executor class.
 
 ---
 
@@ -408,7 +408,7 @@ Common translations:
 
 - **30+ tools** (provider management, combos, memory, cache, compression, 1proxy, skills)
 - **3 transports**: stdio, SSE, Streamable HTTP
-- **13 scopes** for fine-grained authorization
+- **31 scopes** for fine-grained authorization
 
 ### Tool Registration
 
@@ -487,7 +487,7 @@ This handles:
 
 | File                          | Purpose                           |
 | ----------------------------- | --------------------------------- |
-| `providerRegistry.ts`         | 212+ provider definitions         |
+| `providerRegistry.ts`         | 338 provider definitions          |
 | `providerModels.ts`           | Model aliases, format mapping     |
 | `constants.ts`                | Timeouts, limits, status codes    |
 | `defaultThinkingSignature.ts` | Default Claude thinking signature |

docs/frameworks/meta.json

@@ -5,17 +5,26 @@
     "A2A-SERVER",
     "AGENT_PROTOCOLS_GUIDE",
     "ACP",
+    "AGENT-SKILLS",
+    "AGENTBRIDGE",
     "CLOUD_AGENT",
+    "EMBEDDED-SERVICES",
     "EVALS",
     "GAMIFICATION",
+    "LOCAL_CORPUS_CONTEXT",
     "MEMORY",
     "NOTION_CONTEXT",
     "OBSIDIAN_CONTEXT",
     "OPENCODE",
+    "OPEN_SSE_ARCHITECTURE",
+    "PLAYGROUND_STUDIO",
     "PLUGIN_MARKETPLACE",
     "PLUGINS",
     "PLUGIN_SDK",
+    "RADAR",
+    "SEARCH_TOOLS_STUDIO",
     "SKILLS",
+    "TRAFFIC_INSPECTOR",
     "WEBHOOKS"
   ]
 }

docs/getting-started/AUTO-COMBO-GUIDE.md

@@ -201,7 +201,7 @@ Round-robin cycles through providers in order. Auto-combo **scores each provider
 
 - **[Connect a Provider](./PROVIDERS-GUIDE.md)** — Add your first AI provider
 - **[Free Tiers Guide](./FREE-TIERS-GUIDE.md)** — Get free AI with no credit card
-- **[Troubleshooting](./TROUBLESHOOTING.md)** — Fix common issues
+- **[Troubleshooting](../guides/TROUBLESHOOTING.md)** — Fix common issues
 - **[Technical Reference](../routing/AUTO-COMBO.md)** — Deep dive into the scoring algorithm
 
 ---

docs/getting-started/FREE-TIERS-GUIDE.md

@@ -272,5 +272,5 @@ No catch! Providers offer free tiers to attract users. OmniRoute just makes it e
 
 - **[Auto-Combo Guide](./AUTO-COMBO-GUIDE.md)** — Let OmniRoute pick the best AI for you
 - **[Providers Guide](./PROVIDERS-GUIDE.md)** — Connect more providers
-- **[Troubleshooting](./TROUBLESHOOTING.md)** — Fix common issues
+- **[Troubleshooting](../guides/TROUBLESHOOTING.md)** — Fix common issues
 - **[Free Tiers Reference](../reference/FREE_TIERS.md)** — Full list of free tiers

docs/getting-started/PROVIDERS-GUIDE.md

@@ -237,5 +237,5 @@ Go to Providers → click on the provider → click **Disconnect**.
 
 - **[Auto-Combo Guide](./AUTO-COMBO-GUIDE.md)** — Let OmniRoute pick the best AI for you
 - **[Free Tiers Guide](./FREE-TIERS-GUIDE.md)** — Get free AI with no credit card
-- **[Troubleshooting](./TROUBLESHOOTING.md)** — Fix common issues
+- **[Troubleshooting](../guides/TROUBLESHOOTING.md)** — Fix common issues
 - **[Provider Reference](../reference/PROVIDER_REFERENCE.md)** — Full list of 226 providers

docs/getting-started/QUICK-START.md

@@ -153,7 +153,7 @@ You can see the details of the request by clicking [Monitoring/Logs](http://loca
 - **[Auto-Combo Guide](./AUTO-COMBO-GUIDE.md)** — Let OmniRoute pick the best AI for you
 - **[Providers Guide](./PROVIDERS-GUIDE.md)** — Connect more providers (free and paid)
 - **[Free Tiers Guide](./FREE-TIERS-GUIDE.md)** — Get free AI with no credit card
-- **[Troubleshooting](./TROUBLESHOOTING.md)** — Fix common issues
+- **[Troubleshooting](../guides/TROUBLESHOOTING.md)** — Fix common issues
 
 ---
 
@@ -183,6 +183,6 @@ OmniRoute automatically skips failed providers and tries the next one. You don't
 
 ## Need Help?
 
-- **[Troubleshooting](./TROUBLESHOOTING.md)** — Common issues and fixes
+- **[Troubleshooting](../guides/TROUBLESHOOTING.md)** — Common issues and fixes
 - **[Discord](https://discord.gg/U47eFqAXCn)** — Community support
 - **[GitHub Issues](https://github.com/diegosouzapw/OmniRoute/issues)** — Report bugs

docs/getting-started/TROUBLESHOOTING.md

@@ -1,498 +0,0 @@
----
-title: "Troubleshooting"
-version: 3.8.40
-lastUpdated: 2026-06-28
----
-
-# Troubleshooting
-
-> **For Users**: Looking for quick fixes? See the [Quick Reference](#quick-reference) below.
-
-🌐 **Languages:** 🇺🇸 [English](./TROUBLESHOOTING.md) | 🇧🇷 [Português (Brasil)](../i18n/pt-BR/docs/guides/TROUBLESHOOTING.md) | 🇪🇸 [Español](../i18n/es/docs/guides/TROUBLESHOOTING.md) | 🇫🇷 [Français](../i18n/fr/docs/guides/TROUBLESHOOTING.md) | 🇮🇹 [Italiano](../i18n/it/docs/guides/TROUBLESHOOTING.md) | 🇷🇺 [Русский](../i18n/ru/docs/guides/TROUBLESHOOTING.md) | 🇨🇳 [中文 (简体)](../i18n/zh-CN/docs/guides/TROUBLESHOOTING.md) | 🇩🇪 [Deutsch](../i18n/de/docs/guides/TROUBLESHOOTING.md) | 🇮🇳 [हिन्दी](../i18n/in/docs/guides/TROUBLESHOOTING.md) | 🇹🇭 [ไทย](../i18n/th/docs/guides/TROUBLESHOOTING.md) | 🇺🇦 [Українська](../i18n/uk-UA/docs/guides/TROUBLESHOOTING.md) | 🇸🇦 [العربية](../i18n/ar/docs/guides/TROUBLESHOOTING.md) | 🇯🇵 [日本語](../i18n/ja/docs/guides/TROUBLESHOOTING.md) | 🇻🇳 [Tiếng Việt](../i18n/vi/docs/guides/TROUBLESHOOTING.md) | 🇧🇬 [Български](../i18n/bg/docs/guides/TROUBLESHOOTING.md) | 🇩🇰 [Dansk](../i18n/da/docs/guides/TROUBLESHOOTING.md) | 🇫🇮 [Suomi](../i18n/fi/docs/guides/TROUBLESHOOTING.md) | 🇮🇱 [עברית](../i18n/he/docs/guides/TROUBLESHOOTING.md) | 🇭🇺 [Magyar](../i18n/hu/docs/guides/TROUBLESHOOTING.md) | 🇮🇩 [Bahasa Indonesia](../i18n/id/docs/guides/TROUBLESHOOTING.md) | 🇰🇷 [한국어](../i18n/ko/docs/guides/TROUBLESHOOTING.md) | 🇲🇾 [Bahasa Melayu](../i18n/ms/docs/guides/TROUBLESHOOTING.md) | 🇳🇱 [Nederlands](../i18n/nl/docs/guides/TROUBLESHOOTING.md) | 🇳🇴 [Norsk](../i18n/no/docs/guides/TROUBLESHOOTING.md) | 🇵🇹 [Português (Portugal)](../i18n/pt/docs/guides/TROUBLESHOOTING.md) | 🇷🇴 [Română](../i18n/ro/docs/guides/TROUBLESHOOTING.md) | 🇵🇱 [Polski](../i18n/pl/docs/guides/TROUBLESHOOTING.md) | 🇸🇰 [Slovenčina](../i18n/sk/docs/guides/TROUBLESHOOTING.md) | 🇸🇪 [Svenska](../i18n/sv/docs/guides/TROUBLESHOOTING.md) | 🇵🇭 [Filipino](../i18n/phi/docs/guides/TROUBLESHOOTING.md) | 🇨🇿 [Čeština](../i18n/cs/docs/guides/TROUBLESHOOTING.md)
-
-Common problems and solutions for OmniRoute.
-
----
-
-## Quick Reference
-
-**New to OmniRoute?** Start here — these solve 90% of problems:
-
-| I see this              | What it means                       | What to do                                                                                        |
-| ----------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------- |
-| "Can't connect"         | OmniRoute isn't running             | Run `omniroute` or `docker restart omniroute`                                                     |
-| "Invalid API key"       | Your key is wrong or expired        | Re-copy the key from the provider's website                                                       |
-| "Rate limit exceeded"   | You're sending too many requests    | Wait 1 minute, or use `model: "auto"` for automatic fallback                                      |
-| "Quota exceeded"        | You've used up your free/paid quota | Connect more providers, or use free providers (Kiro, Pollinations)                                |
-| "Slow responses"        | Provider is busy or far away        | Use `model: "auto/fast"` or connect a faster provider (Groq, Cerebras)                            |
-| "Wrong provider used"   | `auto` picked a different provider  | That's normal! `auto` picks the best one. Force a specific provider with `model: "openai/gpt-4o"` |
-| "502 Bad Gateway"       | Provider is down                    | Wait and retry, or use `model: "auto"` to switch providers                                        |
-| "401 Unauthorized"      | Your credentials are wrong          | Check your API key or re-authenticate with OAuth                                                  |
-| "429 Too Many Requests" | Rate limited                        | Wait 1 minute, or connect more providers                                                          |
-
-**Still stuck?** See the [Quick Fixes](#quick-fixes) below, or ask on [Discord](https://discord.gg/U47eFqAXCn).
-
----
-
-## npm install Warnings (ERESOLVE / peer / deprecated)
-
-When you run `npm install -g omniroute`, you may see a wall of warnings like `npm warn ERESOLVE`, peer-dependency notices, and `deprecated` messages. **These are expected and harmless.** Your install succeeded if you see `added <N> packages` in the output.
-
-The warnings come from stale peer-dependency ranges in third-party packages OmniRoute doesn't control:
-
-1. **`marked-terminal` wants `marked >=1 <16`, found `marked@18`** — works fine in practice; the upstream peer range is just stale.
-2. **`deprecated prebuild-install@7.1.3`** — the native-binary fetch helper. Only relevant later if a web-cookie provider reports a missing `tls-client-node` native binary (a separate issue, not caused by this warning).
-
-**No action needed** — the warnings cannot be fully silenced without forking upstream packages.
-
----
-
-## Quick Fixes
-
-| Problem                                             | Solution                                                                                                                                                 |
-| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| First login not working                             | Set `INITIAL_PASSWORD` in `.env` (no hardcoded default)                                                                                                  |
-| Dashboard opens on wrong port                       | Set `PORT=20128` and `NEXT_PUBLIC_BASE_URL=http://localhost:20128`                                                                                       |
-| No logs written to disk                             | Set `APP_LOG_TO_FILE=true` and verify call log capture is enabled                                                                                        |
-| EACCES: permission denied                           | Set `DATA_DIR=/path/to/writable/dir` to override `~/.omniroute`                                                                                          |
-| Routing strategy not saving                         | Update to the latest v3.x release (Zod schema fix for settings persistence shipped in earlier versions)                                                  |
-| Login crash / blank page                            | Check Node.js version — see [Node.js Compatibility](#nodejs-compatibility) below                                                                         |
-| `dlopen` / `slice is not valid mach-o file` (macOS) | Run `cd $(npm root -g)/omniroute/app && npm rebuild better-sqlite3 && omniroute` — see [macOS native module rebuild](#macos-native-module-rebuild) below |
-| Proxy "fetch failed"                                | Ensure proxy config is set at the correct level — see [Proxy Issues](#proxy-issues) below                                                                |
-
----
-
-## Node.js Compatibility
-
-<a name="nodejs-compatibility"></a>
-
-### Login page crashes or shows "Module self-registration" error
-
-**Cause:** You are running a Node.js version outside OmniRoute's approved secure runtime floor. The most common case is running an older Node 22 or 24 patch level that falls below the patched security floor OmniRoute requires.
-
-**Symptoms:**
-
-- Login page shows a blank screen or a server error
-- Console shows `Error: Module did not self-register` or similar native binding errors
-- The login page shows an **orange warning banner** with your Node version if the runtime is outside the supported secure policy
-
-**Fix:**
-
-1. Install a supported Node.js LTS release (recommended: Node.js 24.x):
-   ```bash
-   nvm install 24
-   nvm use 24
-   ```
-2. Verify your version: `node --version` should show `v24.0.0` or newer on the 24.x LTS line
-3. Reinstall OmniRoute: `npm install -g omniroute`
-4. Restart: `omniroute`
-
-> **Supported secure versions:** `>=22.22.2 <23` or `>=24.0.0 <27`. Node.js 24.x LTS (Krypton) and Node.js 26 are fully supported.
-
-### macOS: `dlopen` / "slice is not valid mach-o file"
-
-<a name="macos-native-module-rebuild"></a>
-
-**Cause:** After a global `npm install -g omniroute`, the `better-sqlite3` native binary inside the package may have been compiled for a different architecture or Node.js ABI than what is running locally. This is common on macOS (both Apple Silicon and Intel) when the pre-built binary does not match your environment.
-
-**Symptoms:**
-
-- Server fails immediately on startup with a `dlopen` error
-- Error contains `slice is not valid mach-o file`
-- Full example:
-
-```
-dlopen(/Users/<user>/.nvm/versions/node/v24.14.1/lib/node_modules/omniroute/app/node_modules/better-sqlite3/build/Release/better_sqlite3.node, 0x0001): tried: '...' (slice is not valid mach-o file)
-```
-
-**Fix — rebuild for your local environment (no Node.js downgrade required):**
-
-```bash
-cd $(npm root -g)/omniroute/app
-npm rebuild better-sqlite3
-omniroute
-```
-
-> **Note:** This recompiles the native binding against your local Node.js version and CPU architecture, resolving the binary mismatch. The officially supported runtime range is **`>=22.22.2 <23` or `>=24.0.0 <27`** (`SUPPORTED_NODE_RANGE` in `src/shared/utils/nodeRuntimeSupport.ts`, aligned with the `package.json` `engines` field). Node.js 24.x LTS (Krypton) and Node.js 26 are fully supported with `better-sqlite3` v12.x.
-
----
-
-## Proxy Issues
-
-<a name="proxy-issues"></a>
-
-### Provider validation shows "fetch failed"
-
-**Cause:** The API key validation endpoint (`POST /api/providers/validate`) was previously bypassing proxy configuration, causing failures in environments that require proxy routing.
-
-**Fix (v3.5.5+):** This is now fixed. Provider validation routes through `runWithProxyContext`, honoring provider-level and global proxy settings automatically.
-
-### Token health check fails with "fetch failed"
-
-**Cause:** Background OAuth token refresh was not resolving proxy configuration per connection.
-
-**Fix (v3.5.5+):** The token health check scheduler now resolves proxy config per connection before attempting refresh. Update to v3.5.5+.
-
-### SOCKS5 proxy returns "invalid onRequestStart method"
-
-**Cause:** On Node.js 22, the undici@8 dispatcher is incompatible with Node's built-in `fetch()` implementation.
-
-**Fix (v3.5.5+):** OmniRoute now uses undici's own `fetch()` function when a proxy dispatcher is active, ensuring consistent behavior. Update to v3.5.5+.
-
----
-
-## Provider Issues
-
-### "Language model did not provide messages"
-
-**Cause:** Provider quota exhausted.
-
-**Fix:**
-
-1. Check dashboard quota tracker
-2. Use a combo with fallback tiers
-3. Switch to cheaper/free tier
-
-### Rate Limiting
-
-**Cause:** Subscription quota exhausted.
-
-**Fix:**
-
-- Add fallback: `cc/claude-opus-4-6 → glm/glm-4.7 → if/qwen3.8-max-preview`
-- Use GLM/MiniMax as cheap backup
-
-### OAuth Token Expired
-
-OmniRoute auto-refreshes tokens. If issues persist:
-
-1. Dashboard → Provider → Reconnect
-2. Delete and re-add the provider connection
-
-### Kiro multi-account: second account invalidates the first
-
-**Cause:** Kiro's backend enforces a single active session per OIDC client registration.
-When two accounts share the same registered client (connections imported before v3.8.0),
-refreshing one account's token invalidates the other's refresh token.
-
-**Fix (v3.8.0+):** Re-import affected connections.
-Starting with v3.8.0, every new Kiro connection created via **Import Token**,
-**Google/GitHub social login**, or **Auto-Import** automatically registers its own
-dedicated OIDC client. The connection is therefore fully isolated and refreshing one
-account has no effect on any other account.
-
-Connections that were imported _before_ v3.8.0 do not carry a per-connection client
-registration. Those connections continue to use the shared social-auth refresh endpoint.
-To gain isolation, delete the old connection from Dashboard → Providers and re-add it
-via any of the three import flows.
-
-For full details and step-by-step instructions for adding two Kiro accounts side by side,
-see [`docs/guides/KIRO_SETUP.md`](../guides/KIRO_SETUP.md).
-
----
-
-## Cloud Issues
-
-### Cloud Sync Errors
-
-1. Verify `BASE_URL` points to your running instance (e.g., `http://localhost:20128`)
-2. Verify `CLOUD_URL` points to your cloud endpoint (e.g., `https://omniroute.dev`)
-3. Keep `NEXT_PUBLIC_*` values aligned with server-side values
-
-### Cloud `stream=false` Returns 500
-
-**Symptom:** `Unexpected token 'd'...` on cloud endpoint for non-streaming calls.
-
-**Cause:** Upstream returns SSE payload while client expects JSON.
-
-**Workaround:** Use `stream=true` for cloud direct calls. Local runtime includes SSE→JSON fallback.
-
-### Cloud Says Connected but "Invalid API key"
-
-1. Create a fresh key from local dashboard (`/api/keys`)
-2. Run cloud sync: Enable Cloud → Sync Now
-3. Old/non-synced keys can still return `401` on cloud
-
----
-
-## Docker Issues
-
-### CLI Tool Shows Not Installed
-
-1. Check runtime fields: `curl http://localhost:20128/api/cli-tools/runtime/codex | jq`
-2. For portable mode: use image target `runner-cli` (bundled CLIs)
-3. For host mount mode: set `CLI_EXTRA_PATHS` and mount host bin directory as read-only
-4. If `installed=true` and `runnable=false`: binary was found but failed healthcheck
-
-### Quick Runtime Validation
-
-```bash
-curl -s http://localhost:20128/api/cli-tools/codex-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-curl -s http://localhost:20128/api/cli-tools/claude-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-curl -s http://localhost:20128/api/cli-tools/openclaw-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-```
-
----
-
-## Cost Issues
-
-### High Costs
-
-1. Check usage stats in Dashboard → Usage
-2. Switch primary model to GLM/MiniMax
-3. Use free tier (Qoder, Kiro) for non-critical tasks
-4. Set cost budgets per API key: Dashboard → API Keys → Budget
-
----
-
-## Debugging
-
-### Enable Log Files
-
-Set `APP_LOG_TO_FILE=true` in your `.env` file. Application logs are written under `logs/`.
-Request artifacts are stored under `${DATA_DIR}/call_logs/` when the call log pipeline is
-enabled in settings.
-When pipeline capture is enabled, set `CALL_LOG_PIPELINE_CAPTURE_STREAM_CHUNKS=false` to omit
-stream chunk payloads, or tune `CALL_LOG_PIPELINE_MAX_SIZE_KB` to change the artifact cap in KB.
-
-### Check Provider Health
-
-```bash
-# Health dashboard
-http://localhost:20128/dashboard/health
-
-# API health check
-curl http://localhost:20128/api/monitoring/health
-```
-
-### Runtime Storage
-
-- Main state: `${DATA_DIR}/storage.sqlite` (providers, combos, aliases, keys, settings)
-- Usage: SQLite tables in `storage.sqlite` (`usage_history`, `call_logs`, `proxy_logs`) + optional `${DATA_DIR}/call_logs/`
-- Application logs: `<repo>/logs/...` (when `APP_LOG_TO_FILE=true`)
-- Call log artifacts: `${DATA_DIR}/call_logs/YYYY-MM-DD/...` when the call log pipeline is enabled
-
-The Request Logs page's **Clean history** action clears `call_logs`, legacy
-`request_detail_logs`, and the local `${DATA_DIR}/call_logs/` artifact directory.
-
----
-
-## Circuit Breaker Issues
-
-### Provider stuck in OPEN state
-
-When a provider's circuit breaker is OPEN, requests are blocked until the cooldown expires.
-
-**Fix:**
-
-1. Go to **Dashboard → Settings → Resilience**
-2. Check the circuit breaker card for the affected provider
-3. Click **Reset All** to clear all breakers, or wait for the cooldown to expire
-4. Verify the provider is actually available before resetting
-
-### Provider keeps tripping the circuit breaker
-
-If a provider repeatedly enters OPEN state:
-
-1. Check **Dashboard → Health → Provider Health** for the failure pattern
-2. Go to **Settings → Resilience → Provider Profiles** and increase the failure threshold
-3. Check if the provider has changed API limits or requires re-authentication
-4. Review latency telemetry — high latency may cause timeout-based failures
-
----
-
-## Audio Transcription Issues
-
-### "Unsupported model" error
-
-- Ensure you're using the correct prefix: `deepgram/nova-3` or `assemblyai/best`
-- Verify the provider is connected in **Dashboard → Providers**
-
-### Transcription returns empty or fails
-
-- Check supported audio formats: `mp3`, `wav`, `m4a`, `flac`, `ogg`, `webm`
-- Verify file size is within provider limits (typically < 25MB)
-- Check provider API key validity in the provider card
-
----
-
-## Translator Debugging
-
-Use **Dashboard → Translator** to debug format translation issues:
-
-| Mode             | When to Use                                                                                  |
-| ---------------- | -------------------------------------------------------------------------------------------- |
-| **Playground**   | Compare input/output formats side by side — paste a failing request to see how it translates |
-| **Chat Tester**  | Send live messages and inspect the full request/response payload including headers           |
-| **Test Bench**   | Run batch tests across format combinations to find which translations are broken             |
-| **Live Monitor** | Watch real-time request flow to catch intermittent translation issues                        |
-
-### Common format issues
-
-- **Thinking tags not appearing** — Check if the target provider supports thinking and the thinking budget setting
-- **Tool calls dropping** — Some format translations may strip unsupported fields; verify in Playground mode
-- **System prompt missing** — Claude and Gemini handle system prompts differently; check translation output
-- **SDK returns raw string instead of object** — Resolved in v1.x; response sanitizer strips non-standard fields (`x_groq`, `usage_breakdown`, etc.) that cause OpenAI SDK Pydantic validation failures. If you still see this on v3.x+, please file an issue.
-- **GLM/ERNIE rejects `system` role** — Resolved in v1.x; role normalizer automatically merges system messages into user messages for incompatible models. If you still see this on v3.x+, please file an issue.
-- **`developer` role not recognized** — Resolved in v1.x; automatically converted to `system` for non-OpenAI providers. If you still see this on v3.x+, please file an issue.
-- **`json_schema` not working with Gemini** — Resolved in v1.x; `response_format` is now converted to Gemini's `responseMimeType` + `responseSchema`. If you still see this on v3.x+, please file an issue.
-
----
-
-## Resilience Settings
-
-### Auto rate-limit not triggering
-
-- Auto rate-limit only applies to API key providers (not OAuth/subscription)
-- Verify **Settings → Resilience → Provider Profiles** has auto-rate-limit enabled
-- Check if the provider returns `429` status codes or `Retry-After` headers
-
-### Tuning exponential backoff
-
-Provider profiles support these settings:
-
-- **Base delay** — Initial wait time after first failure (default: 1s)
-- **Max delay** — Maximum wait time cap (default: 30s)
-- **Multiplier** — How much to increase delay per consecutive failure (default: 2x)
-
-### Anti-thundering herd
-
-When many concurrent requests hit a rate-limited provider, OmniRoute uses mutex + auto rate-limiting to serialize requests and prevent cascading failures. This is automatic for API key providers.
-
----
-
-## Optional RAG / LLM failure taxonomy (16 problems)
-
-Some OmniRoute users place the gateway in front of RAG or agent stacks. In those setups it is common to see a strange pattern: OmniRoute looks healthy (providers up, routing profiles ok, no rate limit alerts) but the final answer is still wrong.
-
-In practice these incidents usually come from the downstream RAG pipeline, not from the gateway itself.
-
-If you want a shared vocabulary to describe those failures you can use the WFGY ProblemMap, an external MIT license text resource that defines sixteen recurring RAG / LLM failure patterns. At a high level it covers:
-
-- retrieval drift and broken context boundaries
-- empty or stale indexes and vector stores
-- embedding versus semantic mismatch
-- prompt assembly and context window issues
-- logic collapse and overconfident answers
-- long chain and agent coordination failures
-- multi agent memory and role drift
-- deployment and bootstrap ordering problems
-
-The idea is simple:
-
-1. When you investigate a bad response, capture:
-   - user task and request
-   - route or provider combo in OmniRoute
-   - any RAG context used downstream (retrieved documents, tool calls, etc)
-2. Map the incident to one or two WFGY ProblemMap numbers (`No.1` … `No.16`).
-3. Store the number in your own dashboard, runbook, or incident tracker next to the OmniRoute logs.
-4. Use the corresponding WFGY page to decide whether you need to change your RAG stack, retriever, or routing strategy.
-
-Full text and concrete recipes live here (MIT license, text only):
-
-[WFGY ProblemMap README](https://github.com/onestardao/WFGY/blob/main/ProblemMap/README.md)
-
-You can ignore this section if you do not run RAG or agent pipelines behind OmniRoute.
-
----
-
-## v3.8.0 Known Issues
-
-Issues specific to the v3.8.0 release and their current workarounds. If a fix lands in a later patch, the entry will be updated or removed.
-
-### Devin CLI auth failures
-
-**Symptoms:**
-
-- "Devin CLI not found" or "auth failed" when invoking Devin-backed tools
-- CLI runtime check reports `installed=false`
-
-**Causes:**
-
-- `CLI_DEVIN_BIN` points to a path that does not exist
-- Devin CLI is not installed on the host
-
-**Fix:**
-
-1. Install the Devin CLI for your platform
-2. Set `CLI_DEVIN_BIN=/usr/local/bin/devin` (or the real path) in `.env`
-3. Restart OmniRoute and re-test from **Dashboard → CLI Tools**
-
-### Model cooldown stuck (manual reset)
-
-**Symptoms:**
-
-- A model stays listed in cooldown even after the expiration time has passed
-- Requests still skip the model in combo routing despite the timestamp being in the past
-
-**Manual reset:**
-
-- **Dashboard:** **Settings → Model Cooldowns** → click **Re-enable** on the affected card
-- **API:** `DELETE /api/resilience/model-cooldowns` with management auth headers
-
-### Command Code provider connection fails with 403
-
-**Symptoms:**
-
-- 403 when testing the Command Code provider connection
-- The provider card shows "unauthorized" after a fresh add
-
-**Cause:** The OAuth flow did not complete (callback not received or token not persisted).
-
-**Fix:**
-
-- Run `omniroute providers` from the CLI to re-trigger the OAuth flow, or
-- Re-run OAuth from **Dashboard → Providers → Command Code → Reconnect**
-
-### ModelScope returns aggressive 429 cooldowns
-
-**Symptoms:**
-
-- Very short or immediate cooldowns on ModelScope after a small burst of requests
-- Combo routing skips ModelScope earlier than expected
-
-**Cause:** ModelScope emits provider-specific `Retry-After` headers. v3.8.0 ships dedicated handling for those headers, so older versions misread them as generic rate-limit hints.
-
-**Fix:**
-
-- Ensure you are on v3.8.0 or later
-- Verify the `useUpstream429BreakerHints` toggle is enabled under **Settings → Resilience**
-
-### OMNIROUTE_WS_BRIDGE_SECRET missing in production
-
-**Symptoms:**
-
-- 401 on every Codex/Responses WebSocket bridge request when running on a remote production host
-- WebSocket bridge handshake closes immediately after connect
-
-**Cause:** The `OMNIROUTE_WS_BRIDGE_SECRET` env var is missing from the production environment.
-
-**Fix:**
-
-1. Generate a random secret: `openssl rand -hex 32`
-2. Set `OMNIROUTE_WS_BRIDGE_SECRET=<random-secret>` in the production server env (and any client that talks to the bridge)
-3. Restart OmniRoute
-
-### Responses API: background mode degraded to synchronous
-
-**Symptoms:**
-
-- Warning logged: `background mode degraded to synchronous`
-- A `background: true` request returns a normal synchronous response instead of a background job handle
-
-**Cause:** v3.8.0 intentionally degrades `background: true` on the Responses API to synchronous execution while emitting a warning. Full async background execution is a future deliverable.
-
-**Fix:**
-
-- Adjust the client to call without `background`, or
-- Wait for a later release that ships full async background mode (track the changelog)
-
----
-
-## Still Stuck?
-
-- **GitHub Issues**: [github.com/diegosouzapw/OmniRoute/issues](https://github.com/diegosouzapw/OmniRoute/issues)
-- **Architecture**: See [`docs/architecture/ARCHITECTURE.md`](../architecture/ARCHITECTURE.md) for internal details
-- **API Reference**: See [`docs/reference/API_REFERENCE.md`](../reference/API_REFERENCE.md) for all endpoints
-- **Health Dashboard**: Check **Dashboard → Health** for real-time system status
-- **Translator**: Use **Dashboard → Translator** to debug format issues

docs/getting-started/meta.json

@@ -6,6 +6,6 @@
     "AUTO-COMBO-GUIDE",
     "PROVIDERS-GUIDE",
     "FREE-TIERS-GUIDE",
-    "TROUBLESHOOTING"
+    "WEB-COOKIE-GUIDE"
   ]
 }

docs/guides/DOCKER_GUIDE.md

@@ -336,6 +336,57 @@ Endpoint tunnel panels (Cloudflare, Tailscale, ngrok) can be shown or hidden fro
 
 Multi-platform manifest: `linux/amd64` + `linux/arm64` native (Apple Silicon, AWS Graviton, Raspberry Pi). Docker selects the matching architecture automatically; pass `--platform linux/amd64` if you need to force AMD64 emulation on ARM hosts.
 
+### Release Channels
+
+OmniRoute publishes separate Docker channels for stable releases, active release-branch testing, and development builds.
+
+| Channel                         | Source                              | Mutability                  | Recommended use                                                                                 |
+| ------------------------------- | ----------------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------- |
+| `:<version>` / `:<version>-web` | Signed/versioned release            | Immutable                   | Production deployments that pin an exact release                                                |
+| `:latest` / `:latest-web`       | Highest stable release              | Mutable stable pointer      | Production deployments that intentionally follow stable releases                                |
+| `:next` / `:next-web`           | Current default `release/v*` branch | Mutable pre-release pointer | Testing fixes that have landed on the active release branch but are not yet in a stable release |
+| `:main` / `:main-web`           | `main` branch                       | Mutable development pointer | Development and integration testing only                                                        |
+
+#### Using the pre-release channel
+
+The `next` channel is rebuilt on every push to the current default `release/v*` branch and is published for both AMD64 and ARM64. Older maintenance branches cannot overwrite it. The channel provides a pullable image for fixes that have merged into the active release branch before the next stable tag is cut.
+
+```bash
+docker pull diegosouzapw/omniroute:next
+docker pull diegosouzapw/omniroute:next-web
+```
+
+For Docker Compose, override the image tag used by the selected profile, then pull and recreate the service:
+
+```yaml
+services:
+  omniroute:
+    image: diegosouzapw/omniroute:next
+```
+
+```bash
+docker compose pull
+docker compose up -d
+```
+
+#### Safety and rollback
+
+`next` is a floating pre-release channel. It may change on any push to the active release branch and is **not supported for production use**. Pin the image digest while evaluating a specific build:
+
+```bash
+docker pull diegosouzapw/omniroute:next
+docker image inspect diegosouzapw/omniroute:next --format '{{index .RepoDigests 0}}'
+```
+
+Before testing, back up the OmniRoute data volume or bind-mounted data directory. To roll back, restore the previously used stable version or digest and recreate the container:
+
+```bash
+docker pull diegosouzapw/omniroute:<stable-version>
+docker compose up -d
+```
+
+A release-branch build can never move `latest`; only an eligible stable semantic version may promote the stable pointer. The `next` images retain the release image inspection and blocking CRITICAL-vulnerability gate.
+
 ## Important Notes
 
 - **SQLite WAL Mode:** `docker stop` should be allowed to finish so OmniRoute can checkpoint the latest changes back into `storage.sqlite`. The bundled Compose files already set a 40s stop grace period. If you run the image directly, keep `--stop-timeout 40`.

docs/guides/DOCKER_RELEASE_CHANNELS.md

@@ -1,58 +0,0 @@
----
-title: "Docker Release Channels"
-version: 3.8.50
-lastUpdated: 2026-08-06
----
-
-# Docker Release Channels
-
-OmniRoute publishes separate Docker channels for stable releases, active release-branch testing, and development builds.
-
-## Channel summary
-
-| Channel | Source | Mutability | Recommended use |
-| --- | --- | --- | --- |
-| `:<version>` / `:<version>-web` | Signed/versioned release | Immutable | Production deployments that pin an exact release |
-| `:latest` / `:latest-web` | Highest stable release | Mutable stable pointer | Production deployments that intentionally follow stable releases |
-| `:next` / `:next-web` | Current default `release/v*` branch | Mutable pre-release pointer | Testing fixes that have landed on the active release branch but are not yet in a stable release |
-| `:main` / `:main-web` | `main` branch | Mutable development pointer | Development and integration testing only |
-
-## Using the pre-release channel
-
-The `next` channel is rebuilt on every push to the current default `release/v*` branch and is published for both AMD64 and ARM64. Older maintenance branches cannot overwrite it. The channel provides a pullable image for fixes that have merged into the active release branch before the next stable tag is cut.
-
-```bash
-docker pull diegosouzapw/omniroute:next
-docker pull diegosouzapw/omniroute:next-web
-```
-
-For Docker Compose, override the image tag used by the selected profile, then pull and recreate the service:
-
-```yaml
-services:
-  omniroute:
-    image: diegosouzapw/omniroute:next
-```
-
-```bash
-docker compose pull
-docker compose up -d
-```
-
-## Safety and rollback
-
-`next` is a floating pre-release channel. It may change on any push to the active release branch and is **not supported for production use**. Pin the image digest while evaluating a specific build:
-
-```bash
-docker pull diegosouzapw/omniroute:next
-docker image inspect diegosouzapw/omniroute:next --format '{{index .RepoDigests 0}}'
-```
-
-Before testing, back up the OmniRoute data volume or bind-mounted data directory. To roll back, restore the previously used stable version or digest and recreate the container:
-
-```bash
-docker pull diegosouzapw/omniroute:<stable-version>
-docker compose up -d
-```
-
-A release-branch build can never move `latest`; only an eligible stable semantic version may promote the stable pointer. The `next` images retain the release image inspection and blocking CRITICAL-vulnerability gate.

docs/guides/I18N.md

@@ -88,9 +88,9 @@ README variants) are not yet handled by the new pipeline and are still used.
 ### Source of Truth
 
 - **UI strings**: `src/i18n/messages/en.json` (English source, ~2800 keys)
-- **Locale files**: `src/i18n/messages/{locale}.json` (30 translations)
+- **Locale files**: `src/i18n/messages/{locale}.json` (43 translations)
 - **Framework**: `next-intl` with cookie-based locale resolution
-- **Config**: `src/i18n/config.ts` — defines all 30 locales, language names, flags
+- **Config**: `src/i18n/config.ts` — defines all 43 locales, language names, flags
 
 ### Runtime Flow
 
@@ -304,7 +304,7 @@ invocation. Use `config lang set` to persist.
 
 43 locale files ship in `bin/cli/locales/`. Full translations: `en`, `pt-BR`.
 Scaffold-only (all keys fall back to `en`): `bn`, `gu`, `he`, `in`, `mr`, `ms`, `phi`, `sw`, `ta`, `te`, `ur`.
-All other 29 locales have `common` + `program` keys translated.
+All other 30 locales have `common` + `program` keys translated.
 
 ### Adding a new CLI locale
 
@@ -533,7 +533,7 @@ python3 scripts/i18n/validate_translation.py quick -l '${{ matrix.lang }}'
 
 ```
 src/i18n/
-├── config.ts                    # Locale definitions (30 locales, RTL config)
+├── config.ts                    # Locale definitions (43 locales, RTL config)
 ├── request.ts                   # Runtime locale resolution
 └── messages/
     ├── en.json                  # Source of truth (~2800 keys)

docs/guides/TROUBLESHOOTING.md

@@ -38,6 +38,19 @@ Common problems and solutions for OmniRoute.
 
 ---
 
+## npm install Warnings (ERESOLVE / peer / deprecated)
+
+When you run `npm install -g omniroute`, you may see a wall of warnings like `npm warn ERESOLVE`, peer-dependency notices, and `deprecated` messages. **These are expected and harmless.** Your install succeeded if you see `added <N> packages` in the output.
+
+The warnings come from stale peer-dependency ranges in third-party packages OmniRoute doesn't control:
+
+1. **`marked-terminal` wants `marked >=1 <16`, found `marked@18`** — works fine in practice; the upstream peer range is just stale.
+2. **`deprecated prebuild-install@7.1.3`** — the native-binary fetch helper. Only relevant later if a web-cookie provider reports a missing `tls-client-node` native binary (a separate issue, not caused by this warning).
+
+**No action needed** — the warnings cannot be fully silenced without forking upstream packages.
+
+---
+
 ## Quick Fixes
 
 | Problem                                                    | Solution                                                                                                                                                  |

docs/guides/meta.json

@@ -11,11 +11,17 @@
     "COST_TRACKING",
     "I18N",
     "KIRO_SETUP",
+    "ANTIGRAVITY-ONBOARDING",
+    "CLAUDE-CODE-CONFIGURATION",
     "CODEX-CLI-CONFIGURATION",
+    "CLI-INTEGRATIONS",
+    "MANAGEMENT-AUTH",
+    "REMOTE-MODE",
     "PWA_GUIDE",
     "TERMUX_GUIDE",
     "TIERS",
     "USAGE_QUOTA_GUIDE",
+    "TROUBLESHOOTING",
     "UNINSTALL"
   ]
 }

docs/i18n/ar/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/az/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/bg/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/bn/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/cs/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/da/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/de/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/es/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/fa/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/fi/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/fr/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/gu/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/he/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/hi/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/hu/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/id/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/in/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/it/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ja/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ko/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/mr/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ms/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/nl/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/no/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/phi/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/pl/docs/INCIDENT_RESPONSE.md

@@ -1,232 +0,0 @@
-# Runbook reagowania na incydenty — OmniRoute (2026-06-18)
-
-**Status**: Dokument autorytatywny. Audyt 71 filarów (L61) odwołuje się do tego
-dokumentu w bramce `Obs > 2.00`.
-**Właściciel**: observability-circle (lead: security-circle lead).
-**SLO**: zob. `docs/PERF_BUDGETS.md` § 1 (SLO najwyższego poziomu) oraz
-`ops/slos.yaml` (forma maszynowo czytelna, generowana przez zespół Bifrost).
-**Polityka ujawniania**: zob. `SECURITY.md` (wyłącznie ujawnianie podatności,
-osobny przepływ).
-
-Ten runbook to operacyjny playbook dla incydentów **niezwiązanych z bezpieczeństwem**:
-awarie, regresje opóźnień, spalanie budżetu błędów oraz awarie po stronie
-dostawców. Ujawnianie podatności pozostaje w `SECURITY.md`; nie kieruj
-tych spraw przez ten runbook.
-
----
-
-## 1. Skala ważności
-
-| Sev       | Definicja                                                                                                    | Przykłady                                                                       | Powiadomienie                             | Rozwiązanie do               |
-| --------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- | ----------------------------------------- | ---------------------------- |
-| **SEV-1** | Awaria widoczna dla użytkownika; > 50 % żądań kończy się niepowodzeniem lub naruszenie SLO > 2x przez 5 min. | Klaster niedostępny; warstwa auth uszkodzona; powódź 5xx.                       | On-call P0 (natychmiast)                  | 4 h                          |
-| **SEV-2** | Znacząca degradacja; naruszenie SLO 1,5–2x przez 15 min lub wpływ na jednego najemcę.                        | Jeden dostawca niedostępny; p95 > 1,5x budżetu; niekontrolowane rate-limity.    | On-call P1 (15 min)                       | 24 h                         |
-| **SEV-3** | Uśpiony błąd lub near-miss; brak bieżącego wpływu na użytkownika, ale budżet błędów zagrożony.               | Wyciek pamięci w trendzie wzrostowym; circuit breaker wyłącza jednego dostawcę. | Slack `#omniroute-ops` (następny standup) | 7 d                          |
-| **SEV-4** | Kosmetyczny / informacyjny.                                                                                  | Szum w logach; nieblokujący glitch UI.                                          | Następny przegląd tygodniowy              | Następny cykl refaktoryzacji |
-
-**Eskalacja burn-rate** (zgodnie z `docs/PERF_BUDGETS.md` § 1): 6x przez 5 min
-to SEV-1; 2x przez 1 h to SEV-2; utrzymanie < 1x przez 7 d obniża do SEV-3.
-
----
-
-## 2. Źródła detekcji
-
-| Źródło                            | Sygnał                               | Routing                               |
-| --------------------------------- | ------------------------------------ | ------------------------------------- |
-| Prometheus (`/metrics`)           | Delty liczników (5xx, latency)       | Alertmanager → PagerDuty              |
-| Panele SLO w Grafana              | Panele burn-rate SLO                 | Slack `#omniroute-ops`                |
-| Sonda uptime (`/api/health/ping`) | 3 kolejne niepowodzenia z 3 regionów | Alertmanager → PagerDuty              |
-| Dependabot                        | Nowe CVE w zależności (CVSS ≥ 7)     | GitHub Security → security-circle     |
-| Ręczny raport użytkownika         | Zgłoszenie w Discord / GitHub issue  | Triage przez dyżurnego (on-call)      |
-| Chaos-drill (kwartalny)           | Wstrzyknięte awarie                  | Planowany drill; wyniki w `docs/ops/` |
-
-Alerty **nie** idą na prywatne DM. Domyślny kanał to `#omniroute-ops`; PagerDuty
-stronicuje rotację on-call. Pełna matryca alertów: `ops/alertmanager/rules.yml`
-(gdy jest wdrożona; do tego czasu reguły są w konfiguracji Prometheus w
-`deploy/observability/`).
-
----
-
-## 3. Pierwsze 15 minut (SEV-1 / SEV-2)
-
-1. **Potwierdź**. Otwórz panel SLO i sprawdź, czy alert jest prawdziwy, a nie
-   flapping. Jeśli flapping — wycisz na 15 min i zbadaj.
-2. **Zadeklaruj**. Opublikuj w `#omniroute-ops`:
-   ```
-   INCIDENT <sev> — <jedna linia objawu>
-   IC: @you
-   Status: investigating
-   Następna aktualizacja: <teraz + 15 min>
-   ```
-3. **Stabilizuj** przed diagnozą główną przyczyny. Preferowana kolejność:
-   - Odetnij zły deploy: `kubectl rollout undo deploy/omniroute` (lub
-     równoważne dla Twojego środowiska; zob. `docs/ops/DEPLOYMENT.md`).
-   - Przełącz combo / dostawcę: `POST /api/combos/:id/switch` lub MCP
-     `switch_combo`.
-   - Włącz tryb degradacji: ustaw
-     `OMNIROUTE_DEGRADATION_MODE=lite` (pomija niekrytyczne middleware).
-   - Rate-limit ruch wejściowy na edge, jeśli to flood.
-4. **Aktualizuj** co 15 min do złagodzenia lub rozwiązania.
-
-Nie debuguj w produkcji przy SEV-1. Przywróć ostatni znany dobry stan, potem
-rób post-mortem offline.
-
----
-
-## 4. Macierz runbooków
-
-| Klasa awarii                         | Pierwszy ruch                                                 | Runbook                                                    |
-| ------------------------------------ | ------------------------------------------------------------- | ---------------------------------------------------------- |
-| Całkowity outage (wszystkie regiony) | Rollback ostatniego deployu; sprawdź status edge / DNS        | `docs/ops/DEPLOYMENT.md` § rollback                        |
-| Pojedynczy dostawca 5xx / timeout    | Wyłącz dostawcę w combo; włącz fallback                       | `docs/architecture/RESILIENCE_GUIDE.md`                    |
-| Spalanie budżetu błędów (latency)    | Sprawdź p95 per-route; włącz compression / cache              | `docs/PERF_BUDGETS.md` § 1–3                               |
-| Wyczerpanie połączeń SQLite          | Zrestartuj z większym pool; sprawdź długotrwałe transakcje    | `docs/architecture/CODEBASE_DOCUMENTATION.md` (warstwa DB) |
-| Wyciek pamięci / OOM                 | Heap snapshot; rolling restart; oznacz SEV-3 na follow-up     | wewnętrzny runbook profilowania                            |
-| Wygaśnięcie certu / TLS              | Wdróż odnowiony cert; sprawdź automatyzację renew             | `docs/ops/TLS.md` (gdy jest; w przeciwnym razie ręcznie)   |
-| Awaria odświeżania tokena OAuth      | Wymuś re-auth na dotkniętych kontach; sprawdź status dostawcy | `docs/security/OAUTH.md`                                   |
-| Powódź rate-limit (wejście)          | Zaciśnij limity na kluczu API; zbanuj obrażający klucz        | `docs/architecture/AUTHZ_GUIDE.md`                         |
-| Awaria zależności (npm / CVE)        | Pin / patch; w razie potrzeby wyłącz funkcję                  | `SECURITY.md` + Dependabot                                 |
-
-Każdy runbook musi kończyć się kryteriami **done** i właścicielem follow-upu.
-
----
-
-## 5. Role w czasie incydentu
-
-| Rola                        | Kto                                  | Odpowiedzialności                                                |
-| --------------------------- | ------------------------------------ | ---------------------------------------------------------------- |
-| **Incident Commander (IC)** | Dyżurny on-call (lub delegat)        | Deklaruje sev, prowadzi mostek, zatwierdza mitigacje, zamyka     |
-| **Tech lead**               | Inżynier znający dotknięty podsystem | Diagnozuje, proponuje mitigacje, wdraża poprawki                 |
-| **Comms**                   | IC lub wolontariusz                  | Aktualizacje na Slacku, status page, odpowiedzi dla użytkowników |
-| **Scribe**                  | Wolontariusz                         | Notatki z linii czasu na potrzeby post-mortem                    |
-| **Executive sponsor**       | Tylko SEV-1                          | Escalation path; decyzje o zasobach                              |
-
-Jedna osoba = jedna rola, gdy to możliwe. IC **nie** debuguje.
-
----
-
-## 6. Komunikacja
-
-- **Wewnętrzna**: `#omniroute-ops` jest źródłem prawdy. Wątek na incydent na
-  deklarację; wszystkie aktualizacje w wątku.
-- **Zewnętrzna** (gdy dotyczy użytkowników zewnętrznych): status page
-  (status.omniroute.example — zastąp prawdziwym URL, gdy będzie live). SEV-1
-  dostaje publiczny post w ≤ 30 min; SEV-2 w ≤ 2 h, jeśli wpływ jest
-  zewnętrzny.
-- **Nie** spekuluj o root cause publicznie. Podawaj objawy i ETA mitigacji.
-- Po złagodzeniu: jedna wiadomość „mitigated, monitoring for 30 min”, potem
-  „resolved” z linkiem do post-mortem (gdy będzie gotowy).
-
----
-
-## 7. Łagodzenie vs rozwiązanie
-
-| Stan            | Znaczenie                                                | Kiedy używać                               |
-| --------------- | -------------------------------------------------------- | ------------------------------------------ |
-| `investigating` | Alert potwierdzony, przyczyna nieznana                   | Pierwsze 15 min                            |
-| `mitigating`    | Stosowana poprawka; wpływ powinien spadać                | Podczas rollbacku / failover               |
-| `mitigated`     | Wpływ na użytkownika ustał; root cause może być otwarty  | Po udanej stabilizacji                     |
-| `resolved`      | Root cause znany i trwale naprawiony (lub zaakceptowany) | Po merge poprawki lub decyzji o akceptacji |
-| `wontfix`       | Zaakceptowane ryzyko; udokumentowane                     | Tylko SEV-3/4 za zgodą IC                  |
-
-SEV-1/2 nie mogą pozostać w `mitigated` dłużej niż 7 dni bez eskalacji do
-executive sponsora.
-
----
-
-## 8. Post-mortem (obowiązkowy dla SEV-1/2)
-
-Szablon (skopiuj do `docs/postmortems/YYYY-MM-DD-<slug>.md`):
-
-```markdown
-# Post-mortem: <tytuł>
-
-- Data: YYYY-MM-DD
-- Sev: SEV-N
-- IC: @handle
-- Czas trwania: wykrycie → mitigacja → rozwiązanie
-- Dotknięci użytkownicy / budżet błędów spalony: <liczby>
-
-## Streszczenie
-
-<5 zdań, bez winy>
-
-## Linia czasu
-
-| Czas (UTC) | Event |
-| ---------- | ----- |
-| HH:MM      | ...   |
-
-## Root cause
-
-<co faktycznie się zepsuło; 5× dlaczego jeśli pomocne>
-
-## Co poszło dobrze
-
-- ...
-
-## Co poszło źle
-
-- ...
-
-## Action items
-
-| AI  | Właściciel | Termin     | Status |
-| --- | ---------- | ---------- | ------ |
-| ... | @handle    | YYYY-MM-DD | open   |
-
-## Lekcje
-
-<1–3 trwałe zmiany procesu lub kodu>
-```
-
-Zasady:
-
-- **Bez obwiniania.** System zawiódł, nie osoba.
-- Action items mają właściciela i termin; otwarte AI są przeglądane na
-  cotygodniowym standupie ops.
-- Opublikuj w ciągu **5 dni roboczych** od rozwiązania.
-- SEV-3 dostaje post-mortem tylko gdy IC uzna to za wartościowe; SEV-4 nigdy.
-
----
-
-## 9. Kwartalne chaos-drille
-
-Harmonogram (własność: observability-circle):
-
-| Kwartał | Scenariusz                                  | Sukces =                                      |
-| ------- | ------------------------------------------- | --------------------------------------------- |
-| Q1      | Kill pod główny podczas peak load           | Failover < 30 s; zero utraty danych           |
-| Q2      | Wstrzyknij 5xx u top-1 dostawcy             | Combo przełącza się; budżet błędów trzyma się |
-| Q3      | Partycja sieci do SQLite (gdy sklastrowany) | Degradacja read-only; brak korupcji           |
-| Q4      | Wygaśnięcie certu TLS (staging)             | Alert odpala; renew w SLO                     |
-
-Wyniki lądują w `docs/ops/chaos/YYYY-QN.md`. Niezaliczony drill otwiera SEV-3
-z AI na lukę.
-
----
-
-## 10. Powiązane dokumenty
-
-| Dokument                                | Rola                                  |
-| --------------------------------------- | ------------------------------------- |
-| `docs/PERF_BUDGETS.md`                  | SLO, budżety błędów, progi burn-rate  |
-| `ops/slos.yaml`                         | Maszynowa forma SLO (Bifrost)         |
-| `SECURITY.md`                           | Ujawnianie podatności (osobny flow)   |
-| `docs/architecture/RESILIENCE_GUIDE.md` | Fallback, circuit breaker, degradacja |
-| `docs/ops/DEPLOYMENT.md`                | Deploy / rollback                     |
-| `docs/architecture/AUTHZ_GUIDE.md`      | Nadużycia kluczy API, rate-limity     |
-| `docs/postmortems/`                     | Archiwum wpisów post-mortem           |
-
----
-
-## 11. Historia zmian
-
-| Data       | Zmiana                                         |
-| ---------- | ---------------------------------------------- |
-| 2026-06-18 | Wstępna wersja autorytatywna (L61 / gate Obs). |
-
----
-
-_Ten dokument jest autorytatywny dla operacyjnego reagowania na incydenty.
-Poprawki: PR do `docs/INCIDENT_RESPONSE.md` z recenzją observability-circle._

docs/i18n/pl/docs/PERF_BUDGETS.md

@@ -1,231 +0,0 @@
-# Budżety wydajności — OmniRoute (2026-06-18)
-
-**Status**: Miarodajny. Cele SLO, do których odwołuje się audyt 71 filarów (L13)
-przy bramce `Perf > 2.00`.
-**Metodyka**: budżety opóźnień p50/p95/p99 per endpoint oraz
-nadrzędne SLO dostępności. Budżety wyprowadzono z topologii 3 replik
-Caddy + Redis (commit `038439fa7`); korygować przy zmianie infrastruktury.
-**Egzekwowanie**: na razie brak. § 6 szkicuje skrypt k6 `benches/perf-gate.k6.js`,
-który asertowałby poniższe SLO, lecz jest to odniesienie projektowe,
-a nie zacommitowany plik — w repozytorium nie ma dziś katalogu `bench/` ani `benches/`.
-Ten dokument służy wyłącznie do ustalania celów, dopóki bramka CI
-nie powstanie jako praca następcza.
-**Częstotliwość ponownej oceny**: kwartalnie lub przy każdej istotnej zmianie infrastruktury.
-
----
-
-## 1. Nadrzędne SLO
-
-| SLO                                                           | Cel                      | Okno            | Page przy naruszeniu |
-| ------------------------------------------------------------- | ------------------------ | --------------- | -------------------- |
-| **Dostępność** (2xx lub 4xx dla /v1/* i /api/settings/*)      | 99.9%                    | rolling 30 days | on-call P2           |
-| **Tempo spalania error budget** (znormalizowany wskaźnik 1xx) | < 2x for 1h, < 6x for 5m | 1h / 5m windows | on-call P1           |
-| **Zagregowane opóźnienie p95** (wszystkie /v1/*)              | ≤ 1.5 s                  | rolling 5 min   | on-call P2           |
-| **Zagregowane opóźnienie p99** (wszystkie /v1/*)              | ≤ 4.0 s                  | rolling 5 min   | on-call P2           |
-
-**Error budget**: okno 30-dniowe = 43,2 minuty niedostępności przy
-99.9%. Tempo spalania > 2x to P2; > 6x to P1.
-
----
-
-## 2. Budżety opóźnień per endpoint
-
-Wszystkie budżety mierzone **po stronie serwera** (od wejścia do Next.js Route Handler
-do startu odpowiedzi albo do ostatniego bajtu przy streamingu). Endpointy streamowe
-mierzone do time-of-first-byte (TTFB), ponieważ body jest przyrostowe.
-
-### 2.1 Endpointy inferencji (ścieżka krytyczna)
-
-| Endpoint                                  | Method      | p50    | p95    | p99    | Notes                                                         |
-| ----------------------------------------- | ----------- | ------ | ------ | ------ | ------------------------------------------------------------- |
-| `/v1/responses` (non-stream)              | POST        | 800 ms | 1.8 s  | 3.5 s  | Obejmuje translator + roundtrip do providera                  |
-| `/v1/responses` (stream)                  | POST (TTFB) | 350 ms | 900 ms | 1.8 s  | Tylko TTFB; całkowity czas nieograniczony                     |
-| `/v1/relay/chat/completions` (non-stream) | POST        | 1.0 s  | 2.2 s  | 4.0 s  | Obejmuje sprawdzenie rate-limit per-(token,IP)                |
-| `/v1/relay/chat/completions` (stream)     | POST (TTFB) | 400 ms | 1.0 s  | 2.0 s  |                                                               |
-| `/v1/embeddings`                          | POST        | 300 ms | 700 ms | 1.4 s  | Czysty roundtrip do providera; tani                           |
-| `/v1/rerank`                              | POST        | 600 ms | 1.4 s  | 2.8 s  |                                                               |
-| `/v1/moderations`                         | POST        | 250 ms | 600 ms | 1.2 s  | Lekka klasyfikacja                                            |
-| `/v1/audio/speech`                        | POST        | 1.2 s  | 3.0 s  | 6.0 s  | Synteza audio jest wolna; budżet to odzwierciedla             |
-| `/v1/audio/transcriptions`                | POST        | 2.0 s  | 5.0 s  | 10.0 s | STT ograniczony czasem audio + rozmiarem modelu               |
-| `/v1/images/generations`                  | POST        | 4.0 s  | 8.0 s  | 15.0 s | Generacja obrazów ograniczona asynchronicznie przez providera |
-| `/v1/videos/generations`                  | POST (TTFB) | 600 ms | 1.5 s  | 3.0 s  | Async; klient odpytuje `/v1/videos/{id}`                      |
-| `/v1/music/generations`                   | POST        | 3.0 s  | 6.0 s  | 12.0 s |                                                               |
-
-### 2.2 Pliki + batche
-
-| Endpoint                              | Method | p50    | p95    | p99    | Notes                                    |
-| ------------------------------------- | ------ | ------ | ------ | ------ | ---------------------------------------- |
-| `/v1/files` (GET)                     | GET    | 80 ms  | 200 ms | 400 ms | Lista z cache                            |
-| `/v1/files` (POST upload)             | POST   | 500 ms | 1.2 s  | 2.5 s  | Limit 25 MB; parsowanie multipart        |
-| `/v1/files/{id}` (GET)                | GET    | 60 ms  | 150 ms | 300 ms |                                          |
-| `/v1/files/{id}` (DELETE)             | DELETE | 80 ms  | 200 ms | 400 ms |                                          |
-| `/v1/files/{id}/content` (download)   | GET    | 100 ms | 300 ms | 600 ms | + przepustowość per-MB                   |
-| `/v1/batches` (GET)                   | GET    | 150 ms | 400 ms | 800 ms |                                          |
-| `/v1/batches` (POST create)           | POST   | 200 ms | 500 ms | 1.0 s  | Waliduje plik wejściowy, potem enqueuuje |
-| `/v1/batches/{id}` (GET)              | GET    | 100 ms | 300 ms | 600 ms |                                          |
-| `/v1/batches/{id}` (DELETE)           | DELETE | 100 ms | 300 ms | 600 ms |                                          |
-| `/v1/batches/delete-completed` (POST) | POST   | 400 ms | 1.0 s  | 2.0 s  | Masowe usuwanie; n wierszy               |
-
-### 2.3 Agenci
-
-| Endpoint                         | Method | p50    | p95    | p99    | Notes                                                         |
-| -------------------------------- | ------ | ------ | ------ | ------ | ------------------------------------------------------------- |
-| `/v1/agents/health`              | GET    | 1.5 s  | 4.5 s  | 5.0 s  | Limit timeout 5s per provider; oczekiwane łącznie 3 providery |
-| `/v1/agents/credentials`         | GET    | 100 ms | 250 ms | 500 ms | Tylko metadane; wartości nigdy nie są zwracane                |
-| `/v1/agents/tasks` (GET list)    | GET    | 150 ms | 400 ms | 800 ms |                                                               |
-| `/v1/agents/tasks` (POST create) | POST   | 250 ms | 600 ms | 1.2 s  | Tylko enqueuuje; nie uruchamia agenta                         |
-| `/v1/agents/tasks/{id}` (GET)    | GET    | 100 ms | 300 ms | 600 ms |                                                               |
-| `/v1/agents/tasks/{id}` (DELETE) | DELETE | 150 ms | 400 ms | 800 ms |                                                               |
-
-### 2.4 Combos / me / providers
-
-| Endpoint                          | Method | p50    | p95    | p99    |
-| --------------------------------- | ------ | ------ | ------ | ------ |
-| `/v1/combos`                      | GET    | 80 ms  | 200 ms | 400 ms |
-| `/v1/me/status`                   | GET    | 60 ms  | 150 ms | 300 ms |
-| `/v1/providers/{provider}/models` | GET    | 100 ms | 250 ms | 500 ms |
-
-### 2.5 Web / search
-
-| Endpoint        | Method | p50    | p95   | p99   | Notes                                          |
-| --------------- | ------ | ------ | ----- | ----- | ---------------------------------------------- |
-| `/v1/web/fetch` | POST   | 1.5 s  | 4.0 s | 8.0 s | Limit timeout 10s; głębokość rekurencji 3      |
-| `/v1/search`    | POST   | 800 ms | 2.0 s | 4.0 s | Opóźnienie wyszukiwania u providera bywa różne |
-
-### 2.6 Shim VSCode-CLI (scoped tokenem)
-
-To ścieżki legacy passthrough. Budżety są ciaśniejsze, bo
-rozszerzenie VSCode-CLI wywołuje je często w ciasnych pętlach.
-
-| Endpoint                                       | Method | p50    | p95    | p99    |
-| ---------------------------------------------- | ------ | ------ | ------ | ------ |
-| `/v1/vscode/{token}/v1/chat/completions`       | POST   | 700 ms | 1.6 s  | 3.0 s  |
-| `/v1/vscode/{token}/v1/models`                 | GET    | 60 ms  | 150 ms | 300 ms |
-| `/v1/vscode/{token}/combos`                    | GET    | 80 ms  | 200 ms | 400 ms |
-| `/v1/vscode/{token}/chat/completions` (legacy) | POST   | 700 ms | 1.6 s  | 3.0 s  |
-| `/v1/vscode/{token}/models` (legacy)           | GET    | 60 ms  | 150 ms | 300 ms |
-| `/v1/vscode/{token}/responses`                 | POST   | 800 ms | 1.8 s  | 3.5 s  |
-
-### 2.7 Zarządzanie / settings
-
-Endpointy zarządzania są wyłącznie operatorskie i nie należą do ścieżki krytycznej.
-Budżety ustawiono konserwatywnie; naruszenia nie page'ują on-call, ale
-są flagowane w tygodniowym przeglądzie wydajności.
-
-| Endpoint group                        | p50    | p95    | p99    |
-| ------------------------------------- | ------ | ------ | ------ |
-| `/api/settings/*` (GET)               | 100 ms | 300 ms | 600 ms |
-| `/api/settings/*` (POST/PATCH/DELETE) | 200 ms | 500 ms | 1.0 s  |
-| `/api/keys/*` (CRUD)                  | 150 ms | 400 ms | 800 ms |
-| `/api/quota/*` (CRUD)                 | 150 ms | 400 ms | 800 ms |
-| `/api/monitoring/health` (heavy)      | 500 ms | 1.5 s  | 3.0 s  |
-
-### 2.8 Publiczne sondy
-
-| Endpoint                 | Method | p50   | p95   | p99                                   |
-| ------------------------ | ------ | ----- | ----- | ------------------------------------- |
-| `/api/health/ping`       | GET    | 5 ms  | 20 ms | 50 ms                                 |
-| `/api/monitoring/health` | GET    | 5 ms  | 20 ms | 50 ms                                 |
-| `/api/docs`              | GET    | 20 ms | 80 ms | 200 ms (HTML shell, no provider call) |
-
----
-
-## 3. Cele przepustowości
-
-| Tier                    | Per-replica RPS            | Cluster RPS (3 replicas) | Notes                                               |
-| ----------------------- | -------------------------- | ------------------------ | --------------------------------------------------- |
-| Inference (non-stream)  | 50 RPS                     | 150 RPS                  | Ograniczone przez quota providera + CPU translatora |
-| Inference (stream)      | 25 concurrent streams      | 75 streams               | Ograniczone przez event-loop Node + pamięć          |
-| Embeddings              | 200 RPS                    | 600 RPS                  | Tanie                                               |
-| Files (upload)          | 10 RPS                     | 30 RPS                   | Parsowanie multipart + zapis do DB                  |
-| Files (download)        | 100 RPS                    | 300 RPS                  | Treść statyczna przez Next.js                       |
-| Combos / me / providers | 500 RPS                    | 1,500 RPS                | Z cache                                             |
-| WebSocket               | 100 concurrent connections | 300                      | Limit per-IP: 5                                     |
-
-**Sufit klastra** (wszystkie endpointy łącznie, obciążenie ciągłe): ~1 000 RPS,
-zanim p95 latency zacznie rosnąć. Powyżej tego skalować horyzontalnie
-przez dodawanie replik; Caddy LB jest bezstanowy.
-
----
-
-## 4. Budżety zasobów
-
-| Resource                | Per-replica cap | Notes                                                  |
-| ----------------------- | --------------- | ------------------------------------------------------ |
-| RSS memory              | 1.5 GB          | Skoki przy gen. audio/wideo; spodziewane chwilowe 2 GB |
-| Event-loop lag (p99)    | 50 ms           | Alert przez regresję `clinic doctor`                   |
-| Heap retained           | 800 MB          | Strojenie old-gen GC w `node --max-old-space-size`     |
-| File descriptors        | 2,000           | Na hoście zalecane `ulimit -n 4096`                    |
-| DB connections (sql.js) | 1 per replica   | sql.js działa in-process; pool nie jest potrzebny      |
-| Redis connections       | 20 per replica  | Z poola; idle usuwane po 5 min                         |
-
----
-
-## 5. Budżet cold-start
-
-Cold-start Next.js App Router na świeżym kontenerze:
-
-| Phase                            | Budget                                   |
-| -------------------------------- | ---------------------------------------- |
-| Container start → HTTP listening | ≤ 800 ms                                 |
-| First request TTFB (warm)        | ≤ 200 ms                                 |
-| Translator registry bootstrap    | ≤ 500 ms (one-time, first /v1/responses) |
-
-**Skrypt pomiarowy**: `bin/cold-start-bench.sh` (już w repozytorium
-od v3.8.36; `bin/` to kanoniczny katalog skryptów).
-
----
-
-## 6. Bramka regresji (odniesienie k6, jeszcze niezaimplementowane)
-
-Poniższy szkic pokazuje, jak przyszły skrypt `benches/perf-gate.k6.js`
-asertowałby powyższe SLO. Nic z tej sekcji nie jest dziś zacommitowane ani
-podpięte do CI — to odniesienie projektowe do pracy następczej, a nie
-działająca bramka.
-
-```javascript
-// benches/perf-gate.k6.js — pseudo-code; not yet committed
-import http from "k6/http";
-import { check, Trend } from "k6";
-
-const responsesTTFB = new Trend("v1_responses_ttfb", true);
-
-export const options = {
-  scenarios: {
-    smoke: {
-      executor: "constant-vus",
-      vus: 10,
-      duration: "1m",
-    },
-  },
-  thresholds: {
-    "http_req_duration{endpoint:v1_responses}": ["p(95)<1800", "p(99)<3500"],
-    http_req_failed: ["rate<0.01"],
-    v1_responses_ttfb: ["p(95)<900"],
-  },
-};
-
-export default function () {
-  const res = http.post(
-    `${__ENV.BASE_URL}/api/v1/responses`,
-    JSON.stringify({
-      model: "gpt-4o-mini",
-      input: "ping",
-    }),
-    { headers: { Authorization: `Bearer ${__ENV.API_KEY}` } }
-  );
-  check(res, { "status is 200": (r) => r.status === 200 });
-  responsesTTFB.add(res.timings.waiting);
-}
-```
-
----
-
-## 7. Dziennik przeglądów
-
-| Date                 | Reviewer             | Change                                                                                                                                                                                                             |
-| -------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 2026-06-18           | security-circle lead | Wstępne budżety per endpoint wyprowadzone z topologii 3 replik Caddy + Redis                                                                                                                                       |
-| 2026-07-18           | observability-circle | Doprecyzowano, że dokument dziś nie egzekwuje nic (brak katalogu `bench/`/`benches/`, brak bramki CI) oraz poprawiono nieaktualne twierdzenie „not yet committed” o `bin/cold-start-bench.sh` (obecny od v3.8.36). |
-| 2026-07-18 (planned) | observability-circle | Podpięcie `benches/perf-gate.k6.js` do CI; bramka przy naruszeniu p95 + p99                                                                                                                                        |
-| 2026-09-18 (planned) | observability-circle | Przegląd kwartalny; korekta po danych bazowych z ruchu produkcyjnego                                                                                                                                               |

docs/i18n/pl/docs/architecture/sqlite-coupling-inventory.md

@@ -1,226 +0,0 @@
----
-title: "Inwentaryzacja sprzężenia z SQLite"
-status: measured-snapshot
-lastUpdated: 2026-07-23
----
-
-# Inwentaryzacja sprzężenia z SQLite
-
-- **Tracking issue:** [#8075](https://github.com/diegosouzapw/OmniRoute/issues/8075)
-- **Snapshot revision:** `9a3b605f3420ae3ab08bd93d6443034f03a1bcbc`
-- **Scanned-corpus SHA-256:** `72334620a7a18a42bcede1643fb2fdf95da6eae9ffa66a891ae14ed633ad43f6`
-- **Cel:** Zmierz aktualne linie cięcia warstwy persystencji przed zaproponowaniem interfejsów repozytoriów
-- **Wpływ na runtime:** Brak; ten dokument i jego skrypt audytu nie zmieniają zachowania bazy danych
-
-## Jak odtworzyć
-
-Z katalogu głównego repozytorium:
-
-```bash
-node scripts/check/audit-sqlite-coupling.mjs
-node scripts/check/audit-sqlite-coupling.mjs --json
-node --test scripts/check/audit-sqlite-coupling.test.mjs
-```
-
-Skrypt odczytuje śledzone pliki z Gita, skanuje źródła inne niż testowe w `src/`, `open-sse/`,
-`electron/` i `bin/` oraz skanuje SQL migracji w `src/lib/db/migrations/`. Wyklucza
-drzewo testów najwyższego poziomu, współlokalizowane katalogi testów, pliki źródłowe test/spec oraz ścieżki poza tymi
-skonfigurowanymi korzeniami źródeł (w tym dokumentację i skrypty).
-
-Skrypt odmawia uruchomienia, jeśli śledzone pliki w tych korzeniach źródeł różnią się od `HEAD`. Raportuje
-zarówno rewizję narzędzia audytu, jak i SHA-256 nad uporządkowanym korpusem ścieżka/treść. Powyższy snapshot
-został wykonany z wymienionej rewizji źródeł; ten PR zmienia wyłącznie wykluczone ścieżki dokumentacji i skryptów,
-więc ponowne uruchomienie z czystej gałęzi PR daje ten sam digest korpusu.
-
-To jest **inwentaryzacja leksykalna**, a nie semantyczna analiza TypeScript lub SQL:
-
-- liczby to wystąpienia zdefiniowanych wzorców, a nie liczby odrębnych instrukcji SQL;
-- wzorce wywołań adaptera i bezpośredniego singletona najpierw maskują komentarze i treści literałów;
-- treści literałów szablonowych, w tym osadzone wyrażenia, są wykluczone z tych zliczeń
-  składni kodu;
-- lekki masker nie jest parserem JavaScript, więc nietypowa składnia literałów wyrażeń regularnych
-  może nadal wymagać ręcznego przeglądu;
-- komentarze i literały łańcuchowe mogą wnosić wkład do zliczeń sygnałów dialektu, które celowo przeszukują
-  surowy tekst pod kątem osadzonego SQL;
-- dopasowanie `.prepare()` poza `src/lib/db/` to trop do przeglądu, a nie dowód, że wywołanie należy przenieść;
-- wywołania ukryte za inaczej nazwaną nakładką mogą nie być zliczane;
-- liczby plików są deduplikowane, natomiast liczby wystąpień — nie.
-
-Wyjście JSON obejmuje każdą pasującą ścieżkę, dzięki czemu recenzenci mogą sprawdzić lub przeklasyfikować poszczególne
-wyniki zamiast opierać się wyłącznie na sumach.
-
-## Zakres snapshota
-
-W zapisanej rewizji skrypt przeskanował:
-
-- 3 830 śledzonych plików źródłowych innych niż testowe;
-- 129 plików SQL migracji.
-
-Liczba plików źródłowych jest celowo szeroka, ponieważ celem jest znalezienie sprzężenia persystencji, które
-wyszło poza nominalny katalog bazy danych, w tym kod CLI oraz proxy/runtime.
-
-## Sygnały granic
-
-| Signal                                                                           | Files | Occurrences |
-| -------------------------------------------------------------------------------- | ----: | ----------: |
-| Direct `getDbInstance()` call syntax outside comments/literals and `src/lib/db/` |    45 |         150 |
-| `localDb` import consumers                                                       |   211 |           — |
-| `SqliteAdapter` type consumers outside comments/literals and `src/lib/db/`       |     3 |           — |
-
-Barrel `localDb` już daje wielu wywołującym szew funkcji domenowych, ale
-`src/lib/localDb.ts` pozostaje warstwą re-eksportu, a nie kontraktem backendu. 45 bezpośrednich
-konsumentów singletona to najczytelniejszy pierwszy zestaw do przeglądu, ponieważ omijają ten logiczny szew i
-trzymają bezpośrednio uchwyt o kształcie adaptera.
-
-Trzy pliki źródłowe inne niż testowe poza `src/lib/db/`, które w składni kodu wspominają typ `SqliteAdapter`,
-to:
-
-- `src/app/api/db-backups/import/route.ts`;
-- `src/lib/compliance/index.ts`;
-- `src/lib/compliance/noLog.ts`.
-
-To nie są równoważne zadania migracyjne. Import kopii zapasowej jest specyficzny dla możliwości; persystencja
-compliance może być przenośnym stanem domenowym. Przyszła granica powinna je sklasyfikować, a nie
-przenosić wszystkie trzy mechanicznie.
-
-## Składnia wywołań o kształcie adaptera
-
-| Signal            | Occurrences | Files | Outside `src/lib/db/` occurrences | Outside files |
-| ----------------- | ----------: | ----: | --------------------------------: | ------------: |
-| `.prepare()`      |       1,219 |   163 |                               252 |            52 |
-| `.transaction()`  |          62 |    40 |                                12 |            10 |
-| `.immediate()`    |           3 |     3 |                                 0 |             0 |
-| `.pragma()`       |          39 |    11 |                                 6 |             4 |
-| `.backup()`       |           6 |     5 |                                 3 |             3 |
-| `.checkpoint()`   |           0 |     0 |                                 0 |             0 |
-| `lastInsertRowid` |          15 |     7 |                                 1 |             1 |
-
-Ta tabela pokazuje, dlaczego `SqliteAdapter` jest warstwą zgodności runtime SQLite, a nie przenośną
-abstrakcją backendu. Jego synchroniczny kształt instrukcji i transakcji jest szeroko używany, a część
-tego kształtu jest widoczna poza nominalną warstwą bazy danych.
-
-Główni bezpośredni konsumenci `getDbInstance()` poza `src/lib/db/` w tej rewizji to:
-
-| File                                               | Occurrences |
-| -------------------------------------------------- | ----------: |
-| `src/lib/proxySubscription/subscriptionService.ts` |          12 |
-| `src/lib/semanticCache.ts`                         |          10 |
-| `src/lib/usage/callLogs.ts`                        |           9 |
-| `src/lib/cloudAgent/db.ts`                         |           8 |
-| `src/lib/memory/store.ts`                          |           8 |
-| `src/lib/memory/vectorStore.ts`                    |           8 |
-| `src/lib/modelsDevSync.ts`                         |           8 |
-| `src/lib/gamification/badges.ts`                   |           5 |
-| `src/lib/memory/retrieval.ts`                      |           5 |
-| `src/lib/pricingSync.ts`                           |           5 |
-| `src/lib/skills/registry.ts`                       |           5 |
-| `src/lib/usage/usageHistory.ts`                    |           5 |
-
-Lista obejmuje konfigurację control-plane, dane usage/audit, cache, wyszukiwanie memory/vector, skills,
-gamification oraz wsparcie CLI/provider. Jeden generyczny adapter SQL utrwaliłby ten rozrzut;
-repozytoria domenowe dają sposób na jego redukcję plaster po plasterku.
-
-## Sygnały dialektu SQLite i cyklu życia
-
-| Signal                | Occurrences | Files |
-| --------------------- | ----------: | ----: |
-| `PRAGMA` text         |          97 |    41 |
-| `sqlite_master`       |          14 |    11 |
-| `BEGIN IMMEDIATE`     |           2 |     2 |
-| `INSERT OR REPLACE`   |          83 |    45 |
-| `AUTOINCREMENT`       |          34 |    24 |
-| `datetime('now')`     |         171 |    68 |
-| `VACUUM`              |          39 |    10 |
-| `wal_checkpoint`      |          13 |     7 |
-| `fts5`                |          43 |     8 |
-| `vec0`                |           7 |     1 |
-| `last_insert_rowid()` |           1 |     1 |
-
-Te wartości to sygnały tekstowe i obejmują komentarze, jeśli występują. Są przydatne do lokalizowania
-pracy nad przenośnością, a nie do szacowania nakładu implementacji przez mnożenie.
-
-Zweryfikowane obszary wysokiego sprzężenia obejmują:
-
-- `src/lib/db/core.ts`: cykl życia singletona, ścieżki plików SQLite, checkpoint WAL, recovery, schemat,
-  kompaktowanie i tworzenie kopii zapasowych;
-- `src/lib/db/migrationRunner.ts`: wykonywanie ponumerowanych migracji SQL, `sqlite_master`,
-  `PRAGMA table_info`, zachowanie transakcji oraz opcjonalna obsługa FTS5;
-- `src/lib/db/optimizationSettings.ts`: ustawienia page/cache, auto-vacuum, przejścia WAL oraz
-  `VACUUM`;
-- `src/lib/db/backup.ts`: cykl życia kopii zapasowej i przywracania bazy danych;
-- `src/lib/db/schemaColumns.ts`: introspekcja schematu SQLite i kolumny zgodności;
-- `src/lib/memory/vectorStore.ts` oraz `src/lib/memory/retrieval.ts`: zachowanie `vec0` i FTS5;
-- `src/lib/db/adapters/`: implementacje zgodności dla obsługiwanych runtime'ów SQLite.
-
-Tych obszarów nie należy forsować przez interfejs repozytorium najniższego wspólnego mianownika. Potrzebują
-wyraźnych możliwości SQLite albo osobnych implementacji backendu.
-
-## Sprzężenie migracji
-
-Snapshot zawiera 129 śledzonych plików SQL migracji. `src/lib/db/migrationRunner.ts` robi więcej
-niż wykonywanie uporządkowanych plików: posiada odkrywanie migracji, historię wersji, bezpieczeństwo duplikatów wersji,
-sondy schematu, sprawdzenia możliwości FTS5, bezpieczeństwo przed migracją oraz wykonywanie transakcji SQLite.
-
-W konsekwencji:
-
-- inny dialekt SQL nie może bezpiecznie ponownie użyć plików migracji bez zmian;
-- zewnętrzne backendy potrzebują własnej implementacji migracji i historii schematu;
-- logiczne kamienie milowe migracji mogą być współdzielone, ale fizyczny SQL i sondy możliwości pozostają
-  specyficzne dla backendu;
-- praca multi-replica wymaga własności migracji lub blokad, zanim zewnętrzny backend zostanie
-  uznany za gotowy.
-
-## Rekomendowane linie cięcia
-
-### 1. Zachowaj nienaruszoną zgodność runtime SQLite
-
-Nie zastępuj `SqliteAdapter` ani kaskady driverów w pierwszym PR dotyczącym repozytoriów. Zachowaj odzyskiwanie plików,
-WAL, backup, optymalizację, FTS5 i zachowanie wektorów za bieżącą implementacją SQLite.
-
-### 2. Zacznij od bezpośrednich konsumentów singletona
-
-Użyj listy 45 plików bezpośrednich konsumentów jako początkowej kolejki przeglądu. Sklasyfikuj każdy plik jako:
-
-- przenośny stan domenowy;
-- konserwację lub wyszukiwanie specyficzne dla backendu;
-- stan lokalny dla procesu lub możliwy do odbudowy;
-- dostęp legacy, który powinien wywoływać istniejący moduł domenowy.
-
-Klasyfikacja musi poprzedzać projekt interfejsu. Samo pojawienie się ścieżki w inwentaryzacji nie jest
-nakazem utworzenia repozytorium.
-
-### 3. Najpierw udowodnij repozytoria na SQLite
-
-Dla jednej ograniczonej domeny:
-
-1. zdefiniuj operacje repozytorium zorientowane na zachowanie;
-2. zaadaptuj bieżące zapytania SQLite za tym repozytorium;
-3. uruchom testy zgodności zachowania i transakcji względem SQLite;
-4. zmigruj wywołujących bez zmiany domyślnego runtime;
-5. dopiero potem zaimplementuj to samo repozytorium dla zewnętrznego backendu.
-
-### 4. Oddziel przenośny stan control-plane od danych specyficznych dla możliwości
-
-Połączenia providerów, klucze API, combos i konfiguracja routingu są kandydatami na pierwszy
-przenośny plaster, z zastrzeżeniem zatwierdzenia przez maintainerów i przeglądu ownership tabel. Wyszukiwanie wektorowe memory,
-backup/odzyskiwanie plików SQLite oraz optymalizacja bazy danych to słabe pierwsze plastry, ponieważ ich zachowanie
-jest celowo specyficzne dla SQLite.
-
-### 5. Traktuj usage, quota, affinity i audit jako późniejszy plaster koordynacji
-
-Te domeny mają semantykę współbieżności i wolumenu wykraczającą poza CRUD. Ich kontrakty repozytoriów powinny
-być projektowane razem z testami transakcji multi-replica, lease, retencji i trybów awarii, a nie
-kopiowane mechanicznie z bieżącego SQL.
-
-## Czego ta inwentaryzacja nie rozstrzyga
-
-Ta inwentaryzacja nie:
-
-- zatwierdza wsparcia PostgreSQL ani MySQL;
-- definiuje interfejsów TypeScript repozytoriów;
-- wybiera pierwszej tabeli ani domeny do migracji;
-- twierdzi, że każde dopasowanie leksykalne jest defektem;
-- twierdzi, że obecne granice modułów są nieskuteczne;
-- zmienia SQLite, migracji, backupu, wyszukiwania ani zachowania runtime.
-
-Jej celem jest uczynienie kolejnej dyskusji projektowej opartej na dowodach i odtwarzalnej.

docs/i18n/pl/docs/combo-context-requirements.md

@@ -1,262 +0,0 @@
-# Funkcja wymagań kontekstu combo (Context Requirements)
-
-## Przegląd
-
-Funkcja Context Requirements pozwala konfiguracjom combo filtrować i sortować cele (targets) na podstawie rozmiaru okna kontekstu. Jest to przydatne w przypadkach użycia wymagających dużych okien kontekstu, takich jak:
-
-- Przetwarzanie długich dokumentów (100k+ tokenów)
-- Analiza dużych baz kodu
-- Rozbudowane historie rozmów
-- Przeglądy kodu obejmujące wiele plików
-
-## Konfiguracja
-
-### Schemat
-
-Dodaj `contextRequirements` do runtime config swojego combo:
-
-```json
-{
-  "contextRequirements": {
-    "minContextWindow": 128000,
-    "preferLargeContext": true,
-    "contextFilterMode": "strict"
-  }
-}
-```
-
-### Pola
-
-#### `minContextWindow` (opcjonalne)
-
-- **Typ**: `number` (0 do 10,000,000)
-- **Domyślnie**: `undefined` (bez filtrowania)
-- **Opis**: Odfiltrowuje modele z oknami kontekstu poniżej tego progu
-
-**Przykłady**:
-
-- `32000` - Odfiltruj modele z kontekstem <32K
-- `128000` - Wymagaj kontekstu 128K+ (GPT-4 Turbo, Claude 3)
-- `200000` - Wymagaj kontekstu 200K+ (Claude 3 Opus)
-- `1000000` - Wymagaj kontekstu 1M+ (Gemini 1.5 Pro)
-
-#### `preferLargeContext` (opcjonalne)
-
-- **Typ**: `boolean`
-- **Domyślnie**: `false`
-- **Opis**: Gdy `true`, sortuje pozostałe cele według rozmiaru kontekstu (malejąco). Modele z dużym kontekstem są próbowane jako pierwsze.
-
-#### `contextFilterMode` (opcjonalne)
-
-- **Typ**: `"strict"` | `"lenient"`
-- **Domyślnie**: `"lenient"`
-- **Opis**: Sposób obsługi modeli z nieznanymi limitami okna kontekstu
-  - `"strict"`: Wyklucza modele z nieznanymi limitami kontekstu
-  - `"lenient"`: Uwzględnia modele z nieznanymi limitami kontekstu
-
-## Zachowanie
-
-### Potok filtrowania
-
-Wymagania kontekstu są stosowane po `filterTargetsByRequestCompatibility()`:
-
-1. **Filtrowanie zgodności żądania** - Usuwa modele niekompatybilne z żądaniem (tools, vision, structured output)
-2. **Filtrowanie wymagań kontekstu** - Stosuje `minContextWindow` i `contextFilterMode`
-3. **Sortowanie według kontekstu** - Jeśli `preferLargeContext` jest true, sortuje malejąco według rozmiaru kontekstu
-
-### Logika trybu filtrowania
-
-Gdy ustawiono `minContextWindow`:
-
-**Tryb lenient** (domyślny):
-
-- ✅ Uwzględnia modele z kontekstem >= minContextWindow
-- ✅ Uwzględnia modele z nieznanymi limitami kontekstu
-- ❌ Wyklucza modele z kontekstem < minContextWindow
-
-**Tryb strict**:
-
-- ✅ Uwzględnia modele z kontekstem >= minContextWindow
-- ❌ Wyklucza modele z nieznanymi limitami kontekstu
-- ❌ Wyklucza modele z kontekstem < minContextWindow
-
-### Logika sortowania
-
-Gdy `preferLargeContext` jest true:
-
-- Modele są sortowane według rozmiaru okna kontekstu (malejąco)
-- Modele z nieznanym kontekstem trafiają na koniec
-- Oryginalna kolejność strategii służy jako rozstrzygnięcie remisów
-
-## Przypadki użycia
-
-### Przykład 1: Przetwarzanie długich dokumentów
-
-```json
-{
-  "name": "Document Analysis",
-  "strategy": "fusion",
-  "config": {
-    "contextRequirements": {
-      "minContextWindow": 128000,
-      "preferLargeContext": true,
-      "contextFilterMode": "strict"
-    }
-  }
-}
-```
-
-Ta konfiguracja:
-
-- Wymaga okna kontekstu 128K+
-- Preferuje modele z większym kontekstem (Gemini 1.5 Pro > Claude 3 Opus > GPT-4 Turbo)
-- Wyklucza modele z nieznanymi limitami kontekstu
-
-### Przykład 2: Analiza dużej bazy kodu
-
-```json
-{
-  "name": "Code Review",
-  "strategy": "auto",
-  "config": {
-    "contextRequirements": {
-      "minContextWindow": 200000,
-      "preferLargeContext": true,
-      "contextFilterMode": "lenient"
-    }
-  }
-}
-```
-
-Ta konfiguracja:
-
-- Wymaga okna kontekstu 200K+
-- Preferuje modele z większym kontekstem
-- Uwzględnia modele z nieznanymi limitami (lenient)
-
-### Przykład 3: Preferencja dużego kontekstu bez ścisłych wymagań
-
-```json
-{
-  "name": "Flexible Chat",
-  "strategy": "weighted",
-  "config": {
-    "contextRequirements": {
-      "preferLargeContext": true
-    }
-  }
-}
-```
-
-Ta konfiguracja:
-
-- Brak minimalnego wymagania (wszystkie modele kwalifikują się)
-- Sortuje według rozmiaru kontekstu (największy najpierw)
-- Przydatne, gdy duży kontekst jest preferowany, ale nie wymagany
-
-## Odpowiedź API
-
-Gdy wymagania kontekstu filtrują cele, logger combo wypisuje:
-
-```
-[COMBO] Context requirements: filtered 10 → 3 targets (minContextWindow: 128000, mode: strict)
-[COMBO] Context requirements: kept models gemini-1.5-pro, claude-3-opus-20240229, gpt-4-turbo
-[COMBO] Context requirements: sorted by context size (descending): gemini-1.5-pro(1000000), claude-3-opus-20240229(200000), gpt-4-turbo(128000)
-```
-
-## Szczegóły implementacji
-
-### Moduł backendu
-
-`open-sse/services/combo/contextRequirements.ts`:
-
-- `applyContextRequirements()` - Główna funkcja filtrowania
-- `getTargetContextWindow()` - Pomocnicza funkcja wyszukiwania kontekstu
-- Używa `getModelContextLimit()` z `modelCapabilities.ts`
-
-### Punkt integracji
-
-`open-sse/services/combo.ts` linia 1187:
-
-```typescript
-orderedTargets = filterTargetsByRequestCompatibility(orderedTargets, body, log);
-orderedTargets = applyContextRequirements(orderedTargets, config.contextRequirements, log);
-```
-
-### Definicja schematu
-
-`src/shared/validation/schemas/combo.ts`:
-
-```typescript
-contextRequirements: z
-  .object({
-    minContextWindow: z.coerce.number().int().min(0).max(10_000_000).optional(),
-    preferLargeContext: z.boolean().optional(),
-    contextFilterMode: z.enum(["strict", "lenient"]).optional(),
-  })
-  .strict()
-  .optional(),
-```
-
-## Testowanie
-
-### Uruchamianie testów
-
-```bash
-# Unit tests (schema + logic)
-npm test tests/unit/combo-context-requirements.test.ts
-
-# Integration tests (end-to-end)
-npm test tests/unit/combo/context-requirements-integration.test.ts
-```
-
-### Pokrycie testami
-
-- Walidacja schematu: 6 testów
-- Logika filtrowania: 6 testów
-- Integracja: 5 testów
-- **Razem**: 17/17 przechodzi ✅
-
-## Rozwiązywanie problemów
-
-### Wszystkie cele odfiltrowane
-
-**Problem**: Wszystkie cele usunięte, combo zwraca „no compatible models”
-
-**Rozwiązania**:
-
-1. Obniż próg `minContextWindow`
-2. Przełącz na tryb `"lenient"`, aby uwzględnić modele z nieznanym kontekstem
-3. Usuń `minContextWindow` i używaj wyłącznie `preferLargeContext`
-
-### Modele z nieznanym kontekstem wykluczone
-
-**Problem**: Niestandardowe/nowe modele wykluczone, mimo że mają duży kontekst
-
-**Rozwiązania**:
-
-1. Przełącz na tryb `"lenient"` (domyślny)
-2. Dodaj limit kontekstu modelu w `modelCapabilities.ts`
-3. Usuń filtrowanie kontekstu i polegaj na kolejności strategii
-
-### Sortowanie nie jest stosowane
-
-**Problem**: `preferLargeContext` nie zmienia kolejności
-
-**Sprawdź**:
-
-1. Zweryfikuj `preferLargeContext: true` w config
-2. Sprawdź, czy wszystkie cele mają nieznany kontekst (wszystkie sortują się równo)
-3. Upewnij się, że po filtrowaniu pozostało wiele celów
-
-## Powiązane
-
-- [Strategie routingu Auto-Combo](./routing/AUTO-COMBO.md)
-- [Przewodnik po odporności (Resilience)](./architecture/RESILIENCE_GUIDE.md)
-
-## Historia wersji
-
-- **v3.8.47**: Pierwsza implementacja
-  - Dodano config `contextRequirements`
-  - Utworzono backendowy moduł filtrowania
-  - Pełne pokrycie testami (brak jeszcze dedykowanego UI w dashboardzie — konfiguracja przez combo JSON)

docs/i18n/pl/docs/getting-started/TROUBLESHOOTING.md

@@ -1,498 +0,0 @@
----
-title: "Rozwiązywanie problemów"
-version: 3.8.40
-lastUpdated: 2026-06-28
----
-
-# Rozwiązywanie problemów
-
-> **Dla użytkowników**: Szukasz szybkich poprawek? Zobacz [Szybki przewodnik](#quick-reference) poniżej.
-
-🌐 **Languages:** 🇺🇸 [English](./TROUBLESHOOTING.md) | 🇧🇷 [Português (Brasil)](../i18n/pt-BR/docs/guides/TROUBLESHOOTING.md) | 🇪🇸 [Español](../i18n/es/docs/guides/TROUBLESHOOTING.md) | 🇫🇷 [Français](../i18n/fr/docs/guides/TROUBLESHOOTING.md) | 🇮🇹 [Italiano](../i18n/it/docs/guides/TROUBLESHOOTING.md) | 🇷🇺 [Русский](../i18n/ru/docs/guides/TROUBLESHOOTING.md) | 🇨🇳 [中文 (简体)](../i18n/zh-CN/docs/guides/TROUBLESHOOTING.md) | 🇩🇪 [Deutsch](../i18n/de/docs/guides/TROUBLESHOOTING.md) | 🇮🇳 [हिन्दी](../i18n/in/docs/guides/TROUBLESHOOTING.md) | 🇹🇭 [ไทย](../i18n/th/docs/guides/TROUBLESHOOTING.md) | 🇺🇦 [Українська](../i18n/uk-UA/docs/guides/TROUBLESHOOTING.md) | 🇸🇦 [العربية](../i18n/ar/docs/guides/TROUBLESHOOTING.md) | 🇯🇵 [日本語](../i18n/ja/docs/guides/TROUBLESHOOTING.md) | 🇻🇳 [Tiếng Việt](../i18n/vi/docs/guides/TROUBLESHOOTING.md) | 🇧🇬 [Български](../i18n/bg/docs/guides/TROUBLESHOOTING.md) | 🇩🇰 [Dansk](../i18n/da/docs/guides/TROUBLESHOOTING.md) | 🇫🇮 [Suomi](../i18n/fi/docs/guides/TROUBLESHOOTING.md) | 🇮🇱 [עברית](../i18n/he/docs/guides/TROUBLESHOOTING.md) | 🇭🇺 [Magyar](../i18n/hu/docs/guides/TROUBLESHOOTING.md) | 🇮🇩 [Bahasa Indonesia](../i18n/id/docs/guides/TROUBLESHOOTING.md) | 🇰🇷 [한국어](../i18n/ko/docs/guides/TROUBLESHOOTING.md) | 🇲🇾 [Bahasa Melayu](../i18n/ms/docs/guides/TROUBLESHOOTING.md) | 🇳🇱 [Nederlands](../i18n/nl/docs/guides/TROUBLESHOOTING.md) | 🇳🇴 [Norsk](../i18n/no/docs/guides/TROUBLESHOOTING.md) | 🇵🇹 [Português (Portugal)](../i18n/pt/docs/guides/TROUBLESHOOTING.md) | 🇷🇴 [Română](../i18n/ro/docs/guides/TROUBLESHOOTING.md) | 🇵🇱 [Polski](../i18n/pl/docs/guides/TROUBLESHOOTING.md) | 🇸🇰 [Slovenčina](../i18n/sk/docs/guides/TROUBLESHOOTING.md) | 🇸🇪 [Svenska](../i18n/sv/docs/guides/TROUBLESHOOTING.md) | 🇵🇭 [Filipino](../i18n/phi/docs/guides/TROUBLESHOOTING.md) | 🇨🇿 [Čeština](../i18n/cs/docs/guides/TROUBLESHOOTING.md)
-
-Typowe problemy i rozwiązania dla OmniRoute.
-
----
-
-## Szybki przewodnik
-
-**Nowy w OmniRoute?** Zacznij tutaj — te wskazówki rozwiązują 90% problemów:
-
-| Widzę to                | Co to oznacza                      | Co zrobić                                                                            |
-| ----------------------- | ---------------------------------- | ------------------------------------------------------------------------------------ |
-| "Can't connect"         | OmniRoute nie działa               | Uruchom `omniroute` lub `docker restart omniroute`                                   |
-| "Invalid API key"       | Klucz jest błędny lub wygasł       | Skopiuj ponownie klucz ze strony providera                                           |
-| "Rate limit exceeded"   | Wysyłasz zbyt wiele żądań          | Poczekaj 1 minutę albo użyj `model: "auto"` do automatycznego fallbacku              |
-| "Quota exceeded"        | Wykorzystałeś darmowy/płatny limit | Podłącz więcej providerów albo użyj darmowych (Kiro, Pollinations)                   |
-| "Slow responses"        | Provider jest obciążony lub daleko | Użyj `model: "auto/fast"` albo podłącz szybszego providera (Groq, Cerebras)          |
-| "Wrong provider used"   | `auto` wybrał innego providera     | To normalne! `auto` wybiera najlepszego. Wymuś konkretnego: `model: "openai/gpt-4o"` |
-| "502 Bad Gateway"       | Provider nie działa                | Poczekaj i spróbuj ponownie albo użyj `model: "auto"`, aby przełączyć providera      |
-| "401 Unauthorized"      | Błędne dane uwierzytelniające      | Sprawdź klucz API albo ponownie uwierzytelnij się przez OAuth                        |
-| "429 Too Many Requests" | Limit zapytań                      | Poczekaj 1 minutę albo podłącz więcej providerów                                     |
-
-**Nadal utknąłeś?** Zobacz [Szybkie poprawki](#quick-fixes) poniżej albo zapytaj na [Discordzie](https://discord.gg/U47eFqAXCn).
-
----
-
-## Ostrzeżenia npm install (ERESOLVE / peer / deprecated)
-
-Po `npm install -g omniroute` możesz zobaczyć lawinę ostrzeżeń typu `npm warn ERESOLVE`, komunikaty o peer-dependency oraz `deprecated`. **Są one oczekiwane i nieszkodliwe.** Instalacja się powiodła, jeśli w wyniku widać `added <N> packages`.
-
-Ostrzeżenia pochodzą z przestarzałych zakresów peer-dependency w pakietach firm trzecich, których OmniRoute nie kontroluje:
-
-1. **`marked-terminal` chce `marked >=1 <16`, znaleziono `marked@18`** — w praktyce działa poprawnie; zakres peer po stronie upstream jest po prostu nieaktualny.
-2. **`deprecated prebuild-install@7.1.3`** — helper do pobierania natywnych binarek. Istotny dopiero później, jeśli provider web-cookie zgłosi brak natywnej binarki `tls-client-node` (osobny problem, nie spowodowany tym ostrzeżeniem).
-
-**Nie trzeba nic robić** — ostrzeżeń nie da się w pełni wyciszyć bez forka pakietów upstream.
-
----
-
-## Szybkie poprawki
-
-| Problem                                             | Rozwiązanie                                                                                                                                                                |
-| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Pierwsze logowanie nie działa                       | Ustaw `INITIAL_PASSWORD` w `.env` (brak wbudowanego domyślnego hasła)                                                                                                      |
-| Dashboard otwiera się na złym porcie                | Ustaw `PORT=20128` i `NEXT_PUBLIC_BASE_URL=http://localhost:20128`                                                                                                         |
-| Brak logów na dysku                                 | Ustaw `APP_LOG_TO_FILE=true` i upewnij się, że przechwytywanie call log jest włączone                                                                                      |
-| EACCES: permission denied                           | Ustaw `DATA_DIR=/path/to/writable/dir`, aby nadpisać `~/.omniroute`                                                                                                        |
-| Strategia routingu się nie zapisuje                 | Zaktualizuj do najnowszego wydania v3.x (poprawka schematu Zod dla persystencji ustawień weszła we wcześniejszych wersjach)                                                |
-| Crash logowania / pusta strona                      | Sprawdź wersję Node.js — zobacz [Zgodność z Node.js](#nodejs-compatibility) poniżej                                                                                        |
-| `dlopen` / `slice is not valid mach-o file` (macOS) | Uruchom `cd $(npm root -g)/omniroute/app && npm rebuild better-sqlite3 && omniroute` — zobacz [przebudowa modułu natywnego na macOS](#macos-native-module-rebuild) poniżej |
-| Proxy "fetch failed"                                | Upewnij się, że konfiguracja proxy jest ustawiona na właściwym poziomie — zobacz [Problemy z proxy](#proxy-issues) poniżej                                                 |
-
----
-
-## Zgodność z Node.js
-
-<a name="nodejs-compatibility"></a>
-
-### Strona logowania się wykrzacza lub pokazuje błąd "Module self-registration"
-
-**Przyczyna:** Uruchamiasz wersję Node.js poniżej zatwierdzonego bezpiecznego poziomu runtime OmniRoute. Najczęstszy przypadek to starszy patch Node 22 lub 24 poniżej wymaganego przez OmniRoute poziomu bezpieczeństwa.
-
-**Objawy:**
-
-- Strona logowania pokazuje pusty ekran lub błąd serwera
-- Konsola pokazuje `Error: Module did not self-register` lub podobne błędy natywnych bindingów
-- Strona logowania pokazuje **pomarańczowy baner ostrzegawczy** z Twoją wersją Node, jeśli runtime jest poza wspieraną bezpieczną polityką
-
-**Naprawa:**
-
-1. Zainstaluj wspierane wydanie Node.js LTS (zalecane: Node.js 24.x):
-   ```bash
-   nvm install 24
-   nvm use 24
-   ```
-2. Sprawdź wersję: `node --version` powinno pokazać `v24.0.0` lub nowsze w linii LTS 24.x
-3. Zainstaluj ponownie OmniRoute: `npm install -g omniroute`
-4. Uruchom ponownie: `omniroute`
-
-> **Wspierane bezpieczne wersje:** `>=22.22.2 <23` lub `>=24.0.0 <27`. Node.js 24.x LTS (Krypton) oraz Node.js 26 są w pełni wspierane.
-
-### macOS: `dlopen` / "slice is not valid mach-o file"
-
-<a name="macos-native-module-rebuild"></a>
-
-**Przyczyna:** Po globalnym `npm install -g omniroute` natywna binarka `better-sqlite3` w pakiecie mogła zostać skompilowana pod inną architekturę lub ABI Node.js niż ta, która działa lokalnie. To częste na macOS (Apple Silicon i Intel), gdy prebuilt nie pasuje do środowiska.
-
-**Objawy:**
-
-- Serwer pada natychmiast przy starcie z błędem `dlopen`
-- Błąd zawiera `slice is not valid mach-o file`
-- Pełny przykład:
-
-```
-dlopen(/Users/<user>/.nvm/versions/node/v24.14.1/lib/node_modules/omniroute/app/node_modules/better-sqlite3/build/Release/better_sqlite3.node, 0x0001): tried: '...' (slice is not valid mach-o file)
-```
-
-**Naprawa — przebuduj pod lokalne środowisko (bez downgrade Node.js):**
-
-```bash
-cd $(npm root -g)/omniroute/app
-npm rebuild better-sqlite3
-omniroute
-```
-
-> **Uwaga:** To rekompiluje natywny binding względem lokalnej wersji Node.js i architektury CPU, usuwając niedopasowanie binarki. Oficjalnie wspierany zakres runtime to **`>=22.22.2 <23` lub `>=24.0.0 <27`** (`SUPPORTED_NODE_RANGE` w `src/shared/utils/nodeRuntimeSupport.ts`, zgodny z polem `engines` w `package.json`). Node.js 24.x LTS (Krypton) oraz Node.js 26 są w pełni wspierane z `better-sqlite3` v12.x.
-
----
-
-## Problemy z proxy
-
-<a name="proxy-issues"></a>
-
-### Walidacja providera pokazuje "fetch failed"
-
-**Przyczyna:** Endpoint walidacji klucza API (`POST /api/providers/validate`) wcześniej omijał konfigurację proxy, co powodowało błędy w środowiskach wymagających routingu przez proxy.
-
-**Naprawa (v3.5.5+):** To już naprawione. Walidacja providera idzie przez `runWithProxyContext` i automatycznie respektuje ustawienia proxy na poziomie providera oraz globalne.
-
-### Token health check kończy się "fetch failed"
-
-**Przyczyna:** Tło odświeżania tokenów OAuth nie rozwiązywało konfiguracji proxy per połączenie.
-
-**Naprawa (v3.5.5+):** Scheduler token health check rozwiązuje teraz config proxy per połączenie przed odświeżeniem. Zaktualizuj do v3.5.5+.
-
-### Proxy SOCKS5 zwraca "invalid onRequestStart method"
-
-**Przyczyna:** Na Node.js 22 dispatcher undici@8 jest niekompatybilny z wbudowaną implementacją `fetch()` w Node.
-
-**Naprawa (v3.5.5+):** OmniRoute używa teraz własnej funkcji `fetch()` z undici, gdy aktywny jest dispatcher proxy, co zapewnia spójne zachowanie. Zaktualizuj do v3.5.5+.
-
----
-
-## Problemy z providerami
-
-### "Language model did not provide messages"
-
-**Przyczyna:** Wyczerpany limit (quota) providera.
-
-**Naprawa:**
-
-1. Sprawdź tracker limitu w dashboardzie
-2. Użyj combo z poziomami fallback
-3. Przełącz się na tańszy/darmowy tier
-
-### Rate limiting
-
-**Przyczyna:** Wyczerpany limit subskrypcji.
-
-**Naprawa:**
-
-- Dodaj fallback: `cc/claude-opus-4-6 → glm/glm-4.7 → if/qwen3.8-max-preview`
-- Użyj GLM/MiniMax jako taniego zapasowego
-
-### Wygasły token OAuth
-
-OmniRoute automatycznie odświeża tokeny. Jeśli problemy trwają:
-
-1. Dashboard → Provider → Reconnect
-2. Usuń i dodaj ponownie połączenie providera
-
-### Kiro multi-account: drugie konto unieważnia pierwsze
-
-**Przyczyna:** Backend Kiro wymusza jedną aktywną sesję na rejestrację klienta OIDC.
-Gdy dwa konta współdzielą tego samego zarejestrowanego klienta (połączenia zaimportowane przed v3.8.0),
-odświeżenie tokenu jednego konta unieważnia refresh token drugiego.
-
-**Naprawa (v3.8.0+):** Zaimportuj ponownie dotknięte połączenia.
-Od v3.8.0 każde nowe połączenie Kiro utworzone przez **Import Token**,
-**Google/GitHub social login** lub **Auto-Import** automatycznie rejestruje własnego
-dedykowanego klienta OIDC. Połączenie jest więc w pełni izolowane i odświeżenie jednego
-konta nie wpływa na żadne inne.
-
-Połączenia zaimportowane _przed_ v3.8.0 nie niosą rejestracji klienta per połączenie.
-Te połączenia nadal używają współdzielonego endpointu odświeżania social-auth.
-Aby uzyskać izolację, usuń stare połączenie z Dashboard → Providers i dodaj je ponownie
-przez dowolny z trzech przepływów importu.
-
-Pełne szczegóły i instrukcja krok po kroku dodawania dwóch kont Kiro obok siebie:
-zobacz [`docs/guides/KIRO_SETUP.md`](../guides/KIRO_SETUP.md).
-
----
-
-## Problemy z chmurą
-
-### Błędy synchronizacji chmury
-
-1. Sprawdź, czy `BASE_URL` wskazuje na działającą instancję (np. `http://localhost:20128`)
-2. Sprawdź, czy `CLOUD_URL` wskazuje na endpoint chmury (np. `https://omniroute.dev`)
-3. Utrzymuj wartości `NEXT_PUBLIC_*` zgodne z wartościami po stronie serwera
-
-### Cloud `stream=false` zwraca 500
-
-**Objaw:** `Unexpected token 'd'...` na endpoincie chmury przy wywołaniach bez streamingu.
-
-**Przyczyna:** Upstream zwraca payload SSE, a klient oczekuje JSON.
-
-**Obejście:** Użyj `stream=true` przy bezpośrednich wywołaniach cloud. Lokalny runtime ma fallback SSE→JSON.
-
-### Cloud pokazuje Connected, ale "Invalid API key"
-
-1. Utwórz świeży klucz z lokalnego dashboardu (`/api/keys`)
-2. Uruchom synchronizację chmury: Enable Cloud → Sync Now
-3. Stare/niesynchronizowane klucze mogą nadal zwracać `401` w chmurze
-
----
-
-## Problemy z Dockerem
-
-### Narzędzie CLI pokazuje Not Installed
-
-1. Sprawdź pola runtime: `curl http://localhost:20128/api/cli-tools/runtime/codex | jq`
-2. Dla trybu portable: użyj targetu obrazu `runner-cli` (dołączone CLI)
-3. Dla trybu host mount: ustaw `CLI_EXTRA_PATHS` i zamontuj katalog bin hosta jako tylko do odczytu
-4. Jeśli `installed=true` i `runnable=false`: binarka znaleziona, ale healthcheck się nie powiódł
-
-### Szybka walidacja runtime
-
-```bash
-curl -s http://localhost:20128/api/cli-tools/codex-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-curl -s http://localhost:20128/api/cli-tools/claude-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-curl -s http://localhost:20128/api/cli-tools/openclaw-settings | jq '{installed,runnable,commandPath,runtimeMode,reason}'
-```
-
----
-
-## Problemy z kosztami
-
-### Wysokie koszty
-
-1. Sprawdź statystyki użycia w Dashboard → Usage
-2. Przełącz model główny na GLM/MiniMax
-3. Używaj darmowego tieru (Qoder, Kiro) do mniej krytycznych zadań
-4. Ustaw budżety kosztów per klucz API: Dashboard → API Keys → Budget
-
----
-
-## Debugowanie
-
-### Włącz pliki logów
-
-Ustaw `APP_LOG_TO_FILE=true` w pliku `.env`. Logi aplikacji trafiają do `logs/`.
-Artefakty żądań są przechowywane w `${DATA_DIR}/call_logs/`, gdy pipeline call log jest
-włączony w ustawieniach.
-Gdy przechwytywanie pipeline jest włączone, ustaw `CALL_LOG_PIPELINE_CAPTURE_STREAM_CHUNKS=false`, aby pominąć
-payloady chunków streamu, albo dostrój `CALL_LOG_PIPELINE_MAX_SIZE_KB`, aby zmienić limit artefaktu w KB.
-
-### Sprawdź zdrowie providerów
-
-```bash
-# Health dashboard
-http://localhost:20128/dashboard/health
-
-# API health check
-curl http://localhost:20128/api/monitoring/health
-```
-
-### Przechowywanie w runtime
-
-- Stan główny: `${DATA_DIR}/storage.sqlite` (providers, combos, aliases, keys, settings)
-- Użycie: tabele SQLite w `storage.sqlite` (`usage_history`, `call_logs`, `proxy_logs`) + opcjonalnie `${DATA_DIR}/call_logs/`
-- Logi aplikacji: `<repo>/logs/...` (gdy `APP_LOG_TO_FILE=true`)
-- Artefakty call log: `${DATA_DIR}/call_logs/YYYY-MM-DD/...` gdy pipeline call log jest włączony
-
-Akcja **Clean history** na stronie Request Logs czyści `call_logs`, legacy
-`request_detail_logs` oraz lokalny katalog artefaktów `${DATA_DIR}/call_logs/`.
-
----
-
-## Problemy z circuit breakerem
-
-### Provider utknął w stanie OPEN
-
-Gdy circuit breaker providera jest OPEN, żądania są blokowane do wygaśnięcia cooldownu.
-
-**Naprawa:**
-
-1. Przejdź do **Dashboard → Settings → Resilience**
-2. Sprawdź kartę circuit breakera dla dotkniętego providera
-3. Kliknij **Reset All**, aby wyczyścić wszystkie breakery, albo poczekaj na wygaśnięcie cooldownu
-4. Upewnij się, że provider jest faktycznie dostępny przed resetem
-
-### Provider wciąż wyzwala circuit breaker
-
-Jeśli provider wielokrotnie wchodzi w stan OPEN:
-
-1. Sprawdź **Dashboard → Health → Provider Health** pod kątem wzorca awarii
-2. Przejdź do **Settings → Resilience → Provider Profiles** i zwiększ próg awarii
-3. Sprawdź, czy provider zmienił limity API lub wymaga ponownego uwierzytelnienia
-4. Przejrzyj telemetrię opóźnień — wysoka latencja może powodować awarie oparte na timeoutach
-
----
-
-## Problemy z transkrypcją audio
-
-### Błąd "Unsupported model"
-
-- Upewnij się, że używasz właściwego prefiksu: `deepgram/nova-3` lub `assemblyai/best`
-- Sprawdź, czy provider jest podłączony w **Dashboard → Providers**
-
-### Transkrypcja zwraca pusto lub się nie udaje
-
-- Sprawdź wspierane formaty audio: `mp3`, `wav`, `m4a`, `flac`, `ogg`, `webm`
-- Upewnij się, że rozmiar pliku mieści się w limitach providera (zazwyczaj < 25MB)
-- Sprawdź ważność klucza API na karcie providera
-
----
-
-## Debugowanie translatora
-
-Użyj **Dashboard → Translator**, aby debugować problemy z tłumaczeniem formatów:
-
-| Tryb             | Kiedy używać                                                                                   |
-| ---------------- | ---------------------------------------------------------------------------------------------- |
-| **Playground**   | Porównaj formaty wejścia/wyjścia obok siebie — wklej padające żądanie, by zobaczyć tłumaczenie |
-| **Chat Tester**  | Wysyłaj żywe wiadomości i przeglądaj pełny payload request/response wraz z nagłówkami          |
-| **Test Bench**   | Uruchamiaj testy wsadowe na kombinacjach formatów, by znaleźć zepsute tłumaczenia              |
-| **Live Monitor** | Obserwuj przepływ żądań w czasie rzeczywistym, by wyłapać przerywane problemy z tłumaczeniem   |
-
-### Typowe problemy z formatami
-
-- **Brak tagów thinking** — Sprawdź, czy docelowy provider wspiera thinking i ustawienie thinking budget
-- **Znikające tool calls** — Niektóre tłumaczenia formatów mogą usuwać nieobsługiwane pola; sprawdź w trybie Playground
-- **Brak system prompt** — Claude i Gemini obsługują system prompts inaczej; sprawdź wynik tłumaczenia
-- **SDK zwraca surowy string zamiast obiektu** — Naprawione w v1.x; sanitizer odpowiedzi usuwa niestandardowe pola (`x_groq`, `usage_breakdown` itd.), które powodują błędy walidacji Pydantic w OpenAI SDK. Jeśli nadal to widzisz na v3.x+, zgłoś issue.
-- **GLM/ERNIE odrzuca rolę `system`** — Naprawione w v1.x; normalizer ról automatycznie scala wiadomości system w user dla niekompatybilnych modeli. Jeśli nadal to widzisz na v3.x+, zgłoś issue.
-- **Rola `developer` nierozpoznana** — Naprawione w v1.x; automatycznie konwertowana na `system` dla providerów spoza OpenAI. Jeśli nadal to widzisz na v3.x+, zgłoś issue.
-- **`json_schema` nie działa z Gemini** — Naprawione w v1.x; `response_format` jest teraz konwertowany na `responseMimeType` + `responseSchema` Gemini. Jeśli nadal to widzisz na v3.x+, zgłoś issue.
-
----
-
-## Ustawienia odporności (Resilience)
-
-### Auto rate-limit się nie uruchamia
-
-- Auto rate-limit dotyczy tylko providerów z kluczem API (nie OAuth/subskrypcja)
-- Sprawdź, czy **Settings → Resilience → Provider Profiles** ma włączony auto-rate-limit
-- Sprawdź, czy provider zwraca kody `429` lub nagłówki `Retry-After`
-
-### Dostrajanie exponential backoff
-
-Profile providerów wspierają te ustawienia:
-
-- **Base delay** — Początkowy czas oczekiwania po pierwszej awarii (domyślnie: 1s)
-- **Max delay** — Górny limit czasu oczekiwania (domyślnie: 30s)
-- **Multiplier** — O ile zwiększać opóźnienie przy kolejnych awariach (domyślnie: 2x)
-
-### Anti-thundering herd
-
-Gdy wiele równoległych żądań trafia w providera z limitem zapytań, OmniRoute używa mutexa + auto rate-limiting, aby serializować żądania i zapobiegać awariom kaskadowym. Działa to automatycznie dla providerów z kluczem API.
-
----
-
-## Opcjonalna taksonomia awarii RAG / LLM (16 problemów)
-
-Część użytkowników OmniRoute stawia bramkę przed stackami RAG lub agentów. W takich setupach często widać dziwny wzorzec: OmniRoute wygląda na zdrowe (providery w górze, profile routingu OK, brak alertów rate limit), a ostateczna odpowiedź i tak jest błędna.
-
-W praktyce te incydenty zwykle pochodzą z downstreamowego pipeline'u RAG, a nie z samej bramki.
-
-Jeśli chcesz wspólnego słownika do opisu tych awarii, możesz użyć WFGY ProblemMap — zewnętrznego zasobu tekstowego na licencji MIT, który definiuje szesnaście powtarzających się wzorców awarii RAG / LLM. Na wysokim poziomie obejmuje:
-
-- drift retrieval i zerwane granice kontekstu
-- puste lub nieaktualne indeksy i magazyny wektorów
-- niedopasowanie embeddingów do semantyki
-- składanie promptów i problemy z oknem kontekstu
-- zapaść logiki i nadmiernie pewne odpowiedzi
-- awarie długich łańcuchów i koordynacji agentów
-- dryf pamięci i ról w multi-agent
-- problemy z deploymentem i kolejnością bootstrapu
-
-Idea jest prosta:
-
-1. Gdy badziesz złą odpowiedź, zbierz:
-   - zadanie użytkownika i żądanie
-   - trasę lub combo providerów w OmniRoute
-   - kontekst RAG użyty downstream (pobrane dokumenty, tool calls itd.)
-2. Zmapuj incydent na jeden lub dwa numery WFGY ProblemMap (`No.1` … `No.16`).
-3. Zapisz numer we własnym dashboardzie, runbooku lub trackerze incydentów obok logów OmniRoute.
-4. Użyj odpowiadającej strony WFGY, by zdecydować, czy zmienić stack RAG, retriever, czy strategię routingu.
-
-Pełny tekst i konkretne przepisy są tutaj (licencja MIT, tylko tekst):
-
-- [WFGY ProblemMap README](https://github.com/onestardao/WFGY/blob/main/ProblemMap/README.md)
-
-Możesz zignorować tę sekcję, jeśli nie uruchamiasz pipeline'ów RAG ani agentów za OmniRoute.
-
----
-
-## Znane problemy v3.8.0
-
-Problemy specyficzne dla wydania v3.8.0 i ich obecne obejścia. Gdy poprawka wejdzie w późniejszym patchu, wpis zostanie zaktualizowany lub usunięty.
-
-### Błędy auth Devin CLI
-
-**Objawy:**
-
-- "Devin CLI not found" lub "auth failed" przy wywoływaniu narzędzi opartych o Devin
-- Sprawdzenie runtime CLI raportuje `installed=false`
-
-**Przyczyny:**
-
-- `CLI_DEVIN_BIN` wskazuje na nieistniejącą ścieżkę
-- Devin CLI nie jest zainstalowany na hoście
-
-**Naprawa:**
-
-1. Zainstaluj Devin CLI dla swojej platformy
-2. Ustaw `CLI_DEVIN_BIN=/usr/local/bin/devin` (lub rzeczywistą ścieżkę) w `.env`
-3. Zrestartuj OmniRoute i przetestuj ponownie w **Dashboard → CLI Tools**
-
-### Cooldown modelu utknął (ręczny reset)
-
-**Objawy:**
-
-- Model pozostaje na liście cooldown nawet po upływie czasu wygaśnięcia
-- Żądania nadal pomijają model w routingu combo mimo że znacznik czasu jest w przeszłości
-
-**Ręczny reset:**
-
-- **Dashboard:** **Settings → Model Cooldowns** → kliknij **Re-enable** na dotkniętej karcie
-- **API:** `DELETE /api/resilience/model-cooldowns` z nagłówkami auth zarządzania
-
-### Połączenie providera Command Code kończy się 403
-
-**Objawy:**
-
-- 403 przy testowaniu połączenia providera Command Code
-- Karta providera pokazuje "unauthorized" po świeżym dodaniu
-
-**Przyczyna:** Przepływ OAuth nie zakończył się (callback nieodebrany lub token niezapisany).
-
-**Naprawa:**
-
-- Uruchom `omniroute providers` z CLI, aby ponownie wywołać przepływ OAuth, albo
-- Ponów OAuth z **Dashboard → Providers → Command Code → Reconnect**
-
-### ModelScope zwraca agresywne cooldowny 429
-
-**Objawy:**
-
-- Bardzo krótkie lub natychmiastowe cooldowny na ModelScope po małej serii żądań
-- Routing combo pomija ModelScope wcześniej niż oczekiwano
-
-**Przyczyna:** ModelScope emituje specyficzne dla providera nagłówki `Retry-After`. v3.8.0 zawiera dedykowaną obsługę tych nagłówków, więc starsze wersje odczytują je jako generyczne wskazówki rate-limit.
-
-**Naprawa:**
-
-- Upewnij się, że jesteś na v3.8.0 lub nowszej
-- Sprawdź, że przełącznik `useUpstream429BreakerHints` jest włączony w **Settings → Resilience**
-
-### Brak OMNIROUTE_WS_BRIDGE_SECRET w produkcji
-
-**Objawy:**
-
-- 401 na każdym żądaniu mostka WebSocket Codex/Responses na zdalnym hoście produkcyjnym
-- Handshake mostka WebSocket zamyka się natychmiast po połączeniu
-
-**Przyczyna:** Zmienna środowiskowa `OMNIROUTE_WS_BRIDGE_SECRET` nie jest ustawiona w środowisku produkcyjnym.
-
-**Naprawa:**
-
-1. Wygeneruj losowy sekret: `openssl rand -hex 32`
-2. Ustaw `OMNIROUTE_WS_BRIDGE_SECRET=<random-secret>` w env serwera produkcyjnego (oraz każdego klienta łączącego się z mostkiem)
-3. Zrestartuj OmniRoute
-
-### Responses API: tryb background zdegradowany do synchronicznego
-
-**Objawy:**
-
-- Zalogowane ostrzeżenie: `background mode degraded to synchronous`
-- Żądanie z `background: true` zwraca zwykłą odpowiedź synchroniczną zamiast uchwytu zadania w tle
-
-**Przyczyna:** v3.8.0 celowo degraduje `background: true` w Responses API do wykonania synchronicznego z ostrzeżeniem. Pełne asynchroniczne wykonanie w tle to przyszła funkcjonalność.
-
-**Naprawa:**
-
-- Dostosuj klienta, aby wywoływał bez `background`, albo
-- Poczekaj na późniejsze wydanie z pełnym trybem async background (śledź changelog)
-
----
-
-## Nadal utknąłeś?
-
-- **GitHub Issues**: [github.com/diegosouzapw/OmniRoute/issues](https://github.com/diegosouzapw/OmniRoute/issues)
-- **Architektura**: Zobacz [`docs/architecture/ARCHITECTURE.md`](../architecture/ARCHITECTURE.md) po szczegóły wewnętrzne
-- **API Reference**: Zobacz [`docs/reference/API_REFERENCE.md`](../reference/API_REFERENCE.md) po wszystkie endpointy
-- **Health Dashboard**: Sprawdź **Dashboard → Health** pod kątem statusu systemu w czasie rzeczywistym
-- **Translator**: Użyj **Dashboard → Translator** do debugowania problemów z formatami

docs/i18n/pl/docs/ops/MATURITY_REEVAL.md

@@ -1,115 +0,0 @@
----
-title: "Ponowna ocena dojrzałości quality-gate (Fase 9)"
----
-
-# Ponowna ocena dojrzałości — po falach 0–3 (Quality-Gate v2)
-
-> **Czym jest ten dokument.** Ponowny pomiar dojrzałości systemu quality-gates
-> **po** falach 0–3 programu Quality-Gate v2, w porównaniu z baseline zapisanym w
-> [`QUALITY_GATE_PLAYBOOK.md`](./QUALITY_GATE_PLAYBOOK.md) (2026-06-16). Mierzy, co się zmieniło,
-> względem DSOMM L5 / OpenSSF Scorecard 9 / SLSA L3, rozdzielając to, co jest **mierzalne w CI**
-> (już dostarczone / możliwe do dostarczenia kodem) od tego, co jest **procesem/właścicielem** (ustawienia organizacji).
->
-> **Data:** 2026-06-30. Wygenerowano ze rzeczywistego stanu repozytorium, nie z pamięci.
-> **Benchmarki:** OWASP DSOMM · OpenSSF Scorecard · SLSA · SonarQube "Clean as You Code".
-
----
-
-## 1. Zaktualizowany werdykt
-
-**Ocena ogólna: A− → A („Advanced”, top ~5%).** **Dwie największe słabości strukturalne**
-baseline z 06-16 — _fast-gates gap_ oraz _mutation-score-not-a-ratchet_ — zostały **zamknięte**.
-Pozostałe luki do „absolutnego maksimum” są niemal wyłącznie **zależne od właściciela/infrastruktury** (branch-protection,
-SLSA L3, CodeQL advanced); strona kodowa programu jest zasadniczo ukończona.
-
-| Framework referencyjny            | Baseline 06-16               | Teraz 06-30                                                          | Ruch | Dowód                                                                       |
-| --------------------------------- | ---------------------------- | -------------------------------------------------------------------- | ---- | --------------------------------------------------------------------------- |
-| **OWASP DSOMM** (5 levels)        | L3→L4                        | **L4** w _Test Intensity_ i _Static Depth_; solidne L3 w pozostałych | ▲    | blocking mutation-ratchet + deterministic suite at merge gate               |
-| **OpenSSF Scorecard**             | ~7–8/10                      | ~7–8/10 (bez zmian — bramka to **właściciel**)                       | =    | brak Branch-Protection na `main` (ustawienie właściciela) + actions pinning |
-| **SLSA**                          | L2→L3                        | **L2** (zbliżanie się do L3)                                         | =    | brak hermetic/reproducible builder (infra/właściciel)                       |
-| **SonarQube "Clean as You Code"** | Zgodne z zastrzeżeniem       | Zgodne z zastrzeżeniem                                               | =    | zastrzeżenie _sprawl_ (~46+ gates) nadal — przegląd ROI w toku              |
-| **Quality-Ratchet pattern**       | Exemplar                     | **Exemplar+**                                                        | ▲    | nowy `dedicatedGate` dla `mutationScore` (direction up)                     |
-| **Mutation testing**              | „Almost there” (nie ratchet) | **Active ratchet**                                                   | ▲▲   | `check-mutation-ratchet.mjs` + seeded baseline + blocking nightly job       |
-
----
-
-## 2. Delty od 2026-06-16 (co dostarczyły fale 0–3)
-
-### 2.1 🔴→✅ Luka fast-gates ZAMKNIĘTA (była słabość strukturalna #1)
-
-Baseline ostrzegał: `quality.yml` (PR→`release/**`) uruchamiał **tylko filesystem gates** — bez
-typecheck, tests ani build —, więc deterministyczne regresje wybuchały dopiero przy PR→`main`.
-**Dziś** `.github/workflows/quality.yml` uruchamia w jobie _Fast Quality Gates_: `typecheck:core`,
-**blocking impacted unit tests (TIA) z fail-safe do pełnego suite**,
-vitest fast-path oraz unit shards. Bramka działa teraz **tam, gdzie następuje merge** (shift-left),
-dokładnie zgodnie z zasadą cross-cutting przepisaną w playbooku.
-
-### 2.2 🟠→✅ Mutation score stał się RATCHETEM (była słabość #3 / P0 #1)
-
-Najsilniejsze antidotum na coverage-gaming było **advisory**. **Dziś**:
-
-- `scripts/check/check-mutation-ratchet.mjs` (domyślnie advisory, `--ratchet` blocking, graceful skip);
-- `config/quality/quality-baseline.json` ma zaseedowane wpisy `mutationScore.<module>` (`direction: up`, `dedicatedGate`);
-- `.github/workflows/nightly-mutation.yml` ma job **"Mutation score ratchet (blocking)"**, który unifikuje raporty batch i ratchetuje scalone wyniki per-module.
-
-Skutek: per-module mutation score **nie może regredować** — coverage przestał być vanity metric.
-
-### 2.3 ✅ Bramki quick-win (Phase 6A/7) dostarczone
-
-- **a11y axe-core „fake-green” naprawione:** `@axe-core/playwright` w devDeps; `a11y.spec.ts` z warunkowym skip `REQUIRE_AXE`; job w `nightly-resilience.yml`.
-- **complexity skanuje `bin/`+`electron`:** `check-complexity.mjs` obejmuje te katalogi w `ESLINT_ARGS`.
-- **tracked-artifacts w pre-commit + pre-push:** `.husky/pre-commit` + `pre-push` blokują przypadkowo śledzone artefakty.
-
----
-
-## 3. 12 kategorii — status (ukierunkowany na delty)
-
-| #   | Kategoria                        | Status 06-30                                                                              |
-| --- | -------------------------------- | ----------------------------------------------------------------------------------------- |
-| 1   | Style & formatting               | ✅ bez zmian (Prettier+ESLint lint-staged)                                                |
-| 2   | Types                            | ✅ **wzmocnione** — `typecheck:core` teraz także w bramce PR→release                      |
-| 3   | Tests (intensity)                | ✅ **wzmocnione** — mutation testing stał się ratchetem; deterministic suite w merge gate |
-| 4   | Test policy (anti-gaming)        | ✅ bez zmian (pr-test-policy/test-masking/pr-evidence)                                    |
-| 5   | Complexity & health              | ✅ **wzmocnione** — complexity skanuje bin/electron                                       |
-| 6   | Static security (SAST+secrets)   | 🟡 CodeQL default-setup (advanced = właściciel); semgrep cloud nie wersjonowany           |
-| 7   | Supply-chain (deps)              | ✅ bez zmian (osv/audit/Trivy/Dependabot + allowlist)                                     |
-| 8   | Supply-chain (build/release)     | 🟡 SLSA L2 (L3 = hermetic builder, właściciel/infra)                                      |
-| 9   | Contracts & API                  | 🟡 oasdiff/osv advisory (kandydaci na blocking-with-scope, P1)                            |
-| 10  | Docs & i18n (anti-rot)           | ✅ **wzmocnione** — `fabricated-docs --strict` blocking (exit 0 zweryfikowany)            |
-| 11  | Anti-hallucination / consistency | ✅ bez zmian (known-symbols/fetch-targets/docs-symbols/db-rules)                          |
-| 12  | Resilience & domain              | ✅ bez zmian (chaos/heap/k6/promptfoo/garak nightly)                                      |
-
----
-
-## 4. Pozostałe luki do „absolutnego maksimum”
-
-### 4.1 Mierzalne w CI / możliwe do dostarczenia kodem (backlog tego programu)
-
-- **P1 — osv/oasdiff → blocking z właściwym zakresem:** osv tylko `CRITICAL`+fixable (dwuetapowo jak Trivy); oasdiff blokuje zmiany łamiące kontrakt.
-- **P1 — `require-tighten` blocking (koniec cyklu):** blokuje zyski metryk (zapobiega poluzowaniu baseline bez zapisu).
-- **P1/P2 — przegląd ROI / gate sprawl:** konsolidacja micro-gates doc-sync; pomiar czasu per-gate w `ci-summary` (walka z zmęczeniem — zastrzeżenie SonarQube/DORA). Odroczone merge ROI (unified complexity; unified `/api` anti-hallucination) trafiają tutaj.
-- **P2 — CodeQL config w repo + semgrep wersjonowany:** więcej kontroli/reprodukowalności.
-
-### 4.2 Proces / właściciel (CI nie może ruszyć — ustawienia organizacji)
-
-- **Branch-protection na `main`** (podnosi Scorecard, zamyka lukę DSOMM). Zob. [`BRANCH_PROTECTION_MAIN.md`](./BRANCH_PROTECTION_MAIN.md).
-- **CodeQL Default → Advanced setup.**
-- **SLSA L3** — hermetic/reproducible builder (GitHub SLSA generator). Stretch (malejące zwroty).
-
-### 4.3 Wyraźnie poza zakresem
-
-- **DSOMM L5** jest w dużej mierze **na poziomie org / procesu** (nie da się zakodować w CI).
-- **SLSA L4** (reprodukowalność bit-for-bit) to zadeklarowany stretch goal.
-
----
-
-## 5. Elementy odroczone / usunięte (porządkowanie ogona)
-
-- **`semcheck.yaml` (warstwa LLM na semantic drift docs↔code) — USUNIĘTE.** Było **osierocone**
-  (żaden workflow/skrypt go nie wywoływał) i miało nieaktualne liczniki w regułach. Deterministyczne pokrycie
-  już istnieje (`check:fabricated-docs --strict` + `check:docs-counts-sync` + `check:docs-symbols`),
-  a zastrzeżenie _gate sprawl_ zniechęca do dodawania bramki LLM advisory z kosztem cyklicznym.
-  Może zostać ponownie wprowadzone w przyszłości jako opt-in nightly job, jeśli semantic drift stanie się realnym problemem.
-- **`agent-lsp` scaffold — ODROCZONE / opt-in nie włączone.** Istnieje jako wzmianka w docs
-  (`docs/architecture/QUALITY_GATES.md`, CHANGELOG), ale **bez podpięcia** i bez `.mcp.json.example`
-  w repo. Pozostaje udokumentowanym scaffoldem opt-in; nie jest aktywną bramką ani luką dojrzałości.

docs/i18n/pl/docs/proxy-port-clash-report.md

@@ -1,83 +0,0 @@
-# Analiza konfliktu portów proxy
-
-## Podsumowanie
-
-W systemie proxy auto-select / proxyFallback / proxyEgress **nie ma konfliktu portów**.
-Podsystem proxy używa **wcześniej przypisanych portów z rejestru** — nigdy nie bindowuje
-się bezpośrednio do portów TCP. Prawdziwa historia EADDRINUSE leży w warstwie
-**process supervisor**, gdzie główny port nasłuchu serwera może kolidować podczas
-restartów w pętli awarii (crash-loop).
-
----
-
-## Podsystem proxy: brak bindowania portów
-
-| Moduł                  | Co robi                                                                                               |
-| ---------------------- | ----------------------------------------------------------------------------------------------------- |
-| `proxyAutoSelector.ts` | Wybiera konfigurację proxy z DB, stosując health scores i grupy rotacji                               |
-| `proxyFallback.ts`     | Implementuje strategie retry/fallback, gdy wybrane proxy zawodzi (spróbuj innego proxy, potem direct) |
-| `proxyEgress.ts`       | Sondowanie/propagacja informacji o egress IP do logowania — używa HTTP echo, nie bindowania portów    |
-| `proxyDispatcher.ts`   | Tworzy dispatchery `undici.ProxyAgent` — to poziom HTTP (forward proxy), nie gniazda nasłuchu TCP     |
-| `proxyFetch.ts`        | Spatchowany globalny fetch, który stosuje dispatchery proxy na poziomie undici                        |
-
-Żaden z tych modułów nie wywołuje `net.createServer()`, `http.createServer()` ani `app.listen()`.
-Zarządzanie portami odbywa się wyłącznie w cyklu życia żądania — undici zarządza pulą
-połączeń TCP wewnętrznie.
-
-**Przepływ fallback** (z `proxyFetch.ts` `runWithProxyContext`):
-
-1. Spróbuj przypisanego proxy → proxy dispatcher
-2. Jeśli nieosiągalne → direct fallback (bez dispatchera)
-3. Jeśli nadal zawodzi → błąd propagowany w górę
-
-W tym przepływie nie następuje alokacja ani zwalnianie portów.
-
----
-
-## Prawdziwa przyczyna EADDRINUSE: wyścig restartu w crash-loop
-
-Rzeczywisty konflikt portów był w **process supervisor** (`bin/cli/runtime/`):
-
-| Plik                    | Rola                                                                              |
-| ----------------------- | --------------------------------------------------------------------------------- |
-| `processSupervisor.mjs` | `ServerSupervisor` — uruchamia proces potomny, monitoruje kod wyjścia, restartuje |
-| `supervisorPolicy.mjs`  | `waitUntilPortFree()`, `isPortFree()`, stałe polityki restartu                    |
-
-**Przyczyna główna:** Gdy proces potomny serwera ulegał awarii i był natychmiast restartowany,
-OS nie zdążył jeszcze zwolnić gniazda nasłuchu (TIME_WAIT / TCP lingering). Próba restartu
-bindowała ten sam port i natychmiast kończyła się `EADDRINUSE`, powodując
-kolejną awarię → kolejny restart → wyczerpany budżet restartów → gateway martwy.
-
-**Poprawka (#4425, w `supervisorPolicy.mjs`):**
-
-1. Dodano `isPortFree(port)` — próbuje `net.createServer().listen()` na docelowym
-   porcie; zwraca `false` przy EADDRINUSE.
-2. Dodano `waitUntilPortFree(port, timeoutMs=10000, intervalMs=250)` — odpytuje co 250ms
-   przez maks. 10s, aż port będzie wolny, dopiero potem pozwala na restart.
-3. Podniesiono `RESTART_RESET_MS` z 30s → 60s — okno awarii było zbyt krótkie, co powodowało
-   szybkie kaskadowe restarty w obrębie okna.
-4. Podniesiono `DEFAULT_MAX_RESTARTS` z 2 → 3 — większy zapas na przejściowe awarie.
-
-Narzędzia `writePidFile()` / `killAllSubprocesses()` / `cleanupPidFile()` w
-`bin/cli/utils/pid.mjs` zapewniają czysty cykl życia pliku PID.
-
-## Powiązane: Live-Dashboard EADDRINUSE (#6324)
-
-Równoległa poprawka (`live-ws-eaddrinuse-6324.test.ts`) gwarantuje, że `startLiveDashboardServer()`
-odrzuca z właściwym błędem `EADDRINUSE` (zamiast nieobsłużonego zdarzenia socket 'error',
-które crashowałoby proces). Serwer dashboardu używa osobnego portu względem głównego
-serwera API, więc gdy oba są skonfigurowane na ten sam port, drugie bindowanie kończy się
-niepowodzeniem w sposób kontrolowany (gracefully).
-
----
-
-## Stan obecny
-
-| Ryzyko                                       | Status                  | Pozostało |
-| -------------------------------------------- | ----------------------- | --------- |
-| Supervisor restart EADDRINUSE                | **Naprawione** (#4425)  | Brak      |
-| LiveWS port clash                            | **Naprawione** (#6324)  | Brak      |
-| Proxy selection port clash                   | **Nigdy nie dotyczyło** | Brak      |
-| Two Redis CLIENT factories bind no TCP ports | **Nigdy nie dotyczyło** | Brak      |
-
-Nie są potrzebne dalsze działania w sprawie konfliktu portów.

docs/i18n/pl/docs/proxy-subscriptions.md

@@ -1,370 +0,0 @@
-# Subskrypcje proxy operatora (styl Karing)
-
-> Notatki projektowe i implementacyjne dla operatorowego przepływu subskrypcji
-> proxy w OmniRoute. To jest cięcie v1: pojedynczy operator wkleja linki
-> subskrypcji, wybiera tryb (global lub rule), a OmniRoute wiąże wynikową pulę
-> proxy z istniejącą rezolucją scope. Multi-tenant per-API-key, zaawansowane
-> reguły ruchu, wagi per-rule sterowane latencją itd. są jawnie poza zakresem
-> i wymienione w §7.
-
----
-
-## 1. Motywacja
-
-Dziś pula proxy OmniRoute jest ręcznie kuratorowana: każdy węzeł żyje w
-`proxy_registry` z ręcznie wpisanym host/port/credentials, a każde powiązanie z
-upstreamowymi dispatcherami (account → provider → combo → global → direct) to
-ręczny wiersz `proxy_assignments`. Operatorzy, którzy już utrzymują subskrypcję
-Clash/V2Ray/sing-box (np. z usługi airport), muszą przepisywać każdy węzeł do
-OmniRoute i ponownie je wiązać przy każdej zmianie listy upstream.
-
-Celem v1 jest uczynienie OmniRoute first-class dla subskrypcji
-**dostarczanych przez operatora**, podobnie jak Karing / Clash / sing-box
-pozwalają wkleić URL `https://...` i zostawić zarządzanie cyklem życia klientowi.
-
-## 2. Historie użytkownika
-
-| #   | Jako     | Chcę                                                                  | Aby                                                                                                                            |
-| --- | -------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
-| U1  | Operator | wkleić URL subskrypcji raz                                            | nie przepisywać węzłów przy każdym odświeżeniu airport                                                                         |
-| U2  | Operator | włączać/wyłączać subskrypcję                                          | móc wrócić do direct bez usuwania URL                                                                                          |
-| U3  | Operator | wybrać tryb **global**                                                | cały ruch każdego providera wychodził przez subskrypcję                                                                        |
-| U4  | Operator | wybrać tryb **rule** i wskazać konkretnych providerów                 | tylko wybrani providerzy szli przez proxy; pozostali zostawali direct                                                          |
-| U5  | Operator | podać lokalny endpoint SOCKS5 sing-box/clash                          | węzły SS/VMess/Trojan/VLESS (których dispatcher OmniRoute nie mówi natywnie) stawały się używalne przez lokalny mostek kernela |
-| U6  | Operator | widzieć status pobrania i niedawną zredagowaną (redacted) sumę węzłów | debugować „dlaczego pusto / błąd” bez wycieku credentials                                                                      |
-
-## 3. Poza zakresem (v1)
-
-- Nadpisania subskrypcji per-API-key (multi-tenant). v1 jest wyłącznie operatorskie.
-- Reguły ruchu per-provider poza `global` / `rule-on-selected-providers`.
-- Inteligentny routing oparty o latencję między węzłami subskrypcji a innymi pulami
-  (istniejące `resolveProxyForConnectionFromRegistry` już to robi dla puli
-  globalnej; v1 tylko dokłada do niej węzły subskrypcji).
-- Auto-import URL/hasła z nagłówków lub query params.
-- Mitygacja SSRF poza endpointami local-core wyłącznie na loopback (sam URL
-  subskrypcji jest kontrolowany przez operatora, więc ufamy mu tak samo jak
-  dzisiejszym URL-om providerów upstream).
-
-## 4. Architektura
-
-```
-            ┌─────────────────────────────────────────┐
-            │  dashboard / settings / 代理 / 订阅代理   │
-            │  (client component, SubscriptionTab)    │
-            └──────────────────┬──────────────────────┘
-                               │ fetch
-                               ▼
-   ┌────────────────────────────────────────────────────────┐
-   │  /api/v1/management/proxy-subscriptions                │
-   │  ├ GET    list                                        │
-   │  ├ POST   create                                      │
-   │  ├ GET    /:id                                        │
-   │  ├ PATCH  /:id                                        │
-   │  ├ DELETE /:id                                        │
-   │  ├ POST   /:id/refresh                                │
-   │  └ GET    /:id/nodes                                  │
-   └────────────────────────┬───────────────────────────────┘
-                            │ uses
-                            ▼
-   ┌────────────────────────────────────────────────────────┐
-   │  src/lib/proxySubscription/                           │
-   │  ├ parse.ts          (Clash YAML / V2Ray JSON / URIs) │
-   │  ├ subscriptionService.ts                              │
-   │  │   CRUD, sync, apply, unapply, scheduler            │
-   │  └ index.ts          (barrel)                          │
-   └──────────┬─────────────────────────────┬───────────────┘
-              │ upsert/scope-bind            │ DB
-              ▼                              ▼
-   ┌─────────────────────────┐    ┌──────────────────────────┐
-   │  proxy_registry          │    │  proxy_subscriptions     │
-   │  (existing) +             │    │  (NEW — subscription     │
-   │  subscription_id column  │    │   metadata + scheduler   │
-   │  + status/health checks  │    │   state)                 │
-   └─────────────────────────┘    └──────────────────────────┘
-              │
-              ▼ (existing)
-   resolveProxyForConnectionFromRegistry
-   hasBlockingProxyAssignment (fail-closed)
-   proxyDispatcher (open-sse/utils/proxyDispatcher)
-```
-
-Kluczowa decyzja projektowa: **nie wymyślamy nowego scope ani pipeline’u routingu**.
-Upsertujemy węzły pochodzące z subskrypcji do `proxy_registry` z `source =
-'subscription'` + `subscription_id`, a następnie `applySubscription()` przechodzi
-istniejące API `addProxyToScopePool(scope, scopeId, proxyId)`. Dzięki temu:
-
-- Istniejąca rotacja, health checki i strażniki fail-closed działają „za darmo”.
-- Istniejące dashboardy (ProxyPoolTab, SourceToggleBar, GlobalConfigTab) działają
-  bez zmian — węzły subskrypcji po prostu pojawiają się w puli z odznaką `source`.
-- Usunięcie/wyłączenie subskrypcji czysto usuwa jej powiązania bez
-  ruszania ręcznych proxy.
-
-## 5. Model danych
-
-### 5.1 Nowa tabela `proxy_subscriptions`
-
-| Column                    | Type                             | Notes                                                                  |
-| ------------------------- | -------------------------------- | ---------------------------------------------------------------------- |
-| `id`                      | TEXT PK                          | UUID                                                                   |
-| `name`                    | TEXT NOT NULL                    | nazwa wyświetlana                                                      |
-| `url`                     | TEXT NOT NULL                    | URL subskrypcji                                                        |
-| `enabled`                 | INTEGER NOT NULL DEFAULT 0       | 1 = aktywna                                                            |
-| `mode`                    | TEXT NOT NULL DEFAULT `'global'` | `'global'` lub `'rule'`                                                |
-| `rule_providers`          | TEXT NULL                        | tablica JSON ID providerów (tylko mode='rule')                         |
-| `local_core_endpoint`     | TEXT NULL                        | loopback SOCKS5/HTTP dla SS/VMess/itd. (np. `socks5://127.0.0.1:2080`) |
-| `update_interval_minutes` | INTEGER NOT NULL DEFAULT 60      | kadencja odświeżania w tle                                             |
-| `last_fetched_at`         | TEXT NULL                        | znacznik czasu ISO ostatniego udanego pobrania                         |
-| `status`                  | TEXT NOT NULL DEFAULT `'empty'`  | `'ok'` / `'error'` / `'empty'`                                         |
-| `error`                   | TEXT NULL                        | ostatni tekst błędu / ostrzeżenia (zredagowany)                        |
-| `last_nodes`              | TEXT NULL                        | tablica JSON, zredagowane podsumowania węzłów                          |
-| `created_at`              | TEXT NOT NULL                    | ISO                                                                    |
-| `updated_at`              | TEXT NOT NULL                    | ISO                                                                    |
-
-Indeks: `idx_proxy_subscriptions_enabled (enabled)` na tick schedulera.
-
-### 5.2 Rozszerzone `proxy_registry`
-
-Dodana jedna kolumna:
-
-| Column            | Type      | Notes                                                                                |
-| ----------------- | --------- | ------------------------------------------------------------------------------------ |
-| `subscription_id` | TEXT NULL | FK z konwencji (bez wymuszanego FK; wiersz subskrypcji żyje w `proxy_subscriptions`) |
-
-Istniejące wiersze po upgrade: `subscription_id = NULL`, zachowanie bez zmian.
-Migracja: `ALTER TABLE proxy_registry ADD COLUMN subscription_id TEXT;`
-(stosowana jako `131_proxy_subscriptions.sql`, idempotentna dzięki semantyce
-`ALTER` w migration runnerze).
-
-### 5.3 Izolacja testów rozszerzonego `proxy_subscriptions`
-
-Migration runner stosuje nowe migracje automatycznie; jedyne miejsca, które
-muszą znać nową kolumnę, to `types.ts` i `mappers.ts` (po jednym dodatkowym
-polu) oraz `proxies.ts` (3 instrukcje SQL: INSERT/UPDATE/SELECT).
-
-## 6. Tryby
-
-### 6.1 Tryb global
-
-- Pula powiązana z `scope='global', scope_id=NULL`.
-- Ustawienie `proxyEnabled` wymuszane na `true`, gdy aktywna jest jakakolwiek
-  subskrypcja (lub jakiekolwiek globalne proxy spoza subskrypcji).
-- Cały ruch providerów wychodzi przez pulę subskrypcji, z rotacją/health
-  stosowanymi przez istniejące `resolveProxyForConnectionFromRegistry`.
-
-### 6.2 Tryb rule
-
-- Pula powiązana z `scope='provider', scope_id=<selected provider id>` dla każdego
-  wybranego providera.
-- Providerzy spoza listy przechodzą na direct (własne proxy na poziomie
-  providera albo brak proxy).
-- Przełączenie subskrypcji z global → rule najpierw wywołuje `unapplySubscription`,
-  by odłączyć poprzednie powiązania globalne, a potem ponownie synchronizuje.
-
-## 7. Wsparcie protokołów
-
-Istniejący `proxyDispatcher` mówi tylko **http / https / socks5 / vercel /
-deno / cloudflare**. v1 idzie za tym:
-
-| Parser-detected type              | Goes into pool directly? | Needs `localCoreEndpoint`?             |
-| --------------------------------- | ------------------------ | -------------------------------------- |
-| `http` / `https`                  | yes                      | no                                     |
-| `socks5`                          | yes                      | no                                     |
-| `ss` / `ssr`                      | no                       | yes (sing-box/clash → loopback SOCKS5) |
-| `vmess` / `vless`                 | no                       | yes                                    |
-| `trojan`                          | no                       | yes                                    |
-| `hysteria` / `tuic` / `wireguard` | no                       | yes                                    |
-| `relay` (vercel/deno/cloudflare)  | yes                      | no                                     |
-
-Bez `localCoreEndpoint` węzły klasy SS pojawiają się w statusie jako
-ostrzeżenie, ale **nie są routowane**. To odpowiada polityce „fail-closed, ale
-nie kłam o możliwościach”: nigdy cicho nie gubimy ruchu; raportujemy
-nieroutowalne węzły i zostawiamy decyzję operatorowi.
-
-## 8. Parser (`src/lib/proxySubscription/parse.ts`)
-
-Ręcznie napisany, bez zewnętrznej zależności. Akceptowane wejścia:
-
-1. **Clash / Clash.Meta YAML** — tablica `proxies:`, z dispatch po `type`.
-2. **Lista URI owinięta Base64** — `parseSubscription` wykrywa base64 po długości
-   i zestawie znaków, dekoduje, potem parsuje URI.
-3. **JSON-array-of-URI w stylu V2RayN** — używa URI `vmess://` / `vless://`.
-4. **Zwykła lista URI** — `ss://`, `vmess://`, `vless://`, `trojan://`,
-   `hysteria://`, `tuic://`, `wireguard://`, `socks5://`, `http(s)://`.
-
-Wyjście:
-
-```ts
-type ParsedSubscription = {
-  nodes: DirectlyUsableNode[]; // http/https/socks5/relay
-  needsCore: NeedsCoreNode[]; // ss/vmess/... — redacted summary
-  rawProtocols: string[]; // for diagnostics
-  parserWarnings: string[]; // per-line parse errors, redacted
-};
-
-type DirectlyUsableNode = {
-  name: string;
-  type: "http" | "https" | "socks5" | "vercel" | "deno" | "cloudflare";
-  host: string;
-  port: number;
-  username?: string;
-  password?: string;
-};
-```
-
-`redactedNodeSummary` zwraca serializowalną do JSON tablicę `{name, type,
-host, port, hasCredentials}` z pominiętymi credentials. To trafia do
-`last_nodes` na potrzeby UI operatora.
-
-## 9. Bezpieczeństwo
-
-- **SSRF na `localCoreEndpoint`**: jedyna powierzchnia SSRF to lokalny
-  endpoint core (sam URL subskrypcji dostarcza operator). Dozwolone
-  hosty: `127.0.0.1`, `::1`, `localhost`. Każdy inny host jest odrzucany przy
-  parsowaniu ze statusem `subscription_needs_core_endpoint_invalid`.
-- **Brak outboundu do hostów wewnętrznych operatora** z URL subskrypcji. Pobranie
-  URL idzie przez `fetch` Node (ten sam model zaufania co istniejące
-  health checki `proxyLatency` i taski ping providerów). Operator
-  już ufa URL, bo go wkleił.
-- **Fail-closed**: jeśli proxy subskrypcji jest martwe, ale nadal powiązane ze
-  scope, `hasBlockingProxyAssignment` zwraca true i ruch kończy się fail-closed —
-  zgodnie z istniejącą polityką dla dowolnego proxy z puli. Operator zawsze może
-  wyłączyć subskrypcję lub usunąć powiązanie.
-- **Brak echa sekretów**: `last_nodes` jest zredagowane; UI nigdy nie odsyła
-  sekretów. `password` / `username` są przechowywane zaszyfrowane at rest przez
-  istniejący tor szyfrowania `proxy_registry`.
-- **Brak zapisu cross-tenant**: trasy API są strzeżone przez `requireManagementAuth`
-  (sesja dashboardu LUB klucz API ze scope manage). Nadpisania per-API-key są
-  jawnie poza zakresem.
-
-## 10. UI
-
-Nowa podzakładka **"订阅代理"** w `dashboard / settings / 代理`, umieszczona po
-„documentation”. Widok listy pokazuje:
-
-- Name + URL (obcięty, pełny URL w atrybucie `title`)
-- Odznaka statusu: `ok` / `error` / `empty`
-- Przełącznik Enabled (optimistic toggle)
-- Przyciski akcji: edit / refresh / delete
-
-Formularz edycji ma:
-
-- Name (tekst, wymagane)
-- URL (tekst, wymagane, walidowane jako URL)
-- Przełącznik Mode (global / rule)
-- Multi-select providerów (widoczny tylko w trybie rule; zasilany z
-  `/api/providers`)
-- Local core endpoint (tekst, opcjonalny; placeholder `socks5://127.0.0.1:2080`)
-- Update interval (liczba, domyślnie 60 minut)
-- Przełącznik Enabled
-
-Gdy `status === 'error'`, baner ostrzeżenia inline pokazuje `subscription.error`.
-Gdy `status === 'ok'` i są węzły wymagające local core, miękki
-baner ostrzeżenia pokazuje, które protokoły pominięto.
-
-## 11. Migracja i rollout
-
-1. Nowa migracja `131_proxy_subscriptions.sql` uruchamia się przy pierwszym otwarciu DB po
-   upgrade (auto-wykrywana przez istniejący migration runner).
-2. Migracja jest **idempotentna**: `ALTER TABLE … ADD COLUMN …` na już
-   zmigrowanej DB to no-op w SQLite, gdy owinięte w ścieżkę runnera
-   „ignore duplicate column”. Zob. istniejące precedensy
-   `040_oneproxy_proxy_fields.sql` i `093_proxy_enable_toggles.sql`.
-3. Bez backfill: istniejące wiersze dostają `subscription_id = NULL`, co serwis
-   traktuje jako „manual, not subscription-managed”.
-4. UI ukrywa zakładkę przy zerze subskrypcji, ale API jest zawsze
-   dostępne — to celowe, by operatorzy headless mogli zarządzać
-   subskrypcjami wyłącznie przez API.
-
-## 12. Auto-odświeżanie
-
-`startSubscriptionScheduler()` jest idempotentny i:
-
-- Pomija przeglądarkę (`typeof window !== "undefined"`).
-- Pomija przy `NODE_ENV=test`.
-- W przeciwnym razie startuje 60s `setInterval`, który:
-  - Listuje włączone subskrypcje.
-  - Dla każdej liczy `due = now - lastFetchedAt >= updateIntervalMinutes * 60_000`.
-  - Wywołuje `syncSubscription` dla zaległych, połykając błędy (logowane).
-- Timer interwału ma `.unref()`, więc nigdy nie blokuje wyjścia procesu.
-
-Scheduler startuje przy:
-
-- Pierwszym `GET /api/v1/management/proxy-subscriptions` (otwarcie dashboardu).
-- Dowolnym wywołaniu `syncSubscription` (defensywnie — dla ścieżek CLI / automacji,
-  które omijają GET).
-
-## 13. Strategia testów
-
-`tests/unit/proxySubscription.parse.test.ts` — 7 czystych przypadków parsera, bez DB,
-uruchamialne w <1s:
-
-1. Clash YAML z węzłami `direct` (http) i `needsCore` (ss).
-2. Lista URI owinięta Base64 (poprawnie zdekodowana).
-3. V2Ray JSON-array-of-URI (vmess / vless).
-4. Zwykła lista URI (mieszane protokoły).
-5. Outboundy Clash.Meta (socks5).
-6. Puste / nieznane wejście → `nodes=[]`, `needsCore=[]`, parserWarnings wypełnione.
-7. `redactedNodeSummary` usuwa credentials.
-
-`tests/unit/proxySubscription.service.test.ts` — 4 testy integracyjne używające
-`process.env.DATA_DIR` + `core.resetDbInstance()`:
-
-1. **Global**: utwórz włączoną subskrypcję global → `syncSubscription` →
-   zweryfikuj wiersze puli w `proxy_registry` z ustawionym `subscription_id` →
-   `resolveProxyForConnectionFromRegistry` zwraca jeden z tych wierszy →
-   `proxyEnabled` jest true.
-2. **Rule**: utwórz włączoną subskrypcję rule na providerze P1 → zweryfikuj, że tylko
-   scope P1 jest powiązany, scope P2 nietknięty.
-3. **Fail-closed**: URL pobrania subskrypcji jest nieosiągalny → `status='error'`,
-   pula pusta, a jeśli kiedykolwiek miała wiersze, są wyczyszczone;
-   `hasBlockingProxyAssignment` zwraca false (brak martwych proxy w żadnym scope).
-4. **Delete**: usuń subskrypcję → wiersze rejestru dla tej subskrypcji są
-   usuwane z `force: true` (ręczne usunięcia nie mogą zablokować kaskady) →
-   `proxyEnabled` przeliczone.
-
-Komenda uruchomienia testów:
-
-```bash
-node --import tsx/esm \
-     --import ./open-sse/utils/setupPolyfill.ts \
-     --import ./tests/_setup/isolateDataDir.ts \
-     --test \
-     tests/unit/proxySubscription.parse.test.ts \
-     tests/unit/proxySubscription.service.test.ts
-```
-
-## 14. Prace przyszłe (NIE w v1)
-
-- Nadpisania subskrypcji per-API-key (multi-tenant; wymaga tabeli `key_subscription_overrides`).
-- Reguły ruchu per-provider z matcherami domen (weszłyby w istniejącą tabelę `interceptionRules`).
-- Rotacja ważona latencją między pulami subskrypcji (mamy już `ProxyRotationStrategy = "latency"`; wystarczy wystawić w UI).
-- Proxyowanie samego pobrania subskrypcji przez osobny egress (by operatorzy mogli pobierać zza firmowego firewalla).
-- Podgląd sparsowanej subskrypcji po stronie przeglądarki przed zapisem (dziś trzeba save → wait → see nodes).
-
-## 15. Pliki dodane / zmienione
-
-**Dodane (nowe):**
-
-- `src/lib/proxySubscription/parse.ts`
-- `src/lib/proxySubscription/subscriptionService.ts`
-- `src/lib/proxySubscription/index.ts`
-- `src/lib/db/migrations/131_proxy_subscriptions.sql`
-- `src/app/api/v1/management/proxy-subscriptions/route.ts`
-- `src/app/api/v1/management/proxy-subscriptions/[id]/route.ts`
-- `src/app/api/v1/management/proxy-subscriptions/[id]/refresh/route.ts`
-- `src/app/api/v1/management/proxy-subscriptions/[id]/nodes/route.ts`
-- `src/app/(dashboard)/dashboard/settings/components/proxy/SubscriptionTab.tsx`
-- `tests/unit/proxySubscription.parse.test.ts`
-- `tests/unit/proxySubscription.service.test.ts`
-- `docs/proxy-subscriptions.md` (ten plik)
-
-**Zmodyfikowane (minimalnie):**
-
-- `src/lib/db/proxies/types.ts` — `+ subscriptionId: string | null` na
-  `ProxyRegistryRecord`; `+ subscriptionId?: string | null` na `ProxyPayload`.
-- `src/lib/db/proxies/mappers.ts` — `mapProxyRow` czyta
-  `subscription_id` z wiersza.
-- `src/lib/db/proxies.ts` — INSERT / UPDATE / SELECT dodają `subscription_id`.
-- `src/app/(dashboard)/dashboard/settings/components/ProxyTab.tsx` — dodaje
-  jedną nową podzakładkę ("订阅代理") + fallback `literal` dla etykiet, których
-  jeszcze nie ma w katalogu i18n.

docs/i18n/pl/docs/redis-production-config.md

@@ -1,178 +0,0 @@
-# Przewodnik konfiguracji Redis w produkcji
-
-## Przegląd
-
-Redis to **opcjonalna, miękka zależność** w OmniRoute — aplikacja degraduje się łagodnie (fallbacki
-w pamięci), gdy Redis jest niedostępny. W produkcji strojenie Redis zmniejsza opóźnienia dla trzech
-odrębnych obciążeń:
-
-| Obciążenie    | Sterownik            | Fabryka klienta                                 | Wzorzec kluczy                    |
-| ------------- | -------------------- | ----------------------------------------------- | --------------------------------- |
-| Rate limiting | `rateLimiter.ts`     | `getRedisClient()` — leniwy singleton `ioredis` | Okna rate limit z atomowością Lua |
-| Cache auth    | `apiKeys.ts`         | Ponownie używa klienta `rateLimiter`            | `auth:api_key:<sha256>` z TTL     |
-| Magazyn quota | `redisQuotaStore.ts` | Osobny singleton `getRedisClient(url)`          | Konfigurowalny per instancja      |
-
----
-
-## Bieżąca konfiguracja (domyślne wartości w kodzie)
-
-| Ustawienie                                   | Wartość                                                    | Gdzie                                |
-| -------------------------------------------- | ---------------------------------------------------------- | ------------------------------------ |
-| Zmienna środowiskowa `REDIS_URL`             | `redis://redis:6379` (compose), opcjonalna                 | `rateLimiter.ts:5`, `.env.example`   |
-| Zmienna środowiskowa `QUOTA_STORE_REDIS_URL` | osobna, może różnić się od `REDIS_URL`                     | `quota/storeFactory.ts`              |
-| `QUOTA_STORE_DRIVER`                         | `"sqlite"` (domyślnie), `"redis"` opcjonalnie              | `quota/storeFactory.ts`              |
-| ioredis `maxRetriesPerRequest`               | `3`                                                        | tworzenie klienta w `rateLimiter.ts` |
-| `enableReadyCheck`                           | nieustawione (domyślnie ioredis: `true`)                   | —                                    |
-| `lazyConnect`                                | nieustawione (domyślnie ioredis: `false`)                  | —                                    |
-| `retryStrategy`                              | nieustawione (domyślnie ioredis: baza 200 ms, wykładniczo) | —                                    |
-| TLS / hasło / indeks DB                      | **nieskonfigurowane**                                      | —                                    |
-| Sentinel / Cluster                           | **nieskonfigurowane** — tylko samodzielny pojedynczy węzeł | —                                    |
-
----
-
-## Zalecane strojenie produkcyjne
-
-### 1. Pula połączeń / opcje klienta (konstruktor ioredis `Redis`)
-
-Obecny kod tworzy pojedyncze `new Redis(url)` bez własnych opcji. W produkcyjnych
-wdrożeniach multi‑replica przekaż fabrykę klienta w kodzie albo owiń `getRedisClient()`:
-
-```typescript
-const redis = new Redis(REDIS_URL, {
-  maxRetriesPerRequest: null, // no retry limit; let retryStrategy decide
-  enableReadyCheck: true, // verify server is ready before accepting calls
-  lazyConnect: true, // don't connect on construction; wait for first call
-  retryStrategy: (times) => {
-    if (times > 10) return null; // give up after 10 retries → reconnect later
-    return Math.min(times * 200, 5000); // 200ms, 400ms, …, 5s cap
-  },
-  enableAutoPipelining: true, // coalesce concurrent commands into one TCP write
-  keepAlive: 10000, // TCP keep‑alive every 10s
-});
-```
-
-**Kluczowe kompromisy:**
-
-- `maxRetriesPerRequest: null` + `retryStrategy` — preferowane w produkcji, aby chwilowe
-  restarty Redis nie powodowały natychmiastowej awarii każdego żądania. Fallback w pamięci w
-  `checkRateLimit()` obsługuje ścieżkę błędu.
-- `lazyConnect: true` — unika zależności startowej od dostępności Redis, zanim serwer
-  zacznie przyjmować połączenia.
-- `enableAutoPipelining: true` — zmniejsza liczbę round-tripów przy współbieżnych sprawdzeniach rate-limit;
-  korzystne przy >50 RPS na jednym połączeniu.
-
-### 2. Konfiguracja serwera Redis (`redis.conf`)
-
-```
-# Memory
-maxmemory 80%                        # leave room for OS page cache
-maxmemory-policy allkeys-lru         # evict stale auth cache entries under pressure
-
-# Persistence (optional — OmniRoute is crash‑safe without it)
-save 300 1                           # snapshot at least every 5 min if ≥1 key changed
-appendonly no                        # AOF not needed; data is regeneratable
-appendfsync no                       # no fsync overhead (RDB is sufficient)
-
-# Networking
-timeout 0                            # no idle disconnect
-tcp-keepalive 300                    # 5 min keep‑alive
-tcp-backlog 511                      # connection backlog for bursty load
-
-# Performance
-hz 10                                # default; 100 for latency‑sensitive
-activedefrag yes                     # auto‑defragment when fragmentation >10%
-```
-
-**Kompromis dla `maxmemory-policy allkeys-lru`:** Wpisy cache auth mogą zostać usunięte przy
-presji pamięci. To bezpieczne — `setCachedApiKey` zawsze uzupełnia cache przy miss, a
-fallback SQLite jest autorytatywny. Skrypt Lua rate-limitera tworzy małe klucze, które z
-założenia są krótkotrwałe.
-
-### 3. Ustawienia Docker Compose
-
-Produkcyjny compose (`docker-compose.prod.yml`) używa `redis:8.6.2-alpine`. Dodaj:
-
-```yaml
-redis:
-  image: redis:8.6.2-alpine
-  command:
-    [
-      "redis-server",
-      "--maxmemory",
-      "512mb",
-      "--maxmemory-policy",
-      "allkeys-lru",
-      "--activedefrag",
-      "yes",
-      "--save",
-      "300 1",
-    ]
-  healthcheck:
-    test: ["CMD", "redis-cli", "ping"]
-    interval: 10s
-    timeout: 3s
-    retries: 3
-    start_period: 5s
-```
-
-### 4. Uwagi dotyczące wielu instancji / skalowania
-
-**Jeden Redis dla wszystkich replik** — skrypt Lua rate-limitera zależy od jednej
-autorytatywnej przestrzeni kluczy. Wiele instancji Redis za replikami straciłoby atomowość
-i podwoiłoby budżet. Używaj jednego Redis (lub klastra Redis Sentinel z failover) dla
-wszystkich replik aplikacji.
-
-**Liczba połączeń:** Każda replika aplikacji otwiera **2 połączenia TCP** do Redis
-(klient rate limitera + klient magazynu quota). Przy 10 replikach → 20 połączeń, znacznie
-poniżej domyślnego limitu 10k połączeń instancji Redis.
-
-### 5. Monitoring
-
-Udostępnij przez endpoint health-check:
-
-```typescript
-// src/app/api/monitoring/health/route.ts already calls rateLimiter functions
-// Add Redis-specific checks:
-//   1. PING latency via ioredis .ping()
-//   2. Memory usage via INFO memory
-//   3. Connection count via INFO clients
-//   4. Hit rate for maxmemory-policy (evicted_keys / keyspace_hits)
-```
-
-Kluczowe metryki do obserwacji:
-
-- **Evicted keys / sec** — jeśli trwale niezerowe, zwiększ `maxmemory`
-- **Blocked clients** — wartość niezerowa sugeruje wolne skrypty Lua lub wysoką kontencję
-- **Rejected connections** — osiągnięty limit połączeń; rzadkie przy 20 połączeniach
-
----
-
-## Diagram architektury
-
-```mermaid
-flowchart LR
-    subgraph App["App Replica"]
-        RL[rateLimiter.ts]
-        AK[apiKeys.ts]
-        QS[redisQuotaStore.ts]
-    end
-    RL -- "REDIS_URL" --> R1[(Redis\nshared)]
-    AK -- "reuses RL's client" --> R1
-    QS -- "QUOTA_STORE_REDIS_URL" --> R2[(Redis\nquota store)]
-    R1 --> R2 -- "can be same instance" --> R1
-```
-
----
-
-## Odnośniki
-
-| Plik                               | Przeznaczenie                                                  |
-| ---------------------------------- | -------------------------------------------------------------- |
-| `src/shared/utils/rateLimiter.ts`  | Główny klient Redis, skrypt Lua rate-limit, fallback w pamięci |
-| `src/lib/db/apiKeys.ts`            | Cache auth — fallback Redis→SQLite                             |
-| `src/lib/quota/redisQuotaStore.ts` | Osobny klient Redis dla opcjonalnego magazynu quota            |
-| `src/lib/quota/storeFactory.ts`    | Przełącza sterowniki quota między `sqlite` a `redis`           |
-| `docker-compose.prod.yml`          | Kontener Redis w prod (obraz `redis:8.6.2-alpine`)             |
-| `.env.example`                     | Dokumentacja zmiennych środowiskowych Redis                    |
-| `src/app/api/local/redis/`         | Trasy API do orkiestracji kontenera dev                        |
-| `bin/cli/commands/redis.mjs`       | Komendy CLI do orkiestracji kontenera dev                      |

docs/i18n/pl/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/pt-BR/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/pt/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ro/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ru/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/sk/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/sv/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/sw/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/ta/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/te/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic

docs/i18n/th/llm.txt

@@ -4,7 +4,8 @@
 
 ---
 
-> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 248 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (99 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex-cloud, devin, jules), Guardrails framework, and an Electron desktop app.
+
+> OmniRoute is a free, open-source AI Gateway that acts as a universal API proxy for multi-provider LLMs. It provides smart routing, automatic fallback, load balancing, and format translation across 338 AI providers — all through a single OpenAI-compatible endpoint. Includes a built-in MCP Server (105 tools), A2A v0.3 protocol, Memory/Skills systems, Cloud Agents (codex, cursor, devin, jules), Guardrails framework, and an Electron desktop app.
 
 ## Overview
 
@@ -12,13 +13,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 **Key value:** One endpoint (`http://localhost:20128/v1`), unlimited models, zero downtime, minimal cost.
 
-**Current version:** 3.8.47
+**Current version:** 3.8.50
 
 ## Tech Stack
 
 - **Runtime:** Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
 - **Framework:** Next.js 16 (App Router) with TypeScript 6
-- **Database:** SQLite via better-sqlite3 (local, zero-config, 110+ migrations)
+- **Database:** SQLite via better-sqlite3 (local, zero-config, 144 migrations)
 - **State management:** Zustand (client), SQLite (server persistence)
 - **UI:** React 19, Tailwind CSS 4, Recharts for analytics, @lobehub/icons for 130+ provider SVG icons
 - **Auth:** OAuth 2.0 (PKCE) for providers, bcrypt for local user auth
@@ -26,7 +27,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Background jobs:** Custom token health check scheduler, 24h model auto-sync
 - **Streaming:** Server-Sent Events (SSE) for real-time proxy responses
 - **Proxy engine:** Custom pipeline with format translation, circuit breaker, rate limiting, auto-combo engine
-- **i18n:** next-intl with 40+ languages
+- **i18n:** next-intl with 43 languages
 - **Desktop:** Electron (cross-platform: Windows, macOS, Linux)
 - **Package:** Published on npm (`omniroute`) and Docker Hub (`diegosouzapw/omniroute`)
 
@@ -45,7 +46,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   │       ├── auto-combo/   # Auto-combo engine dashboard
 │   │   │       ├── cache/        # Cache dashboard (semantic cache stats)
 │   │   │       ├── cli-tools/    # CLI tool configuration (Claude Code, Codex, etc.)
-│   │   │       ├── combos/       # Model combo management (18 strategies + 4 templates)
+│   │   │       ├── combos/       # Model combo management (19 strategies + 4 templates)
 │   │   │       ├── costs/        # Cost tracking per provider/model
 │   │   │       ├── endpoint/     # Unified: Endpoint Proxy, MCP, A2A, API Endpoints tabs
 │   │   │       ├── health/       # System health (uptime, circuit breakers, latency)
@@ -98,7 +99,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── configAudit.ts        # Configuration auditing
 │   │   └── responses.ts          # Domain response types
 │   ├── i18n/                     # Internationalization
-│   │   └── messages/             # 40+ language JSON files
+│   │   └── messages/             # 43 language JSON files
 │   ├── lib/                      # Core libraries
 │   │   ├── a2a/                  # Agent-to-Agent v0.3 protocol server
 │   │   │   ├── skills/           # A2A skills (quotaManagement, smartRouting)
@@ -169,7 +170,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   └── manager.ts            # MITM proxy manager
 │   ├── shared/                   # Shared utilities, components, and constants
 │   │   ├── components/           # Reusable UI components (Card, Badge, Button, Modal, Sidebar, ProviderIcon, etc.)
-│   │   ├── constants/            # Provider definitions (248), model lists, pricing, routing strategies, MCP scopes
+│   │   ├── constants/            # Provider definitions (338), model lists, pricing, routing strategies, MCP scopes
 │   │   ├── contracts/            # Shared API contracts
 │   │   ├── hooks/                # React hooks
 │   │   ├── middleware/           # Shared middleware utilities
@@ -186,7 +187,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 ├── open-sse/                     # Standalone SSE server (npm workspace)
 │   ├── config/                   # Model registries (providerRegistry, embedding, image, audio, video,
 │   │                             #   music, rerank, moderation, search, CLI fingerprints, Ollama models)
-│   ├── executors/                # Provider-specific request executors (78 executor modules)
+│   ├── executors/                # Provider-specific request executors (101 executor modules)
 │   │   ├── base.ts               # Base executor with shared logic
 │   │   ├── default.ts            # Default OpenAI-compatible executor
 │   │   ├── cursor.ts             # Cursor IDE (protobuf + checksum)
@@ -212,11 +213,11 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── moderations.ts        # Content moderation
 │   │   ├── rerank.ts             # Reranking API
 │   │   └── search.ts             # Web search API
-│   ├── mcp-server/               # Built-in MCP server (99 tools, 3 transports: stdio/SSE/streamable-HTTP)
+│   ├── mcp-server/               # Built-in MCP server (105 tools, 3 transports: stdio/SSE/streamable-HTTP)
 │   │   ├── server.ts             # MCP server core (tool registration, scope enforcement)
 │   │   ├── tools/                # Tool implementations (advancedTools, memoryTools, skillTools)
 │   │   ├── schemas/              # Zod input schemas (tools, audit, a2a)
-│   │   ├── scopeEnforcement.ts   # Scope-based access control (32 scopes)
+│   │   ├── scopeEnforcement.ts   # Scope-based access control (31 scopes)
 │   │   ├── audit.ts              # Tool call audit logging
 │   │   ├── runtimeHeartbeat.ts   # MCP runtime heartbeat
 │   │   └── httpTransport.ts      # HTTP transport handler
@@ -228,7 +229,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   │   ├── accountFallback.ts    # Multi-account fallback
 │   │   ├── sessionManager.ts     # Session management
 │   │   ├── wildcardRouter.ts     # Wildcard model routing
-│   │   ├── autoCombo/            # Auto-combo engine (12-factor scoring, bandit exploration)
+│   │   ├── autoCombo/            # Auto-combo engine (14-factor scoring, bandit exploration)
 │   │   ├── intentClassifier.ts   # Request intent classification
 │   │   ├── taskAwareRouter.ts    # Task-aware routing
 │   │   ├── thinkingBudget.ts     # Thinking budget management
@@ -267,8 +268,8 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 │   ├── i18n/                     # 43-language translated docs
 │   ├── architecture/             # ARCHITECTURE.md, CODEBASE_DOCUMENTATION.md, REPOSITORY_MAP.md, AUTHZ_GUIDE.md, RESILIENCE_GUIDE.md, QUALITY_GATES.md
 │   ├── reference/                # API_REFERENCE.md, PROVIDER_REFERENCE.md, CLI-TOOLS.md
-│   ├── frameworks/               # MCP-SERVER.md (99 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
-│   ├── routing/                  # AUTO-COMBO.md (12-factor scoring), REASONING_REPLAY.md
+│   ├── frameworks/               # MCP-SERVER.md (105 tools), A2A-SERVER.md, SKILLS.md, MEMORY.md, CLOUD_AGENT.md, EVALS.md, WEBHOOKS.md
+│   ├── routing/                  # AUTO-COMBO.md (14-factor scoring), REASONING_REPLAY.md
 │   ├── security/                 # GUARDRAILS.md, COMPLIANCE.md, STEALTH_GUIDE.md, PUBLIC_CREDS.md, ERROR_SANITIZATION.md
 │   ├── guides/                   # USER_GUIDE.md, TROUBLESHOOTING.md, ELECTRON_GUIDE.md, I18N.md
 │   ├── ops/                      # RELEASE_CHECKLIST.md, TUNNELS_GUIDE.md, VM deployment
@@ -279,15 +280,15 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 └── .env.example                  # Environment variable template
 ```
 
-## Key Features (v3.8.47)
+## Key Features (v3.8.50)
 
 ### Core Proxy
-- **248 AI providers** with automatic format translation
+- **338 AI providers** with automatic format translation
 - **Provider categories**: Free (90+ free tiers), OAuth, API Key, Self-Hosted, Custom (OpenAI/Anthropic-compatible)
 - **18 routing strategies**: priority, weighted, round-robin, fill-first, p2c, random, least-used, cost-optimized, reset-aware, reset-window, headroom, strict-random, auto, lkgp, context-optimized, context-relay, fusion, pipeline
 - **4-tier fallback**: Subscription → API Key → Cheap → Free
 - **Context Relay strategy**: Session handoff summaries on account rotation for continuity
-- **Auto-combo engine**: Self-healing routing optimization with **12-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
+- **Auto-combo engine**: Self-healing routing optimization with **14-factor scoring** (see `docs/routing/AUTO-COMBO.md`), bandit exploration, progressive cooldown
 - **Semantic caching** with cache hit/miss headers
 - **Idempotency** with configurable dedup window
 - **3-layer resilience**: Provider Circuit Breaker / Connection Cooldown / Model Lockout
@@ -316,7 +317,7 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 
 ### Dashboard Pages (23 sections)
 - **Providers** — OAuth, API key, and free provider management with ProviderIcon SVG icons
-- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 18 strategies
+- **Combos** — Multi-model combo builder with 4 templates (Free Stack, High Availability, Cost Saver, Balanced) + 19 strategies
 - **Auto-Combo** — Auto-combo engine dashboard with scoring metrics
 - **Analytics** — Token consumption, cost, heatmaps, distributions
 - **Health** — Uptime, memory, latency percentiles, circuit breakers
@@ -346,13 +347,13 @@ OmniRoute solves the problem of managing multiple AI provider subscriptions, quo
 - **Gemini** — `/v1beta/models`, `/v1beta/models/{...path}`
 - **Ollama** — `/v1/api/chat`, `/api/tags`
 - **Search** — `/v1/search` (Perplexity, Serper, Brave, Exa, Tavily)
-- **MCP** — 99-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
-- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 5 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report)
+- **MCP** — 105-tool MCP server with scope-based auth (3 transports: stdio, SSE, streamable HTTP)
+- **A2A** — Agent-to-Agent v0.3 protocol (JSON-RPC 2.0, 6 skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities)
 - **ACP** — Agent Communication Protocol registry and manager
 
-### MCP Server (99 Tools)
+### MCP Server (105 Tools)
 
-99 tools across modules: **36 base** (health, combos, quotas, routing, cost, models, cache,
+105 tools across modules: **43 base** (health, combos, quotas, routing, cost, models, cache,
 diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool**, **notion**,
 **obsidian**, **localCorpus**, **gamification**, and **plugin** modules. Full per-tool inventory:
 `docs/frameworks/MCP-SERVER.md`.
@@ -373,7 +374,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 **Custom Providers:** OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) with custom base URLs
 
 ### Internationalization
-- 40+ languages for UI (all dashboard pages)
+- 43 languages for UI (all dashboard pages)
 - 40 translated documentation sets in docs/i18n/
 - Language switcher in documentation
 
@@ -385,7 +386,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 3. **Connection-based provider model:** Providers are stored as "connections" in SQLite. Each connection has an `id`, `provider`, `authType` (oauth/apikey/free), `isActive` flag, and credentials. Multiple connections per provider for multi-account rotation.
 
-4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 18 strategies including auto-combo with self-healing and context-relay for session continuity.
+4. **Combo system for fallback:** Users create "combos" — ordered lists of `provider/model` pairs. The proxy tries each in order until one succeeds. Supports 19 strategies including auto-combo with self-healing and context-relay for session continuity.
 
 5. **SSE proxy pipeline:** The proxy pipeline is middleware-based: request → auth resolution → rate limiting → circuit breaker → format translation → upstream call → response translation → SSE streaming back to client.
 
@@ -439,7 +440,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 4. **Environment variables:** All configuration is in `.env` (from `.env.example`). Key vars: `PORT`, `NEXT_PUBLIC_BASE_URL`, `API_KEY`, `ADMIN_PASSWORD`.
 
-5. **Database layer:** Operations go through `src/lib/db/` modules (99 domain-specific files, 117 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
+5. **Database layer:** Operations go through `src/lib/db/` modules (117 domain-specific files, 144 migrations). `localDb.ts` is re-exports only — add new functions to the proper `db/*.ts` module.
 
 6. **Tests** use Node.js built-in test runner + Vitest. Run `npm test`. Vitest for MCP/autoCombo (`npm run test:vitest`). Playwright for E2E (`npm run test:e2e`). Coverage gate: ratchet vs `quality-baseline.json`, absolute floor 60% statements/lines/functions/branches.
 
@@ -447,7 +448,7 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 8. **ACP agents** are in `src/lib/acp/registry.ts` with detection cache. Custom agents stored via settings DB.
 
-9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **12-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
+9. **Auto-combo engine** in `open-sse/services/autoCombo/` — **14-factor scoring** (weights and factors in `docs/routing/AUTO-COMBO.md`), 4 mode packs, bandit exploration, progressive cooldown.
 
 10. **Docker:** Dockerfile has two targets: `runner-base` and `runner-cli`. `docker-compose.yml` for dev (3 profiles), `docker-compose.prod.yml` for production (port 20130).
 
@@ -480,10 +481,10 @@ diagnostics) plus **memory**, **skill**, **agentSkill**, **githubSkill**, **pool
 
 ## v3.8.x Highlights
 
-- **248-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
-- **18 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
-- **12-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
-- **MCP server expanded to 99 tools / 32 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
+- **338-provider catalog** with 90+ free tiers, one-click account imports, and bulk key add
+- **19 routing strategies** — including `fusion` (parallel panel + judge synthesis), `pipeline`, `reset-aware`, `reset-window`, `headroom`, and `context-relay`
+- **14-factor Auto-Combo scoring** with bandit exploration and progressive cooldown
+- **MCP server expanded to 105 tools / 31 scopes** (base + memory/skill/agentSkill/githubSkill/pool/notion/obsidian/localCorpus/gamification/plugin modules)
 - **Cloud Agents** (Codex Cloud, Devin, Jules), **Guardrails**, **Evals**, **Webhooks**, **Compliance** frameworks
 - **Embedded services** manager (install/start/stop bundled services from the dashboard)
 - **Prompt compression** (RTK + Caveman codecs) saving up to ~95% tokens on eligible traffic