refactor(dashboard): shrink HomePageClient back under the size gate

The prefetch fix in the parent commit tripped check:file-size — the frozen
budget for this file is 1377 lines and a naive fix measured 1391, because
`href` + `prefetch={false}` + `className` no longer fits Prettier's 100-column
budget, so three one-line <Link> elements each expanded to five.

Followed the gate's own first suggestion (extract/DRY) before touching the
baseline: the quick-start links repeated the same className literal four
times, and the docs link carried a 180-char one inline. Hoisting both into
INLINE_LINK / DOCS_LINK collapses five wrapped <Link> blocks back to a single
line each and removes the duplication — 1391 -> 1381.

The remaining +4 over the frozen budget is the five prefetch attributes
themselves, which cannot be expressed in fewer lines. Rebaselined to 1381
with the rationale recorded in file-size-baseline.json under
_rebaseline_2026_07_29_8281_home_quickstart_prefetch.

tests/unit/sidebar-prefetch-policy-8281.test.ts still passes (2/2): it matches
whole <Link ...> blocks, so it is indifferent to the wrapping and only checks
that every internal link opts out of prefetch.

.cbmignore

@@ -1,197 +0,0 @@
-# codebase-memory-mcp ignore list
-#
-# Padrão gitignore-style. Linhas começando com `#` são comentários.
-# Barra final (`/`) = só diretório. Sem barra = casa arquivo OU diretório.
-#
-# O CBM também lê `.gitignore` automaticamente — esta lista deixa explícito o que
-# os hooks do CBM vão pular. Se uma regra entrar em conflito entre os dois arquivos,
-# vale a união. Editar este arquivo é mais barato do que confiar na herança implícita.
-#
-# Última reconciliação: 2026-07-31, status `ready` (513k nodes / 689k edges),
-# `auto_index_limit=50000`, total indexável medido ≈11.546 arquivos (folga 4,3×).
-#
-# Fontes cruzadas:
-#   - `codebase-memory-mcp cli index_status --project home-diegosouzapw-dev-proxys-OmniRoute`
-#     → `not_indexed.dirs` (27) + `not_indexed.files` (336), todos `BY DESIGN`.
-#   - `.gitignore` deste repo (5.691 B) — fonte canônica secundária.
-#
-# Como auditar mudanças: depois de editar este arquivo, rodar `index_repository`
-# (ou esperar `auto_watch` re-indexar) e re-checar `cli index_status` → comparar
-# contagens em `not_indexed.dirs_count` e `not_indexed.files_count`.
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 1. Diretorios de runtime / pacote — nao sao codigo-fonte
-# ─────────────────────────────────────────────────────────────────────────────
-node_modules/
-node_modules
-
-# Builds e artefatos reproduziveis (Layer 1 Next.js / Electron)
-.build/
-dist/
-.next/
-out/
-
-# Electron especifico
-electron/dist-electron/
-electron/node_modules/
-icon.iconset/
-
-# Workspaces internos que tem proprio node_modules
-@omniroute/opencode-plugin/dist/
-@omniroute/opencode-plugin/node_modules/
-@omniroute/opencode-provider/dist/
-@omniroute/opencode-provider/node_modules/
-
-# Recursos nativos compilados (C/JNI/wasm)
-src/mitm/tproxy/native/build/
-
-# Artefatos locais do Stryker / Playwright / coverage
-.stryker-tmp/
-reports/mutation/
-stryker-output-*.json
-.playwright-mcp/
-test-results/
-playwright-report/
-blob-report/
-
-# Analise / linters / caches
-.analysis/
-.sisyphus/
-.plans/
-.gitnexus
-.worktrees
-.codegraph/
-
-# Quality artifacts (gerados por npm run lint --cache etc)
-.eslintcache
-.eslintcache-complexity
-
-# Claude Code local state
-.claude/scheduled_tasks.lock
-.claude/scheduled_tasks/
-.claude/sessions/
-.claude/state.json
-.claude/settings.local.json
-
-# Serena / Antigravity / outras tools locais
-.serena/
-.antigravitycli/
-.gemini/
-.config/
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 2. Diretorios com prefixo `_` — locais / privados (regra global do .gitignore)
-# ─────────────────────────────────────────────────────────────────────────────
-_*/
-_artifacts/
-_cache/
-_mono_repo/
-_references/
-_tasks/
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 3. Diretorios de tooling IA (state local, nao codigo)
-# ─────────────────────────────────────────────────────────────────────────────
-.agents/
-.claude/
-.vscode/
-.idea/
-.junie/
-.omc/
-.data/
-.data-dev/
-.local-data/
-.logs/
-.artifacts/
-.source/
-.superpowers/
-.claude-flow/
-.omnivscodeagent/
-omnirouteCloud/
-omnirouteSite/
-.omniroute/
-.stent/
-
-# Subpaths especificos do Claude Code que nao estao em .claude/ (criados sob repo)
-.claude/worktrees/
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 4. Diretorios de dados / runtime locais (storage, env, secrets, scratch)
-# ─────────────────────────────────────────────────────────────────────────────
-data/
-src/lib/env/
-src/app/api/agent-skills/coverage/
-src/app/api/cloud/
-src/app/api/sync/cloud/
-src/app/api/system/env/
-tests/golden-set/data/
-
-# Logs e saida de teste
-logs/*
-test_output.log
-home-diegosouzapw-dev-automacoes-*.txt
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 5. Diretorios do monorepo por subprojeto (nao fazem parte do app principal)
-# ─────────────────────────────────────────────────────────────────────────────
-security-analysis/
-vscode-extension/
-obsidian-plugin/node_modules/
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 6. Diretorios de documentacao interna / workflow
-# ─────────────────────────────────────────────────────────────────────────────
-docs/superpowers/
-
-# ─────────────────────────────────────────────────────────────────────────────
-# 7. Arquivos especificos (nao diretorios inteiros)
-# ─────────────────────────────────────────────────────────────────────────────
-
-# Segredos e env — NUNCA indexar
-.env
-.env.*
-!.env.example
-!.env.homolog.example
-
-# TypeScript build info e next env declaration
-*.tsbuildinfo
-next-env.d.ts
-typescript
-
-# SQLite transient files (WAL/SHM/journal)
-*.sqlite-shm
-*.sqlite-wal
-*.sqlite-journal
-
-# Mapas e source maps
-*.map
-
-# Bun / npm lockfiles ruidosos
-bun.lock
-
-# `cheaper-inference-gateway.svg` e arquivos de midia na raiz/asset ja cobertos
-# pelos `ignored-suffix` do indexador (svg/png/jpg/ico/etc >50kB ou >500linhas);
-# manter a regra explicita aqui ajuda a auditar:
-cheaper-inference-gateway.svg
-cheaper-inference-gateway-*.svg
-
-# Husky internals
-.husky/_/
-
-# CI / quality metric artifacts
-config/quality/quality-metrics.json
-config/quality/test-impact-map.json
-audit-report.json
-.gh-discussions.json
-
-# i18n audit (gerado por npm run scripts)
-scripts/i18n/_audit.json
-scripts/i18n/_pending-keys.json
-
-# Cli binario local (scratch)
-bin/omniroute.mjs
-
-# Deploy / docker backups
-deploy.sh
-docker-compose.yml.bak
-docker-compose.minimal.yml

.env.example

@@ -1414,6 +1414,10 @@ APP_LOG_TO_FILE=true
 # Default: ~/.omniroute/plugins/  Override in dev/CI to point at a local plugin tree.
 # OMNIROUTE_PLUGIN_PATH=
 
+# Allow plugins to request the 'exec' permission (spawn child processes from the
+# plugin worker sandbox). Disabled by default; set to 1 to enable (local operator only).
+# OMNIROUTE_PLUGINS_ALLOW_EXEC=0
+
 # ── Prompt cache (system prompt deduplication) ──
 # Used by: open-sse/services — caches identical system prompts across requests.
 # PROMPT_CACHE_MAX_SIZE=50              # Max cached entries (default: 50)

.github/pull_request_template.md

@@ -9,14 +9,11 @@
 
 ## Validation
 
-Choose the change type and focused loop from the
-[Contribution Golden Path](../docs/dev/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):
+Run only the focused loop for what you changed — 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
-- [ ] Focused tests and category gates from the golden path
+- [ ] Focused tests for the change: `node --import tsx/esm --test tests/unit/<file>.test.ts`
 - [ ] `npm run lint`
-- [ ] Reconciled with the current active release base; focused checks rerun afterward
 - [ ] Production-code changes include a new or updated automated test in this PR
 - [ ] SonarQube PR analysis is green or any remaining issues are explicitly documented below
 
@@ -32,4 +29,4 @@ Vitest, the 60% coverage gate, and the production build all run in CI on this PR
 
 ## Reviewer Notes
 
-- Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.
+- Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

.github/workflows/build-fork.yml

@@ -0,0 +1,71 @@
+name: Publish Fork Image to GHCR
+
+on:
+  push:
+    branches: [main]
+    tags:
+      - "v*"
+  workflow_dispatch:
+
+# Least-privilege default: read-only at the top level; the build job that pushes to
+# GHCR grants packages: write itself (Scorecard TokenPermissions).
+permissions:
+  contents: read
+
+env:
+  IMAGE_NAME: ghcr.io/kang-heewon/omniroute
+
+jobs:
+  build:
+    name: Build and Push Fork Image
+    if: github.repository == 'kang-heewon/OmniRoute'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v4
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+
+      - name: Login to GitHub Container Registry
+        uses: docker/login-action@v4
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract Docker metadata
+        id: meta
+        uses: docker/metadata-action@v6
+        with:
+          images: ${{ env.IMAGE_NAME }}
+          tags: |
+            type=raw,value=latest,enable={{is_default_branch}}
+            type=sha,prefix=sha-
+            type=ref,event=tag
+          labels: |
+            org.opencontainers.image.title=omniroute
+            org.opencontainers.image.description=Unified AI proxy/router — fork image
+            org.opencontainers.image.url=https://github.com/kang-heewon/OmniRoute
+            org.opencontainers.image.source=https://github.com/kang-heewon/OmniRoute
+            org.opencontainers.image.licenses=MIT
+
+      - name: Build and push
+        uses: docker/build-push-action@v7
+        with:
+          context: .
+          target: runner-base
+          platforms: linux/amd64,linux/arm64
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max

.github/workflows/build-rinseaid-image.yml

@@ -0,0 +1,39 @@
+name: Build Rinseaid OmniRoute image
+
+on:
+  push:
+    branches: [build-k3-reasoning-image]
+    paths:
+      - Dockerfile
+      - package-lock.json
+      - package.json
+      - open-sse/**
+      - scripts/build/**
+      - .github/workflows/build-rinseaid-image.yml
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: docker/setup-buildx-action@v3
+
+      - uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - uses: docker/build-push-action@v6
+        with:
+          context: .
+          target: runner-base
+          platforms: linux/amd64
+          push: true
+          tags: ghcr.io/rinseaid/omniroute:k3-reasoning-${{ github.sha }}

.github/workflows/ci.yml

@@ -42,18 +42,6 @@ jobs:
       - uses: actions/setup-node@v7
         with:
           node-version: ${{ env.CI_NODE_VERSION }}
-      # Refuse a PR that targets its own head branch before spending anything on it. #8912 has
-      # head == base == release/v3.8.50: no diff, can never merge, and it sits in the queue with
-      # a full check board attached on every push to that branch. One field comparison.
-      - name: Reject a PR that targets its own branch
-        if: github.event_name == 'pull_request'
-        env:
-          HEAD_REF: ${{ github.head_ref }}
-          BASE_REF: ${{ github.base_ref }}
-          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
-          BASE_SHA: ${{ github.event.pull_request.base.sha }}
-        run: node scripts/check/check-pr-self-target.mjs
-
       - id: classify
         env:
           EVENT_NAME: ${{ github.event_name }}
@@ -137,17 +125,6 @@ jobs:
       - run: npm run check:route-guard-membership
       - run: npm run check:test-discovery
       - run: npm run check:tracked-artifacts
-      # (gap 30) Also lives in quality.yml's PR-only "Merge integrity" job — because the
-      # CHANGELOG half of that job needs a base to diff against. This half does NOT: the
-      # generator either reproduces the committed SKILL.md files or it does not.
-      #
-      # Keeping it PR-only left a real hole. This cycle's merge trains landed in batches with
-      # `--admin`, which bypasses required checks, so three SKILL.md files drifted from the route
-      # catalog, rode the release squash into `main`, and the next cycle's sync-back turned them
-      # into a base-red that blocked EVERY PR into release/v3.8.50 until #8954. Running it here
-      # means a push to `main` catches the drift at the source instead of the next cycle
-      # inheriting it.
-      - run: npm run check:agent-skills-sync
       # WS1.7 (v3.8.49 plan): Dockerfile lint (hadolint, pinned by digest).
       # failure-threshold=error keeps the 5 pre-existing warnings (DL3008/DL3003/
       # DL3016 version pinning / WORKDIR) visible without blocking; any ERROR fails.
@@ -353,16 +330,8 @@ jobs:
           install -m 0755 /tmp/osv/*linux_amd64 "$HOME/.local/bin/osv-scanner"
           # actionlint — official download script
           bash <(curl -fsSL https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash) latest "$HOME/.local/bin"
-          # zizmor — PyPI (pipx preferred, pip --user fallback); lands in ~/.local/bin.
-          # PINNED on purpose. Unpinned, the runner installed whatever PyPI served that day and
-          # measured 1 finding MORE than the devbox on the identical commit (190 vs 189) during
-          # the v3.8.49 cycle — which cost a second rebaseline push per release, chasing a
-          # number that was never the code's. The ratchet compares counts across machines, so
-          # the auditor version has to be the same on both. Bump this deliberately, and
-          # rebaseline in the same commit: check-workflows.mjs now prints `zizmorVersion=` next
-          # to the count so the new number is traceable to the tool that produced it.
-          ZIZMOR_VERSION=1.25.2
-          pipx install "zizmor==$ZIZMOR_VERSION" || pip install --user "zizmor==$ZIZMOR_VERSION"
+          # zizmor — PyPI (pipx preferred, pip --user fallback); lands in ~/.local/bin
+          pipx install zizmor || pip install --user zizmor
           # oasdiff — download latest linux amd64 tarball via gh (authed), extract binary
           rm -rf /tmp/oasd && mkdir -p /tmp/oasd
           gh release download --repo oasdiff/oasdiff --pattern '*linux_amd64.tar.gz' --dir /tmp/oasd
@@ -751,13 +720,7 @@ jobs:
   test-unit:
     name: Unit Tests (${{ matrix.shard }}/8)
     # Same dynamic-runner rule as Build (own-origin only; fallback ubuntu-latest).
-    # PINNED to hosted, deliberately not on the USE_VPS_RUNNER switch (gap 19). One variable
-    # governed the build and the test jobs, which want OPPOSITE machines: the build needs the
-    # .113's RAM, the tests need the hosted runner's link. Measured on 2026-07-29 —
-    # actions/setup-node took 20m06s on .113 with 4 concurrent runners versus 16s hosted (npm
-    # cache restore saturating the link), while the tests themselves tied, 2m54 vs 2m31. So
-    # self-hosted is strictly worse here and there is nothing to configure.
-    runs-on: ubuntu-latest
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
     timeout-minutes: 25
     # needs: changes (not build) — this job never downloads the next-build artifact;
     # gating it on Build only serialized ~20min of wall-clock for nothing. Jobs that
@@ -829,13 +792,7 @@ jobs:
   test-vitest:
     name: Vitest (MCP / autoCombo / UI components)
     # Same dynamic-runner rule as Build (own-origin only; fallback ubuntu-latest).
-    # PINNED to hosted, deliberately not on the USE_VPS_RUNNER switch (gap 19). One variable
-    # governed the build and the test jobs, which want OPPOSITE machines: the build needs the
-    # .113's RAM, the tests need the hosted runner's link. Measured on 2026-07-29 —
-    # actions/setup-node took 20m06s on .113 with 4 concurrent runners versus 16s hosted (npm
-    # cache restore saturating the link), while the tests themselves tied, 2m54 vs 2m31. So
-    # self-hosted is strictly worse here and there is nothing to configure.
-    runs-on: ubuntu-latest
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
     timeout-minutes: 15
     # needs: changes (not build) — no artifact consumed; see test-unit note.
     needs: changes
@@ -1272,8 +1229,6 @@ jobs:
       - name: Generate dashboard
         env:
           EVENT_NAME: ${{ github.event_name }}
-          # Workflow-controlled data (job results), not user input — safe to read here.
-          NEEDS_JSON: ${{ toJSON(needs) }}
         run: |
           status() {
             case "$1" in
@@ -1288,29 +1243,6 @@ jobs:
           echo "# 🚀 CI Dashboard" >> "$GITHUB_STEP_SUMMARY"
           echo "" >> "$GITHUB_STEP_SUMMARY"
 
-          # (gap 12) A cancelled job never reported a verdict, and in a long table that reads the
-          # same as a green one. `cancel-in-progress` plus incremental fixing cancels jobs on every
-          # push, and this cycle the Vitest job was cancelled in rounds 1, 2 and 3 — it only ran to
-          # completion in round 4, where it revealed a suite that had been broken the whole cycle
-          # plus two production bugs. A gate that never finishes is indistinguishable from one that
-          # passes, so name them at the TOP instead of leaving them to be spotted mid-table.
-          CANCELLED_JOBS=$(printf '%s' "$NEEDS_JSON" \
-            | jq -r 'to_entries | map(select(.value.result == "cancelled")) | .[].key' 2>/dev/null \
-            | sort | paste -sd", " -) || CANCELLED_JOBS=""
-          if [ -n "$CANCELLED_JOBS" ]; then
-            {
-              echo "> ### ⚫ Cancelled — no verdict was reported"
-              echo ">"
-              echo "> \`$CANCELLED_JOBS\`"
-              echo ">"
-              echo "> These did not fail; they never finished, so nothing was checked. Treat this"
-              echo "> run as INCOMPLETE for those gates. If the cancellation came from"
-              echo "> \`cancel-in-progress\` on a newer push, the newer run covers it — otherwise"
-              echo "> re-run them before reading this dashboard as green."
-              echo ""
-            } >> "$GITHUB_STEP_SUMMARY"
-          fi
-
           echo "## 🧱 Core Checks" >> "$GITHUB_STEP_SUMMARY"
           echo "| Job | Status |" >> "$GITHUB_STEP_SUMMARY"
           echo "|-----|--------|" >> "$GITHUB_STEP_SUMMARY"

.github/workflows/docker-publish.yml

@@ -155,13 +155,13 @@ jobs:
         uses: docker/setup-buildx-action@v4
 
       - name: Login to Docker Hub
-        uses: docker/login-action@v4.5.2
+        uses: docker/login-action@v4
         with:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Login to GitHub Container Registry
-        uses: docker/login-action@v4.5.2
+        uses: docker/login-action@v4
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
@@ -255,13 +255,13 @@ jobs:
         uses: docker/setup-buildx-action@v4
 
       - name: Login to Docker Hub
-        uses: docker/login-action@v4.5.2
+        uses: docker/login-action@v4
         with:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Login to GitHub Container Registry
-        uses: docker/login-action@v4.5.2
+        uses: docker/login-action@v4
         with:
           registry: ghcr.io
           username: ${{ github.actor }}
@@ -390,7 +390,7 @@ jobs:
       - name: Upload Trivy SARIF to Security tab
         if: needs.prepare.outputs.version != 'main'
         continue-on-error: true
-        uses: github/codeql-action/upload-sarif@v4.37.3
+        uses: github/codeql-action/upload-sarif@v4
         with:
           sarif_file: trivy-results.sarif
           category: trivy-image

.github/workflows/electron-release.yml

@@ -120,18 +120,6 @@ jobs:
         env:
           JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
           NODE_OPTIONS: "--max_old_space_size=6144"
-          # Linux builds with webpack, not Turbopack. Turbopack's production build
-          # allocates natively (Rust, off the V8 heap), so --max_old_space_size does
-          # not bound it, and on this module graph it peaks above what the hosted
-          # runner can give — the VM is reclaimed mid-compile with "The runner has
-          # received a shutdown signal", no exit code. That is what silently took the
-          # whole desktop channel out of v3.8.49: the linux leg died, `release` was
-          # skipped, and the release shipped with ZERO assets. Measured on a 32 GB
-          # box the same build passes and peaks past 14 GB. The webpack fallback is
-          # the project's documented escape hatch for RAM-constrained machines
-          # (docs/reference/ENVIRONMENT.md, #6409) and is the same remedy already
-          # applied to nightly-compat's Node 26 build (#8090).
-          OMNIROUTE_USE_TURBOPACK: ${{ matrix.platform == 'linux' && '0' || '1' }}
         run: npm run build
 
       - name: Sync version in electron/package.json
@@ -229,16 +217,6 @@ jobs:
   release:
     name: Create Release
     needs: [validate, build]
-    # Fail-partial, not fail-closed. `build` is a 4-leg matrix with `fail-fast: false`,
-    # so the legs that succeed still upload their artifacts — but a default `needs:`
-    # gate skips this job the moment ANY leg fails, discarding all of them. That is
-    # exactly what happened to v3.8.49: the linux leg died and the release shipped with
-    # ZERO assets, throwing away 1.7 GB of good Windows/macOS installers **and** the
-    # source archives + SBOM, which do not depend on a build at all. The result was
-    # indistinguishable from "this version has no desktop channel".
-    # Now: attach everything that did build, then fail the job loudly (see the last
-    # step) so an incomplete channel is visible instead of silent.
-    if: ${{ !cancelled() && needs.validate.result == 'success' }}
     runs-on: ubuntu-latest
     permissions:
       contents: write # softprops/action-gh-release creates the GitHub Release
@@ -249,33 +227,11 @@ jobs:
           persist-credentials: false
           fetch-depth: 0
 
-      # `merge-multiple` is deliberately OFF. It resolves same-name collisions by ARRIVAL
-      # ORDER, and the two macOS jobs each emit their own `latest-mac.yml` listing only their
-      # own dmg (measured: 338 and 350 bytes, different content, identical name). One silently
-      # overwrote the other — arm64 won in the published v3.8.48, and since the Intel dmg
-      # carries no arch suffix in its name, electron-updater's
-      # `files.find(url includes process.arch) ?? files.shift()` sends every Intel Mac to the
-      # ARM dmg. Downloading into per-artifact subdirectories keeps both, so they can be
-      # merged on purpose instead of by luck.
       - name: Download all artifacts
         uses: actions/download-artifact@v8
         with:
-          path: artifacts
-
-      # Writes release-assets/latest-mac.yml with BOTH dmgs, un-suffixed entry first (that is
-      # the one electron-updater can only reach through its fallback). Refuses to write when the
-      # inputs disagree on version — a manifest stitched from two builds is worse than none.
-      - name: Merge the per-arch macOS updater manifests
-        run: node scripts/release/merge-mac-update-manifest.mjs artifacts release-assets
-
-      # Everything else moves across as-is. The partial latest-mac.yml files are excluded so
-      # they cannot clobber the merged one; -n is a second belt on the same braces.
-      - name: Collect the remaining artifacts
-        run: |
-          mkdir -p release-assets
-          find artifacts -type f ! -name latest-mac.yml -exec cp -n {} release-assets/ \;
-          echo "release-assets:"
-          ls -la release-assets/
+          path: release-assets
+          merge-multiple: true
 
       - name: Create source archives
         env:
@@ -319,47 +275,6 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
-  verify-desktop-assets:
-    name: Verify desktop assets landed
-    needs: [validate, release]
-    # Deliberately a SEPARATE job, not a final step of `release`: failing inside
-    # `release` would cascade into `publish-npm` (which gates on `needs: release`) and
-    # block the npm channel over a desktop-only gap. Here the assets are attached, npm
-    # still publishes, and an incomplete desktop channel shows up as a red job instead
-    # of passing unnoticed — the v3.8.49 release had ZERO assets and every gate was
-    # green, because nothing ever asserted the release HAS binaries.
-    if: ${{ !cancelled() && needs.release.result == 'success' }}
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-    steps:
-      - name: Assert every platform is present on the release
-        env:
-          # Regex-validated (^v[0-9]+\.[0-9]+\.[0-9]+$) in the `validate` job, and
-          # passed via env rather than interpolated into the script body.
-          VERSION: ${{ needs.validate.outputs.version }}
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          names=$(gh release view "$VERSION" --repo "$GITHUB_REPOSITORY" \
-                    --json assets --jq '.assets[].name')
-          echo "Assets on $VERSION:"
-          echo "$names" | sed 's/^/  /'
-
-          missing=""
-          # `[ ... ] && missing=...` as the last command in a branch returns 1 and
-          # would abort the whole script under Actions' default `set -e`. Use if/fi.
-          for want in '\.exe$' '\.dmg$' '\.AppImage$' '\.deb$' '^latest.*\.yml$' '\.source\.tar\.gz$'; do
-            if ! echo "$names" | grep -qE "$want"; then
-              missing="$missing $want"
-            fi
-          done
-
-          if [ -n "$missing" ]; then
-            echo "::error::Desktop channel incomplete on $VERSION — no asset matching:$missing"
-            exit 1
-          fi
-          echo "✓ every platform present on $VERSION"
-
   publish-npm:
     name: Publish to npm
     needs: [validate, release]

.github/workflows/npm-publish.yml

@@ -56,15 +56,8 @@ env:
 
 jobs:
   publish:
-    # Same dynamic-runner rule as ci.yml's `build`/`test-unit`: `build:cli` falls back to a
-    # full `next build`, whose working set outgrew the 16 GB hosted runner during the
-    # v3.8.49 cycle — the publish died with "The runner has received a shutdown signal"
-    # mid-"Creating an optimized production build" while v3.8.48 had still fit in 16min.
-    # This job never runs on `pull_request`, so the fork-safety clause is always true here;
-    # it is kept verbatim so the expression stays greppable against ci.yml.
-    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
+    runs-on: ubuntu-latest
     permissions:
-      actions: read # find + download the CI run's next-build artifact for this SHA
       contents: write # gh release upload (attach SBOM to the GitHub Release)
       id-token: write # npm provenance
       packages: write # publish to npm.pkg.github.com
@@ -152,74 +145,6 @@ jobs:
         run: |
           npm version "$VERSION" --no-git-tag-version --allow-same-version
 
-      # Fast path: CI already built the standalone tree for THIS commit and uploaded it as
-      # `next-build`. `build:cli` (scripts/build/prepublish.ts) only shells out to a full
-      # `next build` when `.build/next/standalone/server.js` is missing — restoring the
-      # artifact turns the heaviest step of the publish into a download. Matching on
-      # `head_sha` is the tree-equality guarantee: same commit, same tree.
-      # Best-effort by design (retention is 1 day): every miss falls through to the build
-      # step below, which is why the dynamic runner above matters as the backstop.
-      #
-      # The `head_repository.full_name == env.REPO` clause is a supply-chain guard, not a
-      # filter refinement. This artifact becomes the published npm tarball. `pull_request`
-      # runs from forks execute in THIS repository's context and upload their own
-      # `next-build` built from fork-controlled source, and the runs API returns them for a
-      # matching `head_sha` — 57 such runs exist in this repo today. Without the clause,
-      # anything that made a fork's head commit coincide with the publish commit could put
-      # attacker-built bytes on npm. Requiring the run to originate from this repository
-      # excludes every fork run while keeping the fast path intact (verified: the same
-      # single run is selected either way for the current tip).
-      # CodeQL: actions/artifact-poisoning/critical.
-      - name: Reuse CI's next-build artifact (skips the heavy rebuild)
-        if: steps.resolve.outputs.skip != 'true'
-        continue-on-error: true
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          HEAD_SHA: ${{ github.sha }}
-          REPO: ${{ github.repository }}
-        run: |
-          set -uo pipefail
-          # The question is "which run HAS the artifact", not "which run passed" (gap 16).
-          # Requiring `conclusion == "success"` on the whole run discarded a perfectly good tree
-          # whenever any unrelated shard went red — one flaky test then pushed the publish into
-          # the 40-minute build this step exists to avoid. The artifact is only uploaded if the
-          # Build job itself succeeded, so its PRESENCE is the accurate signal; the run's overall
-          # conclusion is noise from jobs that have nothing to do with the tree.
-          #
-          # `head_repository.full_name == env.REPO` stays, and it is not a filter refinement:
-          # this tree becomes the published npm tarball, and fork `pull_request` runs execute in
-          # THIS repository's context uploading their own next-build. That clause is the
-          # supply-chain guard (CodeQL actions/artifact-poisoning).
-          CANDIDATES=$(gh api "repos/$REPO/actions/runs?head_sha=$HEAD_SHA&per_page=100" \
-            --jq '[.workflow_runs[]
-                   | select(.name == "CI"
-                            and .head_repository.full_name == env.REPO)]
-                  | sort_by(.run_started_at) | reverse | .[0:5] | .[].id') || CANDIDATES=""
-          if [ -z "$CANDIDATES" ]; then
-            echo "::notice::no CI run from this repository for $HEAD_SHA — falling back to a full build"
-            exit 0
-          fi
-          RUN=""
-          for candidate in $CANDIDATES; do
-            if gh run download "$candidate" --repo "$REPO" --name next-build --dir /tmp/next-build 2>/dev/null; then
-              RUN="$candidate"
-              break
-            fi
-            echo "  run $candidate carries no usable next-build — trying the next"
-          done
-          if [ -z "$RUN" ]; then
-            echo "::notice::none of the candidate runs still carries next-build (1-day retention) — falling back to a full build"
-            exit 0
-          fi
-          tar -xzf /tmp/next-build/e2e-build.tar.gz -C .
-          rm -rf /tmp/next-build
-          if [ -f .build/next/standalone/server.js ]; then
-            echo "✅ standalone tree restored from CI run $RUN — build:cli will skip next build"
-          else
-            echo "::notice::extract did not yield .build/next/standalone — falling back to a full build"
-            rm -rf .build
-          fi
-
       - name: Build CLI bundle (standalone app)
         if: steps.resolve.outputs.skip != 'true'
         env:
@@ -256,18 +181,6 @@ jobs:
         if: steps.resolve.outputs.skip != 'true'
         run: npm run check:pack-boot
 
-      # The boot-smoke above proves a CLEAN install boots. It does not prove the path that
-      # actually broke us: installing over an existing version, where ~110 SQLite migrations
-      # run against a populated database. v3.8.48 shipped as a hotfix because the published
-      # 3.8.47 crashed on boot, and the v3.8.49 upgrade path was first exercised end-to-end
-      # by hand on a real 3.8.48 box (VPS .16) — after publishing, which is exactly backwards.
-      # Runs BEFORE `npm stage publish` so a broken upgrade never reaches the registry at all;
-      # a staged package that is never approved simply expires, with no `npm deprecate` needed.
-      - name: Prove clean-install AND upgrade-over-previous both boot
-        if: steps.resolve.outputs.skip != 'true'
-        timeout-minutes: 30
-        run: npm run check:install-upgrade
-
       # WS1.3 (D2, v3.8.49 plan): STAGED publishing by default — `npm stage publish`
       # parks the exact bytes on the registry WITHOUT making them installable; the
       # owner then verifies and approves with 2FA (`npm stage approve`), moving the

.github/workflows/quality.yml

@@ -112,20 +112,7 @@ jobs:
     # release captain has USE_VPS_RUNNER=true AND this is not a fork PR (own-origin
     # branches only — a fork PR must never execute on the LAN runner). Var unset/false
     # or a fork PR falls back to ubuntu-latest, so this is inert until the flag flips.
-    # PINNED to hosted (gap 19). This job carried the USE_VPS_RUNNER expression, and that
-    # expression was DEAD CONFIGURATION: across 160 quality.yml runs the job never once landed on
-    # a self-hosted runner — every non-skipped sample is `GitHub Actions NNNN`. The classifier is
-    # not at fault: in the same window ci.yml's Build demonstrably ran on omniroute-113-7 and
-    # omniroute-113-6, so self-hosted runs are visible when they happen.
-    #
-    # And if it ever HAD fired it would have inherited the measured penalty, because this job's
-    # first two steps are exactly the bottleneck: actions/setup-node + npm ci took 20m06s on .113
-    # with 4 concurrent runners versus 16s hosted (npm cache restore saturating the link). Median
-    # here is 5.6 min hosted across 72 successful runs.
-    #
-    # With this pinned, USE_VPS_RUNNER governs ONLY build-like jobs — one variable, one coherent
-    # purpose. That is what gap 19 asked for; a second variable turned out to be unnecessary.
-    runs-on: ubuntu-latest
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
     # tsx gates (known-symbols, route-guard-membership) import modules that open
     # SQLite on load; provide DB env so a fresh CI DB initializes cleanly.
     env:
@@ -179,81 +166,6 @@ jobs:
       # Complexity + cognitive-complexity: ONE ESLint walk (both baselines still
       # enforced separately by ruleId). Avoids two cold tree walks on fast-path.
       - run: npm run check:complexity-ratchets
-      # ── G0 (trilho .50): gates do trilho A que faltavam no trilho B ──────────────
-      # The god-file refactor happens in PRs→release/**; without these, the release
-      # rail never sees a new import cycle, dead code, duplication or a security
-      # regression until the release PR to main. Deliberately NOT brought here:
-      # bundle-size (self-skips without a build — this rail's build job is advisory
-      # and uploads nothing, so it would be dead configuration) and the coverage
-      # run (fast-unit already runs the full suite; the coverage ratchet stays on
-      # the main rail via --allow-missing in lint-guard).
-      - run: npm run check:cycles
-      - run: npm run check:lockfile
-      - name: Duplication ratchet
-        run: npm run check:duplication
-      - name: Dead-code ratchet (knip)
-        run: npm run check:dead-code
-      - name: Type coverage ratchet
-        run: npm run check:type-coverage
-      - name: Compression budget ratchet
-        run: npm run check:compression-budget
-      # Security scanners — same hardened install as ci.yml quality-extended
-      # (gh release download = authenticated, 5000 req/hr; curl to api.github.com
-      # is rate-limited to 60/hr and silently no-ops when throttled). The blocking
-      # gates below SKIP (exit 0) when their binary is absent — only a measured
-      # regression vs config/quality/quality-baseline.json blocks.
-      - name: Install security scanners (gitleaks/osv/actionlint/zizmor/oasdiff)
-        continue-on-error: true
-        env:
-          GH_TOKEN: ${{ github.token }}
-        run: |
-          set +e
-          mkdir -p "$HOME/.local/bin"
-          # Ratchets compare scanner COUNTS across runs. Pin every auditor: a rule-set
-          # update must be an explicit PR that re-measures/rebaselines, never a random
-          # red (or green) caused by whatever "latest" served that morning.
-          GITLEAKS_VERSION=v8.30.1
-          OSV_SCANNER_VERSION=v2.3.8
-          ACTIONLINT_VERSION=v1.7.12
-          ZIZMOR_VERSION=1.25.2
-          OASDIFF_VERSION=v1.19.1
-          # gitleaks — pinned linux x64 tarball via gh (authed), extract binary
-          rm -rf /tmp/gl && mkdir -p /tmp/gl
-          gh release download "$GITLEAKS_VERSION" --repo gitleaks/gitleaks --pattern '*linux_x64.tar.gz' --dir /tmp/gl
-          tar -xzf /tmp/gl/*linux_x64.tar.gz -C "$HOME/.local/bin" gitleaks
-          # osv-scanner — pinned linux amd64 bare binary via gh (authed)
-          rm -rf /tmp/osv && mkdir -p /tmp/osv
-          gh release download "$OSV_SCANNER_VERSION" --repo google/osv-scanner --pattern '*linux_amd64' --dir /tmp/osv
-          install -m 0755 /tmp/osv/*linux_amd64 "$HOME/.local/bin/osv-scanner"
-          # actionlint — official installer from a pinned release tag (never main)
-          bash <(curl -fsSL "https://raw.githubusercontent.com/rhysd/actionlint/${ACTIONLINT_VERSION}/scripts/download-actionlint.bash") "$ACTIONLINT_VERSION" "$HOME/.local/bin"
-          # zizmor — pinned PyPI package (same version as ci.yml quality-extended)
-          pipx install "zizmor==$ZIZMOR_VERSION" || pip install --user "zizmor==$ZIZMOR_VERSION"
-          # oasdiff — pinned linux amd64 tarball via gh (authed), extract binary
-          rm -rf /tmp/oasd && mkdir -p /tmp/oasd
-          gh release download "$OASDIFF_VERSION" --repo Tufin/oasdiff --pattern '*linux_amd64.tar.gz' --dir /tmp/oasd
-          tar -xzf /tmp/oasd/*linux_amd64.tar.gz -C "$HOME/.local/bin" oasdiff
-          # ALWAYS export the bin dir (even if any step above failed)
-          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
-          "$HOME/.local/bin/gitleaks" version || true
-          "$HOME/.local/bin/actionlint" -version || true
-          "$HOME/.local/bin/osv-scanner" --version || true
-          "$HOME/.local/bin/oasdiff" --version || true
-          zizmor --version || true
-      - name: Secret scan (gitleaks, ratchet, blocking)
-        run: npm run check:secrets -- --ratchet
-      - name: Vulnerability ratchet (osv-scanner, ratchet, blocking)
-        run: npm run check:vuln-ratchet -- --ratchet
-      - name: Workflow lint (actionlint+zizmor, ratchet, blocking)
-        run: npm run check:workflows -- --ratchet
-      # BASE_REF is read by the script from the env (never interpolated into a
-      # shell body) — workflow-injection-safe. actions/checkout fetches remote
-      # refs, not a local branch named github.base_ref, so prefix origin/ or this
-      # gate self-skips every PR with reason=base-unresolved.
-      - name: OpenAPI breaking-change (oasdiff, ratchet, blocking)
-        env:
-          BASE_REF: ${{ github.base_ref && format('origin/{0}', github.base_ref) || '' }}
-        run: npm run check:openapi-breaking -- --ratchet
       - name: Typecheck (core)
         run: npm run typecheck:core
       # #7033: dashboard-scoped typecheck gate — src/app/(dashboard) TSX is not
@@ -348,13 +260,7 @@ jobs:
     needs: changes
     if: ${{ github.event_name != 'pull_request' || ((github.event.pull_request.draft == false || startsWith(github.head_ref, 'mergify/merge-queue/')) && needs.changes.outputs.code == 'true') }}
     # Dynamic runner — see fast-gates (own-origin + flag; fork/unset → ubuntu-latest).
-    # PINNED to hosted, deliberately not on the USE_VPS_RUNNER switch (gap 19). One variable
-    # governed the build and the test jobs, which want OPPOSITE machines: the build needs the
-    # .113's RAM, the tests need the hosted runner's link. Measured on 2026-07-29 —
-    # actions/setup-node took 20m06s on .113 with 4 concurrent runners versus 16s hosted (npm
-    # cache restore saturating the link), while the tests themselves tied, 2m54 vs 2m31. So
-    # self-hosted is strictly worse here and there is nothing to configure.
-    runs-on: ubuntu-latest
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
     env:
       JWT_SECRET: ci-lint-secret-with-sufficient-length-for-validation
       API_KEY_SECRET: ci-lint-api-key-secret-long
@@ -390,13 +296,7 @@ jobs:
     # critical path again (~8.5min → ~4.5min on ubuntu-latest; ~2min on the 8-slot
     # runner box). Node's native --test-shard=N/total takes any denominator — only
     # this matrix and the TEST_SHARD env below encode the shard count.
-    # PINNED to hosted, deliberately not on the USE_VPS_RUNNER switch (gap 19). One variable
-    # governed the build and the test jobs, which want OPPOSITE machines: the build needs the
-    # .113's RAM, the tests need the hosted runner's link. Measured on 2026-07-29 —
-    # actions/setup-node took 20m06s on .113 with 4 concurrent runners versus 16s hosted (npm
-    # cache restore saturating the link), while the tests themselves tied, 2m54 vs 2m31. So
-    # self-hosted is strictly worse here and there is nothing to configure.
-    runs-on: ubuntu-latest
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository)) && fromJSON('["self-hosted","omni-release"]') || 'ubuntu-latest' }}
     strategy:
       fail-fast: false
       matrix:
@@ -439,12 +339,6 @@ jobs:
     if: ${{ github.event_name != 'pull_request' || ((github.event.pull_request.draft == false || startsWith(github.head_ref, 'mergify/merge-queue/')) && needs.changes.outputs.code == 'true') }}
     runs-on: ubuntu-latest
     continue-on-error: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == true }}
-    # G0 (trilho .50): security-events:read lets the CodeQL ratchet below read open
-    # code-scanning alerts via `gh api .../code-scanning/alerts` (same as ci.yml's
-    # quality-gate job). contents: read keeps checkout working.
-    permissions:
-      contents: read
-      security-events: read
     steps:
       - uses: actions/checkout@v7
         with:
@@ -466,29 +360,6 @@ jobs:
       - name: ESLint (baseline congelado — warning novo = vermelho)
         # lint:json writes the report; --max-warnings 0 keeps no-new-warnings policy.
         run: npm run lint:json -- --max-warnings 0
-      # ── G0 (trilho .50): motor de ratchet também no trilho B ─────────────────────
-      # This job just wrote .artifacts/eslint-results.json — collect-metrics prefers
-      # that file, so the ratchet engine lands here at ZERO extra ESLint cost (one
-      # inventory, two consumers; same reason ci.yml chains lint → quality-gate).
-      # The coverage-report artifact does not exist on this rail, so both ratchet
-      # invocations run --allow-missing: coverage.* metrics skip gracefully while
-      # the deterministic ones (eslint / openapi-coverage / i18n-ui) stay BLOCKING.
-      # Coverage authority remains on the main rail (ci.yml test-coverage → quality-gate).
-      - run: npm run quality:collect
-      - name: Ratchet check (blocking)
-        run: node scripts/quality/check-quality-ratchet.mjs --allow-missing --summary .artifacts/quality-ratchet.md
-      - name: Require-tighten (blocking)
-        run: node scripts/quality/check-quality-ratchet.mjs --allow-missing --require-tighten
-      # CodeQL alerts ratchet — same semantics as ci.yml quality-gate: exits 1 ONLY
-      # on a real regression (open alerts > baseline in quality-baseline.json);
-      # a measurement failure (gh/auth/api) self-skips with exit 0.
-      - name: CodeQL alerts ratchet (blocking)
-        run: npm run check:codeql-ratchet
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      - name: Append ratchet summary
-        if: always()
-        run: cat .artifacts/quality-ratchet.md >> "$GITHUB_STEP_SUMMARY" || true
 
   # Merge-integrity: pega no PR os dois vazamentos crônicos de merge que hoje só
   # explodem na release-PR. (1) CHANGELOG-eat — o auto-resolve do merge come

.gitignore

@@ -171,6 +171,7 @@ config/quality/test-impact-map.json
 # GitNexus local index
 .gitnexus
 .worktrees
+bin/omniroute.mjs
 
 # Consistent with .dockerignore / .npmignore
 .omc/
@@ -200,10 +201,7 @@ scripts/i18n/_pending-keys.json
 .codegraph/
 
 # Fumadocs generated source
-/.source/
-
-# Temporary local worktrees used to build unpublished npm tarballs
-/.deploy-build-*/
+.source/
 
 # AI agent local settings and configs
 .agents/
@@ -252,4 +250,3 @@ tests/homolog/.auth/
 tests/homolog/ui/.auth/
 homolog-report/
 docker-compose.yml.bak
-.playwright-cli/

.mergify.yml

@@ -17,13 +17,6 @@
 #   • Fallback path if Mergify misbehaves or the OSS plan changes: the manual
 #     merge-train runbook (docs/ops/MERGE_TRAIN.md) — remove labels, proceed by hand.
 
-# Auto-enqueue (current Mergify model, 2026): auto_merge_conditions in
-# merge_protections_settings — the rules-based queue action / autoqueue path is
-# deprecated (EOL 2026-07-16). The owner-applied `queue` label IS the approval.
-merge_protections_settings:
-  auto_merge_conditions:
-    - label = queue
-
 queue_rules:
   - name: release
     # Any current or future release branch — the reason GitHub's native queue was
@@ -41,26 +34,14 @@ queue_rules:
     # is intentionally NOT a condition here: the owner-applied `queue` label IS the
     # approval in this repo's single-maintainer model (see governance header).
     merge_conditions:
-      # "Zero failures" — EXCEPT the advisory "Build (advisory)" job (quality.yml):
-      # continue-on-error by design, and its GH-hosted Turbopack build hangs
-      # recurrently mid-"Creating an optimized production build" (100% failure rate
-      # across every sampled PR since the job was added 2026-07-27, always killed by
-      # a runner timeout/shutdown signal, never a real compile error). Any OTHER
-      # failure still blocks (anti-fail-open kept). The prior dast-smoke exception
-      # (#7225) was dropped here: dast-smoke's hang (#7226) has been dormant for
-      # weeks (0 failures in the last 30 runs; 2 all-time, none since 2026-07-13) —
-      # carrying its tolerance forward would mask problems it no longer causes.
-      - or:
-          - "#check-failure=0"
-          - and:
-              - "#check-failure=1"
-              - check-failure=Build (advisory)
+      - "#check-failure=0"
       - "#check-pending=0"
       - "#check-success>=1"
       - check-success=Merge integrity (changelog + generated skills)
-    # NO batching: 'Merge Queue Batch' requires a paid Mergify tier (live finding
-    # 2026-07-15 — the queue command fails with "Cannot use Merge Queue batch" on
-    # the free plan). Serial queue (1 PR at a time) still automates the train.
+    # Batching: validate up to 10 queued PRs together (the manual train's sweet spot);
+    # don't hold a lone PR hostage waiting for siblings.
+    batch_size: 10
+    batch_max_wait_time: 5 min
     # Squash keeps the one-commit-per-PR history the CHANGELOG reconciliation expects.
     merge_method: squash
 

.source/dynamic.ts

@@ -0,0 +1,8 @@
+// @ts-nocheck
+import { dynamic } from 'fumadocs-mdx/runtime/dynamic';
+import * as Config from '../source.config';
+
+const create = await dynamic<typeof Config, import("fumadocs-mdx/runtime/types").InternalTypeConfig & {
+  DocData: {
+  }
+}>(Config, {"configPath":"source.config.ts","environment":"next","outDir":".source"}, {"doc":{"passthroughs":["extractedReferences"]}});

.source/source.config.mjs

@@ -0,0 +1,22 @@
+// source.config.ts
+import { defineDocs, defineConfig } from "fumadocs-mdx/config";
+var docs = defineDocs({
+  dir: "docs",
+  docs: {
+    files: [
+      "./architecture/**/*.md",
+      "./guides/**/*.md",
+      "./reference/**/*.md",
+      "./frameworks/**/*.md",
+      "./routing/**/*.md",
+      "./security/**/*.md",
+      "./compression/**/*.md",
+      "./ops/**/*.md"
+    ]
+  }
+});
+var source_config_default = defineConfig();
+export {
+  source_config_default as default,
+  docs
+};

AGENTS.md

@@ -1,117 +1,600 @@
-# OmniRoute agent guide
+# omniroute — Agent Guidelines
 
 ## Project
 
-OmniRoute is a unified AI proxy/router. The repository contains the Next.js application
-(`src/`), streaming engine workspace (`open-sse/`), Electron desktop app (`electron/`),
-CLI (`bin/`), and tests (`tests/`).
+Unified AI proxy/router — route any LLM through one endpoint. Multi-provider support
+with **290 provider entries** (OpenAI, Anthropic, Gemini, DeepSeek, Groq, xAI, Mistral, Fireworks,
+Cohere, NVIDIA, Cerebras, Pollinations, Puter, Cloudflare AI, HuggingFace, DeepInfra,
+SambaNova, Meta Llama API, Moonshot AI, AI21 Labs, Databricks, Snowflake, and many more)
+with **MCP Server** (104 tools), **A2A v0.3 Protocol**, and **Electron desktop app**.
 
-## Setup and focused checks
+> **Live counts (v3.8.49)**: providers 290 · MCP tools 104 · MCP scopes 30 · A2A skills 6 ·
+> open-sse services 134 · routing strategies 17 · auto-combo scoring factors 12 ·
+> DB modules 95 · DB migrations 110 · base tables 17 · search providers 11 ·
+> i18n locales 42. **Refresh with `npm run check:docs-all`.**
 
-- Runtime: Node.js `>=22.22.3 <23` or `>=24.0.0 <27`; npm 10+.
-- Install dependencies: `npm install`.
-- Start development: `npm run dev`.
-- Build: `npm run build`; release build: `npm run build:release`.
-- Lint: `npm run lint`.
-- Core type check: `npm run typecheck:core`.
-- Run the most focused test for changed code first:
-  `node --import tsx/esm --test tests/unit/<file>.test.ts`.
-- Other suites: `npm run test:vitest`, `npm run test:e2e`,
-  `npm run test:protocols:e2e`, and `npm run test:ecosystem`.
-- Run `npm run check:docs-all` after changing documentation.
+## Doc Accuracy Discipline (read before writing any doc)
 
-For the complete test matrix, coverage requirements, and pull-request gates, read
-[`CONTRIBUTING.md`](CONTRIBUTING.md#running-tests).
+> **If `grep -rn "name" src/ open-sse/ bin/` returns nothing, the name does not exist. Do not document it.**
 
-## Documentation accuracy
+The recurring failure mode in AI-generated docs is _plausible-but-unverified specifics_.
+Every claim in a `.md` file under `docs/` should be verifiable against the source.
 
-Documentation must describe verified behavior, not plausible behavior.
+**Rules (enforced by `npm run check:fabricated-docs`):**
 
-1. Before documenting an API name, endpoint, path, CLI command, or environment variable,
-   search for it: `rg -n "name" src/ open-sse/ bin/`. If it has no source match, do not
-   document it.
-2. Measure mutable counts instead of writing them from memory: use `wc -l <file>` or a
-   directory-specific count command.
-3. Copy code examples from working usage or run them. Prefer a source link such as
-   `path/to/file.ts:line` to an invented signature.
-4. Run `npm run check:docs-all` for edits under `docs/`; it includes the fabricated-docs
-   validation.
+1. **Never state an API name, endpoint, path, CLI command, or env var without grepping for it first.**
+   ```bash
+   grep -rn "theName" src/ open-sse/ bin/
+   # 0 hits → do not document
+   ```
+2. **Never write a line count, file size, migration count, provider count, or strategy count from memory.**
+   ```bash
+   wc -l <file>           # exact line count
+   ls <dir>/*.ts | wc -l  # file count
+   ```
+3. **Every code example should be copy-pasted from real usage or actually run** — not synthesized.
+   Link to a real call site (`path:line`) instead of inventing a signature.
+4. **Prefer citing real source (`file.ts:line`) over paraphrasing behavior** — verifiable and self-correcting.
+5. **A shorter doc that is 100% accurate beats a comprehensive one with fabrications.**
+   Wrong docs cost more than missing docs, because people trust and act on them.
 
-## Code conventions
+The script `scripts/check/check-fabricated-docs.mjs` extracts every route path, env var, hook
+name, function name, and file reference from `docs/**/*.md` and verifies each one against the
+codebase. Run it locally before pushing docs; it runs in CI via `npm run check:docs-all`.
 
-- Format with Prettier: two spaces, semicolons, double quotes, 100-character line width,
-  and ES5 trailing commas. Run Prettier on changed files.
-- TypeScript target is ES2022 with bundler module resolution. Prefer explicit types.
-- Import order: external, internal (`@/` and `@omniroute/open-sse`), then relative.
-- Do not add logic to `src/lib/localDb.ts`; import from the owning `src/lib/db/` module.
-- Use specific errors and contextual logging. Do not silently swallow SSE-stream failures;
-  use abort signals for cleanup and return appropriate HTTP status codes.
+## Stack
 
-## Security requirements
+- **Runtime**: Next.js 16 (App Router), Node.js `>=22.0.0 <23 || >=24.0.0 <27`, ES Modules (`"type": "module"`)
+- **Language**: TypeScript 6.0 (`src/`) + JavaScript (`open-sse/`, `electron/`)
+- **Database**: better-sqlite3 (SQLite) — `DATA_DIR` configurable, default `~/.omniroute/`
+- **Streaming**: SSE via `open-sse` internal workspace package
+- **Styling**: Tailwind CSS v4
+- **i18n**: next-intl with 42 locales (`src/i18n/messages/`) — refresh with `ls src/i18n/messages/*.json | wc -l`
+- **Desktop**: Electron (cross-platform: Windows, macOS, Linux)
+- **Schemas**: Zod v4 for all API / MCP input validation
 
-- Never commit credentials or log SQLite encryption keys.
-- Validate API inputs with Zod and use the route's required authentication path.
-- Sanitize user HTML with DOMPurify.
-- Use `resolvePublicCred()` for public upstream OAuth identifiers; never add them as string
-  literals. See [`docs/security/PUBLIC_CREDS.md`](docs/security/PUBLIC_CREDS.md).
-- Use `buildErrorBody()` or `sanitizeErrorMessage()` for HTTP, SSE, executor, and MCP errors;
-  do not return raw `err.stack` or `err.message`. See
-  [`docs/security/ERROR_SANITIZATION.md`](docs/security/ERROR_SANITIZATION.md).
-- Pass runtime values to `exec()` or `spawn()` through `env`, not interpolation into a script.
+---
 
-## Repository map
+## Build, Lint, and Test Commands
 
-Read the nearest `AGENTS.md` and the linked deep-dive before making a non-trivial change.
+| Command                             | Description                                                        |
+| ----------------------------------- | ------------------------------------------------------------------ |
+| `npm run dev`                       | Start Next.js dev server                                           |
+| `npm run build`                     | Production build: `next build` → `.build/next/` + assemble `dist/` |
+| `npm run build:release`             | Clean rebuild + HEAD sentinel (`dist/BUILD_SHA`) — use for deploy  |
+| `npm run start`                     | Run production build                                               |
+| `npm run build:cli`                 | Build CLI package                                                  |
+| `npm run lint`                      | ESLint on all source files                                         |
+| `npm run typecheck:core`            | TypeScript core type checking                                      |
+| `npm run typecheck:noimplicit:core` | Strict checking (no implicit any)                                  |
+| `npm run check`                     | Run lint + test                                                    |
+| `npm run check:cycles`              | Check for circular dependencies                                    |
+| `npm run electron:dev`              | Run Electron app in dev mode                                       |
+| `npm run electron:build`            | Build Electron app for current OS                                  |
 
-| Area                               | Location                                                | Start here                                                                                                                                       |
-| ---------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
-| API routes                         | `src/app/api/v1/`                                       | [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md)                                                                         |
-| Streaming request handling         | `open-sse/handlers/`                                    | [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md)                                                                         |
-| Provider execution and translation | `open-sse/executors/`, `open-sse/translator/`           | [`docs/architecture/CODEBASE_DOCUMENTATION.md`](docs/architecture/CODEBASE_DOCUMENTATION.md)                                                     |
-| Routing and resilience             | `open-sse/services/`                                    | [`open-sse/services/AGENTS.md`](open-sse/services/AGENTS.md), [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md)                         |
-| Database and migrations            | `src/lib/db/`, `db/migrations/`                         | [`src/lib/db/AGENTS.md`](src/lib/db/AGENTS.md)                                                                                                   |
-| Domain policy                      | `src/domain/`                                           | [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md)                                                                         |
-| MCP and A2A                        | `open-sse/mcp-server/`, `src/lib/a2a/`                  | [`docs/frameworks/MCP-SERVER.md`](docs/frameworks/MCP-SERVER.md), [`docs/frameworks/A2A-SERVER.md`](docs/frameworks/A2A-SERVER.md)               |
-| Agent features                     | `src/lib/{acp,memory,skills,cloudAgent}/`               | [`docs/frameworks/AGENT_PROTOCOLS_GUIDE.md`](docs/frameworks/AGENT_PROTOCOLS_GUIDE.md), [`docs/frameworks/SKILLS.md`](docs/frameworks/SKILLS.md) |
-| Safety and governance              | `src/lib/{guardrails,compliance}/`, `src/server/authz/` | [`docs/security/GUARDRAILS.md`](docs/security/GUARDRAILS.md), [`docs/architecture/AUTHZ_GUIDE.md`](docs/architecture/AUTHZ_GUIDE.md)             |
-| Operations                         | `src/mitm/`, tunnel modules, `electron/`                | [`docs/ops/TUNNELS_GUIDE.md`](docs/ops/TUNNELS_GUIDE.md), [`docs/guides/ELECTRON_GUIDE.md`](docs/guides/ELECTRON_GUIDE.md)                       |
+**Build output layout:**
 
-## Review focus
+| Directory | Purpose                                            | Gitignored |
+| --------- | -------------------------------------------------- | ---------- |
+| `src/`    | Application source (TypeScript / TSX)              | No         |
+| `.build/` | Build intermediates (`distDir = .build/next`)      | Yes        |
+| `dist/`   | Shippable bundle assembled by `assembleStandalone` | Yes        |
 
-- Keep database operations in `src/lib/db/`; do not issue raw SQL from routes.
-- Send provider requests through `open-sse/handlers/`.
-- Keep MCP and A2A pages as tabs inside `/dashboard/endpoint`.
-- Preserve SSE cleanup, rate-limit header parsing, Zod validation, and provider-schema
-  validation.
-- Treat Memory and Skills as cross-cutting changes that can affect MCP tools, the request
-  pipeline, and A2A skills.
-- Do not close a contributor pull request after using its code; merge it through GitHub so
-  the contributor receives credit.
+The pipeline is a single `next build` pass — intermediates land in `.build/next/`, the
+assembled bundle in `dist/`. VPS deploys rsync `dist/` into the remote
+`/usr/lib/node_modules/omniroute/app/` directory (VPS image path is unchanged).
 
-## Upstream contributions
+### Running Tests
 
-This checkout is a fork of `diegosouzapw/OmniRoute`. Keep fork-only deployment and personal
-automation changes out of upstream PRs.
+```bash
+# All tests (unit + vitest + ecosystem + e2e)
+npm run test:all
 
-Start upstream work from the active upstream default branch, not `main`:
+# Single test file (Node.js native test runner — most tests use this)
+node --import tsx/esm --test tests/unit/your-file.test.ts
+node --import tsx/esm --test tests/unit/plan3-p0.test.ts
+node --import tsx/esm --test tests/unit/fixes-p1.test.ts
+node --import tsx/esm --test tests/unit/security-fase01.test.ts
+
+# Integration tests
+node --import tsx/esm --test tests/integration/*.test.ts
+
+# Vitest (MCP server, autoCombo)
+npm run test:vitest
+
+# E2E with Playwright
+npm run test:e2e
+
+# Protocol clients E2E (MCP transports, A2A)
+npm run test:protocols:e2e
+
+# Ecosystem compatibility tests
+npm run test:ecosystem
+
+# Coverage (see CONTRIBUTING.md)
+npm run test:coverage
+```
+
+**For authoritative coverage requirements, test execution, and PR gates, see [`CONTRIBUTING.md`](CONTRIBUTING.md#running-tests).**
+
+---
+
+## Code Style Guidelines
+
+### Formatting (Prettier — enforced via lint-staged)
+
+2 spaces · semicolons required · double quotes (`"`) · 100 char width · es5 trailing commas.
+Always run `prettier --write` on changed files.
+
+### TypeScript
+
+- **Target**: ES2022 · **Module**: `esnext` · **Resolution**: `bundler`
+- `strict: false` — prefer explicit types, don't rely on inference
+- Path aliases: `@/*` → `src/`, `@omniroute/open-sse` → `open-sse/`, `@omniroute/open-sse/*` → `open-sse/*`
+
+### ESLint Rules
+
+- **Security (error, everywhere)**: `no-eval`, `no-implied-eval`, `no-new-func`
+- **Relaxed in `open-sse/` and `tests/`**: `@typescript-eslint/no-explicit-any` = warn
+- React hooks rules and `@next/next/no-assign-module-variable` disabled in `open-sse/` and `tests/`
+
+### Naming
+
+| Element             | Convention                       | Example                              |
+| ------------------- | -------------------------------- | ------------------------------------ |
+| Files               | camelCase / kebab-case           | `chatCore.ts`, `tokenHealthCheck.ts` |
+| React components    | PascalCase                       | `Dashboard.tsx`, `ProviderCard.tsx`  |
+| Functions/variables | camelCase                        | `getHealth()`, `switchCombo()`       |
+| Constants           | UPPER_SNAKE                      | `MAX_RETRIES`, `DEFAULT_TIMEOUT`     |
+| Interfaces          | PascalCase (`I` prefix optional) | `ProviderConfig`                     |
+| Enums               | PascalCase (members too)         | `LogLevel.Error`                     |
+
+### Imports
+
+- **Order**: external → internal (`@/`, `@omniroute/open-sse`) → relative (`./`, `../`)
+- **No barrel imports** from `localDb.ts` — import from the specific `db/` module instead
+
+### Error Handling
+
+- try/catch with specific error types; always log with context (pino logger)
+- Never silently swallow errors in SSE streams — use abort signals for cleanup
+- Return proper HTTP status codes (4xx client, 5xx server)
+
+### Security
+
+- **NEVER** commit API keys, secrets, or credentials
+- Validate all user inputs with Zod schemas
+- Auth middleware required on all API routes
+- Never log SQLite encryption keys
+- Sanitize user content (dompurify for HTML)
+- **Public upstream OAuth identifiers** (Gemini / Antigravity / Windsurf-style client_id/secret + Firebase Web keys extracted from public CLIs): use `resolvePublicCred()` from `open-sse/utils/publicCreds.ts`, **never** as string literals. Full pattern in `docs/security/PUBLIC_CREDS.md`.
+- **Error responses** (HTTP / SSE / executor / MCP): use `buildErrorBody()` or `sanitizeErrorMessage()` from `open-sse/utils/error.ts`, **never** put raw `err.stack` / `err.message` in a Response body. Full pattern in `docs/security/ERROR_SANITIZATION.md`.
+- **`exec()` / `spawn()` with runtime values**: pass via the `env` option, **never** string-interpolate paths/values into the script body. Reference: `src/mitm/cert/install.ts::updateNssDatabases`.
+- Prefer secure-by-default libraries when available — see [tldrsec/awesome-secure-defaults](https://github.com/tldrsec/awesome-secure-defaults) for the curated list (Helmet.js, DOMPurify, ssrf-req-filter, safe-regex, Google Tink, etc.).
+
+---
+
+## Architecture
+
+### Data Layer (`src/lib/db/`)
+
+All persistence uses SQLite through **95 domain-specific modules** in `src/lib/db/`. Top modules:
+
+- Core: `core.ts`, `migrationRunner.ts`, `encryption.ts`, `stateReset.ts`
+- Providers / catalog: `providers.ts`, `models.ts`, `providerLimits.ts`, `compressionAnalytics.ts`
+- Routing: `combos.ts`, `modelComboMappings.ts`, `domainState.ts`, `commandCodeAuth.ts`
+- Auth: `apiKeys.ts`, `secrets.ts`, `registeredKeys.ts`, `sessionAccountAffinity.ts`
+- Usage / billing: `quotaSnapshots.ts`, `creditBalance.ts`, `usage*.ts`, `compressionCacheStats.ts`
+- Storage: `backup.ts`, `cleanup.ts`, `jsonMigration.ts`, `healthCheck.ts`, `databaseSettings.ts`
+- Extension modules: `evals.ts`, `webhooks.ts`, `reasoningCache.ts`, `readCache.ts`, `tierConfig.ts`, `compressionCombos.ts`, `compressionScheduler.ts`, `batches.ts`, `files.ts`, `syncTokens.ts`, `proxies.ts`, `oneproxy.ts`, `upstreamProxy.ts`, `versionManager.ts`, `cliToolState.ts`, `prompts.ts`, `detailedLogs.ts`, `contextHandoffs.ts`, `compression.ts`, `stats.ts`
+
+Live count: `ls src/lib/db/*.ts | wc -l` (currently 95). Drift detection: `npm run check:docs-counts`.
+Schema migrations live in `db/migrations/` (**110 files** as of v3.8.43) and run via `migrationRunner.ts`.
+`src/lib/localDb.ts` is a **re-export layer only** — never add logic there.
+
+#### DB Internals
+
+- **`core.ts`**: `getDbInstance()` returns a singleton `better-sqlite3` instance with WAL
+  journaling. `SCHEMA_SQL` defines **17 base tables** (verify with `grep -c "CREATE TABLE" src/lib/db/core.ts` minus 1 for the bookkeeping `_omniroute_migrations` table). Helpers: `rowToCamel`, `encryptConnectionFields`.
+- **`migrationRunner.ts`**: Applies versioned SQL files from `db/migrations/` inside transactions.
+  Tracks applied migrations in `_omniroute_migrations` table.
+- **Migrations**: 110 files (`001_initial_schema.sql` → `110_*.sql`).
+  Each migration is idempotent and runs in a transaction. Live count: `ls src/lib/db/migrations/*.sql | wc -l`.
+- **Domain modules** import `getDbInstance()` from `core.ts` for all CRUD operations.
+  Each module owns a specific table/set of tables (e.g., `providers.ts` → `provider_connections`,
+  `combos.ts` → `combos`). Encryption helpers protect sensitive fields at rest.
+- **`localDb.ts`** re-exports all domain modules — consumers import from here for convenience.
+
+### API Route Layer (`src/app/api/v1/`)
+
+Next.js App Router routes — each follows a consistent pattern:
+
+```
+Route → CORS preflight → Body validation (Zod) → Optional auth (extractApiKey/isValidApiKey)
+  → API key policy enforcement (enforceApiKeyPolicy) → Handler delegation (open-sse)
+```
+
+| Route                           | Handler                   | Notes                                                         |
+| ------------------------------- | ------------------------- | ------------------------------------------------------------- |
+| `chat/completions/route.ts`     | `handleChat()`            | + prompt injection guard (clones request)                     |
+| `responses/route.ts`            | `handleChat()` (unified)  | Responses API format                                          |
+| `embeddings/route.ts`           | `handleEmbedding()`       | Model listing + creation                                      |
+| `images/generations/route.ts`   | `handleImageGeneration()` | Model listing + creation                                      |
+| `audio/transcriptions/route.ts` | audio handler             | Multipart form data                                           |
+| `audio/speech/route.ts`         | TTS handler               | Binary audio response                                         |
+| `videos/generations/route.ts`   | video handler             | ComfyUI/SD WebUI                                              |
+| `music/generations/route.ts`    | music handler             | ComfyUI workflows                                             |
+| `moderations/route.ts`          | moderation handler        | Content safety                                                |
+| `rerank/route.ts`               | rerank handler            | Document relevance                                            |
+| `search/route.ts`               | search handler            | Web search (12 providers per `open-sse/handlers/search.ts:6`) |
+
+**No global Next.js middleware file** — interception is route-specific. Auth is optional
+(controlled by `REQUIRE_API_KEY` env). Prompt injection guard is unique to chat completions.
+
+### Request Pipeline (`open-sse/`)
+
+The `open-sse/` workspace is the core streaming engine. Full request flow:
+
+```
+Client Request
+  → src/app/api/v1/.../route.ts (Next.js route)
+    → open-sse/handlers/chatCore.ts::handleChatCore()
+      → Semantic/signature cache check
+      → Rate limit check (rateLimitManager)
+      → Combo routing? → open-sse/services/combo.ts::handleComboChat()
+        → resolveComboTargets() → ordered ResolvedComboTarget[]
+        → For each target: handleSingleModel() (wraps chatCore)
+      → translateRequest() (open-sse/translator/)
+        → Convert source format (e.g., OpenAI) → target format (e.g., Claude)
+      → getExecutor() → provider-specific executor instance
+        → executor.execute() (BaseExecutor → DefaultExecutor or provider-specific)
+          → buildUrl() + buildHeaders() + transformRequest()
+          → fetch() to upstream provider
+          → Retry logic with exponential backoff
+      → Response translation back to client format
+      → If Responses API: responsesTransformer.ts TransformStream
+  → SSE stream or JSON response to client
+```
+
+**Handlers** (`open-sse/handlers/`): `chatCore.ts`, `responsesHandler.ts`, `embeddings.ts`,
+`imageGeneration.ts`, `videoGeneration.ts`, `musicGeneration.ts`, `audioSpeech.ts`,
+`audioTranscription.ts`, `moderations.ts`, `rerank.ts`, `search.ts`.
+
+**Upstream headers**: merged after default auth; same header name replaces executor value.
+**T5 intra-family fallback** recomputes headers using only the fallback model id.
+Forbidden header names: `src/shared/constants/upstreamHeaders.ts` — keep sanitize,
+Zod schemas, and unit tests aligned when editing.
+
+### Provider Categories
+
+- **Free** (2): Qoder AI, Kiro AI
+- **OAuth** (13): Claude Code, Antigravity, Codex, GitHub Copilot, Cursor, Kimi Coding, Kilo Code, Cline, Kiro, Qoder, Gemini, Windsurf (v3.8), GitLab Duo (v3.8)
+- **API Key** (120+): OpenAI, Anthropic, Gemini, DeepSeek, Groq, xAI, Mistral, Perplexity,
+  Together, Fireworks, Cerebras, Cohere, NVIDIA, Nebius, SiliconFlow, Hyperbolic,
+  HuggingFace, OpenRouter, Vertex AI, Cloudflare AI, Scaleway, AI/ML API, Pollinations,
+  Puter, Longcat, Alibaba, Kimi, Minimax, Blackbox, Synthetic, Kilo Gateway,
+  Z.AI, GLM, Deepgram, AssemblyAI, ElevenLabs, Cartesia, PlayHT, Inworld,
+  NanoBanana, SD WebUI, ComfyUI, Ollama Cloud, Perplexity Search, Serper, Brave, Exa,
+  Tavily, OpenCode Zen/Go, Bailian Coding Plan, DeepInfra, Vercel AI Gateway,
+  Lambda AI, SambaNova, nScale, OVHcloud AI, Baseten, PublicAI, Moonshot AI,
+  Meta Llama API, v0 (Vercel), Morph, Featherless AI, FriendliAI, LlamaGate,
+  Galadriel, Weights & Biases Inference, Volcengine, AI21 Labs, Venice.ai,
+  Codestral, Upstage, Maritalk, Xiaomi MiMo, Inference.net, NanoGPT, Predibase,
+  Bytez, Heroku AI, Databricks, Snowflake Cortex, GigaChat (Sber), CrofAI,
+  AgentRouter, ChatGPT Web, Baidu Qianfan, AWS Polly, RunwayML, GitLab Duo,
+  Amazon Q, Empower, Poe, and many more.
+- **Self-Hosted** (8+): LM Studio, vLLM, Lemonade, Llamafile, Triton, Docker Model Runner, Xinference, Oobabooga
+- **Custom**: OpenAI-compatible (`openai-compatible-*`) and Anthropic-compatible (`anthropic-compatible-*`) prefixes
+
+Providers are registered in `src/shared/constants/providers.ts` with Zod validation at module load.
+
+### Executors (`open-sse/executors/`)
+
+Provider-specific request executors: `base.ts`, `default.ts`, `cursor.ts`, `codex.ts`,
+`antigravity.ts`, `github.ts`, `kiro.ts`, `qoder.ts`, `vertex.ts`,
+`cloudflare-ai.ts`, `opencode.ts`, `pollinations.ts`, `puter.ts`.
+
+#### Executor Internals
+
+- **`base.ts`** (`BaseExecutor`): Abstract base with `buildUrl()`, `buildHeaders()`,
+  `transformRequest()`, retry logic (exponential backoff), and `execute()`. Subclasses
+  override URL/header/transform methods for provider-specific behavior.
+- **`default.ts`** (`DefaultExecutor extends BaseExecutor`): Handles most OpenAI-compatible
+  providers. Reads provider config from `providerRegistry.ts` to resolve base URL, auth
+  header format, and request transformations.
+- **`getExecutor()`** (`executors/index.ts`): Factory that returns the correct executor
+  instance based on provider ID. Provider-specific executors (Cursor, Codex, Vertex, etc.)
+  override only what differs from the default.
+
+### Translator (`open-sse/translator/`)
+
+Translates between API formats (OpenAI-format ↔ Anthropic, Gemini, etc.).
+Includes request/response translators with helpers for image handling.
+
+#### Translator Internals
+
+- **`translator/index.ts`**: Exports `translateRequest()` and format constants. Called by
+  `chatCore.ts` before executor dispatch.
+- **Flow**: `translateRequest(body, sourceFormat, targetFormat)` → detects source format
+  (OpenAI, Anthropic, Gemini) → applies the matching translator module → returns
+  transformed body ready for the target provider.
+- **Response translation** runs in reverse after upstream response, converting back to
+  the client's expected format.
+
+### Transformer (`open-sse/transformer/`)
+
+`responsesTransformer.ts` — transforms Responses API format to/from Chat Completions format.
+
+#### Transformer Internals
+
+- **`createResponsesApiTransformStream()`**: Returns a `TransformStream` that converts
+  Chat Completions SSE chunks (`data: {"choices":[...]}`) into Responses API SSE events
+  (`response.output_item.added`, `response.output_text.delta`, etc.).
+- Used when the client sends a Responses API request: the request is internally converted
+  to Chat Completions format, dispatched normally, and the response is piped through this
+  transform stream before reaching the client.
+
+### Services (`open-sse/services/`)
+
+134 service modules in `open-sse/services/` (top-level only; more including sub-dirs like `autoCombo/` and `compression/`). Refresh: `ls open-sse/services/*.ts | wc -l`. Key modules:
+`combo.ts` (routing engine), `usage.ts`, `tokenRefresh.ts`,
+`rateLimitManager.ts`, `accountFallback.ts`, `sessionManager.ts`, `wildcardRouter.ts`,
+`autoCombo/`, `intentClassifier.ts`, `taskAwareRouter.ts`, `thinkingBudget.ts`,
+`contextManager.ts`, `modelDeprecation.ts`, `modelFamilyFallback.ts`,
+`emergencyFallback.ts`, `workflowFSM.ts`, `backgroundTaskDetector.ts`, `ipFilter.ts`,
+`signatureCache.ts`, `volumeDetector.ts`, `contextHandoff.ts`, `compression/` (prompt
+compression pipeline), and more.
+
+#### Prompt Compression Pipeline (`compression/`)
+
+Modular prompt compression that runs proactively before the existing reactive context manager.
+
+- **`strategySelector.ts`**: Selects compression mode based on config, compression combo assignments,
+  combo overrides, auto-trigger thresholds, and defaults. Priority: assigned compression combo >
+  combo override > auto-trigger > default mode > off.
+- **`lite.ts`**: 5 lite-mode techniques: `collapseWhitespace`, `dedupSystemPrompt`,
+  `compressToolResults`, `removeRedundantContent`, `replaceImageUrls`. Target: 10-15% savings at
+  <1ms latency.
+- **`caveman.ts` / `cavemanRules.ts`**: Caveman-style semantic condensation backed by built-in
+  rules plus file-loaded language packs under `compression/rules/`.
+- **`engines/rtk/`**: Rule-based terminal/tool-output compression inspired by RTK patterns. Detects
+  command output classes, applies JSON filter packs, deduplicates repeated lines, strips ANSI/code
+  noise, and preserves errors/actionable context. The RTK JSON DSL supports replace,
+  match-output short-circuit, strip/keep, per-line truncation, head/tail/max-line truncation,
+  inline tests, trust-gated project/global custom filters, and optional redacted raw-output
+  retention for authenticated recovery.
+- **`engines/registry.ts`**: Registers engines (`caveman`, `rtk`) and powers stacked pipelines.
+- **`stats.ts`**: Per-request compression stats tracking (original tokens, compressed tokens,
+  savings %, techniques used, engine breakdown, compression combo id).
+- **`types.ts`**: `CompressionMode` (off/lite/standard/aggressive/ultra/rtk/stacked),
+  `CompressionConfig`, `CompressionStats`, `CompressionResult`.
+- DB settings in `src/lib/db/compression.ts`, compression combos in
+  `src/lib/db/compressionCombos.ts`, API routes under `src/app/api/settings/compression/`,
+  `src/app/api/context/*`, and preview/language-pack routes under `src/app/api/compression/*`.
+
+#### Combo Routing Engine (`combo.ts`)
+
+- **`handleComboChat()`**: Entry point for combo-routed requests. Receives the combo config
+  and iterates through targets in order until one succeeds or all fail.
+- **`resolveComboTargets()`**: Expands a combo configuration into an ordered array of
+  `ResolvedComboTarget[]`, each specifying provider + model + account + credentials.
+- **Strategies** (17): priority, weighted, fill-first, round-robin, P2C, random, least-used, reset-aware (v3.8),
+  reset-window, cost-optimized, strict-random, auto, lkgp, context-optimized, context-relay, headroom, fusion. Source: `ROUTING_STRATEGY_VALUES` in `src/shared/constants/routingStrategies.ts`.
+- Each target calls **`handleSingleModel()`** which wraps `handleChatCore()` with
+  per-target error handling and circuit breaker checks.
+
+### Domain Layer (`src/domain/`)
+
+Policy engine modules: `policyEngine.ts`, `comboResolver.ts`, `costRules.ts`,
+`degradation.ts`, `fallbackPolicy.ts`, `lockoutPolicy.ts`, `modelAvailability.ts`,
+`providerExpiration.ts`, `quotaCache.ts`, `responses.ts`, `configAudit.ts`.
+
+### MCP Server (`open-sse/mcp-server/`)
+
+**104 tools** total (`TOTAL_MCP_TOOL_COUNT`, `open-sse/mcp-server/server.ts`): a 42-entry base registry (`MCP_TOOLS` in `schemas/tools.ts`, bundling the core / cache / compression / 1proxy / advanced tools) **plus** standalone module sets — memory (3), skill (4), agentSkill (3), pool (6), gamification (8), plugin (8), notion (6), obsidian (22). 3 transports (stdio / SSE / Streamable HTTP). Scoped auth (31 scopes — see `OMNIROUTE_MCP_SCOPES`), Zod schemas. See [`docs/frameworks/MCP-SERVER.md`](docs/frameworks/MCP-SERVER.md).
+
+**Core tools** (20): get_health, list_combos, get_combo_metrics, switch_combo, check_quota,
+route_request, cost_report, list_models_catalog, web_search, simulate_route, set_budget_guard,
+set_routing_strategy, set_resilience_profile, test_combo, get_provider_metrics,
+best_combo_for_task, explain_route, get_session_snapshot, db_health_check, sync_pricing.
+
+**Cache tools** (2): cache_stats, cache_flush.
+
+**Compression tools** (5): compression_status, compression_configure, set_compression_engine,
+list_compression_combos, compression_combo_stats.
+
+**1proxy tools** (3): oneproxy_fetch, oneproxy_rotate, oneproxy_stats.
+
+**Memory tools** (3): memory_search, memory_add, memory_clear.
+
+**Skill tools** (4): skills_list, skills_enable, skills_execute, skills_executions.
+
+**Agent-skill tools** (3): A2A skill discovery / invocation bridges.
+
+**Gamification tools** (8): levels, badges, leaderboard, and community-federation queries.
+
+**Plugin tools** (8): plugin marketplace listing, install/enable/disable, and runtime inspection.
+
+**Notion tools** (6) + **Obsidian tools** (22): knowledge-base read/write integrations (the largest tool family — vault search, note CRUD, WebDAV-backed file ops).
+
+#### MCP Internals
+
+- **Tool registration**: Each tool is an object with `{ name, description, inputSchema: ZodSchema,
+handler: async (args) => {...} }`. Zod validates inputs before the handler fires.
+- **`createMcpServer()`** and **`startMcpStdio()`** exported from `mcp-server/index.ts`.
+  `createMcpServer()` wires all tool sets; `startMcpStdio()` launches the stdio transport.
+- **Transports**: stdio (CLI `omniroute --mcp`), SSE (`/api/mcp/sse`), Streamable HTTP
+  (`/api/mcp/stream`). All share the same tool/scope engine.
+- **Scopes** (30): Control which tool categories an API key can access. Enforcement happens
+  before handler dispatch.
+- **Audit**: Every tool invocation is logged to SQLite (`mcp_audit` table) with tool name,
+  args, success/failure, API key attribution, and timestamp.
+
+### A2A Server (`src/lib/a2a/`)
+
+JSON-RPC 2.0, SSE streaming, Task Manager with TTL cleanup.
+Agent Card at `/.well-known/agent.json`.
+Skills (6): `smartRouting.ts`, `quotaManagement.ts`, `providerDiscovery.ts`, `costAnalysis.ts`, `healthReport.ts`, `listCapabilities.ts`.
+
+#### A2A Internals
+
+- **`taskManager.ts`**: State machine lifecycle for tasks: `submitted → working →
+completed | failed | canceled`. Tasks have TTL and are cleaned up automatically.
+- **JSON-RPC methods**: `message/send` (sync), `message/stream` (SSE), `tasks/get`,
+  `tasks/cancel`. Dispatched via `POST /a2a`.
+- **Skills**: Registered in a DB-backed registry. Each skill receives task context
+  (messages, metadata) and returns structured results. `quotaManagement.ts` summarizes
+  quota; `smartRouting.ts` recommends routing decisions.
+- **Agent Card**: `/.well-known/agent.json` exposes capabilities, skills, and metadata
+  for client auto-discovery.
+
+### ACP Module (`src/lib/acp/`)
+
+Agent Communication Protocol registry and manager.
+
+### Memory System (`src/lib/memory/`)
+
+Extraction, injection, retrieval, summarization, and store modules for persistent
+conversational memory across sessions.
+
+### Skills System (`src/lib/skills/`)
+
+Extensible skill framework: registry, executor, sandbox, built-in skills,
+custom skill support, interception, and injection.
+
+#### Skills Internals
+
+- **`registry.ts`**: DB-backed skill registration and discovery. Skills have metadata
+  (name, description, version, enabled status) stored in SQLite.
+- **`executor.ts`**: Execution engine with configurable timeout and retry logic.
+  Receives skill name + input, looks up the skill, runs it in the sandbox.
+- **`sandbox.ts`**: Isolation layer for custom (user-provided) skills. Limits resource
+  access and execution time.
+- **Built-in skills**: Ship with OmniRoute (e.g., quota management, routing). Located
+  alongside the registry.
+- **Interception/Injection**: Skills can intercept requests in the pipeline (pre/post
+  processing) or inject context into prompts.
+
+### Compliance (`src/lib/compliance/`)
+
+Policy index for compliance enforcement.
+
+### MITM Proxy (`src/mitm/`)
+
+MITM proxy capability with certificate management, DNS handling, and target routing.
+
+### Middleware (`src/middleware/`)
+
+Request middleware including `promptInjectionGuard.ts`.
+
+### Guardrails (`src/lib/guardrails/`)
+
+Hot-reloadable guardrails framework (3 built-in: pii-masker, prompt-injection, vision-bridge). Fail-open. The `pii-masker` guardrail is registered and runs on every request, but its data-mutating logic is **opt-in** and OFF by default — it only redacts when `PII_REDACTION_ENABLED` (request) / `PII_RESPONSE_SANITIZATION` (response + streaming) are enabled (both `defaultValue: "false"`); with them off, payloads pass through untouched. A request can additionally opt OUT of any guardrail via header (`x-omniroute-disabled-guardrails`). Never make PII default-on (Hard Rule #20). See [`docs/security/GUARDRAILS.md`](docs/security/GUARDRAILS.md).
+
+### Cloud Agents (`src/lib/cloudAgent/`)
+
+`CloudAgentBase` abstract class + 3 agents (codex-cloud, devin, jules). Tasks persisted in `cloud_agent_tasks`; management auth required. See [`docs/frameworks/CLOUD_AGENT.md`](docs/frameworks/CLOUD_AGENT.md).
+
+### Evals (`src/lib/evals/`)
+
+Generic eval framework: `evalRunner.ts`, `runtime.ts`. Targets: combo / model / suite-default. See [`docs/frameworks/EVALS.md`](docs/frameworks/EVALS.md).
+
+### Webhooks (`src/lib/webhookDispatcher.ts`)
+
+HMAC-signed delivery, exponential backoff, auto-disable after 10 failures. 7 event types. See [`docs/frameworks/WEBHOOKS.md`](docs/frameworks/WEBHOOKS.md).
+
+### Authorization Pipeline (`src/server/authz/`)
+
+`classify → policies → enforce`. 3 route classes (PUBLIC / CLIENT_API / MANAGEMENT). See [`docs/architecture/AUTHZ_GUIDE.md`](docs/architecture/AUTHZ_GUIDE.md).
+
+### Reasoning Replay (`src/lib/db/reasoningCache.ts` + `open-sse/services/reasoningCache.ts`)
+
+Hybrid in-memory + SQLite cache for `reasoning_content`. Re-injects on multi-turn for strict providers (DeepSeek V4, Kimi K2, Qwen-Thinking, GLM, xiaomi-mimo). See [`docs/routing/REASONING_REPLAY.md`](docs/routing/REASONING_REPLAY.md).
+
+### Tunnels (`src/lib/{cloudflaredTunnel,ngrokTunnel}.ts` + `src/app/api/tunnels/`)
+
+Cloudflare Quick/Named, ngrok, Tailscale Funnel. See [`docs/ops/TUNNELS_GUIDE.md`](docs/ops/TUNNELS_GUIDE.md).
+
+### Adding a New Provider
+
+1. Register in `src/shared/constants/providers.ts`
+2. Add executor in `open-sse/executors/` (if custom logic needed)
+3. Add translator in `open-sse/translator/` (if non-OpenAI format)
+4. Add OAuth config in `src/lib/oauth/constants/oauth.ts` (if OAuth-based)
+5. Add models in `open-sse/config/providerRegistry.ts`
+
+---
+
+## Subdirectory AGENTS.md Files
+
+- **[`src/lib/db/AGENTS.md`](src/lib/db/AGENTS.md)** — SQLite persistence, domain modules, migrations
+- **[`open-sse/services/AGENTS.md`](open-sse/services/AGENTS.md)** — Routing engine, combo resolution, strategy selection
+
+## Reference Documentation (docs/)
+
+For any non-trivial change, read the matching deep-dive first:
+
+| Area                                       | Doc                                                                                                             |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
+| Repo navigation                            | [`docs/architecture/REPOSITORY_MAP.md`](docs/architecture/REPOSITORY_MAP.md)                                    |
+| Architecture                               | [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md)                                        |
+| Engineering reference                      | [`docs/architecture/CODEBASE_DOCUMENTATION.md`](docs/architecture/CODEBASE_DOCUMENTATION.md)                    |
+| Auto-Combo (12-factor, 18 strategies)      | [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md)                                                      |
+| Resilience (3 layers)                      | [`docs/architecture/RESILIENCE_GUIDE.md`](docs/architecture/RESILIENCE_GUIDE.md)                                |
+| Skills                                     | [`docs/frameworks/SKILLS.md`](docs/frameworks/SKILLS.md)                                                        |
+| Memory                                     | [`docs/frameworks/MEMORY.md`](docs/frameworks/MEMORY.md)                                                        |
+| Cloud agents                               | [`docs/frameworks/CLOUD_AGENT.md`](docs/frameworks/CLOUD_AGENT.md)                                              |
+| Guardrails                                 | [`docs/security/GUARDRAILS.md`](docs/security/GUARDRAILS.md)                                                    |
+| Evals                                      | [`docs/frameworks/EVALS.md`](docs/frameworks/EVALS.md)                                                          |
+| Compliance                                 | [`docs/security/COMPLIANCE.md`](docs/security/COMPLIANCE.md)                                                    |
+| Webhooks                                   | [`docs/frameworks/WEBHOOKS.md`](docs/frameworks/WEBHOOKS.md)                                                    |
+| Authz                                      | [`docs/architecture/AUTHZ_GUIDE.md`](docs/architecture/AUTHZ_GUIDE.md)                                          |
+| Stealth                                    | [`docs/security/STEALTH_GUIDE.md`](docs/security/STEALTH_GUIDE.md)                                              |
+| Reasoning replay                           | [`docs/routing/REASONING_REPLAY.md`](docs/routing/REASONING_REPLAY.md)                                          |
+| Agent protocols (A2A / ACP / Cloud)        | [`docs/frameworks/AGENT_PROTOCOLS_GUIDE.md`](docs/frameworks/AGENT_PROTOCOLS_GUIDE.md)                          |
+| MCP server                                 | [`docs/frameworks/MCP-SERVER.md`](docs/frameworks/MCP-SERVER.md)                                                |
+| A2A server                                 | [`docs/frameworks/A2A-SERVER.md`](docs/frameworks/A2A-SERVER.md)                                                |
+| API reference                              | [`docs/reference/API_REFERENCE.md`](docs/reference/API_REFERENCE.md) + [`docs/openapi.yaml`](docs/openapi.yaml) |
+| Provider catalog (auto-generated)          | [`docs/reference/PROVIDER_REFERENCE.md`](docs/reference/PROVIDER_REFERENCE.md)                                  |
+| Tunnels                                    | [`docs/ops/TUNNELS_GUIDE.md`](docs/ops/TUNNELS_GUIDE.md)                                                        |
+| Electron desktop                           | [`docs/guides/ELECTRON_GUIDE.md`](docs/guides/ELECTRON_GUIDE.md)                                                |
+| Release flow                               | [`docs/ops/RELEASE_CHECKLIST.md`](docs/ops/RELEASE_CHECKLIST.md)                                                |
+| Quality gates (35 gates, allowlist policy) | [`docs/architecture/QUALITY_GATES.md`](docs/architecture/QUALITY_GATES.md)                                      |
+| Cluster opt-in profiles (memory, bifrost)  | [`docs/architecture/cluster-decisions.md`](docs/architecture/cluster-decisions.md)                              |
+
+---
+
+## Fork / Upstream Workflow
+
+This repository is a fork of `diegosouzapw/OmniRoute`. Keep fork-only operational
+changes (for example GHCR image publishing, personal deployment workflows, or local
+automation) out of upstream contribution PRs.
+
+When preparing a PR for upstream, always start the work branch from the upstream
+**default branch** — the active `release/vX.Y.Z` line (today `release/v3.8.49`).
+Never branch from `main`: `main` only receives release squash-merges, so a branch
+cut there is weeks behind and produces conflict-heavy PRs
+(see `CONTRIBUTING.md` and `docs/ops/BRANCHING_MODEL.md`):
 
 ```bash
 git fetch upstream
-git switch -c <branch-name> upstream/<default-branch>
+# the default branch is the active release line, e.g. release/v3.8.49
+git switch -c <branch-name> upstream/release/vX.Y.Z
 ```
 
-Target that same release branch in the pull request. Stage only the intended files, run the
-focused checks, and use a Conventional Commit message (for example, `docs: slim AGENTS.md`).
+Only cherry-pick or reapply the changes intended for the upstream PR.
 
-## Reference documentation
+---
 
-Use the source of truth for the area you are changing:
+## Review Focus
 
-| Area                                   | Reference                                                                                                                                                                                                                                              |
-| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Repository navigation and architecture | [`docs/architecture/REPOSITORY_MAP.md`](docs/architecture/REPOSITORY_MAP.md), [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md)                                                                                                 |
-| API and providers                      | [`docs/reference/API_REFERENCE.md`](docs/reference/API_REFERENCE.md), [`docs/reference/PROVIDER_REFERENCE.md`](docs/reference/PROVIDER_REFERENCE.md), [`docs/openapi.yaml`](docs/openapi.yaml)                                                         |
-| Routing, resilience, and reasoning     | [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md), [`docs/architecture/RESILIENCE_GUIDE.md`](docs/architecture/RESILIENCE_GUIDE.md), [`docs/routing/REASONING_REPLAY.md`](docs/routing/REASONING_REPLAY.md)                                   |
-| Security                               | [`docs/security/GUARDRAILS.md`](docs/security/GUARDRAILS.md), [`docs/security/COMPLIANCE.md`](docs/security/COMPLIANCE.md), [`docs/security/STEALTH_GUIDE.md`](docs/security/STEALTH_GUIDE.md)                                                         |
-| Platform features                      | [`docs/frameworks/MCP-SERVER.md`](docs/frameworks/MCP-SERVER.md), [`docs/frameworks/A2A-SERVER.md`](docs/frameworks/A2A-SERVER.md), [`docs/frameworks/SKILLS.md`](docs/frameworks/SKILLS.md), [`docs/frameworks/MEMORY.md`](docs/frameworks/MEMORY.md) |
-| Releases and quality                   | [`docs/ops/RELEASE_CHECKLIST.md`](docs/ops/RELEASE_CHECKLIST.md), [`docs/architecture/QUALITY_GATES.md`](docs/architecture/QUALITY_GATES.md)                                                                                                           |
+- **DB ops** go through `src/lib/db/` modules, never raw SQL in routes
+- **Provider requests** flow through `open-sse/handlers/`
+- **MCP/A2A pages** are tabs inside `/dashboard/endpoint`, not standalone routes
+- **No memory leaks** in SSE streams (abort signals, cleanup)
+- **Rate limit headers** must be parsed correctly
+- All API inputs validated with **Zod schemas**
+- **Provider constants** validated at module load via Zod (`src/shared/validation/providerSchema.ts`)
+- **Pricing data** syncs from LiteLLM via `src/lib/pricingSync.ts`
+- **Memory/Skills** are cross-cutting: affect MCP tools, request pipeline, and A2A skills
+- **⛔ NEVER close a contributor's PR** after using their code — always merge via GitHub so they get credit. See `.agents/workflows/review-prs.md` for full policy.

AMIT

@@ -0,0 +1 @@
+

CHANGELOG.md

@@ -8,18 +8,6 @@
 
 ---
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1440,6 +1428,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

CLAUDE.md

@@ -45,7 +45,7 @@ For full test matrix, see `CONTRIBUTING.md` → "Running Tests". For deep archit
 | 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 (95 files, 110 migrations)                                                                                                        |
 | Domain/Policy | `src/domain/`           | Policy engine, cost rules, fallback logic                                                                                                               |
 | MCP Server    | `open-sse/mcp-server/`  | 104 tools (42 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                                                                                                                             |
@@ -72,7 +72,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`): 18 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, 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 12-factor Auto-Combo scoring + the full strategy table and `docs/architecture/RESILIENCE_GUIDE.md` for the 3 resilience layers.
 
 ---
 
@@ -332,7 +332,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 (12-factor scoring, 18 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`                             |
@@ -461,18 +461,10 @@ own dedicated branch, and you MUST confirm the base branch with the operator bef
    git fetch origin "$BASE_BRANCH"
    git worktree add ".claude/worktrees/${TASK##*/}" -b "$TASK" "origin/$BASE_BRANCH"
    cd ".claude/worktrees/${TASK##*/}"
-   # Reuse the main checkout's node_modules to skip a per-worktree npm install.
-   # HARD LINKS (`cp -al`), never a symlink: ~5s for the whole tree and near-zero extra
-   # disk (the inodes are shared), and unlike a symlink it does not break the dev server.
-   cp -al "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
+   # symlink node_modules from the main checkout to skip a per-worktree npm install:
+   ln -s "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
    ```
 
-   **Never `ln -s` node_modules.** Turbopack rejects a symlink that resolves outside the
-   project root, so `npm run dev` dies with a FATAL panic (`Symlink [project]/node_modules
-   is invalid, it points out of the filesystem root`) while typecheck, lint and the test
-   runners all keep passing — the error names "filesystem root", not the worktree, so it
-   reads like a Next/build bug and costs real time to trace (incident 2026-07-31, #9043).
-
    In Claude Code prefer the native `EnterWorktree` tool (it already creates worktrees under
    `.claude/worktrees/`): create the worktree with the command above, then call `EnterWorktree`
    with its `path`.

CONTRIBUTING.md

@@ -2,11 +2,6 @@
 
 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,
-UI/UX, i18n, CLI, database, and build/deploy changes to their contracts, focused tests, CI
-coverage, and reconciliation steps.
-
 ---
 
 ## Development Setup
@@ -203,11 +198,10 @@ 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
-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):
+Before opening a PR, 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):
 
 - Run the test files that cover your change: `node --import tsx/esm --test tests/unit/<file>.test.ts`
 - Run `npm run lint`
@@ -277,7 +271,7 @@ src/                        # TypeScript (.ts / .tsx)
 │   ├── a2a/                # Agent-to-Agent v0.3 protocol server
 │   ├── acp/                # Agent Communication Protocol registry
 │   ├── compliance/         # Compliance policy engine
-│   ├── db/                 # SQLite domain modules + 130 migrations
+│   ├── db/                 # SQLite database layer (21 modules + 16 migrations)
 │   ├── memory/             # Persistent conversational memory
 │   ├── oauth/              # OAuth providers, services, and utilities
 │   ├── skills/             # Extensible skill framework
@@ -287,7 +281,7 @@ src/                        # TypeScript (.ts / .tsx)
 ├── mitm/                   # MITM proxy (cert, DNS, target routing)
 ├── shared/
 │   ├── components/         # React components (.tsx)
-│   ├── constants/          # Provider definitions (290), MCP scopes, 19 routing strategies
+│   ├── constants/          # Provider definitions (177), MCP scopes, 14 routing strategies
 │   ├── utils/              # Circuit breaker, sanitizer, auth helpers
 │   └── validation/         # Zod v4 schemas
 └── sse/                    # SSE proxy pipeline
@@ -295,7 +289,7 @@ src/                        # TypeScript (.ts / .tsx)
 open-sse/                   # @omniroute/open-sse workspace
 ├── executors/              # 14 provider-specific request executors
 ├── handlers/               # 11 request handlers (chat, responses, embeddings, images, etc.)
-├── mcp-server/             # MCP server (104 tools, 3 transports, 31 scopes)
+├── mcp-server/             # MCP server (25 tools, 3 transports, 10 scopes)
 ├── services/               # 36+ services (combo, autoCombo, rateLimitManager, etc.)
 ├── translator/             # Format translators (OpenAI ↔ Claude ↔ Gemini ↔ Responses ↔ Ollama)
 ├── transformer/            # Responses API transformer

README.md

@@ -67,46 +67,32 @@
 
 <table>
   <tr>
-    <td align="right"><b>🚀 Start</b></td>
-    <td align="center"><a href="#-quick-start">🚀 Quick Start</a></td>
-    <td align="center"><a href="#-more-install-methods--docker-source-pnpm-arch">📦 Install</a></td>
-    <td align="center"><a href="#-works-the-second-you-install-it--no-keys-no-config">🆓 Zero-config</a></td>
+    <td align="center"><a href="#-quick-start"><b>🚀 Quick Start</b></a></td>
+    <td align="center"><a href="#-combos--the-flagship"><b>🎯 Combos</b></a></td>
+    <td align="center"><a href="#-290-ai-providers--90-free"><b>🌐 Providers</b></a></td>
   </tr>
   <tr>
-    <td align="right"><b>💡 Learn</b></td>
+    <td align="center"><a href="#-full-cli--a2a--mcp"><b>🔌 CLI &amp; MCP</b></a></td>
+    <td align="center"><a href="#%EF%B8%8F-save-1595-tokens--automatically"><b>🗜️ Compression</b></a></td>
+    <td align="center"><a href="https://omniroute.online"><b>🌍 Website</b></a></td>
+  </tr>
+</table>
+
+<table>
+  <tr>
     <td align="center"><a href="#-the-promise">💥 The Promise</a></td>
-    <td align="center"><a href="#-why-omniroute">🤔 Why OmniRoute</a></td>
+    <td align="center"><a href="#-why-omniroute">🤔 Why</a></td>
     <td align="center"><a href="#-what-sets-omniroute-apart">🏆 What Sets Apart</a></td>
   </tr>
   <tr>
-    <td align="right"><b>⚙️ Features</b></td>
-    <td align="center"><a href="#-combos--the-flagship">🎯 Combos</a></td>
-    <td align="center"><a href="#-290-ai-providers--90-free">🌐 Providers</a></td>
-    <td align="center"><a href="#-full-cli--a2a--mcp">🔌 CLI &amp; MCP</a></td>
-  </tr>
-  <tr>
-    <td align="right"></td>
-    <td align="center"><a href="#%EF%B8%8F-save-1595-tokens--automatically">🗜️ Compression</a></td>
+    <td align="center"><a href="#-compatible-clis--coding-agents">🤖 Compatible CLIs</a></td>
     <td align="center"><a href="#%EF%B8%8F-where-omniroute-runs--anywhere">🖥️ Where It Runs</a></td>
     <td align="center"><a href="#-private--local-first">🔒 Private</a></td>
   </tr>
   <tr>
-    <td align="right"><b>👀 See it</b></td>
     <td align="center"><a href="#-omniroute-in-action">🎬 In Action</a></td>
-    <td align="center"><a href="#-whats-new">✨ What's New</a></td>
-    <td align="center"><a href="#-compatible-clis--coding-agents">🤖 Compatible CLIs</a></td>
-  </tr>
-  <tr>
-    <td align="right"><b>💚 Support</b></td>
-    <td align="center"><a href="#-support-omniroute">💚 Support / Donate</a></td>
-    <td align="center"><a href="#-community--help">💬 Community</a></td>
-    <td align="center"><a href="#-sponsors">💖 Sponsors</a></td>
-  </tr>
-  <tr>
-    <td align="right"><b>📦 Project</b></td>
-    <td align="center"><a href="#%EF%B8%8F-tech-stack">🛠️ Tech Stack</a></td>
-    <td align="center"><a href="#-documentation">📖 Docs</a></td>
-    <td align="center"><a href="#-500-contributors">👥 Contributors</a></td>
+    <td align="center"><a href="#-dashboard-screenshots">📸 Screenshots</a></td>
+    <td align="center"><a href="#-support--community">📧 Support</a></td>
   </tr>
 </table>
 
@@ -241,53 +227,12 @@ curl http://localhost:20128/v1/chat/completions \
       <b>What Kimi's support powers:</b> Kimi's API credits power OmniRoute's AI-validated release pipeline — the <i>merge validation powered by Kimi K3</i> stage that reviews every pull request before it ships — plus day-to-day feature development. First-class Kimi support ships on both rails: the direct <a href="https://platform.kimi.ai?aff=omniroute">Kimi API</a> (<code>kimi-k3</code>) and the <a href="https://www.kimi.com/code?aff=omniroute">Kimi Code coding plan</a> (OAuth and API key). OmniRoute is also the first Brazilian open-source project in Kimi's support program. <a href="https://platform.kimi.ai?aff=omniroute"><b>Get a Kimi API key →</b></a>
     </td>
   </tr>
-  <tr>
-    <td align="center" width="150">
-      <a href="https://cheaperinference.com/?utm_source=omniroute">
-        <img src="public/providers/cheaperinference.svg" width="64" alt="Cheaper Inference"/>
-      </a>
-      <br/><b>Cheaper Inference</b><br/><sub>cheaperinference.com</sub><br/><br/>
-      <img src="https://img.shields.io/badge/Open_Source_Friend-31f889?style=flat-square&labelColor=04170d" alt="Open Source Friend"/>
-    </td>
-    <td>
-      Thanks to <b>Cheaper Inference</b>, an OmniRoute Open Source Friend, for backing this project! Cheaper Inference is a cost-ranked gateway that resells 42 frontier models — Claude, GPT-5.x, Gemini, Kimi K3, GLM, DeepSeek, Grok and MiniMax — behind one OpenAI-compatible endpoint, routing each request to the cheapest eligible provider without ever charging above the model maker's list price.
-      <br/><br/>
-      <b>First-class support in OmniRoute:</b> Chat Completions, the native <code>/v1/responses</code> endpoint, vision, tool calling and 3 image models (<code>grok-imagine</code>, <code>nano-banana-pro</code>, <code>nano-banana-2</code>, reachable as <code>cheaperinference/&lt;model&gt;</code>). <a href="https://cheaperinference.com/?utm_source=omniroute"><b>Get an API key →</b></a>
-    </td>
-  </tr>
 </table>
 
 <sub>Links tagged <code>aff=omniroute</code> are partner links. They fund the project at no extra cost to you.</sub>
 
 <br/>
 
-<details open>
-<summary><sub><b>🎟️ Affiliates Promo</b> — free signup coupons from providers we don't sponsor (click to expand)</sub></summary>
-
-<sub><i>This section is for referral/coupon codes only. Sponsored partnerships live in <b>🤝 Supported by our Open Source Friends</b> above. OmniRoute has no sponsorship or partnership with the providers listed here — these are public coupons anyone can use.</i></sub>
-
-<table>
-  <tr>
-    <td align="center" width="120">
-      <a href="https://agentrouter.org/register?aff=70LM">
-        <img src="public/providers/agentrouter.png" width="32" alt="AgentRouter"/>
-      </a>
-      <br/><sub><b>AgentRouter</b></sub><br/><sub>agentrouter.org</sub>
-    </td>
-    <td>
-      <sub><b><a href="https://agentrouter.org/register?aff=70LM">AgentRouter</a></b> — affiliate signup · <b>$100 free credits</b> on signup (free server, expect higher latency — best for testing, not production). First-class support in OmniRoute since <b>v3.8.50</b>: Chat Completions, the Anthropic-compatible wire format and the OpenAI-compatible path. Available models include <code>claude-opus-4-8</code>, <code>claude-opus-5</code>, <code>gpt-5.6-sol</code> and more. <b><a href="https://agentrouter.org/register?aff=70LM">Grab your $100 →</a></b></sub>
-      <br/><br/>
-      <sub>⚠️ <i>Affiliate link — OmniRoute has no sponsorship or partnership with this provider.</i></sub>
-    </td>
-  </tr>
-</table>
-
-<sub>Know another provider with a generous free signup coupon that benefits OmniRoute users? Open an issue and we'll add it here.</sub>
-
-</details>
-
-<br/>
-
 <div align="center">
 
 ## 🎯 Combos — The Flagship
@@ -445,50 +390,13 @@ All **19** strategies — mix & match per combo step:
 
 <br/>
 
-## 💚 Support OmniRoute
+## ❤️ Support
 
-OmniRoute is MIT-licensed and maintained in the open. If it saves you time or money, here's how to keep it independent — pick whatever fits you. Sponsorship never affects routing priority; it buys visibility, not ranking.
+OmniRoute is free and open source, built and maintained in the open. If it saves you time or money, consider supporting development:
 
-<table>
-  <tr><td nowrap>⭐ <b>Star the repo</b></td><td>Free — genuinely helps visibility</td><td><a href="https://github.com/diegosouzapw/OmniRoute">Star OmniRoute</a></td></tr>
-  <tr><td nowrap>🐙 <b>GitHub Sponsors</b></td><td>One-off or monthly · zero platform fee</td><td><a href="https://github.com/sponsors/diegosouzapw">github.com/sponsors/diegosouzapw</a></td></tr>
-  <tr><td nowrap>🏢 <b>Open Collective</b></td><td><b>Companies</b> — issues an invoice/receipt · transparent books</td><td><a href="https://opencollective.com/omniroute">opencollective.com/omniroute</a></td></tr>
-  <tr><td nowrap>☕ <b>Ko-fi</b></td><td>Quick one-off tip, no signup for the donor</td><td><a href="https://ko-fi.com/diegosouzapw">ko-fi.com/diegosouzapw</a></td></tr>
-  <tr><td nowrap>🧋 <b>Buy Me a Coffee</b></td><td>Small, informal gesture</td><td><a href="https://www.buymeacoffee.com/diegosouzapw">buymeacoffee.com/diegosouzapw</a></td></tr>
-  <tr><td nowrap>🖐 <b>Liberapay</b></td><td>Recurring · non-profit · open source</td><td><a href="https://liberapay.com/diegosouzapw">liberapay.com/diegosouzapw</a></td></tr>
-  <tr><td nowrap>🇧🇷 <b>PIX</b> (Brazil)</td><td>Instant, no fees</td><td>key &amp; QR below</td></tr>
-  <tr><td nowrap>₿ <b>Crypto</b></td><td>BTC · ETH · USDT-TRC20 · USDC-Solana</td><td>addresses below</td></tr>
-</table>
-
-**🇧🇷 PIX** — instant, no fees (Brazil)
-
-<img src="docs/assets/pix-qr.png" width="140" align="right" alt="OmniRoute PIX QR code"/>
-
-Key (random): `5d865059-bc44-483a-962d-43ceb80126eb`
-
-Pix copia-e-cola:
-
-```
-00020101021126580014br.gov.bcb.pix01365d865059-bc44-483a-962d-43ceb80126eb5204000053039865802BR5922OMNIROUTE CONTRIBUICAO6006BRASIL62070503***630475DD
-```
-
-<br clear="right"/>
-
-<details>
-<summary><b>₿ Crypto</b> — BTC · ETH · USDT-TRC20 · USDC-Solana (click to expand)</summary>
-
-<table>
-  <tr><td nowrap><b>₿ BTC</b></td><td nowrap>Bitcoin (SegWit)</td><td><code>bc1qh00smz004sy85wyl28v77tenkt3ckl6eaep7fd</code></td></tr>
-  <tr><td nowrap><b>Ξ ETH</b></td><td nowrap>Ethereum (ERC20)</td><td><code>0x64Cf6B68A6Ff34288e89172950a2d00102337a84</code></td></tr>
-  <tr><td nowrap><b>₮ USDT</b></td><td nowrap>Tron (TRC20)</td><td><code>TKAF41JpuQrHbKTnsQa9svJE2T192Hvsc2</code></td></tr>
-  <tr><td nowrap><b>$ USDC</b></td><td nowrap>Solana</td><td><code>2emNNZzVVWQc3FQ2wk9M6qXUQmW8AKdjjL174fXR28Tu</code></td></tr>
-</table>
-
-<sub>⚠️ Send each coin only on the network shown — sending on the wrong network can lose the funds.</sub>
-
-</details>
-
-🐛 Found a bug or have feedback? Open a [Discussion](https://github.com/diegosouzapw/OmniRoute/discussions).
+- ⭐ **Star the repo** — it genuinely helps visibility
+- 💖 **[GitHub Sponsors](https://github.com/sponsors/diegosouzapw)** — fund ongoing maintenance and new providers
+- 🐛 **Report bugs and share feedback** in [Discussions](https://github.com/diegosouzapw/OmniRoute/discussions)
 
 <br/>
 
@@ -997,7 +905,7 @@ same process on one port, so there is no separate CLI-only package today.
 
 <div align="center">
 
-# 📧 Community & Help
+# 📧 Support & Community
 
 > Everything in one place — follow the maintainer, chat with the community, or open an issue.
 
@@ -1013,7 +921,7 @@ same process on one port, so there is no separate CLI-only package today.
 | 📦 **Source code**                         | [github.com/diegosouzapw/OmniRoute](https://github.com/diegosouzapw/OmniRoute)                                            |
 | 🐛 **Report a bug**                        | [open an issue](https://github.com/diegosouzapw/OmniRoute/issues) — attach `npm run system-info` output                   |
 | 🤝 **Contribute**                          | [CONTRIBUTING.md](CONTRIBUTING.md) · [Branching & Release Model](docs/ops/BRANCHING_MODEL.md) · pick a `good first issue` |
-| 💚 **Support the project**                 | [Ways to support ↑](#-support-omniroute) · [GitHub Sponsors](https://github.com/sponsors/diegosouzapw)                    |
+| ⭐ **Support the project**                 | [Star the repo](https://github.com/diegosouzapw/OmniRoute) · [GitHub Sponsors](https://github.com/sponsors/diegosouzapw)  |
 
 </div>
 

changelog.d/features/8980-deprecate-gemini-cli-provider.md

@@ -1 +0,0 @@
-- **feat(sse):** deprecated the legacy `gemini-cli` **upstream provider**. It was not routable (no registry entry, no executor), yet the scheduler kept refreshing its token against Google — maintaining a credential that could never serve a request. A stored connection now becomes terminal with a legible reason and a working migration path: re-add the account under `gemini`, which uses the same Google OAuth client. The `gemini-cli` **client identity** (requests arriving *from* the Gemini CLI, issue #7034) is untouched ([#8980](https://github.com/diegosouzapw/OmniRoute/pull/8980))

changelog.d/fixes/8985-release-tooling-hidden-work.md

@@ -1 +0,0 @@
-- **fix(ci):** the reconciliation helper no longer bounds its scan with `git describe --tags` — releases squash-merge, so that range re-listed 1361 commits instead of the cycle's real 22, which is how ~200 PRs once slipped through without a changelog bullet. The base is now resolved from the commit that opened the cycle, and a new `sweep:stale-fragments` gate removes `changelog.d/` fragments that a back-merge from `main` resurrected after they had already been folded in ([#8985](https://github.com/diegosouzapw/OmniRoute/pull/8985))

changelog.d/fixes/8988-mac-updater-manifest-and-runner-split.md

@@ -1 +0,0 @@
-- **fix(ci):** fixed a live auto-update defect where **Intel Macs downloaded the ARM dmg** — the two macOS jobs each emitted their own `latest-mac.yml` and `merge-multiple` let one silently overwrite the other by arrival order, leaving `electron-updater`'s arch fallback pointing at the wrong build. The manifests are now merged deliberately, un-suffixed entry first. Also: test jobs pinned to hosted runners (`setup-node` measured 20m06s self-hosted vs 16s hosted), the npm publish no longer discards a valid build artifact because an unrelated shard was flaky, the agent-skills gate now runs on pushes to `main` instead of PRs only, and the CI summary names every job that ended cancelled ([#8988](https://github.com/diegosouzapw/OmniRoute/pull/8988))

changelog.d/fixes/9022-stream-error-diagnostic.md

@@ -1 +0,0 @@
-- **fix(sse):** error-only streams now preserve sanitized executor diagnostics for operators without changing stream-readiness fallback classification ([#9022](https://github.com/diegosouzapw/OmniRoute/pull/9022)) — thanks @shixi-li

changelog.d/fixes/9053-claude-to-openai-max-passthrough.md

@@ -1 +0,0 @@
-- **fix(translator):** pass `output_config.effort="max"` through verbatim instead of unconditionally rewriting it to `xhigh`, so Anthropic → OpenAI-shape upstream calls reach `sanitizeReasoningEffortForProvider` with the carrier intact and providers that accept `max` literally (Ollama Cloud, opencode-go DeepSeek, Moonshot K3, native Claude) no longer 400 on `invalid reasoning value: 'xhigh'`. Regression guard: end-to-end test in `tests/unit/base-executor-sanitize-effort.test.ts`.

changelog.d/fixes/9250-cli-compatible-provider-apply.md

@@ -1 +0,0 @@
-- **fix(cli-tools):** keep Apply enabled for active OpenAI-compatible and Anthropic-compatible providers without static catalog entries. (thanks @lazysaltyfish)

changelog.d/fixes/9253-translator-format-detection-2949.md

@@ -1 +0,0 @@
-- **fix(translator):** harden Claude format detection for relative message endpoints and kebab-case version metadata. (thanks @ervareza)

changelog.d/maintenance/8966-remove-iflow-ttl.md

@@ -1 +0,0 @@
-- **chore(sse):** dropped the leftover `iflow` entry from the token-refresh TTL map — the provider was removed from the product but its 24-hour refresh lead outlived it, and the identifier had exactly two occurrences left repo-wide ([#8966](https://github.com/diegosouzapw/OmniRoute/pull/8966))

changelog.d/maintenance/8967-remove-fork-publish-workflows.md

@@ -1 +0,0 @@
-- **chore(ci):** removed two fork-owned image-publish workflows that had ridden into the repo as unrelated extra files in on-topic PRs — `build-fork.yml` (`ghcr.io/kang-heewon`, job-level guard, so it instantiated a skipped run on every push to main and every tag) and `build-rinseaid-image.yml` (`ghcr.io/rinseaid`, no guard, never fired). Neither could authenticate against this repository's token; a new policy guard now fails CI on any workflow targeting a foreign registry namespace ([#8967](https://github.com/diegosouzapw/OmniRoute/pull/8967))

changelog.d/maintenance/8977-promote-latest-test-epipe.md

@@ -1 +0,0 @@
-- **test(ci):** fixed the intermittent `spawnSync bash EPIPE` failure in the `:latest` promotion guard — the script exits on a pre-release version before reading stdin, so the harness's pipe-backed `input:` raced that exit; stdin is now file-backed, which makes the race structurally impossible ([#8977](https://github.com/diegosouzapw/OmniRoute/pull/8977))

config/quality/file-size-baseline.json

@@ -177,7 +177,7 @@
     "tests/unit/account-fallback-service.test.ts": 1563,
     "tests/unit/batch_api.test.ts": 1324,
     "tests/unit/cc-compatible-provider.test.ts": 1217,
-    "tests/unit/chatcore-translation-paths.test.ts": 2776,
+    "tests/unit/chatcore-translation-paths.test.ts": 2769,
     "tests/unit/chatgpt-web.test.ts": 3148,
     "tests/unit/combo-routing-engine.test.ts": 3449,
     "tests/unit/db-migration-runner.test.ts": 1499,
@@ -342,7 +342,7 @@
     "_rebaseline_pr1043_minimax_tts": "Upstream port decolua/9router#1043 (toanalien) own growth: audioSpeech.ts 965->1061 (+96). Adds MiniMax T2A v2 TTS dispatch (handleMinimaxSpeech + hexToBytes helper) — provider entry was already in audioRegistry (format: minimax-tts) but no handler existed, falling through to the OpenAI-compatible default that fails (T2A has custom shape + hex-encoded audio + base_resp envelope). New branch sits next to the other inline provider branches (xiaomi-mimo, coqui, tortoise, aws-polly) — extracting would just create indirection. Covered by tests/unit/minimax-tts-1043.test.ts (3 tests, GREEN: success, base_resp error, invalid-hex).",
     "_rebaseline_pr4592_exclude_exhausted_auto": "Reconcile #4592 already-merged growth: combo.ts 2991->3036 (+45, terminal-status quota-cutoff exclusion in buildAutoCandidates + opt-in gate). Fast-gate PR->release does not run check:file-size.",
     "open-sse/executors/antigravity.ts": 1528,
-    "open-sse/executors/base.ts": 1578,
+    "open-sse/executors/base.ts": 1562,
     "open-sse/executors/chatgpt-web.ts": 3241,
     "open-sse/executors/codex.ts": 1534,
     "open-sse/executors/cursor.ts": 1560,
@@ -365,7 +365,7 @@
     "open-sse/services/rateLimitManager.ts": 1060,
     "open-sse/translator/response/openai-responses.ts": 1174,
     "open-sse/utils/cursorAgentProtobuf.ts": 1505,
-    "open-sse/utils/stream.ts": 2889,
+    "open-sse/utils/stream.ts": 2887,
     "src/app/(dashboard)/dashboard/HomePageClient.tsx": 1381,
     "src/app/(dashboard)/dashboard/analytics/ComboHealthTab.tsx": 1031,
     "src/app/(dashboard)/dashboard/api-manager/ApiManagerPageClient.tsx": 3117,
@@ -385,8 +385,7 @@
     "src/app/(dashboard)/dashboard/settings/components/SystemStorageTab.tsx": 1573,
     "src/app/(dashboard)/dashboard/usage/components/BudgetTab.tsx": 1028,
     "src/app/(dashboard)/dashboard/usage/components/EvalsTab.tsx": 2148,
-    "_rebaseline_2026_07_30_8916_quota_compact_layout": "PR #8916 (apoapostolov, feat/improve-provider-quota-layouts) own growth: src/app/(dashboard)/dashboard/usage/components/ProviderLimits/index.tsx 1109->1153 (+44) adds Full/Compact layout toggle — LS_LAYOUT_MODE constant, LayoutMode type, layoutMode state, toggleLayoutMode callback, toggle button with icon. At existing filter/settings chokepoint. Not extractable without splitting state + toolbar away from data-fetching. Covered by tests/unit/quota-card-grid-compact-layout-8916.test.ts.",
-    "src/app/(dashboard)/dashboard/usage/components/ProviderLimits/index.tsx": 1153,
+    "src/app/(dashboard)/dashboard/usage/components/ProviderLimits/index.tsx": 1109,
     "src/app/api/providers/[id]/models/route.ts": 2250,
     "src/app/api/v1/models/catalog.ts": 1549,
     "src/lib/db/apiKeys.ts": 1529,
@@ -414,6 +413,5 @@
   "_rebaseline_2026_07_28_8860_tokenrefresh_projectid": "PR #8860 (fix/antigravity-projectid-centralized) own test growth: tests/unit/token-refresh-service.test.ts 1311->1378 (+67 = 4 cases covering projectId discovery on the tokenRefresh.ts path — the Dashboard/health-check refresh route, which #8842 did not reach since that fixed the executor path). Covered by the same file.",
   "_rebaseline_2026_07_28_8861_xiaomi_token_plan": "PR #8861 (feat/xiaomi-token-plan-protocol-selector) own growth: EditConnectionModal.tsx 1283->1316 (+33 = the per-connection API-protocol selector field) and open-sse/executors/base.ts 1540->1562 (+22 = alternate-format resolution at the existing buildUrl/headers chokepoint). Both are irreducible wiring at existing call sites.",
   "_rebaseline_2026_07_28_8863_firefly_detail_level": "PR #8863 (fix/adobe-firefly-gpt-detail-level-max) own growth: adobeFireflyClient.ts 2317->2322 (+5 = gpt-image detailLevel defaulting to maximal at the existing payload-build site). Covered by tests/unit/adobe-firefly.test.ts.",
-"_rebaseline_2026_07_29_8281_home_quickstart_prefetch": "Release v3.8.49 base-red fix (no PR — captain sweep): src/app/(dashboard)/dashboard/HomePageClient.tsx 1377->1381 (+4). #8292 added prefetch={false} to the sidebar but left /home's five quick-start Links prefetching, so first paint still fired 12 speculative RSC requests — caught by navigation.spec.ts only after the e2e helper bug (APP_ROUTE_PATTERN missing /home) was repaired in the same cycle. Growth is the five prefetch attributes; it was offset first by extracting the repeated className literals (INLINE_LINK x4, DOCS_LINK x1), which collapsed five wrapped <Link> blocks back to one line each — a naive fix measured 1391. Guard: tests/unit/sidebar-prefetch-policy-8281.test.ts.",
-  "_rebaseline_2026_08_02_v3850_agentrouter_responses": "Release v3.8.50 AgentRouter/Codex compatibility reconciliation. open-sse/executors/base.ts 1562->1578: #9190 wires AgentRouter's selected Claude/OpenAI/Responses protocol through the existing executor URL, auth, identity-header and fingerprint chokepoints; the reusable alternate resolver remains outside base.ts. open-sse/utils/stream.ts 2887->2889: #9213 evaluates Responses ID and usage normalization independently so response.completed always receives finite usage.total_tokens instead of short-circuiting after an ID rewrite. tests/unit/chatcore-translation-paths.test.ts 2769->2776: #9191 updates the existing Claude-Code bridge assertions for the dynamic AgentRouter wire image. PR #9224 offsets its own chatCore growth by extracting the AgentRouter protocol decisions into chatCore/agentRouterProtocol.ts, leaving chatCore below its frozen ceiling. Covered by agentrouter executor/chatCore protocol tests, chatcore translation-path tests, and responses-commentary-passthrough tests."
+  "_rebaseline_2026_07_29_8281_home_quickstart_prefetch": "Release v3.8.49 base-red fix (no PR — captain sweep): src/app/(dashboard)/dashboard/HomePageClient.tsx 1377->1381 (+4). #8292 added prefetch={false} to the sidebar but left /home's five quick-start Links prefetching, so first paint still fired 12 speculative RSC requests — caught by navigation.spec.ts only after the e2e helper bug (APP_ROUTE_PATTERN missing /home) was repaired in the same cycle. Growth is the five prefetch attributes; it was offset first by extracting the repeated className literals (INLINE_LINK x4, DOCS_LINK x1), which collapsed five wrapped <Link> blocks back to one line each — a naive fix measured 1391. Guard: tests/unit/sidebar-prefetch-policy-8281.test.ts."
 }

config/quality/install-upgrade-allowlist.json

@@ -1,6 +0,0 @@
-{
-  "_doc": "Tables that exist ONLY in databases upgraded from an older version — residue whose CREATE left the migration set in some past cycle but survives where it already existed. Harmless (nothing references them), but recorded here so check-install-upgrade.mjs can still fail on a NEW divergence. The opposite direction (a table a clean install creates but an upgrade does not) is NEVER allowlisted: it means every existing user is missing structure the code expects.",
-  "residualTables": {
-    "cache_metrics": "Measured 2026-07-30 on a real 3.8.48 install upgraded to 3.8.49 (VPS .16, 165 MB database, 114 → 117 tables). Present in upgraded databases, absent from clean installs. No code path referenced it during the upgrade (zero `no such table` in 150 log lines, both installs healthy). Left in place rather than dropped: a DROP migration on a table we cannot prove is unused everywhere is the riskier change. Revisit when the cache subsystem is next touched."
-  }
-}

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/dev/CONTRIBUTION_GOLDEN_PATH.md

@@ -1,229 +0,0 @@
----
-title: "Contribution Golden Path"
----
-
-# Contribution Golden Path
-
-Use this guide to choose the smallest reliable development loop for a pull request. It does not
-replace the area-specific architecture and security documents linked below; it connects each common
-change type to its contracts, focused checks, and CI coverage.
-
-## The path every change follows
-
-1. **Choose the base before editing.** Find the highest active `release/v*` branch and branch from
-   its tip. Target that branch, not `main`. If a release freeze is active, do not target the frozen
-   branch; use the next active cycle described in
-   [Branching & Release Model](../ops/BRANCHING_MODEL.md).
-2. **Name the contracts.** Identify every catalog, schema, generated artifact, public API, or user
-   interface that the change affects. The table below gives the minimum starting set.
-3. **Write or update focused tests.** Production changes in `src/`, `open-sse/`, `electron/`, or
-   `bin/` require an automated test in the same PR. Run the smallest test files that prove the
-   behavior, then the listed focused gates.
-4. **Let CI run the broad matrix.** The complete unit shards, Vitest, coverage ratchet, and
-   production build run on the PR. Run a broad suite locally only when a focused failure points to
-   wider impact or when the change spans several subsystems.
-5. **Reconcile before review.** Fetch the active base, inspect its new commits and your diff against
-   it, then rebase or merge the base according to the contributor workflow. Resolve generated-file
-   and catalog conflicts from their source, regenerate them, rerun the focused loop, and confirm the
-   PR still targets the active release branch.
-6. **Record evidence.** In the PR template, list the commands run, every test file added or changed,
-   migrations or feature flags, and any CI-only validation still pending.
-
-## Golden paths by change type
-
-Commands below are minimum focused checks, not permission to skip a test that directly covers the
-behavior you changed.
-
-### Provider
-
-**Contracts**
-
-- Provider definition in `src/shared/constants/providers/` and its composition in
-  `src/shared/constants/providers.ts`.
-- Models and capabilities in `open-sse/config/providerRegistry.ts` or its extracted registry files.
-- Executor/translator selection, OAuth or API-key configuration, dashboard assets, and generated
-  provider reference when applicable.
-- Public credentials must use `resolvePublicCred()`; error responses must use the shared sanitized
-  error helpers. See [Public Credentials](../security/PUBLIC_CREDS.md) and
-  [Error Sanitization](../security/ERROR_SANITIZATION.md).
-
-**Focused loop**
-
-```bash
-npm run check:provider-consistency
-npm run check:provider-assets
-node --import tsx/esm --test tests/unit/provider-translate-path-golden.test.ts
-node --import tsx/esm --test tests/unit/<provider-or-executor>.test.ts
-npm run gen:provider-reference   # when the catalog changes; commit the generated diff
-npm run lint
-```
-
-Also test every affected request family: chat, Responses, images, embeddings, audio, or video.
-Review generated catalog and golden diffs as contract changes; do not accept them blindly.
-
-### Routing
-
-**Contracts**
-
-- Public strategy values and UI metadata in `src/shared/constants/routingStrategies.ts`.
-- Dispatch and ordering under `open-sse/services/combo.ts` and `open-sse/services/combo/`.
-- Combo schemas, persistence, resilience state, model capabilities, and API/UI controls.
-- [Auto-Combo Engine](../routing/AUTO-COMBO.md) and resilience documentation when behavior changes.
-
-**Focused loop**
-
-```bash
-node --import tsx/esm --test tests/unit/combo-<behavior>.test.ts
-npm run test:combo:matrix        # strategy or dispatch changes
-npm run check:known-symbols      # strategy registration changes
-npm run lint
-```
-
-Use deterministic mocked-upstream tests locally. Live combo smokes require credentials and are
-manual, not CI substitutes.
-
-### UI / UX
-
-**Contracts**
-
-- Next.js route/page and shared component boundaries under `src/app/` and
-  `src/shared/components/`.
-- API response shapes, loading/empty/error states, keyboard and screen-reader behavior,
-  responsive layout, theming, and locale expansion.
-- English UI source strings in `src/i18n/messages/en.json`; do not hard-code new user-facing copy.
-
-**Focused loop**
-
-```bash
-node --import tsx --test tests/unit/dashboard/<feature>.test.ts
-npx vitest run --config vitest.config.ts tests/unit/ui/<component>.test.tsx
-npm run check:dashboard-typecheck
-npm run lint
-```
-
-Run the app for interaction or visual changes and check both narrow and wide viewports. CI runs the
-production build and broader suites; visual behavior still needs a focused component, Playwright,
-or documented manual check appropriate to the change.
-
-### i18n
-
-**Contracts**
-
-- `src/i18n/messages/en.json` is the UI source; `config/i18n.json` is the locale source.
-- CLI catalogs live separately under `bin/cli/locales/`.
-- Preserve ICU placeholders and tags exactly. Do not translate product/provider/model names,
-  protocol and header names, commands, code/JSON identifiers, URLs, environment variables, or
-  protected terms such as `OmniRoute`, `OAuth`, `MCP`, and `A2A`. The current source list is
-  `scripts/i18n/glossary/protected-terms.json`.
-
-**Focused loop**
-
-```bash
-npm run i18n:sync-ui:dry
-npm run i18n:check-ui-coverage
-npm run i18n:check-value-drift
-npm run i18n:check-glossary
-npm run check:cli-i18n          # when CLI strings/catalogs change
-npm run lint
-```
-
-This is guidance for the existing system, not an invitation to expand its tooling or key model.
-Keep i18n patches surgical while the replacement system is being designed. Do not run translation
-commands that call external services unless the task explicitly requires generated translations and
-you have reviewed the resulting diff.
-
-### CLI
-
-**Contracts**
-
-- Public commands and flags in `bin/cli/`, generated API commands, exit codes, stdout/stderr and
-  JSON output shapes, config/environment behavior, and packaged files.
-- CLI user-facing strings must use the CLI i18n layer and keep `en`/`pt-BR` catalogs aligned.
-- Preserve Node as the supported runtime and the published binary contract.
-
-**Focused loop**
-
-```bash
-node --import tsx/esm --test tests/unit/cli/<command>.test.ts
-npm run check:cli-i18n
-npm run build:cli             # generated/bundled CLI changes
-npm run check:pack-policy     # package-surface changes
-npm run lint
-```
-
-Use the exact command in a temporary data directory when behavior depends on parsing, files, or exit
-status. CI performs the broader package artifact and ecosystem checks.
-
-### Database
-
-**Contracts**
-
-- Domain modules under `src/lib/db/`; `src/lib/localDb.ts` remains a re-export layer only.
-- Numbered, idempotent SQL migrations under `src/lib/db/migrations/`, transaction safety, upgrade
-  behavior, indexes, and every caller affected by the schema.
-- Routes and handlers never issue raw SQL directly.
-
-**Focused loop**
-
-```bash
-npm run check:migration-numbering
-npm run check:db-rules
-node --import tsx/esm --test tests/unit/db/<domain>.test.ts
-node --import tsx/esm --test tests/unit/db/migration-<number>.test.ts
-npm run lint
-```
-
-Test both a fresh database and upgrade from the prior schema when adding a migration. Database tests
-must close handles and call `resetDbInstance()` during cleanup. Run `npm run test:bun:db` only when
-the best-effort Bun adapter path changes; Node remains authoritative.
-
-### Build / deploy
-
-**Contracts**
-
-- Root and workspace manifests/lockfile, `scripts/build/`, Next.js standalone assembly, `dist/`
-  package contents, Electron platform metadata, CI workflows, and deployment sentinels.
-- Supported Node ranges and the allow-listed Bun use in `CLAUDE.md` must remain intact.
-- Build artifacts stay untracked; dependency, license, workflow, and package policies apply.
-
-**Focused loop**
-
-```bash
-node --import tsx/esm --test tests/unit/build/<behavior>.test.ts
-npm run check:build-scope
-npm run check:lockfile         # dependency or lockfile changes
-npm run check:pack-policy      # published package surface changes
-npm run lint
-```
-
-Use `npm run build` locally only when the change affects compilation, standalone assembly, assets,
-or runtime bundling. Use `npm run build:release` only for release/deploy validation. CI's build is
-the final cross-platform signal; platform-specific Electron changes need the matching focused build
-or smoke evidence.
-
-## Local loop versus CI
-
-| Run locally for each patch                                                    | CI supplies the broad signal                                      |
-| ----------------------------------------------------------------------------- | ----------------------------------------------------------------- |
-| Direct behavior tests and category gates above                                | Sharded full unit suite and serial tests                          |
-| `npm run lint`                                                                | Vitest suites and coverage/quality ratchets                       |
-| Typecheck or build only when the affected contract calls for it               | Production build, security, docs, dependency, and PR-policy gates |
-| Manual interaction/live checks only when automation cannot prove the behavior | Cross-job integration and platform checks configured by workflow  |
-
-A green focused loop is evidence about the changed contract, not proof that unrelated CI checks
-will pass. Conversely, do not make every local edit wait for the full repository matrix.
-
-## Reconciliation checklist
-
-Before requesting review:
-
-- Confirm the PR base is still the highest active `release/v*` branch.
-- Fetch that base and review commits that landed since you branched.
-- Review `git diff <active-base>...HEAD` for accidental or generated churn.
-- Resolve catalog and generated-document conflicts by updating the source and regenerating output.
-- Rerun every focused test/gate listed in the PR description after reconciliation.
-- Never weaken assertions or drop required tests merely to match a moved base.
-
-For release-freeze and retargeting rules, use
-[Branching & Release Model](../ops/BRANCHING_MODEL.md). For the complete CI inventory, use
-[Quality Gates Reference](../architecture/QUALITY_GATES.md).

docs/guides/ANTIGRAVITY-ONBOARDING.md

@@ -1,278 +0,0 @@
----
-title: "Antigravity (Google One AI) — Onboarding with OmniRoute"
-version: 3.8.50
-lastUpdated: 2026-07-31
----
-
-# OmniRoute Antigravity (Google One AI) Onboarding Guide
-
-> **What you get**: Access to Gemini 3.1 Pro, Gemini 3.5 Flash, Claude Sonnet 4.6, and other models through your Google One AI Pro subscription — routed through OmniRoute as a unified gateway.
-
-**Official references**:
-
-- [Google Antigravity](https://antigravity.google) — product homepage
-- [Antigravity Plans & Pricing](https://antigravity.google/pricing) — subscription tiers
-- [Antigravity Docs: Plans](https://antigravity.google/docs/plans) — baseline quota details
-- [Google One AI Plans](https://one.google.com/about/google-ai-plans/) — Google One subscription comparison
-- [Antigravity CLI Blog](https://antigravity.google/blog/introducing-google-antigravity-cli) — CLI announcement
-
----
-
-## 1. Antigravity vs Antigravity CLI (agy)
-
-Both providers share the **same Google backend** — identical OAuth client, token refresh, endpoints, and Google accounts. The difference is what models you see.
-
-> See [Antigravity CLI announcement](https://antigravity.google/blog/introducing-google-antigravity-cli) for Google's official comparison.
-
-| Aspect               | `antigravity` (IDE)                       | `agy` (CLI)                                         |
-| -------------------- | ----------------------------------------- | --------------------------------------------------- |
-| **Google product**   | Antigravity 2.0 / Antigravity IDE         | Antigravity CLI                                     |
-| **Backend**          | Same Google Cloud Code API                | Same Google Cloud Code API                          |
-| **OAuth / Token**    | Same client, same refresh                 | Same client, same refresh                           |
-| **Model catalog**    | Static curated list (OmniRoute hardcoded) | Live-probed from Google via `:fetchAvailableModels` |
-| **Claude models**    | Sonnet 4.6, Opus 4.6 (4 variants each)    | Sonnet 4.6, Opus 4.6 (4 variants each)              |
-| **Gemini naming**    | Clean labels (Low/Medium/High)            | Upstream IDs (extra-low/low/agent)                  |
-| **Extra models**     | `gpt-oss-120b-medium`                     | May include additional models from Google           |
-| **Default use case** | IDE integration (VS Code, JetBrains)      | CLI / API access                                    |
-| **Quota**            | Shared with agy (same Google account)     | Shared with antigravity (same Google account)       |
-
-**Available models (verified via experiment, 2026-07-29)**:
-
-- Gemini: 3.6 Flash, 3.5 Flash, 3.1 Pro, 3 Flash, 2.5 Flash (various thinking levels)
-- Claude: Sonnet 4.6, Opus 4.6 (each with default/low/medium/high variants)
-- Other: GPT-OSS 120B Medium
-- **Claude Sonnet 5 is NOT available** — only 4.6 variants are supported
-
-**Why the model catalog differs**: Google's CLI is "optimized for speed and low overhead" and "co-optimized with Gemini models" (per Google's official blog). The Web/IDE product is "optimized for comprehensiveness." The CLI uses `:fetchAvailableModels` to dynamically discover models, while the IDE uses a static curated list.
-
-**In practice**: Use `agy/` prefix for Gemini models (e.g. `agy/gemini-3.5-flash-high`). Use `antigravity/` for the static curated list. Both hit the same Google backend, but expose different model naming. The quota is shared — using either provider counts against the same Google account's limits.
-
----
-
-## 2. Google One AI Pro: Quota System
-
-> See [Antigravity Docs: Plans](https://antigravity.google/docs/plans) for official quota details and [Changes to Antigravity Plans](https://antigravity.google/blog/changes-to-antigravity-plans) for the latest pricing updates.
-
-Google Antigravity uses a **dual-layer quota** based on "Work Done" (computational weight), not message count.
-
-### The Two Layers
-
-| Layer              | What it is                    | Refresh cycle                                                      |
-| ------------------ | ----------------------------- | ------------------------------------------------------------------ |
-| **5-hour sprint**  | Immediate pool of "work done" | Resets 5 hours after first request in a session                    |
-| **7-day baseline** | Weekly hard cap               | Overrides 5-hour refresh if hit; locks out until next 7-day period |
-
-**How "Work Done" is calculated**: Agent-heavy tasks (e.g. "Refactor this entire repository") drain quota much faster than simple tasks (e.g. "Fix this function"). There is no real-time dashboard showing consumption.
-
-### Plan Tiers
-
-| Plan         | Price      | Quota                              | Weekly limit                  |
-| ------------ | ---------- | ---------------------------------- | ----------------------------- |
-| Free         | $0         | Meaningful quota, refreshed weekly | Yes                           |
-| AI Pro       | $19.99/mo  | High quota, 5-hour rolling refresh | Yes (overrides 5-hour if hit) |
-| AI Ultra 5x  | $99.99/mo  | 5x Pro quota                       | No weekly limit               |
-| AI Ultra 20x | $199.99/mo | 20x Pro quota                      | No weekly limit               |
-
-### Gemini vs Non-Gemini Models
-
-- **Gemini models** (Flash + Pro): Share a single rate limit, drawn down by API pricing. If Flash is 8x cheaper than Pro, you get 8x more Flash tokens.
-- **Non-Gemini models** (Claude, GPT-OSS): Have **separate** rate limits. May remain available even when Gemini is locked out.
-
-### AI Credits (Overage)
-
-> See [Google One AI credits](https://support.google.com/googleone/answer/14534406) for how credits work.
-
-When baseline quota is exhausted:
-
-- **Never**: Wait for quota to refresh; shows "Baseline model quota reached"
-- **Always**: Auto-use AI credits; switches back to baseline when it refreshes
-
-Credits are purchased separately and deducted at standard API pricing.
-
-### Key Details
-
-- Quota is **account-level shared** — the same Google account in Antigravity IDE, CLI, and OmniRoute shares one quota pool
-- Each Google account has its own independent quota — multiple accounts = multiple quota pools
-- AI Pro users have reported **7-day lockouts** instead of 5-hour resets when weekly baseline is hit (Google confirmed this is by design for high demand)
-
-**When your account is exhausted**: OmniRoute automatically retries with the next available account in the combo route. No manual intervention needed.
-
----
-
-## 3. How to Get a projectId
-
-Every antigravity/agy connection needs a Google Cloud Code `projectId`. Without it, the `/v1internal:models` endpoint returns 404.
-
-### Method A: Automatic (Recommended)
-
-OmniRoute handles this automatically. When you add a new Google account via Dashboard OAuth:
-
-1. OmniRoute refreshes the token
-2. Calls `loadCodeAssist` to discover the projectId
-3. If no project exists, calls `onboardUser` to create one
-4. Retries `loadCodeAssist` to get the newly created projectId
-5. Saves it to the database
-
-**This works for most accounts** — no manual steps needed.
-
-### Method B: Manual via agy CLI
-
-If automatic discovery fails (see Section 5 for when this happens):
-
-```bash
-# Install agy CLI (if not already)
-npm install -g @anthropic-ai/agy
-
-# Login with your Google account
-agy login
-
-# Select the account that needs onboarding
-# This triggers Cloud Code registration and assigns a projectId
-```
-
-After `agy login` succeeds, refresh the token in OmniRoute Dashboard. The projectId will be discovered automatically.
-
-### How to verify
-
-Check the database:
-
-```bash
-# Inside OmniRoute container
-node -e "const db=require('better-sqlite3')('/app/data/storage.sqlite'); \
-  console.log(JSON.stringify(db.prepare(\
-    'SELECT email,project_id FROM provider_connections WHERE provider=\"agy\"'\
-  ).all(), null, 2))"
-```
-
-Or check the logs:
-
-```
-podman logs omniroute 2>&1 | grep "projectId discovered"
-```
-
----
-
-## 4. OAuth Redirect URI
-
-### The Problem
-
-Google OAuth requires a valid redirect URI. OmniRoute's default uses `http://127.0.0.1:20128/callback` (loopback). This works for local builds but **fails for remote deployments** (e.g., a server accessed via LAN IP).
-
-Google rejects redirect URIs that:
-
-- Use IP addresses (must be a domain ending in `.com`, `.org`, etc.)
-- Don't match the registered redirect URIs in the OAuth client config
-
-### The Solution
-
-**Option A: Use the built-in OAuth flow (default)**
-
-- Works when you access OmniRoute from `localhost` or `127.0.0.1`
-- No configuration needed
-
-**Option B: Custom OAuth credentials**
-
-- Set `ANTIGRAVITY_OAUTH_CLIENT_TYPE=web` in your environment
-- Provide your own Google OAuth credentials:
-  ```
-  GOOGLE_OAUTH_CLIENT_ID=your-client-id
-  GOOGLE_OAUTH_CLIENT_SECRET=your-client-secret
-  ```
-- Register `https://your-domain.com/callback` as an authorized redirect URI in Google Cloud Console
-
-**Option C: Use agy CLI for initial login**
-
-- Run `agy login` on the machine that will access OmniRoute
-- The OAuth flow completes locally, tokens are stored
-- Import the connection into OmniRoute via Dashboard
-
-### Limitations
-
-- Custom OAuth credentials require a domain name (Google does not accept IP addresses as redirect URIs)
-- If you don't have a domain, use Option A or C instead
-
----
-
-## 5. Troubleshooting: When Automatic Setup Fails
-
-OmniRoute handles projectId discovery and onboarding automatically for most accounts. When it fails, the root cause is usually one of these:
-
-### Account region is blocked
-
-**Symptom**: `agy login` returns "Eligibility check failed: Your current account is not eligible for Antigravity, because it is not currently available in your location."
-
-**Root cause**: Google accounts have a backend "Country Association" field set at registration time. The agy CLI and Cloud Code API check this field strictly — unlike web Gemini which only checks your current IP.
-
-> To check or change your account's associated region, visit [Google Country Association Form](https://policies.google.com/country-association-form).
-
-**Why web Gemini works but agy doesn't**:
-
-- Web Gemini / Google One: checks current IP only (proxy passes)
-- agy CLI / Cloud Code API: reads backend Country Association field (proxy doesn't help)
-
-**Fix**:
-
-1. Visit [Google Country Association Form](https://policies.google.com/country-association-form) while on a US IP
-2. Submit region change request (select "I live in a different country")
-3. Wait 1-24 hours for Google to process + email notification
-4. Then `agy login` should succeed
-
-### Account has no Cloud Code project
-
-**Symptom**: Logs show `loadCodeAssist returned no project id` and `onboardUser failed (400)`.
-
-**Root cause**: The account has never been registered with Google Cloud Code, and the automatic onboarding failed.
-
-**Fix**: Run `agy login` manually to trigger Cloud Code registration, then refresh the token in OmniRoute Dashboard.
-
-### Token expired or revoked
-
-**Symptom**: 401 errors in logs, or "Token has expired" messages.
-
-**Fix**: Refresh the token in Dashboard → Providers → agy → Click refresh icon. If the refresh token itself is revoked, you'll need to re-authenticate via OAuth.
-
----
-
-## Decision Flowchart
-
-```
-Account not working?
-│
-├─ Does it have a projectId in the database?
-│  ├─ YES → Problem is elsewhere (token expired, rate limit, etc.)
-│  └─ NO ↓
-│
-├─ Is the account's Country Association set to a restricted region?
-│  ├─ YES → Change region at Google Country Association Form
-│  │         (https://policies.google.com/country-association-form)
-│  │         Wait 1-24 hours, then retry
-│  └─ NO ↓
-│
-├─ Does the account have Google One AI Pro subscription?
-│  ├─ NO → Subscribe first at one.google.com
-│  └─ YES ↓
-│
-├─ Try automatic discovery (refresh token in Dashboard)
-│  ├─ Works → Done
-│  └─ Still fails ↓
-│
-└─ Manual: Run `agy login` on the machine
-   ├─ Works → Refresh token in Dashboard, projectId discovered
-   └─ Fails → Check error message, likely region or subscription issue
-```
-
----
-
-## Quick Reference
-
-| Task                  | Command / URL                                                                           |
-| --------------------- | --------------------------------------------------------------------------------------- |
-| Change account region | [Google Country Association Form](https://policies.google.com/country-association-form) |
-| agy CLI login         | `agy login`                                                                             |
-| Check projectId in DB | `SELECT email,project_id FROM provider_connections WHERE provider='agy'`                |
-| Check logs            | `podman logs omniroute 2>&1 \| grep projectId`                                          |
-| Refresh token         | Dashboard → Providers → agy → Click refresh icon                                        |
-
----
-
-_Last updated: 2026-07-31. Based on OmniRoute v3.8.50._

docs/i18n/ar/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/az/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/bg/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/bn/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/cs/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/da/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/de/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/es/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/fa/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/fi/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/fr/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/gu/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/he/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/hi/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/hu/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/id/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/in/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/it/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ja/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ko/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/mr/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ms/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/nl/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/no/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/phi/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/pl/CHANGELOG.md

@@ -8,18 +8,6 @@
 
 ---
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1154,7 +1142,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1440,6 +1427,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/pl/CLAUDE.md

@@ -461,18 +461,10 @@ own dedicated branch, and you MUST confirm the base branch with the operator bef
    git fetch origin "$BASE_BRANCH"
    git worktree add ".claude/worktrees/${TASK##*/}" -b "$TASK" "origin/$BASE_BRANCH"
    cd ".claude/worktrees/${TASK##*/}"
-   # Reuse the main checkout's node_modules to skip a per-worktree npm install.
-   # HARD LINKS (`cp -al`), never a symlink: ~5s for the whole tree and near-zero extra
-   # disk (the inodes are shared), and unlike a symlink it does not break the dev server.
-   cp -al "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
+   # symlink node_modules from the main checkout to skip a per-worktree npm install:
+   ln -s "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
    ```
 
-   **Never `ln -s` node_modules.** Turbopack rejects a symlink that resolves outside the
-   project root, so `npm run dev` dies with a FATAL panic (`Symlink [project]/node_modules
-   is invalid, it points out of the filesystem root`) while typecheck, lint and the test
-   runners all keep passing — the error names "filesystem root", not the worktree, so it
-   reads like a Next/build bug and costs real time to trace (incident 2026-07-31, #9043).
-
    In Claude Code prefer the native `EnterWorktree` tool (it already creates worktrees under
    `.claude/worktrees/`): create the worktree with the command above, then call `EnterWorktree`
    with its `path`.

docs/i18n/pt-BR/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/pt/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ro/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ru/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/sk/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/sv/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/sw/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ta/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/te/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/th/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/tr/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/uk-UA/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/ur/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/vi/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/zh-CN/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/i18n/zh-CN/CLAUDE.md

@@ -415,18 +415,10 @@ git push -u origin feat/your-feature
    git fetch origin "$BASE_BRANCH"
    git worktree add ".claude/worktrees/${TASK##*/}" -b "$TASK" "origin/$BASE_BRANCH"
    cd ".claude/worktrees/${TASK##*/}"
-   # 复用主工作区的 node_modules，省去每个 worktree 的 npm install。
-   # 必须用硬链接（`cp -al`），绝不能用符号链接：整棵树约 5 秒，几乎不占额外磁盘
-   # （inode 是共享的），而且与符号链接不同，它不会破坏开发服务器。
-   cp -al "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
+   # 从主工作区符号链接 node_modules，省去每个 worktree 的 npm install：
+   ln -s "$(git -C <main_checkout> rev-parse --show-toplevel)/node_modules" node_modules
    ```
 
-   **绝不要对 node_modules 使用 `ln -s`。** Turbopack 会拒绝解析到项目根目录之外的符号链接，
-   因此 `npm run dev` 会以 FATAL panic 崩溃（`Symlink [project]/node_modules is invalid, it
-   points out of the filesystem root`），而 typecheck、lint 和测试运行器却都照常通过 —— 错误信息
-   提到的是 "filesystem root" 而不是 worktree，看起来像 Next/构建的 bug，排查会浪费大量时间
-   （事故 2026-07-31，#9043）。
-
    在 Claude Code 中优先使用原生的 `EnterWorktree` 工具（它已经在 `.claude/worktrees/` 下创建 worktree）：先用上述命令创建 worktree，然后用其 `path` 调用 `EnterWorktree`。
 
 3. **工作、提交、推送、发起 PR — 全部在 worktree 内部完成。** 绝不在另一个会话可能共享的 worktree 内 `git checkout` 不同分支。

docs/i18n/zh-TW/CHANGELOG.md

@@ -6,18 +6,6 @@
 
 ## [3.8.31] — 2026-06-20
 
-## [3.8.50] — TBD
-
-_Living section — cycle opened at the v3.8.49 freeze (parallel-cycle model). Bullets are aggregated from `changelog.d/` fragments at each `/generate-release` phase._
-
-### ✨ New Features
-
-### 🐛 Bug Fixes
-
-### 📝 Maintenance
-
----
-
 ## [3.8.49] — 2026-07-28
 
 _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62333b0 → tip). Bullets carry the merged PR and its author; direct pushes listed separately. Finalized at the v3.8.49 release._
@@ -1152,7 +1140,6 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - **fix(api):** stop JSON.stringify-ing messages before estimateTokens (restores #8368 image estimate) [recovered from #8599] ([#8740](https://github.com/diegosouzapw/OmniRoute/pull/8740))
 - **fix(quality):** let --update remove baseline entries that already fit the cap ([#8741](https://github.com/diegosouzapw/OmniRoute/pull/8741)) — thanks @MumuTW
 - **fix:** escape angle brackets in i18n messages to prevent next-intl INVALID_MESSAGE errors ([#8747](https://github.com/diegosouzapw/OmniRoute/pull/8747)) — thanks @SteeleHu
-- **fix(dashboard):** the /home quick-start cards no longer prefetch — #8292 opted the sidebar out of automatic route prefetch but left the landing page's own five links untouched, so first paint still fired 12 speculative RSC requests. The e2e guard shipped in that same PR could not catch it: it hung in the auth helper and never reached its assertion until this release's CI.
 - **fix(dashboard):** Request Logs detail no longer crashes on a structured error object — #7920 introduced `formatErrorForDisplay` for exactly this, but the combo-503 / cooldown checks added by #8213 read the raw field and called `.toLowerCase()` on it. Both paths now share the helper.
 - **fix(dashboard):** the logs detail modal stops reopening on first close again — #6830 fixed it by reading the deep-link id once, and the #8354 page rewrite regressed it by reading the live `searchParams` on every render, flipping the prop mid-session.
 ### 📚 Docs
@@ -1438,6 +1425,10 @@ _Living section — regenerated 2026-07-19 from all 306 cycle commits (bump 2c62
 - chore(tests): fix all 70 failing `test:vitest:ui` tests across 30 files (was advisory/parked) — root causes were 15 node:test-authored `.tsx` files never collected by vitest, a missing `window.matchMedia` jsdom polyfill, stale assertions against a redesigned BuildTab wizard / CompressionHub Phase-2 UI, and one obsolete test for a retired Plans screen; suite is now 158/158 files, 870/870 tests green (promotion to blocking is a follow-up)
 
 
+
+
+
+
 ### 🙌 Contributors
 
 Thanks to everyone whose work landed in v3.8.49:

docs/openapi.yaml

@@ -1,7 +1,7 @@
 openapi: 3.1.0
 info:
   title: OmniRoute API
-  version: 3.8.50
+  version: 3.8.49
   description: |
     OmniRoute is a local-first AI API proxy router. It provides an OpenAI-compatible
     endpoint that routes requests to multiple AI providers with load balancing,

docs/reference/ENVIRONMENT.md

@@ -414,6 +414,7 @@ detection above).
 | `OMNIROUTE_HTTP_TIMEOUT_MS`    | `30000`    | `bin/cli/api.mjs`                       | Per-attempt HTTP timeout (ms) for CLI → server requests.                                                                           |
 | `OMNIROUTE_VERBOSE`            | `0`        | `bin/cli/api.mjs`                       | Set to `1` to print retry/backoff diagnostics to stderr during CLI commands.                                                       |
 | `OMNIROUTE_PLUGIN_PATH`        | _(unset)_  | `bin/cli/plugins.mjs`                   | Custom directory for CLI plugin discovery (`omniroute-cmd-*` packages). Defaults to `~/.omniroute/plugins/` when unset.            |
+| `OMNIROUTE_PLUGINS_ALLOW_EXEC` | `0`        | `src/lib/plugins/pluginWorker.ts`       | Set to `1` to allow plugins to request the `exec` permission (spawn child processes from the worker sandbox). Local operator only. |
 
 ---
 

docs/reference/PROVIDER_REFERENCE.md

@@ -1,14 +1,14 @@
 ---
 title: "Provider Reference"
-version: 3.8.50
-lastUpdated: 2026-07-30
+version: 3.8.49
+lastUpdated: 2026-07-28
 ---
 
 # Provider Reference
 
 > **Auto-generated** from `src/shared/constants/providers.ts` — do not edit by hand.
 > Regenerate with: `npm run gen:provider-reference`
-> **Last generated:** 2026-07-30
+> **Last generated:** 2026-07-28
 
 Total providers: **290**. See category breakdown below.
 

docs/routing/AUTO-COMBO.md

@@ -167,21 +167,21 @@ The Auto-Combo Engine dynamically selects the best provider/model for each reque
 
 > Source: [diagrams/auto-combo-12factor.mmd](../diagrams/auto-combo-12factor.mmd) (regenerate via `npm run docs:render-diagrams`). Diagram/filename predate the `cacheAffinity` factor added by #8008 and still show 12 factors.
 
-| Factor                | Default Weight | Description                                                                                                                                                                                 |
-| :-------------------- | :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `health`              | 0.20           | Health score from circuit breaker (CLOSED=1.0, HALF_OPEN=0.5, OPEN=0.0)                                                                                                                     |
-| `quota`               | 0.15           | Remaining quota / rate-limit headroom [0..1]                                                                                                                                                |
-| `costInv`             | 0.15           | Inverse **blended** cost (60% input + 40% output token price, normalized) — cheaper = higher score                                                                                          |
-| `latencyInv`          | 0.12           | Inverse p95 latency normalized to pool — faster = higher score                                                                                                                              |
-| `taskFit`             | 0.08           | Task-type fitness (coding, review, planning, analysis, debugging, docs)                                                                                                                     |
-| `stability`           | 0.05           | Variance-based stability (low latency stdDev / error rate)                                                                                                                                  |
-| `tierPriority`        | 0.05           | Account-tier priority — Ultra=1.0, Pro=0.67, Standard=0.33, Free=0.0                                                                                                                        |
-| `tierAffinity`        | 0.05           | Affinity between the candidate's tier and the manifest-recommended tier                                                                                                                     |
-| `specificityMatch`    | 0.05           | Match between request specificity (manifest hint) and model tier                                                                                                                            |
-| `contextAffinity`     | 0.05           | Affinity between the request's context-window need and the model's context window                                                                                                           |
-| `connectionDensity`   | 0.05           | Spreads load across connections of the same provider (anti-concentration)                                                                                                                   |
+| Factor                | Default Weight | Description                                                                                        |
+| :-------------------- | :------------- | :------------------------------------------------------------------------------------------------- |
+| `health`              | 0.20           | Health score from circuit breaker (CLOSED=1.0, HALF_OPEN=0.5, OPEN=0.0)                            |
+| `quota`               | 0.15           | Remaining quota / rate-limit headroom [0..1]                                                       |
+| `costInv`             | 0.15           | Inverse **blended** cost (60% input + 40% output token price, normalized) — cheaper = higher score |
+| `latencyInv`          | 0.12           | Inverse p95 latency normalized to pool — faster = higher score                                     |
+| `taskFit`             | 0.08           | Task-type fitness (coding, review, planning, analysis, debugging, docs)                            |
+| `stability`           | 0.05           | Variance-based stability (low latency stdDev / error rate)                                         |
+| `tierPriority`        | 0.05           | Account-tier priority — Ultra=1.0, Pro=0.67, Standard=0.33, Free=0.0                               |
+| `tierAffinity`        | 0.05           | Affinity between the candidate's tier and the manifest-recommended tier                            |
+| `specificityMatch`    | 0.05           | Match between request specificity (manifest hint) and model tier                                   |
+| `contextAffinity`     | 0.05           | Affinity between the request's context-window need and the model's context window                  |
+| `connectionDensity`   | 0.05           | Spreads load across connections of the same provider (anti-concentration)                          |
 | `cacheAffinity`       | 0.00           | Rendezvous-hash affinity toward the connection likeliest to already hold this request's prompt-cache prefix (`open-sse/services/combo/promptCacheAffinity.ts`); disabled by default (#8008) |
-| `resetWindowAffinity` | 0.00           | Bias toward connections whose quota reset window is favorable (disabled by default)                                                                                                         |
+| `resetWindowAffinity` | 0.00           | Bias toward connections whose quota reset window is favorable (disabled by default)                |
 
 **Sum:** `0.20 + 0.15 + 0.15 + 0.12 + 0.08 + 0.05 + 0.05 + 0.05 + 0.05 + 0.05 + 0.05 + 0.00 + 0.00 = 1.0` (validated by `validateWeights()`).
 
@@ -215,11 +215,11 @@ combo's stored config. These apply only to the `auto` strategy and only for the
 that carries them; the combo's saved `modePack`/`budgetCap`/`budgetFallback` are used
 when the header is absent.
 
-| Header                        | Accepts                                                                                                                                                                                 | Effect                                                                                                                                                                                                                                               |
-| :---------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `X-OmniRoute-Mode`            | a preset alias (`fast`, `balanced`, `quality`, `cheap`, `reliable`, `offline`) or a raw pack name (`ship-fast`, `cost-saver`, `quality-first`, `offline-friendly`, `reliability-first`) | Overrides the scoring weights for this request. `balanced`/`default` force the default weights (no pack). Unknown values are ignored (config preserved).                                                                                             |
-| `X-OmniRoute-Budget`          | a positive number (max USD per request)                                                                                                                                                 | Hard cost ceiling: candidates whose estimated cost exceeds it are filtered before selection. What happens when **every** candidate exceeds it is controlled by `X-OmniRoute-Budget-Fallback` below.                                                  |
-| `X-OmniRoute-Budget-Fallback` | `cheapest` (default, aliases: `cheapest-viable`, `soft`) or `strict` (aliases: `block`, `hard`)                                                                                         | `cheapest`: falls back to the globally cheapest candidate even though it still exceeds the cap (legacy behavior). `strict`: refuses to select — the request fails fast with `HTTP 402` instead of silently overspending. Unknown values are ignored. |
+| Header                        | Accepts                                                                                                                                                                                 | Effect                                                                                                                                                                                              |
+| :----------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `X-OmniRoute-Mode`            | a preset alias (`fast`, `balanced`, `quality`, `cheap`, `reliable`, `offline`) or a raw pack name (`ship-fast`, `cost-saver`, `quality-first`, `offline-friendly`, `reliability-first`) | Overrides the scoring weights for this request. `balanced`/`default` force the default weights (no pack). Unknown values are ignored (config preserved).                                            |
+| `X-OmniRoute-Budget`          | a positive number (max USD per request)                                                                                                                                                 | Hard cost ceiling: candidates whose estimated cost exceeds it are filtered before selection. What happens when **every** candidate exceeds it is controlled by `X-OmniRoute-Budget-Fallback` below. |
+| `X-OmniRoute-Budget-Fallback` | `cheapest` (default, aliases: `cheapest-viable`, `soft`) or `strict` (aliases: `block`, `hard`)                                                                                        | `cheapest`: falls back to the globally cheapest candidate even though it still exceeds the cap (legacy behavior). `strict`: refuses to select — the request fails fast with `HTTP 402` instead of silently overspending. Unknown values are ignored. |
 
 ```bash
 # Force the fastest profile, cap this request at $0.05, and hard-block instead of overspending
@@ -240,27 +240,27 @@ resolved values feed the engine's existing `config.modePack` / `config.budgetCap
 
 OmniRoute's combo engine supports **19 routing strategies** (declared in `src/shared/constants/routingStrategies.ts` → `ROUTING_STRATEGY_VALUES`). The Auto Combo engine itself is exposed under the `auto` strategy; the others are available for persisted combos.
 
-| Strategy            | Description                                                                                                                                                                               |
-| :------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `priority`          | First-target ordered list with explicit priority                                                                                                                                          |
-| `weighted`          | Weighted random by per-target weight                                                                                                                                                      |
-| `round-robin`       | Cycle through targets in order                                                                                                                                                            |
-| `context-relay`     | Hand off context across targets (long conversations)                                                                                                                                      |
-| `fill-first`        | Fill each target's quota before moving to next                                                                                                                                            |
-| `p2c`               | Power-of-2-choices random load balancing                                                                                                                                                  |
-| `random`            | Uniform random selection                                                                                                                                                                  |
-| `least-used`        | Pick target with lowest current load                                                                                                                                                      |
-| `cost-optimized`    | Minimize $ per request given catalog pricing                                                                                                                                              |
-| `reset-aware` ⭐    | Prioritize by quota reset time — short reset windows ranked higher                                                                                                                        |
-| `reset-window`      | Prefer targets whose quota window resets soonest                                                                                                                                          |
-| `headroom`          | Pick the target with the most remaining quota headroom                                                                                                                                    |
-| `strict-random`     | Random without deduplication of repeats                                                                                                                                                   |
-| `auto`              | Use Auto Combo scoring (9-factor) — **recommended**                                                                                                                                       |
-| `lkgp`              | Last-Known-Good Path (sticky route to last successful target)                                                                                                                             |
-| `context-optimized` | Pick target with best fit for current context size                                                                                                                                        |
+| Strategy            | Description                                                                                                                  |
+| :------------------ | :--------------------------------------------------------------------------------------------------------------------------- |
+| `priority`          | First-target ordered list with explicit priority                                                                             |
+| `weighted`          | Weighted random by per-target weight                                                                                         |
+| `round-robin`       | Cycle through targets in order                                                                                               |
+| `context-relay`     | Hand off context across targets (long conversations)                                                                         |
+| `fill-first`        | Fill each target's quota before moving to next                                                                               |
+| `p2c`               | Power-of-2-choices random load balancing                                                                                     |
+| `random`            | Uniform random selection                                                                                                     |
+| `least-used`        | Pick target with lowest current load                                                                                         |
+| `cost-optimized`    | Minimize $ per request given catalog pricing                                                                                 |
+| `reset-aware` ⭐    | Prioritize by quota reset time — short reset windows ranked higher                                                           |
+| `reset-window`      | Prefer targets whose quota window resets soonest                                                                             |
+| `headroom`          | Pick the target with the most remaining quota headroom                                                                       |
+| `strict-random`     | Random without deduplication of repeats                                                                                      |
+| `auto`              | Use Auto Combo scoring (9-factor) — **recommended**                                                                          |
+| `lkgp`              | Last-Known-Good Path (sticky route to last successful target)                                                                |
+| `context-optimized` | Pick target with best fit for current context size                                                                           |
 | `cache-optimized`   | Reorder targets by prompt-cache affinity — the connection likeliest to already hold this request's cached prefix is tried first (`open-sse/services/combo/promptCacheAffinity.ts`, #8008) |
-| `fusion` 🧬         | Fan out to a panel of models in parallel, then synthesize one answer via a judge (see below)                                                                                              |
-| `pipeline`          | Run targets sequentially, threading each step's output into the next step's input; only the final answer is returned (#6396)                                                              |
+| `fusion` 🧬         | Fan out to a panel of models in parallel, then synthesize one answer via a judge (see below)                                 |
+| `pipeline`          | Run targets sequentially, threading each step's output into the next step's input; only the final answer is returned (#6396) |
 
 ⭐ = New in v3.8.0 · 🧬 = New in v3.8.36
 
@@ -679,11 +679,11 @@ See `docs/marketing/TIERS.md` for tier definitions and provider classification.
 
 ### Deterministic routing-decision matrix (`npm run test:combo:matrix`)
 
-`tests/integration/combo-matrix/*.test.ts` proves the routing **decision** of all 19
+`tests/integration/combo-matrix/*.test.ts` proves the routing **decision** of all 18
 public strategies end-to-end through the real combo pipeline with a mocked upstream.
 Coverage includes:
 
-- All 19 `ROUTING_STRATEGY_VALUES` strategies (ordered, weighted, cost, context, fusion, …).
+- All 18 `ROUTING_STRATEGY_VALUES` strategies (ordered, weighted, cost, context, fusion, …).
 - `quota-share` (internal) end-to-end: DRR fairness + saturation deprioritization via the
   real `selectQuotaShareTarget` seam (`registerQuotaFetcher` / `setLKGP` /
   `__setHeadroomSaturationFetcherForTests`).

docs/security/AGENTROUTER_WAF.md

@@ -1,91 +0,0 @@
-# agentrouter.org WAF (Web Application Firewall)
-
-The `agentrouter` upstream gateway runs a keyword-based content filter on
-`messages[].content`. The filter is partially deterministic (always blocks
-certain phrases) and partially probabilistic (burst-sensitive — becomes
-more aggressive after rapid requests, recovers after a cooldown).
-
-When the WAF blocks a request it returns:
-
-```
-HTTP/1.1 400 Bad Request
-{"error":{"code":"content-blocked","message":"content-blocked (request id: ...)","param":"","type":"agent_router_api_error"}}
-```
-
-## Scope of the filter
-
-The WAF inspects `messages[].content` only. It does **not** inspect:
-
-- The `system` prompt
-- Structured content blocks (`tool_result`, `tool_use`, `thinking`, `image`)
-- Tool `description` and `input_schema` fields
-- Request metadata, headers, or model id
-
-## Always-blocked patterns (case-insensitive)
-
-| Pattern                       | Notes                                  |
-|-------------------------------|----------------------------------------|
-| Any `Lorem ipsum` variant     | Full Latin lorem vocabulary is blocked |
-| `language model` (alone)      | "the language model" and "large language model" pass |
-| `virtual assistant`           | "AI assistant" passes                   |
-| `I'm here to help`            | "here to help" alone also blocks        |
-| `Claude, made by Anthropic`   | Full phrase only                        |
-
-## Almost-always-blocked patterns
-
-| Pattern           | Notes                                                   |
-|-------------------|---------------------------------------------------------|
-| `placeholder`     | When it stands alone (not as a parameter name, etc.)  |
-| `dummy data`      | Common seed phrase for fixtures                        |
-| `foo bar baz`     | Canonical placeholder phrase                           |
-| Repeated short tokens (`AAA BBB CCC`, `test test test`) | Detector for keyword stuffing |
-
-## Behavior under load
-
-After ~5 rapid requests in a short window, the WAF begins blocking content
-that would normally pass. The bucket relaxes after ~5–10 seconds of idle
-time. This is the same IP-and-key-bound rate limiter that causes
-intermittent `400 content-blocked` errors when Claude Code or Codex CLI
-makes multiple tool-use / message-send calls in quick succession.
-
-## Mitigations already applied in OmniRoute
-
-1. **`open-sse/services/wafRateLimit.ts`** — burst guard that enforces a
-   500 ms minimum gap between outbound requests to any `agentrouter:*`
-   URL. The gap is well below human perception of latency and prevents
-   the WAF from activating on normal traffic.
-
-2. **`BaseExecutor.WAF_RETRY_CONFIG`** — when an upstream returns
-   `400 content-blocked`, the executor retries the same URL with
-   exponential backoff (1.5 s, 3.0 s, max 2 attempts). After the backoff
-   the WAF usually relaxes and the retry succeeds.
-
-3. **`tests/unit/compression/harness.test.ts`** — the test fixture
-   `longInput` was changed from `"lorem ipsum dolor sit amet ".repeat(40)`
-   to `"example content for testing purposes ".repeat(40)` so that when
-   Claude Code reads this file via the `Read` tool, the file contents
-   do not flow back through a `tool_result` block and trip the WAF.
-
-## Guidance for prompts and tool output
-
-If a Claude Code or Codex CLI session repeatedly hits
-`400 content-blocked`, check the most recent user message and the most
-recent tool result for any of the patterns above and rephrase. Common
-workarounds:
-
-- Replace `Lorem ipsum …` with `example text …` or the actual content
-  the test or fixture is trying to model.
-- Replace `placeholder` (when standing alone) with `example value`,
-  `sample value`, or the real value.
-- Replace `language model` with `large language model` or `the model`.
-- Replace `dummy data` with `sample data` or realistic seed values.
-- Replace `I'm here to help` / `here to help` with a more specific
-  opener (e.g. "I'll review the file you mentioned").
-
-## Reporting the false positives upstream
-
-The current filter is overly aggressive — it blocks "Lorem ipsum" in
-`tool_result` blocks even though the operator clearly did not intend to
-inject a prompt. Operators who want this fixed at the source should
-contact `agentrouter.org` to report the false positives. The blocklist
-above is the empirical result of probing the upstream as of 2026-08-03.

electron/package.json

@@ -1,6 +1,6 @@
 {
   "name": "omniroute-desktop",
-  "version": "3.8.50",
+  "version": "3.8.49",
   "description": "OmniRoute Desktop Application",
   "main": "main.js",
   "author": {

eslint.config.mjs

@@ -13,29 +13,6 @@ const TO_NUMBER_RESTRICTION = {
     "canonical coercion shape and the `toNumberOrNull`/`toNumberArray` variants.",
 };
 
-const LOCAL_DB_IMPORT_RESTRICTION = {
-  regex: "^(?:@/lib/localDb(?:\\.ts)?|(?:\\.\\.?/)+(?:lib/)?localDb(?:\\.ts)?)$",
-  message:
-    "The localDb compatibility barrel is restricted — import the owning domain module " +
-    "from `@/lib/db/` instead.",
-};
-
-const EXECUTOR_IMPORT_RESTRICTION = {
-  regex: "^(?:@omniroute/)?open-sse/executors(?:/|$)",
-  message:
-    "Executor implementations must stay behind an open-sse handler or service boundary.",
-};
-
-const PROP_TYPES_RESTRICTION = {
-  name: "prop-types",
-  message: "PropTypes are deprecated. Use TypeScript types/interfaces instead.",
-};
-
-const IMPORT_BOUNDARY_RESTRICTIONS = {
-  paths: [PROP_TYPES_RESTRICTION],
-  patterns: [LOCAL_DB_IMPORT_RESTRICTION],
-};
-
 /** @type {import("eslint").Linter.Config[]} */
 const eslintConfig = [
   ...nextVitals,
@@ -62,32 +39,15 @@ const eslintConfig = [
       "no-eval": "error",
       "no-implied-eval": "error",
       "no-new-func": "error",
-      "no-restricted-imports": ["error", IMPORT_BOUNDARY_RESTRICTIONS],
-    },
-  },
-  // G14: DB internals may use the compatibility barrel while it is decomposed; all
-  // other source files must import the owning src/lib/db domain module directly.
-  {
-    files: ["src/lib/db/**/*.{ts,tsx,js,jsx}"],
-    rules: {
       "no-restricted-imports": [
         "error",
         {
-          paths: [PROP_TYPES_RESTRICTION],
-        },
-      ],
-    },
-  },
-  // G14: App routes/components must delegate provider execution through handlers or
-  // services instead of reaching into executor implementations.
-  {
-    files: ["src/app/**/*.{ts,tsx,js,jsx}"],
-    rules: {
-      "no-restricted-imports": [
-        "error",
-        {
-          ...IMPORT_BOUNDARY_RESTRICTIONS,
-          patterns: [LOCAL_DB_IMPORT_RESTRICTION, EXECUTOR_IMPORT_RESTRICTION],
+          paths: [
+            {
+              name: "prop-types",
+              message: "PropTypes are deprecated. Use TypeScript types/interfaces instead.",
+            },
+          ],
         },
       ],
     },

open-sse/config/codexClient.ts

@@ -1,9 +1,4 @@
-import {
-  DEFAULT_CODEX_CLIENT_VERSION,
-  getCodexCliRsHeaders as buildCodexCliRsHeaders,
-} from "@/shared/constants/codexClient";
-
-export { DEFAULT_CODEX_CLIENT_VERSION } from "@/shared/constants/codexClient";
+const DEFAULT_CODEX_CLIENT_VERSION = "0.144.1";
 const DEFAULT_CODEX_USER_AGENT_PLATFORM = "Windows 10.0.26200";
 const DEFAULT_CODEX_USER_AGENT_ARCH = "x64";
 const CODEX_VERSION_OVERRIDE_ENV = "CODEX_CLIENT_VERSION";
@@ -47,10 +42,6 @@ export function getCodexDefaultHeaders(): Record<string, string> {
   };
 }
 
-export function getCodexCliRsHeaders(): Record<string, string> {
-  return buildCodexCliRsHeaders(getCodexClientVersion());
-}
-
 export function normalizeCodexSessionId(value: unknown): string | null {
   if (typeof value !== "string") return null;
   const normalized = value.trim();

open-sse/config/freeModelCatalog.data.ts

@@ -19,9 +19,10 @@ import type { FreeModelBudget } from "./freeModelCatalog.ts";
 export const FREE_CATALOG_CURATED_AT = "2026-07-22";
 
 export const FREE_MODEL_BUDGETS: FreeModelBudget[] = [
-  { provider: "agentrouter", modelId: "claude-opus-4-8", displayName: "Claude Opus 4.8", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
-  { provider: "agentrouter", modelId: "claude-opus-5", displayName: "Claude Opus 5", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
-  { provider: "agentrouter", modelId: "gpt-5.6-sol", displayName: "GPT-5.6 Sol", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
+  { provider: "agentrouter", modelId: "claude-opus-4-6", displayName: "Claude 4.6 Opus", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
+  { provider: "agentrouter", modelId: "claude-haiku-4-5-20251001", displayName: "Claude 4.5 Haiku", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
+  { provider: "agentrouter", modelId: "glm-5.1", displayName: "GLM 5.1", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
+  { provider: "agentrouter", modelId: "deepseek-v3.2", displayName: "DeepSeek V3.2", monthlyTokens: 0, creditTokens: 200000000, freeType: "one-time-initial", poolKey: "agentrouter", tos: "caution" },
   { provider: "agy", modelId: "claude-opus-4-6-thinking", displayName: "Claude Opus 4.6 (Thinking)", monthlyTokens: 0, creditTokens: 0, freeType: "keyless", poolKey: "agy", tos: "avoid" },
   { provider: "agy", modelId: "claude-sonnet-4-6", displayName: "Claude Sonnet 4.6 (Thinking)", monthlyTokens: 0, creditTokens: 0, freeType: "keyless", poolKey: "agy", tos: "avoid" },
   { provider: "agy", modelId: "gemini-3.1-pro-low", displayName: "Gemini 3.1 Pro (Low)", monthlyTokens: 0, creditTokens: 0, freeType: "keyless", poolKey: "agy", tos: "avoid" },

open-sse/config/imageRegistry.ts

@@ -11,7 +11,6 @@ import { KIE_IMAGE_MODELS } from "./providers/registry/kie/imageModels.ts";
 import { FREEPIK_IMAGE_PROVIDER } from "./providers/registry/freepik/index.ts";
 import { STABILITY_AI_IMAGE_MODELS } from "./providers/registry/stability-ai/imageModels.ts";
 import { GEMINI_IMAGEN_PROVIDER } from "./providers/registry/gemini/imageModels.ts";
-import { CHEAPERINFERENCE_IMAGE_PROVIDER } from "./providers/registry/cheaperinference/imageModels.ts";
 
 interface ImageModelEntry {
   id: string;
@@ -715,13 +714,6 @@ export const IMAGE_PROVIDERS: Record<string, ImageProviderConfig> = {
     supportedSizes: ["1:1", "16:9", "9:16", "4:3", "3:4", "1024x1024", "1792x1024", "1024x1792"],
   },
 
-  // Cheaper Inference (OSS-sponsor gateway). Declared AFTER adobe-firefly on
-  // purpose: it shares the nano-banana-pro / nano-banana-2 ids, and parseImageModel
-  // resolves a bare id by first-match over this object's iteration order, so
-  // Firefly keeps the bare ids and these are prefix-only. See the module for the
-  // full collision note.
-  cheaperinference: CHEAPERINFERENCE_IMAGE_PROVIDER,
-
   // Keep Bailian Coding Plan after existing duplicate model owners so adding
   // explicit `bailian-coding-plan/` and `bcp/` routes does not change
   // historical bare-model routing.

open-sse/config/providers/index.ts

@@ -117,7 +117,6 @@ import { uncloseaiProvider } from "./registry/uncloseai/index.ts";
 import { nscaleProvider } from "./registry/nscale/index.ts";
 import { chatgpt_webProvider } from "./registry/chatgpt-web/index.ts";
 import { openrouterProvider } from "./registry/openrouter/index.ts";
-import { cheaperinferenceProvider } from "./registry/cheaperinference/index.ts";
 import { openvectaProvider } from "./registry/openvecta/index.ts";
 import { orcarouterProvider } from "./registry/orcarouter/index.ts";
 import { copilot_webProvider } from "./registry/copilot-web/index.ts";
@@ -338,7 +337,6 @@ export const REGISTRY: Record<string, RegistryEntry> = {
   nscale: nscaleProvider,
   "chatgpt-web": chatgpt_webProvider,
   openrouter: openrouterProvider,
-  cheaperinference: cheaperinferenceProvider,
   openvecta: openvectaProvider,
   orcarouter: orcarouterProvider,
   "copilot-web": copilot_webProvider,

open-sse/config/providers/registry/agentrouter/index.ts

@@ -1,5 +1,4 @@
 import type { RegistryEntry } from "../../shared.ts";
-import { getCodexCliRsHeaders } from "../../../codexClient.ts";
 
 export const agentrouterProvider: RegistryEntry = {
   id: "agentrouter",
@@ -9,22 +8,6 @@ export const agentrouterProvider: RegistryEntry = {
   baseUrl: "https://agentrouter.org/v1/messages",
   authType: "apikey",
   authHeader: "x-api-key",
-  alternateFormats: [
-    {
-      format: "openai",
-      baseUrl: "https://agentrouter.org/v1/chat/completions",
-      authHeader: "bearer",
-      headers: getCodexCliRsHeaders(),
-      label: "OpenAI-compatible (Codex)",
-    },
-    {
-      format: "openai-responses",
-      baseUrl: "https://agentrouter.org/v1/responses",
-      authHeader: "bearer",
-      headers: getCodexCliRsHeaders(),
-      label: "OpenAI Responses (Codex)",
-    },
-  ],
   defaultContextLength: 128000,
   // No static `headers` here: agentrouter now adopts the DYNAMIC Claude-Code
   // wire image via CC_WIRE_IMAGE_BUILTINS (#6056) — the fingerprint/headers are
@@ -32,9 +15,10 @@ export const agentrouterProvider: RegistryEntry = {
   // own baseUrl + x-api-key auth. A static fingerprint here would drift and
   // trip AgentRouter's WAF ("unauthorized client detected").
   models: [
-    { id: "claude-opus-4-8", name: "Claude Opus 4.8" },
-    { id: "claude-opus-5", name: "Claude Opus 5" },
-    { id: "gpt-5.6-sol", name: "GPT-5.6 Sol" },
+    { id: "claude-opus-4-6", name: "Claude 4.6 Opus" },
+    { id: "claude-haiku-4-5-20251001", name: "Claude 4.5 Haiku" },
+    { id: "glm-5.1", name: "GLM 5.1" },
+    { id: "deepseek-v3.2", name: "DeepSeek V3.2" },
   ],
   passthroughModels: true,
 };

open-sse/config/providers/registry/cheaperinference/imageModels.ts

@@ -1,34 +0,0 @@
-/**
- * Cheaper Inference image provider registry entry.
- * Extracted into its own module to keep open-sse/config/imageRegistry.ts
- * under the file-size cap (god-file decomposition; semantic split) — same
- * pattern as FREEPIK_IMAGE_PROVIDER / SEGMIND_IMAGE_PROVIDER.
- *
- * 3 image models measured from GET /v1/models?type=image on 2026-07-31.
- *
- * COLLISION NOTE: nano-banana-pro and nano-banana-2 are ALSO adobe-firefly model
- * ids. parseImageModel() resolves a bare id by first-match over IMAGE_PROVIDERS
- * iteration order, so this entry is spread into that object AFTER adobe-firefly:
- * bare `nano-banana-2` keeps routing to Firefly (pre-existing behaviour) and these
- * models are reachable only as `cheaperinference/<id>` / `cinf/<id>`. Do NOT add
- * IMAGE_MODEL_ALIASES entries for them — that would silently re-route Firefly
- * users. Guarded by tests/unit/cheaperinference-image-models.test.ts.
- *
- * The endpoint ignores `response_format:"url"` and always returns `b64_json`
- * (measured twice). The OpenAI image path already handles b64_json; this is not a
- * bug to "fix". /v1/images/edits returns 404 upstream, so no edit support.
- */
-export const CHEAPERINFERENCE_IMAGE_PROVIDER = {
-  id: "cheaperinference",
-  alias: "cinf",
-  baseUrl: "https://api.cheaperinference.com/v1/images/generations",
-  authType: "apikey",
-  authHeader: "bearer",
-  format: "openai",
-  models: [
-    { id: "grok-imagine", name: "Grok Imagine (Cheaper Inference)" },
-    { id: "nano-banana-pro", name: "Nano Banana Pro (Cheaper Inference)" },
-    { id: "nano-banana-2", name: "Nano Banana 2 (Cheaper Inference)" },
-  ],
-  supportedSizes: ["1024x1024", "2048x2048", "4096x4096"],
-};

open-sse/config/providers/registry/cheaperinference/index.ts

@@ -1,247 +0,0 @@
-import type { RegistryEntry, RegistryModel } from "../../shared.ts";
-
-/**
- * Cheaper Inference (https://api.cheaperinference.com) — cost-ranked OpenAI-compatible
- * gateway, OmniRoute Open Source Friend.
- *
- * Catalog captured from a live `GET /v1/models` on 2026-07-31 (42 entries: these 39
- * `type:"text"` models plus 3 `type:"image"` models that live in imageRegistry.ts —
- * sending an image model here returns HTTP 400 "Use POST /v1/images/generations").
- * `supportsVision`/`supportsReasoning` mirror each entry's `capabilities` object
- * verbatim; they are not inferred from the model name.
- *
- * The gateway also serves a native `/v1/responses` endpoint (`responsesBaseUrl`).
- * It is stateless and REQUIRES `store:false` — see executors/cheaperinference.ts,
- * which injects it and resolves the URL from the per-model `targetFormat` tag.
- */
-export const CHEAPERINFERENCE_MODELS: RegistryModel[] = [
-  { id: "aion-labs.aion-2-0", name: "Aion 2.0", supportsReasoning: true, toolCalling: true },
-  {
-    id: "claude-fable-5",
-    name: "Claude Fable 5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-haiku-4.5",
-    name: "Claude Haiku 4.5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4-7-fast",
-    name: "Claude Opus 4.7 Fast",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4-8-fast",
-    name: "Claude Opus 4.8 Fast",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4.5",
-    name: "Claude Opus 4.5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4.6",
-    name: "Claude Opus 4.6",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4.7",
-    name: "Claude Opus 4.7",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-4.8",
-    name: "Claude Opus 4.8",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-5",
-    name: "Claude Opus 5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-opus-5-fast",
-    name: "Claude Opus 5 Fast",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-sonnet-4.5",
-    name: "Claude Sonnet 4.5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-sonnet-4.6",
-    name: "Claude Sonnet 4.6",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "claude-sonnet-5",
-    name: "Claude Sonnet 5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  { id: "deepseek-v4-flash", name: "DeepSeek V4 Flash", supportsReasoning: true, toolCalling: true },
-  { id: "deepseek-v4-pro", name: "DeepSeek V4 Pro", supportsReasoning: true, toolCalling: true },
-  {
-    id: "gemini-2.5-flash",
-    name: "Gemini 2.5 Flash",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "gemini-3-5-flash",
-    name: "Gemini 3.5 Flash",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "gemini-3-flash-preview",
-    name: "Gemini 3 Flash Preview",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "gemini-3.1-flash-lite",
-    name: "Gemini 3.1 Flash Lite",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "gemini-3.1-pro",
-    name: "Gemini 3.1 Pro",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "gemini-3.1-pro-preview",
-    name: "Gemini 3.1 Pro Preview",
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  { id: "glm-4.5", name: "GLM-4.5", supportsReasoning: true, toolCalling: true },
-  { id: "glm-4.5-air", name: "GLM-4.5 Air", supportsReasoning: true, toolCalling: true },
-  { id: "glm-4.6", name: "GLM-4.6", supportsReasoning: true, toolCalling: true },
-  { id: "glm-4.7", name: "GLM-4.7", supportsReasoning: true, toolCalling: true },
-  { id: "glm-5", name: "GLM-5", supportsReasoning: true, toolCalling: true },
-  { id: "glm-5.1", name: "GLM-5.1", supportsReasoning: true, toolCalling: true },
-  { id: "glm-5.2", name: "GLM-5.2", supportsReasoning: true, toolCalling: true },
-  {
-    id: "google/gemini-3.5-flash-lite",
-    name: "Gemini 3.5 Flash Lite",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  // The GPT-5.x family is tagged for the gateway's native /v1/responses endpoint —
-  // that is the surface OpenAI-family clients (Codex-style) expect for tool loops.
-  {
-    id: "gpt-5.4",
-    name: "GPT-5.4",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "gpt-5.4-mini",
-    name: "GPT-5.4 Mini",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "gpt-5.5",
-    name: "GPT-5.5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "gpt-5.6-luna",
-    name: "GPT-5.6 Luna",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "gpt-5.6-sol",
-    name: "GPT-5.6 Sol",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "gpt-5.6-terra",
-    name: "GPT-5.6 Terra",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-    targetFormat: "openai-responses",
-  },
-  {
-    id: "grok-4.5",
-    name: "Grok 4.5",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  {
-    id: "kimi-k3",
-    name: "Kimi K3",
-    supportsVision: true,
-    supportsReasoning: true,
-    toolCalling: true,
-  },
-  { id: "minimax-m2.7", name: "MiniMax M2.7", supportsReasoning: true, toolCalling: true },
-];
-
-export const cheaperinferenceProvider: RegistryEntry = {
-  id: "cheaperinference",
-  alias: "cinf",
-  format: "openai",
-  executor: "cheaperinference",
-  baseUrl: "https://api.cheaperinference.com/v1/chat/completions",
-  // The gateway serves a native, STATELESS /v1/responses endpoint alongside
-  // /v1/chat/completions. Consumed by CheaperInferenceExecutor.buildUrl for the
-  // models tagged targetFormat: "openai-responses" above.
-  responsesBaseUrl: "https://api.cheaperinference.com/v1/responses",
-  authType: "apikey",
-  authHeader: "bearer",
-  models: CHEAPERINFERENCE_MODELS,
-};

open-sse/executors/base.ts

@@ -34,7 +34,6 @@ import {
   resolveAccountKey,
   isFreeVariantModel,
 } from "../services/openrouterFreeWindow.ts";
-import { gateOutboundRequest } from "../services/wafRateLimit.ts";
 import type { PoolConfig } from "../services/sessionPool/types.ts";
 import type { Session } from "../services/sessionPool/session.ts";
 import { SessionPool } from "../services/sessionPool/sessionPool.ts";
@@ -46,7 +45,6 @@ import {
 } from "../services/apiKeyRotator.ts";
 import type { KeyHealth } from "../services/apiKeyRotator.ts";
 import { getOpenAICompatibleType, isClaudeCodeCompatible } from "../services/provider.ts";
-import { usesCcWireImage } from "../services/ccWireImageBuiltins.ts";
 import {
   runWithOnPersist,
   getRefreshLeadMs,
@@ -251,10 +249,7 @@ function collectThinkingConfigs(body: unknown): Array<Record<string, unknown>> {
   if (!body || typeof body !== "object") return [];
   const root = body as Record<string, unknown>;
   const configs: Array<Record<string, unknown>> = [];
-  const envelopes: unknown[] = [
-    root.generationConfig,
-    (root.request as Record<string, unknown> | undefined)?.generationConfig,
-  ];
+  const envelopes: unknown[] = [root.generationConfig, (root.request as Record<string, unknown> | undefined)?.generationConfig];
   for (const env of envelopes) {
     if (!env || typeof env !== "object") continue;
     const tc = (env as Record<string, unknown>).thinkingConfig;
@@ -450,12 +445,6 @@ export class BaseExecutor {
     );
   }
 
-  protected usesClaudeCodeProtocol(credentials: ProviderCredentials | null): boolean {
-    if (!isClaudeCodeCompatible(this.provider)) return false;
-    const format = this.resolveAlternate(credentials)?.format;
-    return format !== "openai" && format !== "openai-responses";
-  }
-
   /**
    * Resolve the effective API key via extra-keys round-robin rotation.
    * Mutates `credentials.providerSpecificData.selectedKeyId` on rotation.
@@ -600,15 +589,6 @@ export class BaseExecutor {
 
   // Intra-URL retry config: retry same URL before falling back to next node
   static readonly RETRY_CONFIG = { maxAttempts: 2, delayMs: 2000 };
-  // WAF (400 content-blocked) retry config: agentrouter.org's WAF is burst-sensitive
-  // and recovers after a short cooldown. Use exponential backoff with a higher
-  // starting delay than the generic 429 retry (which is 2s) because the WAF
-  // needs more time to clear its per-IP suspicion bucket.
-  static readonly WAF_RETRY_CONFIG = {
-    maxAttempts: 2,
-    delayMs: 1500,
-    backoffMultiplier: 2,
-  };
   // Timeout for receiving the initial upstream response headers. Once the response
   // starts streaming, STREAM_IDLE_TIMEOUT_MS / Undici bodyTimeout handle stalls.
   static FETCH_START_TIMEOUT_MS = FETCH_TIMEOUT_MS;
@@ -854,16 +834,15 @@ export class BaseExecutor {
         );
       }
 
-      const usesClaudeCodeProtocol = this.usesClaudeCodeProtocol(requestCredentials);
-      const fingerprintProvider =
-        usesCcWireImage(this.provider) && !usesClaudeCodeProtocol ? "codex" : this.provider;
-      const ccRequestDefaults = usesClaudeCodeProtocol
+      const ccRequestDefaults = isClaudeCodeCompatible(this.provider)
         ? getClaudeCodeCompatibleRequestDefaults(requestCredentials?.providerSpecificData)
         : {};
       const shouldForwardExtendedContext =
-        extendedContext && modelSupportsContext1mBeta(model) && !usesClaudeCodeProtocol;
+        extendedContext &&
+        modelSupportsContext1mBeta(model) &&
+        !isClaudeCodeCompatible(this.provider);
       const shouldForwardCcCompatibleContext1m =
-        usesClaudeCodeProtocol &&
+        isClaudeCodeCompatible(this.provider) &&
         ccRequestDefaults.context1m === true &&
         !modelHasNativeContext1m(model);
       if (shouldForwardExtendedContext || shouldForwardCcCompatibleContext1m) {
@@ -943,8 +922,8 @@ export class BaseExecutor {
           !activeCredentials?.apiKey;
 
         if (
-          ((this.provider === "claude" && (isClaudeCodeClient || hasClaudeOAuthToken)) ||
-            usesClaudeCodeProtocol) &&
+          this.provider === "claude" &&
+          (isClaudeCodeClient || hasClaudeOAuthToken) &&
           typeof transformedBody === "object" &&
           transformedBody !== null
         ) {
@@ -1221,11 +1200,6 @@ export class BaseExecutor {
             if (ccKeysLower.has(key.toLowerCase())) delete headers[key];
           }
           Object.assign(headers, ccHeaders);
-          if (usesCcWireImage(this.provider) && usesClaudeCodeProtocol) {
-            delete headers["Authorization"];
-            headers["x-api-key"] =
-              activeCredentials?.apiKey || activeCredentials?.accessToken || "";
-          }
           delete headers["X-Stainless-Helper-Method"];
 
           // OS/arch follow the host running the signed binary. Runtime version
@@ -1272,7 +1246,7 @@ export class BaseExecutor {
             // (tool_result must be in immediately next message).
             // Only apply for Claude/Claude-compatible — OpenAI allows results
             // spread across multiple subsequent messages.
-            const isClaude = this.provider === "claude" || usesClaudeCodeProtocol;
+            const isClaude = this.provider === "claude" || isClaudeCodeCompatible(this.provider);
             // For Claude, fixToolAdjacency may strip tool_use blocks whose
             // tool_result isn't in the next message; re-run fixToolPairs to
             // drop any tool_result orphaned by that strip (discussion #2410).
@@ -1291,7 +1265,7 @@ export class BaseExecutor {
         // at this final dispatch point — the single chokepoint every Claude
         // routing mode (grouped/raw/combo) and the native passthrough share,
         // before fingerprinting and CCH signing serialize the body.
-        if (this.provider === "claude" || usesClaudeCodeProtocol) {
+        if (this.provider === "claude" || isClaudeCodeCompatible(this.provider)) {
           enforceThinkingTemperature(transformedBody as Record<string, unknown>);
         }
 
@@ -1308,7 +1282,7 @@ export class BaseExecutor {
         // `contextEditingDisabled` (set by the 400-fallback) suppresses re-injection
         // when a fresh `transformedBody` is built for a retry/fallback URL.
         if (
-          (this.provider === "claude" || usesClaudeCodeProtocol) &&
+          (this.provider === "claude" || isClaudeCodeCompatible(this.provider)) &&
           contextEditing?.enabled &&
           !contextEditingDisabled
         ) {
@@ -1324,17 +1298,17 @@ export class BaseExecutor {
         let bodyString = JSON.stringify(transformedBody);
 
         const shouldFingerprint =
-          isCliCompatEnabled(fingerprintProvider) ||
+          isCliCompatEnabled(this.provider) ||
           (this.provider === "claude" && (isClaudeCodeClient || hasClaudeOAuthToken));
         if (shouldFingerprint) {
-          const fingerprinted = applyFingerprint(fingerprintProvider, headers, transformedBody);
+          const fingerprinted = applyFingerprint(this.provider, headers, transformedBody);
           finalHeaders = fingerprinted.headers;
           bodyString = fingerprinted.bodyString;
         }
 
         // CCH signing — replaces the cch=00000 placeholder in the billing
         // header with an xxHash64 integrity token over the serialized body.
-        if (usesClaudeCodeProtocol || this.provider === "claude") {
+        if (isClaudeCodeCompatible(this.provider) || this.provider === "claude") {
           bodyString = await signRequestBody(bodyString);
         }
 
@@ -1399,13 +1373,6 @@ export class BaseExecutor {
           recordFreeWindowAttempt(openrouterFreeWindowAccountKey);
         }
 
-        // WAF burst guard: agentrouter.org's content filter becomes more
-        // aggressive after rapid requests. Enforce a small inter-request gap
-        // to avoid tripping it. See open-sse/services/wafRateLimit.ts.
-        if (this.provider === "agentrouter") {
-          await gateOutboundRequest(`agentrouter:${url}`);
-        }
-
         let response = await fetchWithStartTimeout(url, fetchOptions);
 
         if (openrouterFreeWindowAccountKey) {
@@ -1429,7 +1396,7 @@ export class BaseExecutor {
             contextEditingDisabled = true;
             delete (transformedBody as Record<string, unknown>).context_management;
             let retryBody = JSON.stringify(transformedBody);
-            if (usesClaudeCodeProtocol || this.provider === "claude") {
+            if (isClaudeCodeCompatible(this.provider) || this.provider === "claude") {
               retryBody = await signRequestBody(retryBody);
             }
             log?.debug?.(
@@ -1468,7 +1435,7 @@ export class BaseExecutor {
             thinkingBudgetClampedMax = upstreamMax;
             if (clampNestedThinkingBudget(transformedBody, upstreamMax)) {
               let retryBody = JSON.stringify(transformedBody);
-              if (usesClaudeCodeProtocol || this.provider === "claude") {
+              if (isClaudeCodeCompatible(this.provider) || this.provider === "claude") {
                 retryBody = await signRequestBody(retryBody);
               }
               log?.info?.(
@@ -1499,7 +1466,7 @@ export class BaseExecutor {
             strippedFields.add(offending);
             delete (transformedBody as Record<string, unknown>)[offending];
             let retryBody = JSON.stringify(transformedBody);
-            if (usesClaudeCodeProtocol || this.provider === "claude") {
+            if (isClaudeCodeCompatible(this.provider) || this.provider === "claude") {
               retryBody = await signRequestBody(retryBody);
             }
             log?.debug?.(
@@ -1524,7 +1491,7 @@ export class BaseExecutor {
                   addParamToBlocklist(this.provider, autoLearned, model);
                   delete (transformedBody as Record<string, unknown>)[autoLearned];
                   let retryBody = JSON.stringify(transformedBody);
-                  if (usesClaudeCodeProtocol || this.provider === "claude") {
+                  if (isClaudeCodeCompatible(this.provider) || this.provider === "claude") {
                     retryBody = await signRequestBody(retryBody);
                   }
                   log?.info?.(
@@ -1543,34 +1510,6 @@ export class BaseExecutor {
           }
         }
 
-        // Intra-URL retry: agentrouter.org WAF returns 400 content-blocked
-        // intermittently (burst-sensitive, recovers after cooldown). Retry the
-        // same URL with exponential backoff before falling through to the
-        // 429/401/fallback chain. See docs/security/AGENTROUTER_WAF.md.
-        if (
-          !skipUpstreamRetry &&
-          response.status === HTTP_STATUS.BAD_REQUEST &&
-          (retryAttemptsByUrl[urlIndex] ?? 0) < BaseExecutor.WAF_RETRY_CONFIG.maxAttempts
-        ) {
-          const wafErrText = await response
-            .clone()
-            .text()
-            .catch(() => "");
-          if (/content[_-]blocked/i.test(wafErrText)) {
-            retryAttemptsByUrl[urlIndex] = (retryAttemptsByUrl[urlIndex] ?? 0) + 1;
-            const wafAttempt = retryAttemptsByUrl[urlIndex];
-            const wafBackoff = BaseExecutor.WAF_RETRY_CONFIG.delayMs *
-              Math.pow(BaseExecutor.WAF_RETRY_CONFIG.backoffMultiplier, wafAttempt - 1);
-            log?.debug?.(
-              "WAF_RETRY",
-              `400 content-blocked intra-retry ${wafAttempt}/${BaseExecutor.WAF_RETRY_CONFIG.maxAttempts} on ${url} — waiting ${wafBackoff}ms`
-            );
-            await new Promise((resolve) => setTimeout(resolve, wafBackoff));
-            urlIndex--; // re-run this urlIndex on the next loop iteration
-            continue;
-          }
-        }
-
         // Intra-URL retry: if 429 and we haven't exhausted per-URL retries, wait and retry the same URL
         if (
           !skipUpstreamRetry &&

open-sse/executors/base/reasoningEffort.ts

@@ -7,11 +7,10 @@ import { supportsClaudeMaxEffort, supportsXHighEffort } from "../../config/provi
 /**
  * Sanitize reasoning_effort for providers that don't accept all values.
  *
- * The claude→openai translator passes output_config.effort through verbatim
- * (including max) and only performs form conversion; provider-aware effort
- * policy is owned here. Combined with runtime alias remapping (e.g.
- * claude-opus-4-6 → mimo/mimo-v2.5-pro), this routes a client's effort value
- * to OpenAI-shape providers that don't accept it:
+ * The claude→openai translator may emit reasoning_effort=max/xhigh when the
+ * client sends output_config.effort=max on a Claude-shape request. Combined with
+ * runtime alias remapping (e.g. claude-opus-4-6 → mimo/mimo-v2.5-pro), this
+ * routes xhigh to OpenAI-shape providers that don't accept the value:
  *
  *   xiaomi-mimo : low|medium|high only — 400 literal_error on xhigh
  *   mistral     : devstral models reject reasoning_effort entirely
@@ -217,7 +216,10 @@ function writeEffortValue(
 }
 
 /** Strip the effort field from every carrier that was present. */
-function stripEffortValue(b: Record<string, unknown>, c: EffortCarriers): Record<string, unknown> {
+function stripEffortValue(
+  b: Record<string, unknown>,
+  c: EffortCarriers
+): Record<string, unknown> {
   const next: Record<string, unknown> = { ...b };
   if (c.hasTopLevelReasoningEffort) delete next.reasoning_effort;
   if (c.hasReasoningEffort && c.reasoning) {

open-sse/executors/cheaperinference.ts

@@ -1,69 +0,0 @@
-import { BaseExecutor, type ProviderCredentials } from "./base.ts";
-import { PROVIDERS } from "../config/constants.ts";
-import { getModelTargetFormat, PROVIDER_ID_TO_ALIAS } from "../config/providerModels.ts";
-
-/**
- * CheaperInferenceExecutor — api.cheaperinference.com.
- *
- * The gateway is OpenAI-compatible on both surfaces, so everything else comes from
- * BaseExecutor. Two provider-specific facts need handling (both measured against the
- * live API on 2026-07-31, not inferred from docs):
- *
- *  1. `/v1/responses` is STATELESS and REQUIRES `store:false`. Omitting it returns
- *     HTTP 400 ("This Responses-compatible endpoint is stateless. Send store=false…").
- *     chatCore.ts deletes `store` for every provider except "openai" — a strip shared
- *     by ~290 providers that must not be special-cased — so we re-add it here, after
- *     that strip has run. A client-supplied `store:true` is overwritten rather than
- *     forwarded: the endpoint cannot honour it, and forwarding would 400.
- *
- *  2. Chat and Responses live at DIFFERENT URLs (unlike providers that switch on a
- *     path suffix). The per-model `targetFormat` registry tag is the single source of
- *     truth for which surface a model uses — the same tag chatCore reads to translate
- *     the body — so resolving the URL from it keeps URL and payload in lockstep.
- *     Same pattern as executors/xai.ts (9router#2439).
- */
-export class CheaperInferenceExecutor extends BaseExecutor {
-  constructor(provider = "cheaperinference") {
-    super(provider, PROVIDERS[provider]);
-  }
-
-  /**
-   * True when this model is served by the native /v1/responses endpoint.
-   *
-   * PROVIDER_MODELS is keyed by provider ALIAS ("cinf"), while PROVIDERS is keyed by
-   * provider ID ("cheaperinference") — so `this.provider` cannot be passed straight
-   * through the way executors/xai.ts does (there the alias equals the id, which hides
-   * the distinction). Resolve the alias first or every lookup silently returns null
-   * and every Responses request 400s upstream.
-   */
-  private usesResponsesEndpoint(model: string): boolean {
-    const alias = PROVIDER_ID_TO_ALIAS[this.provider] || this.provider;
-    return getModelTargetFormat(alias, model) === "openai-responses";
-  }
-
-  buildUrl(model: string, _stream: boolean, _urlIndex = 0): string {
-    if (this.usesResponsesEndpoint(model)) {
-      return this.config.responsesBaseUrl || this.config.baseUrl;
-    }
-    return this.config.baseUrl;
-  }
-
-  transformRequest(
-    model: string,
-    body: unknown,
-    stream: boolean,
-    credentials: ProviderCredentials
-  ): unknown {
-    const cleanedBody = super.transformRequest(model, body, stream, credentials);
-    if (!cleanedBody || typeof cleanedBody !== "object" || Array.isArray(cleanedBody)) {
-      return cleanedBody;
-    }
-    if (!this.usesResponsesEndpoint(model)) {
-      // Chat Completions rejects unknown params — never add `store` on that surface.
-      return cleanedBody;
-    }
-    return { ...(cleanedBody as Record<string, unknown>), store: false };
-  }
-}
-
-export default CheaperInferenceExecutor;

open-sse/executors/default.ts

@@ -55,7 +55,6 @@ import { forwardOpencodeClientHeaders } from "../utils/opencodeHeaders.ts";
 import { resolveZaiUrl } from "./default/zaiFormatOverride.ts";
 import { acquireNvidiaConcurrencySlot } from "./default/nvidiaConcurrencyGate.ts";
 import { resolveAlibabaProviderBaseUrl } from "@/shared/constants/alibabaProviderRegions";
-import { usesCcWireImage } from "../services/ccWireImageBuiltins.ts";
 
 import type { PoolConfig } from "../services/sessionPool/types.ts";
 
@@ -292,10 +291,6 @@ export class DefaultExecutor extends BaseExecutor {
       case "minimax":
       case "minimax-cn":
         return `${this.config.baseUrl}?beta=true`;
-      case "agentrouter":
-        return this.usesClaudeCodeProtocol(credentials)
-          ? `${this.config.baseUrl}?beta=true`
-          : this.config.baseUrl;
       case "gemini":
         return `${this.config.baseUrl}/${model}:${stream ? "streamGenerateContent?alt=sse" : "generateContent"}`;
       default: {
@@ -418,7 +413,7 @@ export class DefaultExecutor extends BaseExecutor {
         applyClineAuthHeaders(headers, credentials, effectiveKey, clientHeaders, false);
         break;
       default:
-        if (this.usesClaudeCodeProtocol(credentials)) {
+        if (isClaudeCodeCompatible(this.provider)) {
           const ccRequestDefaults = getClaudeCodeCompatibleRequestDefaults(
             credentials?.providerSpecificData
           );
@@ -428,10 +423,6 @@ export class DefaultExecutor extends BaseExecutor {
             credentials?.providerSpecificData?.ccSessionId,
             { redactThinking: ccRequestDefaults.redactThinking === true }
           );
-          if (usesCcWireImage(this.provider)) {
-            delete ccHeaders["Authorization"];
-            ccHeaders["x-api-key"] = effectiveKey || credentials.accessToken || "";
-          }
           // CC nodes are also anthropic-compatible-*, so honor operator custom
           // headers here (the early return skips the shared block below).
           applyCustomHeaders(ccHeaders, credentials.providerSpecificData?.customHeaders);

open-sse/executors/index.ts

@@ -50,7 +50,6 @@ import { PoeWebExecutor } from "./poe-web.ts";
 import { VeniceWebExecutor } from "./venice-web.ts";
 import { NotionWebExecutor } from "./notion-web.ts";
 import { V0VercelWebExecutor } from "./v0-vercel-web.ts";
-import { CheaperInferenceExecutor } from "./cheaperinference.ts";
 import { KimiWebExecutor } from "./kimi-web.ts";
 import { DoubaoWebExecutor } from "./doubao-web.ts";
 import { QwenWebExecutor } from "./qwen-web.ts";
@@ -166,8 +165,6 @@ const executors = {
   "kimi-coding": new KimiExecutor(), // Alias
   moonshot: new MoonshotExecutor(),
   kimi: new MoonshotExecutor("kimi"), // Hidden legacy Moonshot provider id
-  cheaperinference: new CheaperInferenceExecutor(),
-  cinf: new CheaperInferenceExecutor("cheaperinference"), // Alias
   "doubao-web": new DoubaoWebExecutor(),
   db: new DoubaoWebExecutor(), // Alias
   "qwen-web": new QwenWebExecutor(),
@@ -285,5 +282,4 @@ export { ZenmuxFreeExecutor } from "./zenmux-free.ts";
 export { HyperAgentExecutor } from "./hyperagent.ts";
 export { XaiExecutor } from "./xai.ts";
 export { MoonshotExecutor } from "./moonshot.ts";
-export { CheaperInferenceExecutor } from "./cheaperinference.ts";
 export { PromptQlExecutor } from "./promptql.ts";