docs(readme): use local SVG flags + convert doc-link tables to lists (#8317)

Flag emoji (regional-indicator) do not render on Windows and several
Safari/WebKit configs, breaking the 'In 42+ languages' table there.
Replace each emoji with a local SVG <img> from flag-icons (MIT), served
from docs/assets/flags/ so the language selector renders everywhere.

Also convert the 5 'Document | Description' reference tables to definition
lists — full-width and scroll-free on GitHub (tables are capped at
width:max-content and scroll horizontally on narrow viewports).

.agents/skills/capture-release-evidences/SKILL.md

@@ -1,52 +0,0 @@
----
-name: capture-release-evidences-cx
-description: Automatically run a browser-automation agent to visually validate all new UI features from the current release and capture evidence WebP recordings of the changes.
----
-
-# Capture Release Evidences Workflow
-
-Use this workflow to automatically drive a browser-automation agent to explore the newly deployed or locally running application and record evidence of the UI changes introduced in the latest release.
-
-> **Tool mapping note (v3.8):** The `browser_subagent` tool referenced below is specific to an earlier agent runtime. In Claude Code, substitute with the available browser MCP tools (e.g. `mcp__claude-in-chrome__*`) for navigation/screenshots, plus the `Write` tool for saving artifacts. The high-level steps remain the same regardless of the browser-automation surface in use.
-
-## Prerequisites
-
-- OmniRoute must be actively running and accessible (e.g. locally at `http://localhost:20128` or on the Local VPS at `http://192.168.0.15:20128`).
-- The user must provide the target URL to be tested, or default to `http://192.168.0.15:20128`.
-
-## Workflow Steps
-
-### 1. Identify Target Features
-
-Review the `CHANGELOG.md` for the latest version to map out the new UI elements. For example:
-
-- **CLI Tools Settings**
-- **New Provider/Model Listings (e.g., Gemini 3.1, Qoder PAT)**
-- **New Feature Modals**
-
-### 2. Run the Browser Subagent
-
-For each identified feature, invoke the `browser_subagent` using the `default_api:browser_subagent` tool.
-**Important Task Guidelines for the Subagent:**
-
-- `TaskName`: Give it a clear name like "Validate CLIProxyAPI Tool Tab".
-- `TaskSummary`: "Navigate to the CLI Tools tab and verify the new Integration settings."
-- `Task`: Provide unambiguous instructions for the subagent, such as: "Navigate to http://192.168.0.15:20128/dashboard. Click on the 'Settings' or 'CLI Tools' nav link. Scroll down to find the CLIProxyAPI integration card. Hover over it to trigger UI state. Verify the components render correctly and exit."
-- `RecordingName`: Ensure it describes the feature (e.g. `v3_4_5_cli_proxy_api`). This is required and strictly automatically saved as a WebP artifacts video by the system.
-
-_(Note: The `browser_subagent` automatically creates a WebP recording named by the `RecordingName` parameter. No additional tools for screenshots are needed.)_
-
-### 3. Generate Report Artifact
-
-After the `browser_subagent` finishes its sessions, generate a final Markdown artifact (using `Write` and `IsArtifact=true`) to present the recordings inline to the user using the `![caption](/absolute/path/to/media.webp)` syntax.
-
-### Example Invocation
-
-\```json
-{
-"TaskName": "Validating Qoder PAT Configuration UI",
-"TaskSummary": "Validates the Qoder provider configuration modal",
-"Task": "Go to http://192.168.0.15:20128/dashboard. Click on the 'Providers' tab. Find 'Qoder' in the list. Click 'Add Token' or 'Configure'. Type 'test_token' and submit. Return when done.",
-"RecordingName": "qoder_pat_ui_validation"
-}
-\```

.agents/skills/deploy-vps-akamai/SKILL.md

@@ -1,45 +0,0 @@
----
-name: deploy-vps-akamai-cx
-description: Deploy the latest OmniRoute code to the Akamai VPS (69.164.221.35)
----
-
-# Deploy to Akamai VPS Workflow
-
-Deploy OmniRoute to the Akamai VPS using `npm pack + scp` + PM2.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` only for independent commands. Do not parallelize dependent build, copy, install, restart, and verification steps.
-- Report each remote result explicitly before finishing.
-
-**Akamai VPS:** `69.164.221.35`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Akamai VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-```

.agents/skills/deploy-vps-both/SKILL.md

@@ -1,56 +0,0 @@
----
-name: deploy-vps-both-cx
-description: Deploy the latest OmniRoute code to BOTH the Akamai VPS and the Local VPS
----
-
-# Deploy to VPS (Both) Workflow
-
-Deploy OmniRoute to the production VPSs using `npm pack + scp` + PM2.
-
-**Akamai VPS:** `69.164.221.35`
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-**PM2 entry:** `/usr/lib/node_modules/omniroute/app/server.js`
-
-> [!IMPORTANT]
-> The npm registry rejects packages > 100MB, so deployment uses **npm pack + scp**.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` only for independent commands.
-- Build/package once first. After the artifact exists, copy/install/verify on Akamai and Local may run in parallel if they do not depend on each other.
-- Report each VPS result explicitly before finishing.
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to both VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/ && scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.agents/skills/deploy-vps-local/SKILL.md

@@ -1,45 +0,0 @@
----
-name: deploy-vps-local-cx
-description: Deploy the latest OmniRoute code to the Local VPS (192.168.0.15)
----
-
-# Deploy to Local VPS Workflow
-
-Deploy OmniRoute to the Local VPS using `npm pack + scp` + PM2.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` only for independent commands. Do not parallelize dependent build, copy, install, restart, and verification steps.
-- Report each remote result explicitly before finishing.
-
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Local VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.agents/skills/generate-release/SKILL.md

@@ -1,368 +0,0 @@
----
-name: generate-release-cx
-description: Create a new release, bump version up to the .10 patch threshold, update changelog, and manage Pull Requests
----
-
-# Generate Release Workflow
-
-Bump version, finalize CHANGELOG, commit, open a **PR to main** and wait for user confirmation before tagging, publishing, and deploying.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads, checks, and GitHub calls.
-- When the workflow says `notify_user` or `BlockedOnUser: true`, present the report/status in the final response and stop. Do not continue into the next phase until the user explicitly approves.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.8.10` → `3.9.0`.
-
-> **🔴 SINGLE BRANCH RULE**: The `release/vX.Y.Z` branch is the **ONLY** development branch for the entire release cycle. ALL work — bug fixes, feature implementations, PR integrations, issue resolutions — MUST be committed directly on this branch. Never create separate `fix/`, `feat/`, or topic branches. When running `/resolve-issues`, `/implement-features`, or `/review-prs`, always work on the current release branch.
-
----
-
-## ⚠️ Two-Phase Flow
-
-```
-Phase 1 (automated): bump → docs → i18n → commit → push → open PR
-  ↕  🛑 STOP: Notify user, wait for PR confirmation
-Phase 2 (post-merge): tag → publish → GitHub release → Docker → deploy
-```
-
-**NEVER push directly to main or create tags before the user confirms the PR.**
-
----
-
-## Phase 0: Security Verification (MANDATORY)
-
-Before creating the release, you must ensure the codebase and supply chain are secure and free of known vulnerabilities.
-
-1. **Run Local Dependencies Audit:**
-
-   ```bash
-   npm audit
-   ```
-
-   _Fix any `high` or `critical` vulnerabilities identified._
-
-2. **Check GitHub CodeQL & Dependabot Alerts:**
-   Navigate to the repository's **Security** tab on GitHub, or use the project's `vulnerability-scanner` skill to analyze active alerts. Ensure all static analysis findings (e.g., prototype pollution, insecure randomness, ReDoS, shell injections) are addressed and logically committed on a target branch.
-
----
-
-## Phase 1: Pre-Merge
-
-### 1. Create release branch
-
-```bash
-git checkout -b release/v3.x.y
-```
-
-### 2. Determine and sync version
-
-Check current version in `package.json`:
-
-```bash
-grep '"version"' package.json
-```
-
-> **🔴 BRANCH-VERSION PARITY RULE**: The logical version in `package.json` MUST exactly match the release branch name. For example, if you are on `release/v3.7.0`, the version in `package.json` MUST be `3.7.0`.
->
-> - If this is the FIRST time generating a release for a new minor/major branch (e.g., bumping from 3.6.9 to 3.7.0), you MUST ensure the version is bumped to match the new branch logic.
-> - If you are just bumping a patch on the current branch (e.g., 3.6.9 to 3.6.10), use:
->   `npm version patch --no-git-tag-version`
-
-> **⚠️ ATOMIC COMMIT RULE — Version bump MUST happen before committing feature files.**
->
-> **CORRECT order:**
->
-> 1. `npm version patch --no-git-tag-version` ← bump first
-> 2. implement features / fix bugs
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **OR if features are already staged:**
->
-> 1. implement features (do NOT commit yet)
-> 2. `npm version patch --no-git-tag-version` ← bump before committing
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **NEVER do this (creates version mismatch in git history):**
->
-> - ~~commit features → then bump version → commit package.json separately~~
->
-> This ensures that `git show v3.x.y` always contains both code changes and the version bump together.
-> The GitHub release tag will point to a commit that includes ALL changes for that version.
-
-### 3. Regenerate lock file (REQUIRED after version bump)
-
-**Mandatory** — skipping causes `@swc/helpers` lock mismatch and CI failures:
-
-```bash
-npm install
-```
-
-### 4. Finalize CHANGELOG.md
-
-> **🔴 NO MIXUPS RULE**: Ensure you do NOT mix the backlog of the previous version with the new one. The new version section must ONLY contain the features and fixes for the current release.
-
-Replace the `[Unreleased]` header with the new version and date.
-Keep an empty `## [Unreleased]` section above it, separated by a horizontal rule (`---`).
-
-```markdown
-## [Unreleased]
-
----
-
-## [3.7.0] — 2026-04-19
-
-### ✨ New Features
-
-- ...
-
-### 🐛 Bug Fixes
-
-- ...
-
----
-
-## [3.6.9] — 2026-04-19
-```
-
-### 5. Update openapi.yaml version ⚠️ MANDATORY
-
-> **CI will fail** if `docs/reference/openapi.yaml` version ≠ `package.json` version (`check:docs-sync` enforces this).
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ openapi.yaml → $VERSION"
-
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-# Re-run install to assert the workspace lockfile is updated
-npm install
-```
-
-### 6. Update README.md and i18n docs
-
-Manually perform these documentation updates (there is no `/update-docs` workflow — it was deprecated in v3.8):
-
-- Update feature table rows and "What's new in vX.Y.Z" section in `README.md`
-- Sync feature changes to all 40 language `docs/i18n/*/README.md` files (use the same row edits across each translated README)
-- Update the relevant `docs/<AREA>.md` if architecture or counts changed
-- Re-run `npm run check:docs-sync` and `npm run check:docs-all` to catch drift
-
-### 7. Run tests
-
-// turbo
-
-```bash
-npm test
-```
-
-All tests must pass before creating the PR.
-
-### 8. Stage, commit, and push
-
-// turbo-all
-
-```bash
-git add -A
-git commit -m "chore(release): v3.x.y — summary of changes"
-git push origin release/v3.x.y
-```
-
-### 9. Open PR to main
-
-### 9. Open PR to main
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-
-# Extract the exact changelog entry for this version from the root CHANGELOG.md
-awk "/^## \\[$VERSION\\]/{flag=1; print; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md > /tmp/changelog_body.txt
-
-# Append test status and next steps
-echo "" >> /tmp/changelog_body.txt
-echo "### Tests" >> /tmp/changelog_body.txt
-echo "- All tests pass" >> /tmp/changelog_body.txt
-echo "" >> /tmp/changelog_body.txt
-echo "### ⚠️ After merging: run Phase 2 steps to tag, publish, and deploy." >> /tmp/changelog_body.txt
-
-gh pr create \
-  --repo diegosouzapw/OmniRoute \
-  --base main \
-  --head release/v$VERSION \
-  --title "Release v$VERSION" \
-  --body-file /tmp/changelog_body.txt
-```
-
-### 10. 🛑 STOP — Notify User & Await PR Confirmation
-
-**This is a mandatory stop point.** Present the report in the final response and stop. Do not continue to the next phase until the user explicitly approves.
-
-Inform the user:
-
-- PR URL
-- Summary of changes
-- Test results
-- List of files changed
-
-**DO NOT proceed to Phase 2 until the user confirms the PR looks good and merges it.**
-
----
-
-## Phase 2: Post-Merge Validation (Local VPS)
-
-> Run these steps only AFTER the user has merged the PR into `main` and all CI jobs have passed.
-
-### 11. Deploy to Local VPS for Final Validation (MANDATORY)
-
-Before cutting the official git tag and publishing to the world, deploy the `main` branch to the Local VPS for a final homologation test.
-
-```bash
-git checkout main
-git pull origin main
-
-# Build and pack locally
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-
-# Deploy to LOCAL VPS (192.168.0.15)
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-
-# Verify
-curl -s -o /dev/null -w "LOCAL:  HTTP %{http_code}\n" http://192.168.0.15:20128/
-```
-
-### 12. 🛑 STOP — Notify User & Await Final OK
-
-**This is a mandatory stop point.**
-Inform the user that the `main` branch is now running on the Local VPS.
-Wait for the user to manually test and give the **OK**.
-**DO NOT proceed to Phase 3 until the user confirms the local deploy is stable.**
-
----
-
-## Phase 3: Official Launch
-
-> Run these steps only AFTER the user gives the final OK from the Phase 2 local validation.
-
-### 13. Create Git Tag and GitHub Release (MANDATORY)
-
-// turbo
-
-```bash
-git checkout main
-git pull origin main
-VERSION=$(node -p "require('./package.json').version")
-
-# Extracts the changelog section for this version
-NOTES=$(awk "/^## \\[$VERSION\\]/{flag=1; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//')
-if [ -z "$NOTES" ]; then NOTES="OmniRoute v$VERSION Release"; fi
-
-git tag -a "v$VERSION" -m "Release v$VERSION"
-git push origin "v$VERSION"
-gh release create "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES" --target main || gh release edit "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES"
-```
-
-### 14. 🐳 Trigger Docker Hub build (MANDATORY — keep npm and Docker in sync)
-
-> **CRITICAL**: Docker Hub and npm MUST always publish the same version.
-> The Docker image is built automatically via GitHub Actions when a new tag is pushed.
-> After pushing the tag in step 13, **verify the workflow runs**:
-
-```bash
-# Verify the Docker workflow triggered
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 3
-
-# Wait for the Docker build to complete (usually 5–10 min)
-gh run watch --repo diegosouzapw/OmniRoute
-```
-
-### 15. Publish to NPM (Optional/Automated)
-
-Normally handled by CI, but if manual publish is required:
-
-```bash
-npm publish
-```
-
-### 16. Deploy to AKAMAI VPS (Production)
-
-Now that the release is officially cut, deploy it to the Akamai VPS.
-
-```bash
-# Deploy to AKAMAI VPS (69.164.221.35)
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-
-# Verify
-curl -s -o /dev/null -w "AKAMAI: HTTP %{http_code}\n" http://69.164.221.35:20128/
-```
-
-## Phase 4: Release Monitoring & Artifact Validation
-
-> After triggering the official release, actively monitor the CI pipelines until all artifacts are successfully generated. If any pipeline fails, stop and apply the necessary corrections before continuing.
-
-### 18. Monitor CI Pipelines
-
-Wait for and verify the successful completion of the following automated jobs:
-
-1. **Docker Hub Publish**
-2. **Electron Build**
-3. **NPM Registry Publish** (Check with `npm info omniroute version`)
-
-```bash
-# Monitor Docker Hub workflow
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 1
-gh run watch <RUN_ID>
-
-# Monitor Electron build
-gh run list --repo diegosouzapw/OmniRoute --workflow electron-release.yml --limit 1
-gh run watch <RUN_ID>
-
-# Verify NPM version
-npm info omniroute version
-```
-
-### 19. Handle Failures (If Any)
-
-If a workflow fails:
-
-- Use `gh run view <RUN_ID> --log-failed` to identify the error.
-- Apply the fix on the `main` branch.
-- If necessary, re-trigger the workflow using `gh workflow run <workflow_name.yml> --repo diegosouzapw/OmniRoute --ref v3.x.y`
-
-### 20. Preserve release branch
-
-```bash
-# Branch is kept for historical purposes. Do not delete.
-```
-
----
-
-## Notes
-
-- Ensure CHANGELOG, README and `docs/*` are current BEFORE this workflow — run `npm run check:docs-all` and `/version-bump` first (there is no `/update-docs` workflow anymore)
-- The `prepublishOnly` script runs `npm run build:cli` automatically during `npm publish`
-- After npm publish, verify with `npm info omniroute version`
-- Lock file sync errors are caused by skipping `npm install` after version bump
-- Use `gh auth switch -u diegosouzapw` if git push fails with wrong account
-
-## Known CI Pitfalls
-
-| CI failure                                                                | Cause                                                              | Fix                                                                    |
-| ------------------------------------------------------------------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
-| `[docs-sync] FAIL - OpenAPI version differs from package.json`            | Skipped step 5 — `docs/reference/openapi.yaml` version not updated | Run step 5 (`sed -i ...`) and commit                                   |
-| `[docs-sync] FAIL - CHANGELOG.md first section must be "## [Unreleased]"` | `## [Unreleased]` missing or not at top of CHANGELOG               | Add `## [Unreleased]\n\n---\n` before the first versioned `## [x.y.z]` |
-| Electron Linux `.deb` build fails (`FpmTarget` error)                     | `fpm` Ruby gem not installed on `ubuntu-latest` runner             | Already fixed in `electron-release.yml` (`gem install fpm` step)       |
-| Docker Hub `502 error writing layer blob`                                 | Transient Docker Hub network error during ARM64 push               | Re-run the Docker publish workflow; no code change needed              |

.agents/skills/issue-triage/SKILL.md

@@ -1,51 +0,0 @@
----
-name: issue-triage-cx
-description: How to respond to GitHub issues with insufficient information
----
-
-# Issue Triage Workflow
-
-Respond to GitHub issues that need more information before they can be investigated.
-
-## Steps
-
-### 1. Identify issues needing triage
-
-```bash
-gh issue list --state open --limit 20
-```
-
-### 2. Evaluate each issue
-
-Check if the issue has:
-
-- Clear reproduction steps
-- Environment details (OS, Node.js version, OmniRoute version)
-- Error logs/screenshots
-- Expected vs actual behavior
-
-### 3. Respond with triage template
-
-For issues missing information:
-
-```markdown
-Thank you for reporting this issue! To help us investigate, please provide:
-
-1. **OmniRoute version**: (`omniroute --version`)
-2. **Node.js version**: (`node --version`)
-3. **Operating system**: (e.g., Ubuntu 24.04, macOS 15, Windows 11)
-4. **Installation method**: (npm, Docker, source)
-5. **Steps to reproduce**: (exact commands/actions that trigger the issue)
-6. **Error logs**: (paste relevant logs from the console)
-7. **Expected behavior**: (what should happen)
-
-This will help us debug and resolve your issue faster. 🙏
-```
-
-### 4. Label the issue
-
-Add appropriate labels: `needs-info`, `bug`, `enhancement`, `question`, etc.
-
-```bash
-gh issue edit <NUMBER> --add-label "needs-info"
-```

.agents/skills/resolve-issues/SKILL.md

@@ -1,173 +0,0 @@
----
-name: resolve-issues-cx
-description: Fetch all open GitHub issues, analyze bugs, resolve what's possible, triage the rest, wait for user validation, then commit and release
----
-
-# /resolve-issues — Automated Issue Resolution Workflow
-
-## Overview
-
-This workflow fetches all open issues from the project's GitHub repository, classifies them, analyzes bugs, proposes a resolution plan, waits for user validation, and ONLY THEN implements the fixes, commits, and closes the issues on the current release branch (`release/vX.Y.Z`). It does NOT merge or release automatically — the release branch is later merged via PR to main.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads, checks, and GitHub calls.
-- The initial report/plan is a hard stop. Do not edit code, close issues, or commit until the user explicitly approves the report.
-- Keep classification and bug analysis bounded enough to produce the user-facing report before deep implementation work.
-
-> **BRANCH RULE**: All work MUST happen on the current `release/vX.Y.Z` branch. Never create separate `fix/` branches. If no release branch exists yet, create one first using `/generate-release` Phase 1 steps 1–5.
-
-> **⛔ PR PROHIBITION**: If a fix is associated with a contributor's PR, you MUST merge their PR — NEVER close it and re-implement the fix yourself. See `/review-prs` workflow for the full policy. The `gh pr close` command is FORBIDDEN unless the repository owner explicitly requests it.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-// turbo
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch All Open Issues
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh issue list` can be truncated by the tool, silently hiding issues. You MUST use the two-step approach below to guarantee **all** issues are fetched.
-
-**Step 3a — Get Issue numbers only** (small output, never truncated):
-
-- Run: `gh issue list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one issue number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each Issue** (one call per issue):
-
-- For each issue number from step 3a, run:
-  `gh issue view <NUMBER> --repo <owner>/<repo> --json number,title,labels,body,comments,createdAt,author`
-- You may batch these into parallel calls (up to 4 at a time).
-- Sort by oldest first (FIFO).
-
-### 4. Classify Each Issue
-
-For each issue, determine its type:
-
-- **Bug** — Has `bug` label, or body contains error messages, stack traces, "doesn't work", "broken", "crash", "error"
-- **Feature Request** — Has `enhancement`/`feature` label, or body describes new functionality
-- **Question** — Has `question` label, or is asking "how to" something
-- **Other** — Anything else
-
-Focus ONLY on **Bugs** for resolution. Feature requests and questions should be skipped with a note in the final report.
-
-### 5. Deep-Read Each Bug Issue (One-by-One Analysis)
-
-**IMPORTANT**: Read each bug issue thoroughly, one at a time, before moving to the next. This is NOT a batch process — each issue needs focused attention.
-
-#### 5a. Understand the Problem
-
-For each bug issue, perform the full analysis:
-
-1. **Read the entire body** — including Description, Steps to Reproduce, Expected/Actual Behavior, Error Logs, and Screenshots
-2. **Read ALL comments** — including bot triage comments (Kilo, etc.) and owner/community responses. Pay attention to:
-   - Whether someone already responded with a fix
-   - Whether a community member confirmed the issue is resolved
-   - Whether the issue was marked as duplicate by a bot. **WARNING: DO NOT blindly trust bot duplicate labels (e.g., kilo-duplicate). Bots make mistakes. You MUST read the full conversation and do your own independent analysis to determine if it is truly a duplicate or a distinct bug.**
-3. **Identify the claimed error** — extract the exact error message, status code, and provider/model involved
-
-#### 5b. Check Information Sufficiency
-
-Verify the issue contains enough to act on:
-
-- [ ] Clear description of the problem
-- [ ] Steps to reproduce OR error logs
-- [ ] Provider/model/version information
-- [ ] Expected vs actual behavior
-
-#### 5c. Determine Issue Disposition
-
-For each bug, classify into one of 5 actions:
-
-| Disposition                  | When to Apply                                                                                                          | Action                                                  |
-| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
-| **✅ CLOSE — Already Fixed** | Owner responded with fix + no user follow-up, OR community confirmed fix                                               | Close with comment citing which version fixed it        |
-| **✅ CLOSE — Duplicate**     | You have independently verified the issue is a duplicate (do NOT rely solely on bot flags) + user provides no new info | Close referencing the original issue                    |
-| **✅ CLOSE — Stale**         | We requested logs/info > 7 days ago with no reply                                                                      | Close thanking the user, invite to reopen if needed     |
-| **📝 RESPOND — Needs Info**  | Issue is real but missing critical reproduction details                                                                | Comment asking for specifics per `/issue-triage`        |
-| **📝 RESPOND — User Config** | Error is caused by unsupported env (Node version, wrong model path, missing API enablement)                            | Comment explaining the user-side fix                    |
-| **🔧 FIX — Code Change**     | Root cause is confirmed in the codebase                                                                                | Research, propose solution in report, wait for approval |
-
-#### 5d. For "FIX — Code Change" Issues
-
-Before coding, perform deep source analysis to formulate a plan:
-
-1. **Search the codebase** — `grep_search` for error strings, relevant function names, affected files
-2. **Search the web** — for upstream API changes, SDK updates, or breaking changes that explain the bug
-3. **Read the full source file** — don't rely on grep snippets; understand the surrounding logic
-4. **Verify the root cause** — confirm the bug is reproducible based on the code, not just a user misconfiguration
-5. **Formulate a proposed solution** — detail the exact files and lines you will change and how you will solve it.
-6. **Create an Implementation Plan file** — write your proposed solution to `_tasks/features-vX.Y.Z/<ISSUE_NUMBER>-<short-description>.plan.md` (e.g. `_tasks/features-v3.7.6/1810-auto-restore-probe-failed-db.plan.md`) where `vX.Y.Z` is the current branch version. The plan should contain an Overview, Pre-Implementation Checklist, and detailed Implementation Steps (Files, Changes).
-7. **DO NOT modify the codebase yet** — wait for user approval on your report and plan first.
-
-#### 5e. For "RESPOND" Issues
-
-Post a substantive comment that:
-
-- Acknowledges the specific error they reported
-- Explains the likely root cause
-- Provides concrete steps to resolve (version upgrade, env var fix, model path correction)
-- Asks for follow-up info if needed
-
-**Do NOT post generic template responses.** Every comment should reference the user's specific error messages and environment.
-
-### 6. Generate Report & Wait for Validation
-
-Present a summary report to the user detailing your proposed actions. For any bugs that need fixing, explicitly explain your proposed solution (files to change and logic) and point out that it will be implemented on the release branch (`release/vX.Y.Z`) after approval.
-
-| Issue | Title | Status        | Proposed Action / Version                 |
-| ----- | ----- | ------------- | ----------------------------------------- |
-| #N    | Title | ✅ Close      | Already fixed / duplicate (explain why)   |
-| #N    | Title | 🔧 Propose    | Explanation of the code fix to be applied |
-| #N    | Title | 📝 Respond    | Guidance comment to be posted             |
-| #N    | Title | ❓ Needs Info | Triage comment to be posted               |
-| #N    | Title | ⏭️ Skip       | Feature request / not a bug               |
-
-> **⚠️ IMPORTANT**: Do NOT implement code changes, commit, push, or close issues at this step.
-> Wait for the user to review the proposed fixes and respond with **OK** before proceeding.
-
-- If the user says **OK** or approves → Proceed to step 7
-- If the user requests changes → Adjust the proposed solution and present the report again
-- If the user rejects → Revert any accidental changes and stop
-
-### 7. Implement Fixes, Run Tests & Commit (only after user approval)
-
-After the user validates and gives the OK:
-
-1. **Implement the fixes** — modify the codebase according to the approved plan.
-2. **Run tests** — `npm run test:all` (or the specific test file) to ensure 100% pass.
-3. **Update CHANGELOG.md** with all new bug fix entries.
-4. **Commit** each fix individually on the release branch with message format: `fix: <description> (#<issue_number>)`.
-5. **Push** the release branch: `git push origin release/vX.Y.Z`.
-6. **Close resolved issues immediately**. For each issue that was marked as Fixed, run:
-   `gh issue close <NUMBER> --repo <owner>/<repo> --comment "Thank you for reporting! This issue has been fixed and will be included in the next release (vX.Y.Z)."`
-7. Likewise, close `Duplicate` issues referencing the original, close `Needs Info` if stale, and post the required comments.
-8. If the project runs automatic releases or needs a PR, proceed to run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user).
-
-If NO fixes were committed, skip closing and source control steps and just conclude the workflow.

.agents/skills/review-discussions/SKILL.md

@@ -1,126 +0,0 @@
----
-name: review-discussions-cx
-description: Read all open GitHub Discussions, summarize them, respond to pending ones, and create issues from actionable feature requests
----
-
-# /review-discussions — GitHub Discussions Review & Response Workflow
-
-## Overview
-
-This workflow reads all open GitHub Discussions, generates a categorized summary, identifies which ones need a response, drafts and posts replies, and optionally creates issues from actionable feature requests. It follows the same flow used for Issues but adapted for the Discussions forum.
-
-> **Tool mapping note (v3.8):** Where steps below say `browser_subagent`, modern runtimes should substitute with the `gh` CLI — `gh api graphql` for reading discussions and mutations for posting comments. `WebFetch` is acceptable for read-only HTML scraping when GraphQL is overkill, but prefer `gh` for any write actions.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads and GitHub/browser fetches.
-- The summary report is a hard stop. Do not post discussion replies or create issues until the user explicitly approves.
-
-// turbo-all
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Fetch All Open Discussions
-
-- Use `WebFetch` to fetch `https://github.com/<owner>/<repo>/discussions`
-- Parse the discussion list to get all discussion titles, IDs, authors, categories, and dates
-- For each discussion, fetch the individual page to read the full content and all comments/replies
-
-### 3. Summarize All Discussions
-
-For each discussion, extract:
-
-- **Title** and **#Number**
-- **Author** (GitHub username)
-- **Category** (Announcements, General, Ideas, Q&A, Show and tell)
-- **Date** created
-- **Summary** of the original post (1-2 sentences)
-- **Comments count** and key participants
-- **Your previous response** (if any)
-- **Pending action** — whether a response or follow-up is needed
-
-### 4. Present Summary Report to User
-
-Present the full summary to the user organized by category, using a table:
-
-| #   | Category | Title | Author | Date   | Status            |
-| --- | -------- | ----- | ------ | ------ | ----------------- |
-| #N  | Ideas    | Title | @user  | Mar 23 | ⚠️ Needs response |
-| #N  | Q&A      | Title | @user  | Mar 9  | ✅ Answered       |
-| #N  | General  | Title | @user  | Mar 19 | ⚠️ Needs response |
-
-Highlight:
-
-- **⚠️ Needs response** — No reply from maintainer, or a follow-up comment was left unanswered
-- **✅ Answered** — Maintainer already responded
-- **🐛 Bug reported** — A bug was mentioned that needs tracking
-- **💡 Actionable** — Contains a concrete feature request that could become an issue
-
-### 5. Draft & Post Responses
-
-For each discussion that needs a response, draft a reply following these guidelines:
-
-#### Response Style
-
-- **Friendly and professional** — Start with "Hey @username!"
-- **Acknowledge the contribution** — Thank the user for their input
-- **Be specific** — Reference existing features, settings, or dashboard pages if the feature already exists
-- **Provide workarounds** — If the request isn't implemented yet, suggest current alternatives
-- **Commit to action** — If the request is valid, state that you'll open an issue or add it to the roadmap
-- **Keep it concise** — 3-5 paragraphs max
-
-#### Posting via Browser
-
-- Use `browser_subagent` to navigate to each discussion and post the comment
-- **IMPORTANT**: When typing text in GitHub comment boxes via the browser, use only plain ASCII characters:
-  - Use regular hyphens `-` instead of em-dashes
-  - Use `->` instead of arrow symbols
-  - Do NOT use emoji Unicode characters (the browser keyboard may fail on them)
-  - Use `**bold**` and `\`code\`` markdown formatting
-- Click the green "Comment" button (or "Reply" for threaded replies) after typing
-- Verify the comment was posted by checking the page shows the new comment
-
-### 6. Create Issues from Actionable Feature Requests
-
-For discussions that contain concrete, actionable feature requests:
-
-1. Ask the user which ones should become issues
-2. For each approved request, create a GitHub issue via `browser_subagent`:
-   - Navigate to `https://github.com/<owner>/<repo>/issues/new`
-   - **Title**: `<Feature Name> - <Short description>`
-   - **Body** should include:
-     - `## Feature Request` header
-     - `**Source:** Discussion #N by @author`
-     - `## Problem` — What limitation the user hit
-     - `## Proposed Solution` — How it could work
-     - `### Implementation Ideas` — Technical approach
-     - `### Current Workarounds` — What users can do today
-     - `## Additional Context` — Links to related issues/discussions
-   - Add `enhancement` label
-   - Click "Submit new issue" / "Create"
-3. After creation, go back to the original discussion and post a comment linking to the new issue:
-   - "I've opened Issue #N to track this feature request. Follow along there for updates!"
-
-### 7. Final Report
-
-Present a final summary to the user:
-
-| Discussion | Action Taken                       |
-| ---------- | ---------------------------------- |
-| #N — Title | Responded with workarounds         |
-| #N — Title | Responded + created Issue #N       |
-| #N — Title | Already answered, no action needed |
-| #N — Title | Responded to follow-up comment     |
-
-## Notes
-
-- This workflow is **interactive** — always present the summary and wait for user approval before posting responses or creating issues
-- If the user says "pode responder" (or similar approval), proceed with posting all drafted responses
-- For discussions in non-English languages, respond in the same language as the original post
-- Always reference specific dashboard paths, config options, or code files when explaining existing features
-- When a discussion reveals a bug, note it separately from feature requests

.agents/skills/review-prs/SKILL.md

@@ -1,268 +0,0 @@
----
-name: review-prs-cx
-description: Analyze open Pull Requests from the project's GitHub repository, generate a critical report, and optionally implement approved changes
----
-
-# /review-prs — PR Review & Analysis Workflow
-
-## ⛔ ABSOLUTE PROHIBITION — Read Before Anything Else
-
-> **NEVER close a contributor's PR if you intend to use ANY of their code, ideas, or fixes.**
->
-> **NEVER manually integrate contributor code into a release branch and then close their PR.**
->
-> These actions are **STRICTLY FORBIDDEN** under all circumstances:
->
-> 1. ❌ Closing a PR and cherry-picking/copying its code into a release branch
-> 2. ❌ Closing a PR "because of conflicts" and re-implementing the same fix yourself
-> 3. ❌ Closing a PR and committing a "similar" solution inspired by it
-> 4. ❌ Using `gh pr close` on any PR whose content was or will be used
->
-> **Why**: Closing a PR after taking the contributor's work means they get ZERO credit on GitHub — no "Merged" badge, no contribution graph entry, no public record. This is effectively stealing their contribution. An audit found this happened to **37 PRs** in the past.
->
-> **The ONLY acceptable flow**: Resolve conflicts IN the contributor's branch, push fixes TO their branch, then merge THEIR PR via `gh pr merge`. See Step 7 and Step 8 for the exact procedure.
->
-> **When to close a PR**: ONLY when the user (repository owner) explicitly requests it, OR when the PR is clearly spam/malicious, OR when the author themselves asks to close it. In ALL other cases, leave it open.
-
-## Overview
-
-This workflow fetches all open PRs from the project's GitHub repository, performs a critical analysis of each one, generates a detailed report, and waits for user approval before proceeding with implementation. **All improvements are committed on the current release branch** (`release/vX.Y.Z`).
-
-> **BRANCH RULE**: PRs are ALWAYS merged into the current `release/vX.Y.Z` branch, NEVER directly into `main`. The release branch acts as a staging area — only after all PRs are integrated and tests pass does the release branch get merged into `main` via the `/generate-release` workflow.
-
-## Codex Execution Notes
-
-The source Claude command uses `// turbo` and `// turbo-all` as execution hints. In Codex, treat them explicitly as follows:
-
-- `// turbo`: batch independent local reads and small `gh`/`git` calls with `multi_tool_use.parallel`.
-- `// turbo-all`: fan out independent per-PR/per-issue calls in practical batches, usually up to 4 GitHub calls at a time.
-- Do not expand Step 4 into exhaustive CI-log debugging before Step 6. Fetch numbers, metadata, diffs/review comments, quick merge/conflict status, and only inspect extra logs when they directly affect the verdict.
-- Step 6 is a hard stop. In Codex, present the report in the final response and wait for the user before Step 7/8.
-- Do not checkout PR branches, edit files, post PR comments, close PRs, merge, cherry-pick, or run broad fix/test loops until the user explicitly approves the report.
-- If `gh pr diff` is too large, record the limit and use `gh pr view --json files` plus `git fetch refs/pull/...` with `git diff --stat` / `git diff --name-status`; only read targeted hunks needed for confirmed findings.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Read `package.json` to get the repository URL, or use the git remote origin URL
-  // turbo
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-# Bump patch: e.g. 3.3.11 → 3.3.12
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch Open Pull Requests
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh pr list` can be truncated by the tool, silently hiding PRs. You MUST use the two-step approach below to guarantee **all** PRs are fetched.
-
-**Step 3a — Get PR numbers only** (small output, never truncated):
-
-- Run: `gh pr list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one PR number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each PR** (one call per PR):
-
-- For each PR number from step 3a, run:
-  `gh pr view <NUMBER> --repo <owner>/<repo> --json number,title,author,headRefName,baseRefName,body,createdAt,additions,deletions,files`
-- You may batch these into parallel calls (up to 4 at a time).
-
-**Step 3c — Fetch diffs for each PR** (one call per PR, saved to /tmp):
-
-- For each PR number, run:
-  `gh pr diff <NUMBER> --repo <owner>/<repo> > /tmp/pr<NUMBER>.diff`
-- Then read each diff file with the appropriate file-read tool (`Read` in Claude Code; equivalent in your agent runtime).
-
-- For each open PR, collect:
-  - PR number, title, author, branch, number of commits, date
-  - PR description/body
-  - Files changed (diff)
-  - Existing review comments (from bots or humans)
-
-**Verification**: Confirm the count of PRs analyzed matches the count from step 3a before proceeding.
-
-### 3.5 Redirect PR Base Branches to Release Branch
-
-// turbo-all
-
-**⚠️ CRITICAL**: Contributors typically open PRs targeting `main`. Before analyzing or merging, redirect ALL open PRs to target the current release branch instead.
-
-```bash
-# Get the current release branch name
-RELEASE_BRANCH=$(git branch --show-current)  # e.g. release/v3.5.4
-
-# For each open PR that targets main, change its base to the release branch
-for PR_NUM in $(gh pr list --repo <owner>/<repo> --state open --json number,baseRefName --jq '.[] | select(.baseRefName == "main") | .number'); do
-  echo "Redirecting PR #$PR_NUM → $RELEASE_BRANCH"
-  gh pr edit "$PR_NUM" --repo <owner>/<repo> --base "$RELEASE_BRANCH"
-done
-```
-
-This ensures:
-
-1. PRs merge into the release branch, not directly into `main`
-2. Merge conflict detection is accurate against the release branch
-3. The release branch accumulates all changes before the final merge to `main`
-4. If the release branch doesn't exist on remote yet, push it first: `git push origin $RELEASE_BRANCH`
-
-### 4. Analyze Each PR — For each open PR, perform the following analysis:
-
-#### 4a. Feature Assessment
-
-- **Does it make sense?** Evaluate if the feature fills a real gap or solves a valid problem
-- **Alignment** — Check if it aligns with the project's architecture and roadmap
-- **Complexity** — Assess if the scope is reasonable or if it should be split
-
-#### 4b. Code Quality Review
-
-- Check for code duplication
-- Evaluate error handling patterns (consistent with existing codebase?)
-- Check naming conventions and code style
-- Verify TypeScript types (any `any` usage, missing types?)
-
-#### 4c. Security Review
-
-- Check for missing authentication/authorization on new endpoints
-- Check for injection vulnerabilities (URL params, SQL, XSS)
-- Verify input validation on all user-controlled data
-- Check for hardcoded secrets or credentials
-
-#### 4d. Architecture Review
-
-- Does the change follow existing patterns?
-- Are there any breaking changes to public APIs?
-- Is the database schema affected? Migration needed?
-- Impact on performance (N+1 queries, missing indexes?)
-
-#### 4e. Test Coverage
-
-- Does the PR include tests?
-- Are edge cases covered?
-- Would existing tests break?
-
-#### 4f. Cross-Layer (Global) Analysis
-
-Perform a **global impact assessment** to verify whether the PR changes are complete across all layers of the application:
-
-- **Backend → Frontend check**: If the PR adds or modifies backend-only resources (new endpoints, services, data models), evaluate whether corresponding frontend changes are missing:
-  - Does a new endpoint require a new screen/page in the dashboard?
-  - Should there be a new action button, menu item, or navigation link?
-  - Are there new data fields that should be displayed or editable in the UI?
-  - Does a new feature need a toggle, configuration panel, or status indicator?
-- **Frontend → Backend check**: If the PR adds frontend elements, verify the backend support exists:
-  - Are the required API endpoints implemented?
-  - Is the data model sufficient for the new UI components?
-- **Cross-cutting concerns**: Check shared layers (types, DTOs, validation schemas, routes, middleware) for completeness
-- **Document gaps** — If missing layers are detected, list them as **IMPORTANT** issues in the report with concrete suggestions for what should be added
-
-### 5. Generate Report — Create a markdown report for each PR including:
-
-- **PR Summary** — What it does, files affected, commit count
-- **Improvements/Benefits** — Numbered list with impact level (HIGH/MEDIUM/LOW)
-- **Risks & Issues** — Categorized as CRITICAL / IMPORTANT / MINOR
-- **Scoring Table** — Rate across: Feature Relevance, Code Quality, Security, Robustness, Tests
-- **Verdict** — Ready to merge? With mandatory vs optional fixes
-- **Next Steps** — What will happen if approved
-
-### 6. Present to User
-
-- Show the report in the final response and stop. Mark this as a blocking checkpoint awaiting explicit user approval before continuing.
-- Wait for user decision:
-  - **Approved** → Proceed to step 7
-  - **Approved with changes** → Implement the fixes and corrections before merging
-  - **Rejected** → Close the PR or leave a review comment
-
-### 7. Pre-Merge Fixes & CI Green-Lighting (if approved)
-
-> **⚠️ Fixes and Conflict Resolutions MUST be pushed back to the PR branch before merging.** We want the PR itself to be green and fully valid before it integrates.
-
-- **Sync latest fixes & Resolve Conflicts:** Merge the current `release` branch into the PR branch. If there are merge conflicts, you MUST resolve them inside the author's PR branch. NEVER resolve conflicts by closing their PR and doing the work in a separate branch, as this steals credit from the original author.
-- **Implement improvements:** Apply the required fixes identified in the analysis directly on the PR branch (e.g., adding missing API routes, fixing SSRF, applying comments from other agents).
-- **Pushing changes to PR branches:**
-
-  ```bash
-  # Checkout the PR locally
-  gh pr checkout <NUMBER>
-
-  # Apply fixes, commit your changes
-  git commit -m "chore: apply review suggestions and missing layers"
-
-  # Attempt to push directly to the PR branch
-  git push
-  ```
-
-- **Fallback (ONLY for external forks without maintainer edit access):**
-  Using `cherry-pick` instead of fixing the contributor's PR directly is a **LAST RESORT**. You MUST ALWAYS attempt to `git push` your fixes to their branch first.
-  **ONLY if `git push` explicitly fails with a permission/access error** (meaning the contributor unchecked "Allow edits from maintainers" or it's a locked fork), you may use `git cherry-pick` to bring their changes into the release branch and fix the issues locally.
-  Even then, ensure you preserve the contributor's authorship (`git commit --author="Contributor Name <email>"` if creating new commits).
-  Once you have integrated their work into the release branch, **DO NOT close their PR**. Leave it open so the contributor retains credit. Under NO CIRCUMSTANCES should you use `gh pr close`.
-
-- Run the project's test suite locally to verify nothing breaks:
-  // turbo
-- Run: `npm test` or equivalent test command
-
-### 8. Merge into Release Branch (NEVER CLOSE!)
-
-> **⚠️ CRITICAL**: NEVER use `gh pr close` for a PR whose idea or code was accepted. Closing a PR in a contributor's face after taking their idea—or closing it just because it had conflicts—is unacceptable.
-> You MUST ALWAYS resolve conflicts and apply fixes ON THE AUTHOR'S PR BRANCH (unless explicitly locked from edits), and then merge the PR using GitHub so the contributor gets the official "Merged" badge and proper credit on their profile. **Do not use cherry-pick just because it is "easier" than resolving conflicts on their branch.**
-
-Even if the PR had severe conflicts or required significant architectural adjustments, you MUST:
-
-1. Resolve any conflicts and apply the fixes directly to their PR branch (as detailed in step 7) or use cherry-picking into the release branch.
-2. If you managed to fix their branch, merge it into the release branch using the GitHub CLI:
-   `gh pr merge <NUMBER> --repo <owner>/<repo> --squash --body "Integrated into release/vX.Y.Z"`
-3. If you had to use cherry-picking because you couldn't push to their branch, DO NOT close the PR. GitHub will sometimes auto-detect the cherry-picked commits and mark it as Merged. If it doesn't, leave it open. The repository owner will handle it. NEVER run `gh pr close`.
-
-In ALL cases:
-
-- Post a **thank-you comment** on the PR via the GitHub API before or immediately after merging.
-- The message should:
-  - Thank the author by name/username for their contribution.
-  - Explain what was adjusted or improved (if we pushed fixes to their branch or cherry-picked).
-  - Note it will be included in the upcoming release.
-  - Be friendly, professional, and encouraging.
-
-> **⚠️ MANDATORY CHANGELOG CREDIT**: When cherry-picking is used (because the PR branch couldn't be pushed to or `gh pr merge` failed), the contributor does NOT get the automatic GitHub "Merged" badge. In this case, you MUST compensate by adding an explicit entry to `CHANGELOG.md` in the `[Unreleased]` section with `(#PR_NUMBER — thanks @username)` format. This ensures the contributor gets public credit in the release notes even if GitHub doesn't auto-detect the cherry-pick. This is NOT optional — skipping it effectively erases the contributor's work from the release record.
-
-### 9. Sync Local Release Branch
-
-After merging PRs, sync the local release branch to include the new changes:
-
-```bash
-git fetch origin
-git pull origin release/vX.Y.Z
-```
-
-### 10. Continue or Finalize
-
-After processing all approved PRs:
-
-- If more PRs remain, go back to step 7
-- When all PRs are processed, **update CHANGELOG.md** on the release branch with all new entries
-- Run **test coverage** to verify the gate (≥75% statements/lines/functions, ≥70% branches — measured ~82%):
-  ```bash
-  npm run test:coverage
-  ```
-- Fix any test regressions introduced by merged PRs
-- Run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user)
-- The `/generate-release` workflow handles the final merge from `release/vX.Y.Z` → `main`

.agents/skills/version-bump/SKILL.md

@@ -1,347 +0,0 @@
----
-name: version-bump-cx
-description: Bump version, auto-generate CHANGELOG from git commits, update all versioned files, and refresh root + docs/ documentation to reflect the current project state
----
-
-# Version Bump Workflow
-
-Automatically bump the project version, generate CHANGELOG entries from git history since the last tag, update every file that references the version, and refresh project documentation to reflect the current state.
-
-## Codex Execution Notes
-
-- Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads, checks, and GitHub calls.
-- Any user-approval phase is a hard stop: present the report/status in the final response and wait before committing, pushing, tagging, publishing, or deploying.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.4.10` → `3.5.0`.
-
----
-
-## Phase 1: Determine Version
-
-### 1. Read current version and last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-CURRENT_VERSION=$(node -p "require('./package.json').version")
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
-CURRENT_BRANCH=$(git branch --show-current)
-echo "Current version: $CURRENT_VERSION"
-echo "Last tag: $LAST_TAG"
-echo "Current branch: $CURRENT_BRANCH"
-```
-
-### 2. Calculate new version
-
-Apply the patch bump rule:
-
-- If the current patch number is `9`, the new version is `3.(minor+1).0`
-- Otherwise, increment patch: `3.x.y` → `3.x.(y+1)`
-
-If the version was ALREADY bumped (e.g. you are on a release branch and package.json already has the new version), **skip the npm version bump** and use the existing version.
-
-### 3. Bump package.json (if needed)
-
-// turbo
-
-```bash
-# Only if version hasn't been bumped yet
-npm version patch --no-git-tag-version
-```
-
-Or for threshold (y=10):
-
-```bash
-# Manual threshold bump
-VERSION="3.X.0"  # compute manually
-npm version "$VERSION" --no-git-tag-version
-```
-
----
-
-## Phase 2: Generate CHANGELOG from Git History
-
-### 4. Collect commits since last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
-echo "=== Commits since $LAST_TAG ==="
-git log "$LAST_TAG"..HEAD --pretty=format:"%h %s" --no-merges | head -100
-echo ""
-echo "=== Merge commits ==="
-git log "$LAST_TAG"..HEAD --merges --pretty=format:"%h %s" | head -50
-```
-
-### 5. Classify commits and generate CHANGELOG section
-
-Analyze each commit message and classify into categories based on the conventional-commit prefix and content:
-
-| Category            | Patterns                                         |
-| ------------------- | ------------------------------------------------ |
-| ✨ New Features     | `feat:`, `feat(*):`                              |
-| 🐛 Bug Fixes        | `fix:`, `fix(*):`                                |
-| ⚠️ Breaking Changes | `BREAKING CHANGE`, `!:` suffix                   |
-| 🛠️ Maintenance      | `chore:`, `refactor:`, `perf:`, `build:`         |
-| 🧪 Tests            | `test:`, `tests:`                                |
-| 📝 Documentation    | `docs:`                                          |
-| 🔒 Security         | `security:`, CVE references, vulnerability fixes |
-| 🌍 i18n             | translation updates, locale changes              |
-
-For each category with entries, create a markdown section with descriptive bullet points. Use the commit messages but rewrite them to be human-readable and descriptive (not raw commit messages).
-
-**If a commit references a PR number** (e.g. `#880`, `PR #885`), include it in the description.
-
-### 6. Update CHANGELOG.md
-
-Replace the `## [Unreleased]` section content with the generated entries, then add the new versioned section:
-
-```markdown
-## [Unreleased]
-
----
-
-## [NEW_VERSION] — YYYY-MM-DD
-
-### ✨ New Features
-
-- **Feature name:** Description (#PR)
-
-### 🐛 Bug Fixes
-
-- **Fix name:** Description (#PR)
-
-### 🛠️ Maintenance
-
-- **Item:** Description
-
----
-
-## [PREVIOUS_VERSION] — YYYY-MM-DD
-
-...
-```
-
-The date must be today's date in `YYYY-MM-DD` format.
-
----
-
-## Phase 3: Sync Version Across All Files
-
-### 7. Update workspace package.json files and openapi.yaml
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-
-# Update docs/reference/openapi.yaml version
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ docs/reference/openapi.yaml → $VERSION"
-
-# Update workspace packages (open-sse, electron)
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-
-echo "✓ All workspace packages synced to $VERSION"
-```
-
-### 8. Update llm.txt version references
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-OLD_VERSION_PATTERN='[0-9]\+\.[0-9]\+\.[0-9]\+'
-
-# Update "Current version:" line
-sed -i "s/\*\*Current version:\*\* $OLD_VERSION_PATTERN/**Current version:** $VERSION/" llm.txt
-
-# Update "Key Features (vX.Y.Z)" header
-sed -i "s/## Key Features (v$OLD_VERSION_PATTERN)/## Key Features (v$VERSION)/" llm.txt
-
-echo "✓ llm.txt → $VERSION"
-```
-
-### 9. Regenerate lock file
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm install
-echo "✓ Lock file regenerated"
-```
-
----
-
-## Phase 4: Update Root Documentation
-
-Based on the CHANGELOG entries generated in Phase 2, review and update these root-level files if relevant changes warrant updates:
-
-### 10. Review and update root documentation files
-
-For each file below, read the current content and determine if the CHANGELOG entries require any updates. Only modify files where substantive changes have occurred:
-
-| File              | When to update                                                                                                              |
-| ----------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `README.md`       | New providers, major features, stats changes (test count, provider count), badges, installation instructions, feature table |
-| `AGENTS.md`       | Architecture changes, new modules, new commands, new providers, new services/handlers/executors                             |
-| `CONTRIBUTING.md` | Dev workflow changes, new tooling, test infrastructure changes                                                              |
-| `SECURITY.md`     | Security fixes, new auth mechanisms, vulnerability disclosures                                                              |
-| `llm.txt`         | Provider count changes, new features, architecture changes                                                                  |
-
-**Update rules:**
-
-- **README.md**: Update provider count, test count, feature highlights table, badges if any numbers changed. If a new provider was added, add it to the provider table. If a major feature was added, add it to the features section.
-- **AGENTS.md**: If new architecture components (handlers, executors, services, DB modules) were added, update the Architecture section. If new commands were added, update the Build/Test table.
-- **SECURITY.md**: Add new vulnerability fixes or security improvements to the relevant section.
-- **llm.txt**: Update provider count, feature list, version references.
-
-### 11. Review and update docs/ files (excluding i18n/)
-
-For each file in `docs/` (excluding `docs/i18n/`), review if CHANGELOG changes affect it:
-
-| File                                          | When to update                                                     |
-| --------------------------------------------- | ------------------------------------------------------------------ |
-| `docs/reference/API_REFERENCE.md`             | New API endpoints, changed request/response formats                |
-| `docs/architecture/ARCHITECTURE.md`           | New modules, new services, changed data flow                       |
-| `docs/architecture/CODEBASE_DOCUMENTATION.md` | New files, architectural changes, module reorganization            |
-| `docs/architecture/REPOSITORY_MAP.md`         | New folders / files / one-line descriptions                        |
-| `docs/reference/CLI-TOOLS.md`                 | New CLI tool integrations, config format changes                   |
-| `docs/guides/USER_GUIDE.md`                   | UX changes, new dashboard pages, settings changes                  |
-| `docs/reference/PROVIDER_REFERENCE.md`        | New providers (regenerate via `scripts/gen-provider-reference.ts`) |
-| `docs/frameworks/MCP-SERVER.md`               | New MCP tools, changed tool signatures, scope changes              |
-| `docs/frameworks/A2A-SERVER.md`               | New A2A skills, protocol changes                                   |
-| `docs/frameworks/AGENT_PROTOCOLS_GUIDE.md`    | New external agent protocols supported                             |
-| `docs/frameworks/CLOUD_AGENT.md`              | Cloud agent additions (codex-cloud, devin, jules) or API changes   |
-| `docs/architecture/AUTHZ_GUIDE.md`            | New route classifications, policy changes                          |
-| `docs/security/GUARDRAILS.md`                 | New guardrails registered, priority/order changes                  |
-| `docs/security/COMPLIANCE.md`                 | Audit log / retention / no-log policy changes                      |
-| `docs/frameworks/SKILLS.md`                   | Skill framework / registry / built-in skill changes                |
-| `docs/frameworks/MEMORY.md`                   | Memory pipeline / extraction / injection / Qdrant changes          |
-| `docs/frameworks/EVALS.md`                    | Evaluation framework changes, new evaluators                       |
-| `docs/frameworks/WEBHOOKS.md`                 | New webhook events, payload schema changes                         |
-| `docs/routing/REASONING_REPLAY.md`            | Reasoning capture/replay pipeline changes                          |
-| `docs/routing/AUTO-COMBO.md`                  | Routing changes, new strategies, scoring weight changes            |
-| `docs/architecture/RESILIENCE_GUIDE.md`       | Circuit breaker / cooldown / lockout behavior changes              |
-| `docs/security/STEALTH_GUIDE.md`              | TLS / CLI fingerprint changes                                      |
-| `docs/ops/TUNNELS_GUIDE.md`                   | Cloudflare tunnel feature changes                                  |
-| `docs/guides/ELECTRON_GUIDE.md`               | Electron build / signing / packaging changes                       |
-| `docs/guides/TROUBLESHOOTING.md`              | New known issues, resolved problems                                |
-| `docs/ops/RELEASE_CHECKLIST.md`               | Process changes                                                    |
-| `docs/ops/COVERAGE_PLAN.md`                   | Coverage gate adjustments, target metrics                          |
-| `docs/reference/openapi.yaml`                 | Already updated in step 7                                          |
-
-**Only update files where the CHANGELOG entries directly affect the documented content.** Do NOT update files just to bump a version number — only when the documented behavior, features, or architecture has actually changed.
-
----
-
-## Phase 5: Verify
-
-### 12. Run lint check
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm run lint
-```
-
-### 13. Run tests
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm test
-```
-
-### 14. Verify version sync across all files
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-echo "Expected version: $VERSION"
-echo ""
-
-echo "--- package.json ---"
-grep '"version"' package.json | head -1
-
-echo "--- open-sse/package.json ---"
-grep '"version"' open-sse/package.json | head -1
-
-echo "--- electron/package.json ---"
-[ -f electron/package.json ] && grep '"version"' electron/package.json | head -1
-
-echo "--- docs/reference/openapi.yaml ---"
-grep "  version:" docs/reference/openapi.yaml | head -1
-
-echo "--- llm.txt ---"
-grep "Current version:" llm.txt
-
-echo "--- CHANGELOG.md (first versioned entry) ---"
-grep "^## \[" CHANGELOG.md | head -2
-```
-
-### 15. 🛑 STOP — Present Summary to User
-
-**STOP** and present a summary to the user including:
-
-- Old version → New version
-- CHANGELOG entries generated
-- Files modified
-- Test results
-- Any documentation updates made
-
-**Wait for the user to confirm before committing.**
-
----
-
-## Phase 6: Commit (only after user approval)
-
-### 16. Stage and commit
-
-// turbo-all
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-git add -A
-VERSION=$(node -p "require('./package.json').version")
-git commit -m "chore(release): bump to v$VERSION — changelog, docs, version sync"
-```
-
----
-
-## Notes
-
-- This workflow does **NOT** create tags, releases, or deploy. Use `/generate-release` for the full release cycle after this.
-- This workflow does **NOT** update `docs/i18n/` translations. Translation updates are handled manually or via release tooling — there is no `/update-i18n` workflow shipped in this repo.
-- The CHANGELOG generation is based on git commits since the last tag. If there are no new commits, the workflow should inform the user and stop.
-- Always verify the generated CHANGELOG entries make sense — raw commit messages may need rewriting for clarity.
-- If the version was already bumped (e.g. you're on a `release/vX.Y.Z` branch), skip the `npm version` step and use the existing version.
-
-## Version Touchpoints Checklist
-
-| File                          | Field/Pattern                                               |
-| ----------------------------- | ----------------------------------------------------------- |
-| `package.json`                | `"version": "X.Y.Z"`                                        |
-| `open-sse/package.json`       | `"version": "X.Y.Z"`                                        |
-| `electron/package.json`       | `"version": "X.Y.Z"`                                        |
-| `docs/reference/openapi.yaml` | `version: X.Y.Z`                                            |
-| `llm.txt`                     | `**Current version:** X.Y.Z` and `## Key Features (vX.Y.Z)` |
-| `CHANGELOG.md`                | `## [X.Y.Z] — YYYY-MM-DD`                                   |

.agents/workflows/capture-release-evidences-ag.md

@@ -1,51 +0,0 @@
----
-description: Automatically run a browser-automation agent to visually validate all new UI features from the current release and capture evidence WebP recordings of the changes.
----
-
-# Capture Release Evidences Workflow
-
-Use this workflow to automatically drive a browser-automation agent to explore the newly deployed or locally running application and record evidence of the UI changes introduced in the latest release.
-
-> **Tool mapping note (v3.8):** The `browser_subagent` tool referenced below is specific to an earlier agent runtime. In Claude Code, substitute with the available browser MCP tools (e.g. `mcp__claude-in-chrome__*`) for navigation/screenshots, plus the `Write` tool for saving artifacts. The high-level steps remain the same regardless of the browser-automation surface in use.
-
-## Prerequisites
-
-- OmniRoute must be actively running and accessible (e.g. locally at `http://localhost:20128` or on the Local VPS at `http://192.168.0.15:20128`).
-- The user must provide the target URL to be tested, or default to `http://192.168.0.15:20128`.
-
-## Workflow Steps
-
-### 1. Identify Target Features
-
-Review the `CHANGELOG.md` for the latest version to map out the new UI elements. For example:
-
-- **CLI Tools Settings**
-- **New Provider/Model Listings (e.g., Gemini 3.1, Qoder PAT)**
-- **New Feature Modals**
-
-### 2. Run the Browser Subagent
-
-For each identified feature, invoke the `browser_subagent` using the `default_api:browser_subagent` tool.
-**Important Task Guidelines for the Subagent:**
-
-- `TaskName`: Give it a clear name like "Validate CLIProxyAPI Tool Tab".
-- `TaskSummary`: "Navigate to the CLI Tools tab and verify the new Integration settings."
-- `Task`: Provide unambiguous instructions for the subagent, such as: "Navigate to http://192.168.0.15:20128/dashboard. Click on the 'Settings' or 'CLI Tools' nav link. Scroll down to find the CLIProxyAPI integration card. Hover over it to trigger UI state. Verify the components render correctly and exit."
-- `RecordingName`: Ensure it describes the feature (e.g. `v3_4_5_cli_proxy_api`). This is required and strictly automatically saved as a WebP artifacts video by the system.
-
-_(Note: The `browser_subagent` automatically creates a WebP recording named by the `RecordingName` parameter. No additional tools for screenshots are needed.)_
-
-### 3. Generate Report Artifact
-
-After the `browser_subagent` finishes its sessions, generate a final Markdown artifact (using `Write` and `IsArtifact=true`) to present the recordings inline to the user using the `![caption](/absolute/path/to/media.webp)` syntax.
-
-### Example Invocation
-
-\```json
-{
-"TaskName": "Validating Qoder PAT Configuration UI",
-"TaskSummary": "Validates the Qoder provider configuration modal",
-"Task": "Go to http://192.168.0.15:20128/dashboard. Click on the 'Providers' tab. Find 'Qoder' in the list. Click 'Add Token' or 'Configure'. Type 'test_token' and submit. Return when done.",
-"RecordingName": "qoder_pat_ui_validation"
-}
-\```

.agents/workflows/deploy-vps-akamai-ag.md

@@ -1,39 +0,0 @@
----
-description: Deploy the latest OmniRoute code to the Akamai VPS (69.164.221.35)
----
-
-# Deploy to Akamai VPS Workflow
-
-Deploy OmniRoute to the Akamai VPS using `npm pack + scp` + PM2.
-
-**Akamai VPS:** `69.164.221.35`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Akamai VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-```

.agents/workflows/deploy-vps-both-ag.md

@@ -1,49 +0,0 @@
----
-description: Deploy the latest OmniRoute code to BOTH the Akamai VPS and the Local VPS
----
-
-# Deploy to VPS (Both) Workflow
-
-Deploy OmniRoute to the production VPSs using `npm pack + scp` + PM2.
-
-**Akamai VPS:** `69.164.221.35`
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-**PM2 entry:** `/usr/lib/node_modules/omniroute/app/server.js`
-
-> [!IMPORTANT]
-> The npm registry rejects packages > 100MB, so deployment uses **npm pack + scp**.
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to both VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/ && scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.agents/workflows/deploy-vps-local-ag.md

@@ -1,39 +0,0 @@
----
-description: Deploy the latest OmniRoute code to the Local VPS (192.168.0.15)
----
-
-# Deploy to Local VPS Workflow
-
-Deploy OmniRoute to the Local VPS using `npm pack + scp` + PM2.
-
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Local VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.agents/workflows/generate-release-ag.md

@@ -1,362 +0,0 @@
----
-description: Create a new release, bump version up to the .10 patch threshold, update changelog, and manage Pull Requests
----
-
-# Generate Release Workflow
-
-Bump version, finalize CHANGELOG, commit, open a **PR to main** and wait for user confirmation before tagging, publishing, and deploying.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.8.10` → `3.9.0`.
-
-> **🔴 SINGLE BRANCH RULE**: The `release/vX.Y.Z` branch is the **ONLY** development branch for the entire release cycle. ALL work — bug fixes, feature implementations, PR integrations, issue resolutions — MUST be committed directly on this branch. Never create separate `fix/`, `feat/`, or topic branches. When running `/resolve-issues`, `/implement-features`, or `/review-prs`, always work on the current release branch.
-
----
-
-## ⚠️ Two-Phase Flow
-
-```
-Phase 1 (automated): bump → docs → i18n → commit → push → open PR
-  ↕  🛑 STOP: Notify user, wait for PR confirmation
-Phase 2 (post-merge): tag → publish → GitHub release → Docker → deploy
-```
-
-**NEVER push directly to main or create tags before the user confirms the PR.**
-
----
-
-## Phase 0: Security Verification (MANDATORY)
-
-Before creating the release, you must ensure the codebase and supply chain are secure and free of known vulnerabilities.
-
-1. **Run Local Dependencies Audit:**
-
-   ```bash
-   npm audit
-   ```
-
-   _Fix any `high` or `critical` vulnerabilities identified._
-
-2. **Check GitHub CodeQL & Dependabot Alerts:**
-   Navigate to the repository's **Security** tab on GitHub, or use the project's `vulnerability-scanner` skill to analyze active alerts. Ensure all static analysis findings (e.g., prototype pollution, insecure randomness, ReDoS, shell injections) are addressed and logically committed on a target branch.
-
----
-
-## Phase 1: Pre-Merge
-
-### 1. Create release branch
-
-```bash
-git checkout -b release/v3.x.y
-```
-
-### 2. Determine and sync version
-
-Check current version in `package.json`:
-
-```bash
-grep '"version"' package.json
-```
-
-> **🔴 BRANCH-VERSION PARITY RULE**: The logical version in `package.json` MUST exactly match the release branch name. For example, if you are on `release/v3.7.0`, the version in `package.json` MUST be `3.7.0`.
->
-> - If this is the FIRST time generating a release for a new minor/major branch (e.g., bumping from 3.6.9 to 3.7.0), you MUST ensure the version is bumped to match the new branch logic.
-> - If you are just bumping a patch on the current branch (e.g., 3.6.9 to 3.6.10), use:
->   `npm version patch --no-git-tag-version`
-
-> **⚠️ ATOMIC COMMIT RULE — Version bump MUST happen before committing feature files.**
->
-> **CORRECT order:**
->
-> 1. `npm version patch --no-git-tag-version` ← bump first
-> 2. implement features / fix bugs
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **OR if features are already staged:**
->
-> 1. implement features (do NOT commit yet)
-> 2. `npm version patch --no-git-tag-version` ← bump before committing
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **NEVER do this (creates version mismatch in git history):**
->
-> - ~~commit features → then bump version → commit package.json separately~~
->
-> This ensures that `git show v3.x.y` always contains both code changes and the version bump together.
-> The GitHub release tag will point to a commit that includes ALL changes for that version.
-
-### 3. Regenerate lock file (REQUIRED after version bump)
-
-**Mandatory** — skipping causes `@swc/helpers` lock mismatch and CI failures:
-
-```bash
-npm install
-```
-
-### 4. Finalize CHANGELOG.md
-
-> **🔴 NO MIXUPS RULE**: Ensure you do NOT mix the backlog of the previous version with the new one. The new version section must ONLY contain the features and fixes for the current release.
-
-Replace the `[Unreleased]` header with the new version and date.
-Keep an empty `## [Unreleased]` section above it, separated by a horizontal rule (`---`).
-
-```markdown
-## [Unreleased]
-
----
-
-## [3.7.0] — 2026-04-19
-
-### ✨ New Features
-
-- ...
-
-### 🐛 Bug Fixes
-
-- ...
-
----
-
-## [3.6.9] — 2026-04-19
-```
-
-### 5. Update openapi.yaml version ⚠️ MANDATORY
-
-> **CI will fail** if `docs/reference/openapi.yaml` version ≠ `package.json` version (`check:docs-sync` enforces this).
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ openapi.yaml → $VERSION"
-
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-# Re-run install to assert the workspace lockfile is updated
-npm install
-```
-
-### 6. Update README.md and i18n docs
-
-Manually perform these documentation updates (there is no `/update-docs` workflow — it was deprecated in v3.8):
-
-- Update feature table rows and "What's new in vX.Y.Z" section in `README.md`
-- Sync feature changes to all 40 language `docs/i18n/*/README.md` files (use the same row edits across each translated README)
-- Update the relevant `docs/<AREA>.md` if architecture or counts changed
-- Re-run `npm run check:docs-sync` and `npm run check:docs-all` to catch drift
-
-### 7. Run tests
-
-// turbo
-
-```bash
-npm test
-```
-
-All tests must pass before creating the PR.
-
-### 8. Stage, commit, and push
-
-// turbo-all
-
-```bash
-git add -A
-git commit -m "chore(release): v3.x.y — summary of changes"
-git push origin release/v3.x.y
-```
-
-### 9. Open PR to main
-
-### 9. Open PR to main
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-
-# Extract the exact changelog entry for this version from the root CHANGELOG.md
-awk "/^## \\[$VERSION\\]/{flag=1; print; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md > /tmp/changelog_body.txt
-
-# Append test status and next steps
-echo "" >> /tmp/changelog_body.txt
-echo "### Tests" >> /tmp/changelog_body.txt
-echo "- All tests pass" >> /tmp/changelog_body.txt
-echo "" >> /tmp/changelog_body.txt
-echo "### ⚠️ After merging: run Phase 2 steps to tag, publish, and deploy." >> /tmp/changelog_body.txt
-
-gh pr create \
-  --repo diegosouzapw/OmniRoute \
-  --base main \
-  --head release/v$VERSION \
-  --title "Release v$VERSION" \
-  --body-file /tmp/changelog_body.txt
-```
-
-### 10. 🛑 STOP — Notify User & Await PR Confirmation
-
-**This is a mandatory stop point.** Present the report in the final response and stop. Do not continue to the next phase until the user explicitly approves.
-
-Inform the user:
-
-- PR URL
-- Summary of changes
-- Test results
-- List of files changed
-
-**DO NOT proceed to Phase 2 until the user confirms the PR looks good and merges it.**
-
----
-
-## Phase 2: Post-Merge Validation (Local VPS)
-
-> Run these steps only AFTER the user has merged the PR into `main` and all CI jobs have passed.
-
-### 11. Deploy to Local VPS for Final Validation (MANDATORY)
-
-Before cutting the official git tag and publishing to the world, deploy the `main` branch to the Local VPS for a final homologation test.
-
-```bash
-git checkout main
-git pull origin main
-
-# Build and pack locally
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-
-# Deploy to LOCAL VPS (192.168.0.15)
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-
-# Verify
-curl -s -o /dev/null -w "LOCAL:  HTTP %{http_code}\n" http://192.168.0.15:20128/
-```
-
-### 12. 🛑 STOP — Notify User & Await Final OK
-
-**This is a mandatory stop point.**
-Inform the user that the `main` branch is now running on the Local VPS.
-Wait for the user to manually test and give the **OK**.
-**DO NOT proceed to Phase 3 until the user confirms the local deploy is stable.**
-
----
-
-## Phase 3: Official Launch
-
-> Run these steps only AFTER the user gives the final OK from the Phase 2 local validation.
-
-### 13. Create Git Tag and GitHub Release (MANDATORY)
-
-// turbo
-
-```bash
-git checkout main
-git pull origin main
-VERSION=$(node -p "require('./package.json').version")
-
-# Extracts the changelog section for this version
-NOTES=$(awk "/^## \\[$VERSION\\]/{flag=1; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//')
-if [ -z "$NOTES" ]; then NOTES="OmniRoute v$VERSION Release"; fi
-
-git tag -a "v$VERSION" -m "Release v$VERSION"
-git push origin "v$VERSION"
-gh release create "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES" --target main || gh release edit "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES"
-```
-
-### 14. 🐳 Trigger Docker Hub build (MANDATORY — keep npm and Docker in sync)
-
-> **CRITICAL**: Docker Hub and npm MUST always publish the same version.
-> The Docker image is built automatically via GitHub Actions when a new tag is pushed.
-> After pushing the tag in step 13, **verify the workflow runs**:
-
-```bash
-# Verify the Docker workflow triggered
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 3
-
-# Wait for the Docker build to complete (usually 5–10 min)
-gh run watch --repo diegosouzapw/OmniRoute
-```
-
-### 15. Publish to NPM (Optional/Automated)
-
-Normally handled by CI, but if manual publish is required:
-
-```bash
-npm publish
-```
-
-### 16. Deploy to AKAMAI VPS (Production)
-
-Now that the release is officially cut, deploy it to the Akamai VPS.
-
-```bash
-# Deploy to AKAMAI VPS (69.164.221.35)
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-
-# Verify
-curl -s -o /dev/null -w "AKAMAI: HTTP %{http_code}\n" http://69.164.221.35:20128/
-```
-
-## Phase 4: Release Monitoring & Artifact Validation
-
-> After triggering the official release, actively monitor the CI pipelines until all artifacts are successfully generated. If any pipeline fails, stop and apply the necessary corrections before continuing.
-
-### 18. Monitor CI Pipelines
-
-Wait for and verify the successful completion of the following automated jobs:
-
-1. **Docker Hub Publish**
-2. **Electron Build**
-3. **NPM Registry Publish** (Check with `npm info omniroute version`)
-
-```bash
-# Monitor Docker Hub workflow
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 1
-gh run watch <RUN_ID>
-
-# Monitor Electron build
-gh run list --repo diegosouzapw/OmniRoute --workflow electron-release.yml --limit 1
-gh run watch <RUN_ID>
-
-# Verify NPM version
-npm info omniroute version
-```
-
-### 19. Handle Failures (If Any)
-
-If a workflow fails:
-
-- Use `gh run view <RUN_ID> --log-failed` to identify the error.
-- Apply the fix on the `main` branch.
-- If necessary, re-trigger the workflow using `gh workflow run <workflow_name.yml> --repo diegosouzapw/OmniRoute --ref v3.x.y`
-
-### 20. Preserve release branch
-
-```bash
-# Branch is kept for historical purposes. Do not delete.
-```
-
----
-
-## Notes
-
-- Ensure CHANGELOG, README and `docs/*` are current BEFORE this workflow — run `npm run check:docs-all` and `/version-bump` first (there is no `/update-docs` workflow anymore)
-- The `prepublishOnly` script runs `npm run build:cli` automatically during `npm publish`
-- After npm publish, verify with `npm info omniroute version`
-- Lock file sync errors are caused by skipping `npm install` after version bump
-- Use `gh auth switch -u diegosouzapw` if git push fails with wrong account
-
-## Known CI Pitfalls
-
-| CI failure                                                                | Cause                                                              | Fix                                                                    |
-| ------------------------------------------------------------------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
-| `[docs-sync] FAIL - OpenAPI version differs from package.json`            | Skipped step 5 — `docs/reference/openapi.yaml` version not updated | Run step 5 (`sed -i ...`) and commit                                   |
-| `[docs-sync] FAIL - CHANGELOG.md first section must be "## [Unreleased]"` | `## [Unreleased]` missing or not at top of CHANGELOG               | Add `## [Unreleased]\n\n---\n` before the first versioned `## [x.y.z]` |
-| Electron Linux `.deb` build fails (`FpmTarget` error)                     | `fpm` Ruby gem not installed on `ubuntu-latest` runner             | Already fixed in `electron-release.yml` (`gem install fpm` step)       |
-| Docker Hub `502 error writing layer blob`                                 | Transient Docker Hub network error during ARM64 push               | Re-run the Docker publish workflow; no code change needed              |

.agents/workflows/issue-triage-ag.md

@@ -1,50 +0,0 @@
----
-description: How to respond to GitHub issues with insufficient information
----
-
-# Issue Triage Workflow
-
-Respond to GitHub issues that need more information before they can be investigated.
-
-## Steps
-
-### 1. Identify issues needing triage
-
-```bash
-gh issue list --state open --limit 20
-```
-
-### 2. Evaluate each issue
-
-Check if the issue has:
-
-- Clear reproduction steps
-- Environment details (OS, Node.js version, OmniRoute version)
-- Error logs/screenshots
-- Expected vs actual behavior
-
-### 3. Respond with triage template
-
-For issues missing information:
-
-```markdown
-Thank you for reporting this issue! To help us investigate, please provide:
-
-1. **OmniRoute version**: (`omniroute --version`)
-2. **Node.js version**: (`node --version`)
-3. **Operating system**: (e.g., Ubuntu 24.04, macOS 15, Windows 11)
-4. **Installation method**: (npm, Docker, source)
-5. **Steps to reproduce**: (exact commands/actions that trigger the issue)
-6. **Error logs**: (paste relevant logs from the console)
-7. **Expected behavior**: (what should happen)
-
-This will help us debug and resolve your issue faster. 🙏
-```
-
-### 4. Label the issue
-
-Add appropriate labels: `needs-info`, `bug`, `enhancement`, `question`, etc.
-
-```bash
-gh issue edit <NUMBER> --add-label "needs-info"
-```

.agents/workflows/resolve-issues-ag.md

@@ -1,166 +0,0 @@
----
-description: Fetch all open GitHub issues, analyze bugs, resolve what's possible, triage the rest, wait for user validation, then commit and release
----
-
-# /resolve-issues — Automated Issue Resolution Workflow
-
-## Overview
-
-This workflow fetches all open issues from the project's GitHub repository, classifies them, analyzes bugs, proposes a resolution plan, waits for user validation, and ONLY THEN implements the fixes, commits, and closes the issues on the current release branch (`release/vX.Y.Z`). It does NOT merge or release automatically — the release branch is later merged via PR to main.
-
-> **BRANCH RULE**: All work MUST happen on the current `release/vX.Y.Z` branch. Never create separate `fix/` branches. If no release branch exists yet, create one first using `/generate-release` Phase 1 steps 1–5.
-
-> **⛔ PR PROHIBITION**: If a fix is associated with a contributor's PR, you MUST merge their PR — NEVER close it and re-implement the fix yourself. See `/review-prs` workflow for the full policy. The `gh pr close` command is FORBIDDEN unless the repository owner explicitly requests it.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-// turbo
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch All Open Issues
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh issue list` can be truncated by the tool, silently hiding issues. You MUST use the two-step approach below to guarantee **all** issues are fetched.
-
-**Step 3a — Get Issue numbers only** (small output, never truncated):
-
-- Run: `gh issue list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one issue number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each Issue** (one call per issue):
-
-- For each issue number from step 3a, run:
-  `gh issue view <NUMBER> --repo <owner>/<repo> --json number,title,labels,body,comments,createdAt,author`
-- You may batch these into parallel calls (up to 4 at a time).
-- Sort by oldest first (FIFO).
-
-### 4. Classify Each Issue
-
-For each issue, determine its type:
-
-- **Bug** — Has `bug` label, or body contains error messages, stack traces, "doesn't work", "broken", "crash", "error"
-- **Feature Request** — Has `enhancement`/`feature` label, or body describes new functionality
-- **Question** — Has `question` label, or is asking "how to" something
-- **Other** — Anything else
-
-Focus ONLY on **Bugs** for resolution. Feature requests and questions should be skipped with a note in the final report.
-
-### 5. Deep-Read Each Bug Issue (One-by-One Analysis)
-
-**IMPORTANT**: Read each bug issue thoroughly, one at a time, before moving to the next. This is NOT a batch process — each issue needs focused attention.
-
-#### 5a. Understand the Problem
-
-For each bug issue, perform the full analysis:
-
-1. **Read the entire body** — including Description, Steps to Reproduce, Expected/Actual Behavior, Error Logs, and Screenshots
-2. **Read ALL comments** — including bot triage comments (Kilo, etc.) and owner/community responses. Pay attention to:
-   - Whether someone already responded with a fix
-   - Whether a community member confirmed the issue is resolved
-   - Whether the issue was marked as duplicate by a bot. **WARNING: DO NOT blindly trust bot duplicate labels (e.g., kilo-duplicate). Bots make mistakes. You MUST read the full conversation and do your own independent analysis to determine if it is truly a duplicate or a distinct bug.**
-3. **Identify the claimed error** — extract the exact error message, status code, and provider/model involved
-
-#### 5b. Check Information Sufficiency
-
-Verify the issue contains enough to act on:
-
-- [ ] Clear description of the problem
-- [ ] Steps to reproduce OR error logs
-- [ ] Provider/model/version information
-- [ ] Expected vs actual behavior
-
-#### 5c. Determine Issue Disposition
-
-For each bug, classify into one of 5 actions:
-
-| Disposition                  | When to Apply                                                                                                          | Action                                                  |
-| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
-| **✅ CLOSE — Already Fixed** | Owner responded with fix + no user follow-up, OR community confirmed fix                                               | Close with comment citing which version fixed it        |
-| **✅ CLOSE — Duplicate**     | You have independently verified the issue is a duplicate (do NOT rely solely on bot flags) + user provides no new info | Close referencing the original issue                    |
-| **✅ CLOSE — Stale**         | We requested logs/info > 7 days ago with no reply                                                                      | Close thanking the user, invite to reopen if needed     |
-| **📝 RESPOND — Needs Info**  | Issue is real but missing critical reproduction details                                                                | Comment asking for specifics per `/issue-triage`        |
-| **📝 RESPOND — User Config** | Error is caused by unsupported env (Node version, wrong model path, missing API enablement)                            | Comment explaining the user-side fix                    |
-| **🔧 FIX — Code Change**     | Root cause is confirmed in the codebase                                                                                | Research, propose solution in report, wait for approval |
-
-#### 5d. For "FIX — Code Change" Issues
-
-Before coding, perform deep source analysis to formulate a plan:
-
-1. **Search the codebase** — `grep_search` for error strings, relevant function names, affected files
-2. **Search the web** — for upstream API changes, SDK updates, or breaking changes that explain the bug
-3. **Read the full source file** — don't rely on grep snippets; understand the surrounding logic
-4. **Verify the root cause** — confirm the bug is reproducible based on the code, not just a user misconfiguration
-5. **Formulate a proposed solution** — detail the exact files and lines you will change and how you will solve it.
-6. **Create an Implementation Plan file** — write your proposed solution to `_tasks/features-vX.Y.Z/<ISSUE_NUMBER>-<short-description>.plan.md` (e.g. `_tasks/features-v3.7.6/1810-auto-restore-probe-failed-db.plan.md`) where `vX.Y.Z` is the current branch version. The plan should contain an Overview, Pre-Implementation Checklist, and detailed Implementation Steps (Files, Changes).
-7. **DO NOT modify the codebase yet** — wait for user approval on your report and plan first.
-
-#### 5e. For "RESPOND" Issues
-
-Post a substantive comment that:
-
-- Acknowledges the specific error they reported
-- Explains the likely root cause
-- Provides concrete steps to resolve (version upgrade, env var fix, model path correction)
-- Asks for follow-up info if needed
-
-**Do NOT post generic template responses.** Every comment should reference the user's specific error messages and environment.
-
-### 6. Generate Report & Wait for Validation
-
-Present a summary report to the user detailing your proposed actions. For any bugs that need fixing, explicitly explain your proposed solution (files to change and logic) and point out that it will be implemented on the release branch (`release/vX.Y.Z`) after approval.
-
-| Issue | Title | Status        | Proposed Action / Version                 |
-| ----- | ----- | ------------- | ----------------------------------------- |
-| #N    | Title | ✅ Close      | Already fixed / duplicate (explain why)   |
-| #N    | Title | 🔧 Propose    | Explanation of the code fix to be applied |
-| #N    | Title | 📝 Respond    | Guidance comment to be posted             |
-| #N    | Title | ❓ Needs Info | Triage comment to be posted               |
-| #N    | Title | ⏭️ Skip       | Feature request / not a bug               |
-
-> **⚠️ IMPORTANT**: Do NOT implement code changes, commit, push, or close issues at this step.
-> Wait for the user to review the proposed fixes and respond with **OK** before proceeding.
-
-- If the user says **OK** or approves → Proceed to step 7
-- If the user requests changes → Adjust the proposed solution and present the report again
-- If the user rejects → Revert any accidental changes and stop
-
-### 7. Implement Fixes, Run Tests & Commit (only after user approval)
-
-After the user validates and gives the OK:
-
-1. **Implement the fixes** — modify the codebase according to the approved plan.
-2. **Run tests** — `npm run test:all` (or the specific test file) to ensure 100% pass.
-3. **Update CHANGELOG.md** with all new bug fix entries.
-4. **Commit** each fix individually on the release branch with message format: `fix: <description> (#<issue_number>)`.
-5. **Push** the release branch: `git push origin release/vX.Y.Z`.
-6. **Close resolved issues immediately**. For each issue that was marked as Fixed, run:
-   `gh issue close <NUMBER> --repo <owner>/<repo> --comment "Thank you for reporting! This issue has been fixed and will be included in the next release (vX.Y.Z)."`
-7. Likewise, close `Duplicate` issues referencing the original, close `Needs Info` if stale, and post the required comments.
-8. If the project runs automatic releases or needs a PR, proceed to run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user).
-
-If NO fixes were committed, skip closing and source control steps and just conclude the workflow.

.agents/workflows/review-discussions-ag.md

@@ -1,120 +0,0 @@
----
-description: Read all open GitHub Discussions, summarize them, respond to pending ones, and create issues from actionable feature requests
----
-
-# /review-discussions — GitHub Discussions Review & Response Workflow
-
-## Overview
-
-This workflow reads all open GitHub Discussions, generates a categorized summary, identifies which ones need a response, drafts and posts replies, and optionally creates issues from actionable feature requests. It follows the same flow used for Issues but adapted for the Discussions forum.
-
-> **Tool mapping note (v3.8):** Where steps below say `browser_subagent`, in modern Claude Code substitute with the `gh` CLI via Bash — `gh api graphql` for reading discussions and mutations for posting comments. `WebFetch` is acceptable for read-only HTML scraping when GraphQL is overkill, but prefer `gh` for any write actions.
-
-// turbo-all
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Fetch All Open Discussions
-
-- Use `WebFetch` to fetch `https://github.com/<owner>/<repo>/discussions`
-- Parse the discussion list to get all discussion titles, IDs, authors, categories, and dates
-- For each discussion, fetch the individual page to read the full content and all comments/replies
-
-### 3. Summarize All Discussions
-
-For each discussion, extract:
-
-- **Title** and **#Number**
-- **Author** (GitHub username)
-- **Category** (Announcements, General, Ideas, Q&A, Show and tell)
-- **Date** created
-- **Summary** of the original post (1-2 sentences)
-- **Comments count** and key participants
-- **Your previous response** (if any)
-- **Pending action** — whether a response or follow-up is needed
-
-### 4. Present Summary Report to User
-
-Present the full summary to the user organized by category, using a table:
-
-| #   | Category | Title | Author | Date   | Status            |
-| --- | -------- | ----- | ------ | ------ | ----------------- |
-| #N  | Ideas    | Title | @user  | Mar 23 | ⚠️ Needs response |
-| #N  | Q&A      | Title | @user  | Mar 9  | ✅ Answered       |
-| #N  | General  | Title | @user  | Mar 19 | ⚠️ Needs response |
-
-Highlight:
-
-- **⚠️ Needs response** — No reply from maintainer, or a follow-up comment was left unanswered
-- **✅ Answered** — Maintainer already responded
-- **🐛 Bug reported** — A bug was mentioned that needs tracking
-- **💡 Actionable** — Contains a concrete feature request that could become an issue
-
-### 5. Draft & Post Responses
-
-For each discussion that needs a response, draft a reply following these guidelines:
-
-#### Response Style
-
-- **Friendly and professional** — Start with "Hey @username!"
-- **Acknowledge the contribution** — Thank the user for their input
-- **Be specific** — Reference existing features, settings, or dashboard pages if the feature already exists
-- **Provide workarounds** — If the request isn't implemented yet, suggest current alternatives
-- **Commit to action** — If the request is valid, state that you'll open an issue or add it to the roadmap
-- **Keep it concise** — 3-5 paragraphs max
-
-#### Posting via Browser
-
-- Use `browser_subagent` to navigate to each discussion and post the comment
-- **IMPORTANT**: When typing text in GitHub comment boxes via the browser, use only plain ASCII characters:
-  - Use regular hyphens `-` instead of em-dashes
-  - Use `->` instead of arrow symbols
-  - Do NOT use emoji Unicode characters (the browser keyboard may fail on them)
-  - Use `**bold**` and `\`code\`` markdown formatting
-- Click the green "Comment" button (or "Reply" for threaded replies) after typing
-- Verify the comment was posted by checking the page shows the new comment
-
-### 6. Create Issues from Actionable Feature Requests
-
-For discussions that contain concrete, actionable feature requests:
-
-1. Ask the user which ones should become issues
-2. For each approved request, create a GitHub issue via `browser_subagent`:
-   - Navigate to `https://github.com/<owner>/<repo>/issues/new`
-   - **Title**: `<Feature Name> - <Short description>`
-   - **Body** should include:
-     - `## Feature Request` header
-     - `**Source:** Discussion #N by @author`
-     - `## Problem` — What limitation the user hit
-     - `## Proposed Solution` — How it could work
-     - `### Implementation Ideas` — Technical approach
-     - `### Current Workarounds` — What users can do today
-     - `## Additional Context` — Links to related issues/discussions
-   - Add `enhancement` label
-   - Click "Submit new issue" / "Create"
-3. After creation, go back to the original discussion and post a comment linking to the new issue:
-   - "I've opened Issue #N to track this feature request. Follow along there for updates!"
-
-### 7. Final Report
-
-Present a final summary to the user:
-
-| Discussion | Action Taken                       |
-| ---------- | ---------------------------------- |
-| #N — Title | Responded with workarounds         |
-| #N — Title | Responded + created Issue #N       |
-| #N — Title | Already answered, no action needed |
-| #N — Title | Responded to follow-up comment     |
-
-## Notes
-
-- This workflow is **interactive** — always present the summary and wait for user approval before posting responses or creating issues
-- If the user says "pode responder" (or similar approval), proceed with posting all drafted responses
-- For discussions in non-English languages, respond in the same language as the original post
-- Always reference specific dashboard paths, config options, or code files when explaining existing features
-- When a discussion reveals a bug, note it separately from feature requests

.agents/workflows/review-prs-ag.md

@@ -1,256 +0,0 @@
----
-description: Analyze open Pull Requests from the project's GitHub repository, generate a critical report, and optionally implement approved changes
----
-
-# /review-prs — PR Review & Analysis Workflow
-
-## ⛔ ABSOLUTE PROHIBITION — Read Before Anything Else
-
-> **NEVER close a contributor's PR if you intend to use ANY of their code, ideas, or fixes.**
->
-> **NEVER manually integrate contributor code into a release branch and then close their PR.**
->
-> These actions are **STRICTLY FORBIDDEN** under all circumstances:
->
-> 1. ❌ Closing a PR and cherry-picking/copying its code into a release branch
-> 2. ❌ Closing a PR "because of conflicts" and re-implementing the same fix yourself
-> 3. ❌ Closing a PR and committing a "similar" solution inspired by it
-> 4. ❌ Using `gh pr close` on any PR whose content was or will be used
->
-> **Why**: Closing a PR after taking the contributor's work means they get ZERO credit on GitHub — no "Merged" badge, no contribution graph entry, no public record. This is effectively stealing their contribution. An audit found this happened to **37 PRs** in the past.
->
-> **The ONLY acceptable flow**: Resolve conflicts IN the contributor's branch, push fixes TO their branch, then merge THEIR PR via `gh pr merge`. See Step 7 and Step 8 for the exact procedure.
->
-> **When to close a PR**: ONLY when the user (repository owner) explicitly requests it, OR when the PR is clearly spam/malicious, OR when the author themselves asks to close it. In ALL other cases, leave it open.
-
-## Overview
-
-This workflow fetches all open PRs from the project's GitHub repository, performs a critical analysis of each one, generates a detailed report, and waits for user approval before proceeding with implementation. **All improvements are committed on the current release branch** (`release/vX.Y.Z`).
-
-> **BRANCH RULE**: PRs are ALWAYS merged into the current `release/vX.Y.Z` branch, NEVER directly into `main`. The release branch acts as a staging area — only after all PRs are integrated and tests pass does the release branch get merged into `main` via the `/generate-release` workflow.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Read `package.json` to get the repository URL, or use the git remote origin URL
-  // turbo
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-# Bump patch: e.g. 3.3.11 → 3.3.12
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch Open Pull Requests
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh pr list` can be truncated by the tool, silently hiding PRs. You MUST use the two-step approach below to guarantee **all** PRs are fetched.
-
-**Step 3a — Get PR numbers only** (small output, never truncated):
-
-- Run: `gh pr list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one PR number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each PR** (one call per PR):
-
-- For each PR number from step 3a, run:
-  `gh pr view <NUMBER> --repo <owner>/<repo> --json number,title,author,headRefName,baseRefName,body,createdAt,additions,deletions,files`
-- You may batch these into parallel calls (up to 4 at a time).
-
-**Step 3c — Fetch diffs for each PR** (one call per PR, saved to /tmp):
-
-- For each PR number, run:
-  `gh pr diff <NUMBER> --repo <owner>/<repo> > /tmp/pr<NUMBER>.diff`
-- Then read each diff file with the appropriate file-read tool (`Read` in Claude Code; equivalent in your agent runtime).
-
-- For each open PR, collect:
-  - PR number, title, author, branch, number of commits, date
-  - PR description/body
-  - Files changed (diff)
-  - Existing review comments (from bots or humans)
-
-**Verification**: Confirm the count of PRs analyzed matches the count from step 3a before proceeding.
-
-### 3.5 Redirect PR Base Branches to Release Branch
-
-// turbo-all
-
-**⚠️ CRITICAL**: Contributors typically open PRs targeting `main`. Before analyzing or merging, redirect ALL open PRs to target the current release branch instead.
-
-```bash
-# Get the current release branch name
-RELEASE_BRANCH=$(git branch --show-current)  # e.g. release/v3.5.4
-
-# For each open PR that targets main, change its base to the release branch
-for PR_NUM in $(gh pr list --repo <owner>/<repo> --state open --json number,baseRefName --jq '.[] | select(.baseRefName == "main") | .number'); do
-  echo "Redirecting PR #$PR_NUM → $RELEASE_BRANCH"
-  gh pr edit "$PR_NUM" --repo <owner>/<repo> --base "$RELEASE_BRANCH"
-done
-```
-
-This ensures:
-
-1. PRs merge into the release branch, not directly into `main`
-2. Merge conflict detection is accurate against the release branch
-3. The release branch accumulates all changes before the final merge to `main`
-4. If the release branch doesn't exist on remote yet, push it first: `git push origin $RELEASE_BRANCH`
-
-### 4. Analyze Each PR — For each open PR, perform the following analysis:
-
-#### 4a. Feature Assessment
-
-- **Does it make sense?** Evaluate if the feature fills a real gap or solves a valid problem
-- **Alignment** — Check if it aligns with the project's architecture and roadmap
-- **Complexity** — Assess if the scope is reasonable or if it should be split
-
-#### 4b. Code Quality Review
-
-- Check for code duplication
-- Evaluate error handling patterns (consistent with existing codebase?)
-- Check naming conventions and code style
-- Verify TypeScript types (any `any` usage, missing types?)
-
-#### 4c. Security Review
-
-- Check for missing authentication/authorization on new endpoints
-- Check for injection vulnerabilities (URL params, SQL, XSS)
-- Verify input validation on all user-controlled data
-- Check for hardcoded secrets or credentials
-
-#### 4d. Architecture Review
-
-- Does the change follow existing patterns?
-- Are there any breaking changes to public APIs?
-- Is the database schema affected? Migration needed?
-- Impact on performance (N+1 queries, missing indexes?)
-
-#### 4e. Test Coverage
-
-- Does the PR include tests?
-- Are edge cases covered?
-- Would existing tests break?
-
-#### 4f. Cross-Layer (Global) Analysis
-
-Perform a **global impact assessment** to verify whether the PR changes are complete across all layers of the application:
-
-- **Backend → Frontend check**: If the PR adds or modifies backend-only resources (new endpoints, services, data models), evaluate whether corresponding frontend changes are missing:
-  - Does a new endpoint require a new screen/page in the dashboard?
-  - Should there be a new action button, menu item, or navigation link?
-  - Are there new data fields that should be displayed or editable in the UI?
-  - Does a new feature need a toggle, configuration panel, or status indicator?
-- **Frontend → Backend check**: If the PR adds frontend elements, verify the backend support exists:
-  - Are the required API endpoints implemented?
-  - Is the data model sufficient for the new UI components?
-- **Cross-cutting concerns**: Check shared layers (types, DTOs, validation schemas, routes, middleware) for completeness
-- **Document gaps** — If missing layers are detected, list them as **IMPORTANT** issues in the report with concrete suggestions for what should be added
-
-### 5. Generate Report — Create a markdown report for each PR including:
-
-- **PR Summary** — What it does, files affected, commit count
-- **Improvements/Benefits** — Numbered list with impact level (HIGH/MEDIUM/LOW)
-- **Risks & Issues** — Categorized as CRITICAL / IMPORTANT / MINOR
-- **Scoring Table** — Rate across: Feature Relevance, Code Quality, Security, Robustness, Tests
-- **Verdict** — Ready to merge? With mandatory vs optional fixes
-- **Next Steps** — What will happen if approved
-
-### 6. Present to User
-
-- Show the report in the final response and stop. Mark this as a blocking checkpoint awaiting explicit user approval.
-- Wait for user decision:
-  - **Approved** → Proceed to step 7
-  - **Approved with changes** → Implement the fixes and corrections before merging
-  - **Rejected** → Close the PR or leave a review comment
-
-### 7. Pre-Merge Fixes & CI Green-Lighting (if approved)
-
-> **⚠️ Fixes and Conflict Resolutions MUST be pushed back to the PR branch before merging.** We want the PR itself to be green and fully valid before it integrates.
-
-- **Sync latest fixes & Resolve Conflicts:** Merge the current `release` branch into the PR branch. If there are merge conflicts, you MUST resolve them inside the author's PR branch. NEVER resolve conflicts by closing their PR and doing the work in a separate branch, as this steals credit from the original author.
-- **Implement improvements:** Apply the required fixes identified in the analysis directly on the PR branch (e.g., adding missing API routes, fixing SSRF, applying comments from other agents).
-- **Pushing changes to PR branches:**
-
-  ```bash
-  # Checkout the PR locally
-  gh pr checkout <NUMBER>
-
-  # Apply fixes, commit your changes
-  git commit -m "chore: apply review suggestions and missing layers"
-
-  # Attempt to push directly to the PR branch
-  git push
-  ```
-
-- **Fallback (ONLY for external forks without maintainer edit access):**
-  Using `cherry-pick` instead of fixing the contributor's PR directly is a **LAST RESORT**. You MUST ALWAYS attempt to `git push` your fixes to their branch first.
-  **ONLY if `git push` explicitly fails with a permission/access error** (meaning the contributor unchecked "Allow edits from maintainers" or it's a locked fork), you may use `git cherry-pick` to bring their changes into the release branch and fix the issues locally.
-  Even then, ensure you preserve the contributor's authorship (`git commit --author="Contributor Name <email>"` if creating new commits).
-  Once you have integrated their work into the release branch, **DO NOT close their PR**. Leave it open so the contributor retains credit. Under NO CIRCUMSTANCES should you use `gh pr close`.
-
-- Run the project's test suite locally to verify nothing breaks:
-  // turbo
-- Run: `npm test` or equivalent test command
-
-### 8. Merge into Release Branch (NEVER CLOSE!)
-
-> **⚠️ CRITICAL**: NEVER use `gh pr close` for a PR whose idea or code was accepted. Closing a PR in a contributor's face after taking their idea—or closing it just because it had conflicts—is unacceptable.
-> You MUST ALWAYS resolve conflicts and apply fixes ON THE AUTHOR'S PR BRANCH (unless explicitly locked from edits), and then merge the PR using GitHub so the contributor gets the official "Merged" badge and proper credit on their profile. **Do not use cherry-pick just because it is "easier" than resolving conflicts on their branch.**
-
-Even if the PR had severe conflicts or required significant architectural adjustments, you MUST:
-
-1. Resolve any conflicts and apply the fixes directly to their PR branch (as detailed in step 7) or use cherry-picking into the release branch.
-2. If you managed to fix their branch, merge it into the release branch using the GitHub CLI:
-   `gh pr merge <NUMBER> --repo <owner>/<repo> --squash --body "Integrated into release/vX.Y.Z"`
-3. If you had to use cherry-picking because you couldn't push to their branch, DO NOT close the PR. GitHub will sometimes auto-detect the cherry-picked commits and mark it as Merged. If it doesn't, leave it open. The repository owner will handle it. NEVER run `gh pr close`.
-
-In ALL cases:
-
-- Post a **thank-you comment** on the PR via the GitHub API before or immediately after merging.
-- The message should:
-  - Thank the author by name/username for their contribution.
-  - Explain what was adjusted or improved (if we pushed fixes to their branch or cherry-picked).
-  - Note it will be included in the upcoming release.
-  - Be friendly, professional, and encouraging.
-
-> **⚠️ MANDATORY CHANGELOG CREDIT**: When cherry-picking is used (because the PR branch couldn't be pushed to or `gh pr merge` failed), the contributor does NOT get the automatic GitHub "Merged" badge. In this case, you MUST compensate by adding an explicit entry to `CHANGELOG.md` in the `[Unreleased]` section with `(#PR_NUMBER — thanks @username)` format. This ensures the contributor gets public credit in the release notes even if GitHub doesn't auto-detect the cherry-pick. This is NOT optional — skipping it effectively erases the contributor's work from the release record.
-
-### 9. Sync Local Release Branch
-
-After merging PRs, sync the local release branch to include the new changes:
-
-```bash
-git fetch origin
-git pull origin release/vX.Y.Z
-```
-
-### 10. Continue or Finalize
-
-After processing all approved PRs:
-
-- If more PRs remain, go back to step 7
-- When all PRs are processed, **update CHANGELOG.md** on the release branch with all new entries
-- Run **test coverage** to verify the gate (≥75% statements/lines/functions, ≥70% branches — measured ~82%):
-  ```bash
-  npm run test:coverage
-  ```
-- Fix any test regressions introduced by merged PRs
-- Run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user)
-- The `/generate-release` workflow handles the final merge from `release/vX.Y.Z` → `main`

.agents/workflows/version-bump-ag.md

@@ -1,341 +0,0 @@
----
-description: Bump version, auto-generate CHANGELOG from git commits, update all versioned files, and refresh root + docs/ documentation to reflect the current project state
----
-
-# Version Bump Workflow
-
-Automatically bump the project version, generate CHANGELOG entries from git history since the last tag, update every file that references the version, and refresh project documentation to reflect the current state.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.4.10` → `3.5.0`.
-
----
-
-## Phase 1: Determine Version
-
-### 1. Read current version and last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-CURRENT_VERSION=$(node -p "require('./package.json').version")
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
-CURRENT_BRANCH=$(git branch --show-current)
-echo "Current version: $CURRENT_VERSION"
-echo "Last tag: $LAST_TAG"
-echo "Current branch: $CURRENT_BRANCH"
-```
-
-### 2. Calculate new version
-
-Apply the patch bump rule:
-
-- If the current patch number is `9`, the new version is `3.(minor+1).0`
-- Otherwise, increment patch: `3.x.y` → `3.x.(y+1)`
-
-If the version was ALREADY bumped (e.g. you are on a release branch and package.json already has the new version), **skip the npm version bump** and use the existing version.
-
-### 3. Bump package.json (if needed)
-
-// turbo
-
-```bash
-# Only if version hasn't been bumped yet
-npm version patch --no-git-tag-version
-```
-
-Or for threshold (y=10):
-
-```bash
-# Manual threshold bump
-VERSION="3.X.0"  # compute manually
-npm version "$VERSION" --no-git-tag-version
-```
-
----
-
-## Phase 2: Generate CHANGELOG from Git History
-
-### 4. Collect commits since last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
-echo "=== Commits since $LAST_TAG ==="
-git log "$LAST_TAG"..HEAD --pretty=format:"%h %s" --no-merges | head -100
-echo ""
-echo "=== Merge commits ==="
-git log "$LAST_TAG"..HEAD --merges --pretty=format:"%h %s" | head -50
-```
-
-### 5. Classify commits and generate CHANGELOG section
-
-Analyze each commit message and classify into categories based on the conventional-commit prefix and content:
-
-| Category            | Patterns                                         |
-| ------------------- | ------------------------------------------------ |
-| ✨ New Features     | `feat:`, `feat(*):`                              |
-| 🐛 Bug Fixes        | `fix:`, `fix(*):`                                |
-| ⚠️ Breaking Changes | `BREAKING CHANGE`, `!:` suffix                   |
-| 🛠️ Maintenance      | `chore:`, `refactor:`, `perf:`, `build:`         |
-| 🧪 Tests            | `test:`, `tests:`                                |
-| 📝 Documentation    | `docs:`                                          |
-| 🔒 Security         | `security:`, CVE references, vulnerability fixes |
-| 🌍 i18n             | translation updates, locale changes              |
-
-For each category with entries, create a markdown section with descriptive bullet points. Use the commit messages but rewrite them to be human-readable and descriptive (not raw commit messages).
-
-**If a commit references a PR number** (e.g. `#880`, `PR #885`), include it in the description.
-
-### 6. Update CHANGELOG.md
-
-Replace the `## [Unreleased]` section content with the generated entries, then add the new versioned section:
-
-```markdown
-## [Unreleased]
-
----
-
-## [NEW_VERSION] — YYYY-MM-DD
-
-### ✨ New Features
-
-- **Feature name:** Description (#PR)
-
-### 🐛 Bug Fixes
-
-- **Fix name:** Description (#PR)
-
-### 🛠️ Maintenance
-
-- **Item:** Description
-
----
-
-## [PREVIOUS_VERSION] — YYYY-MM-DD
-
-...
-```
-
-The date must be today's date in `YYYY-MM-DD` format.
-
----
-
-## Phase 3: Sync Version Across All Files
-
-### 7. Update workspace package.json files and openapi.yaml
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-
-# Update docs/reference/openapi.yaml version
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ docs/reference/openapi.yaml → $VERSION"
-
-# Update workspace packages (open-sse, electron)
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-
-echo "✓ All workspace packages synced to $VERSION"
-```
-
-### 8. Update llm.txt version references
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-OLD_VERSION_PATTERN='[0-9]\+\.[0-9]\+\.[0-9]\+'
-
-# Update "Current version:" line
-sed -i "s/\*\*Current version:\*\* $OLD_VERSION_PATTERN/**Current version:** $VERSION/" llm.txt
-
-# Update "Key Features (vX.Y.Z)" header
-sed -i "s/## Key Features (v$OLD_VERSION_PATTERN)/## Key Features (v$VERSION)/" llm.txt
-
-echo "✓ llm.txt → $VERSION"
-```
-
-### 9. Regenerate lock file
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm install
-echo "✓ Lock file regenerated"
-```
-
----
-
-## Phase 4: Update Root Documentation
-
-Based on the CHANGELOG entries generated in Phase 2, review and update these root-level files if relevant changes warrant updates:
-
-### 10. Review and update root documentation files
-
-For each file below, read the current content and determine if the CHANGELOG entries require any updates. Only modify files where substantive changes have occurred:
-
-| File              | When to update                                                                                                              |
-| ----------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `README.md`       | New providers, major features, stats changes (test count, provider count), badges, installation instructions, feature table |
-| `AGENTS.md`       | Architecture changes, new modules, new commands, new providers, new services/handlers/executors                             |
-| `CONTRIBUTING.md` | Dev workflow changes, new tooling, test infrastructure changes                                                              |
-| `SECURITY.md`     | Security fixes, new auth mechanisms, vulnerability disclosures                                                              |
-| `llm.txt`         | Provider count changes, new features, architecture changes                                                                  |
-
-**Update rules:**
-
-- **README.md**: Update provider count, test count, feature highlights table, badges if any numbers changed. If a new provider was added, add it to the provider table. If a major feature was added, add it to the features section.
-- **AGENTS.md**: If new architecture components (handlers, executors, services, DB modules) were added, update the Architecture section. If new commands were added, update the Build/Test table.
-- **SECURITY.md**: Add new vulnerability fixes or security improvements to the relevant section.
-- **llm.txt**: Update provider count, feature list, version references.
-
-### 11. Review and update docs/ files (excluding i18n/)
-
-For each file in `docs/` (excluding `docs/i18n/`), review if CHANGELOG changes affect it:
-
-| File                                          | When to update                                                     |
-| --------------------------------------------- | ------------------------------------------------------------------ |
-| `docs/reference/API_REFERENCE.md`             | New API endpoints, changed request/response formats                |
-| `docs/architecture/ARCHITECTURE.md`           | New modules, new services, changed data flow                       |
-| `docs/architecture/CODEBASE_DOCUMENTATION.md` | New files, architectural changes, module reorganization            |
-| `docs/architecture/REPOSITORY_MAP.md`         | New folders / files / one-line descriptions                        |
-| `docs/reference/CLI-TOOLS.md`                 | New CLI tool integrations, config format changes                   |
-| `docs/guides/USER_GUIDE.md`                   | UX changes, new dashboard pages, settings changes                  |
-| `docs/reference/PROVIDER_REFERENCE.md`        | New providers (regenerate via `scripts/gen-provider-reference.ts`) |
-| `docs/frameworks/MCP-SERVER.md`               | New MCP tools, changed tool signatures, scope changes              |
-| `docs/frameworks/A2A-SERVER.md`               | New A2A skills, protocol changes                                   |
-| `docs/frameworks/AGENT_PROTOCOLS_GUIDE.md`    | New external agent protocols supported                             |
-| `docs/frameworks/CLOUD_AGENT.md`              | Cloud agent additions (codex-cloud, devin, jules) or API changes   |
-| `docs/architecture/AUTHZ_GUIDE.md`            | New route classifications, policy changes                          |
-| `docs/security/GUARDRAILS.md`                 | New guardrails registered, priority/order changes                  |
-| `docs/security/COMPLIANCE.md`                 | Audit log / retention / no-log policy changes                      |
-| `docs/frameworks/SKILLS.md`                   | Skill framework / registry / built-in skill changes                |
-| `docs/frameworks/MEMORY.md`                   | Memory pipeline / extraction / injection / Qdrant changes          |
-| `docs/frameworks/EVALS.md`                    | Evaluation framework changes, new evaluators                       |
-| `docs/frameworks/WEBHOOKS.md`                 | New webhook events, payload schema changes                         |
-| `docs/routing/REASONING_REPLAY.md`            | Reasoning capture/replay pipeline changes                          |
-| `docs/routing/AUTO-COMBO.md`                  | Routing changes, new strategies, scoring weight changes            |
-| `docs/architecture/RESILIENCE_GUIDE.md`       | Circuit breaker / cooldown / lockout behavior changes              |
-| `docs/security/STEALTH_GUIDE.md`              | TLS / CLI fingerprint changes                                      |
-| `docs/ops/TUNNELS_GUIDE.md`                   | Cloudflare tunnel feature changes                                  |
-| `docs/guides/ELECTRON_GUIDE.md`               | Electron build / signing / packaging changes                       |
-| `docs/guides/TROUBLESHOOTING.md`              | New known issues, resolved problems                                |
-| `docs/ops/RELEASE_CHECKLIST.md`               | Process changes                                                    |
-| `docs/ops/COVERAGE_PLAN.md`                   | Coverage gate adjustments, target metrics                          |
-| `docs/reference/openapi.yaml`                 | Already updated in step 7                                          |
-
-**Only update files where the CHANGELOG entries directly affect the documented content.** Do NOT update files just to bump a version number — only when the documented behavior, features, or architecture has actually changed.
-
----
-
-## Phase 5: Verify
-
-### 12. Run lint check
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm run lint
-```
-
-### 13. Run tests
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm test
-```
-
-### 14. Verify version sync across all files
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-echo "Expected version: $VERSION"
-echo ""
-
-echo "--- package.json ---"
-grep '"version"' package.json | head -1
-
-echo "--- open-sse/package.json ---"
-grep '"version"' open-sse/package.json | head -1
-
-echo "--- electron/package.json ---"
-[ -f electron/package.json ] && grep '"version"' electron/package.json | head -1
-
-echo "--- docs/reference/openapi.yaml ---"
-grep "  version:" docs/reference/openapi.yaml | head -1
-
-echo "--- llm.txt ---"
-grep "Current version:" llm.txt
-
-echo "--- CHANGELOG.md (first versioned entry) ---"
-grep "^## \[" CHANGELOG.md | head -2
-```
-
-### 15. 🛑 STOP — Present Summary to User
-
-**STOP** and present a summary to the user including:
-
-- Old version → New version
-- CHANGELOG entries generated
-- Files modified
-- Test results
-- Any documentation updates made
-
-**Wait for the user to confirm before committing.**
-
----
-
-## Phase 6: Commit (only after user approval)
-
-### 16. Stage and commit
-
-// turbo-all
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-git add -A
-VERSION=$(node -p "require('./package.json').version")
-git commit -m "chore(release): bump to v$VERSION — changelog, docs, version sync"
-```
-
----
-
-## Notes
-
-- This workflow does **NOT** create tags, releases, or deploy. Use `/generate-release` for the full release cycle after this.
-- This workflow does **NOT** update `docs/i18n/` translations. Translation updates are handled manually or via release tooling — there is no `/update-i18n` workflow shipped in this repo.
-- The CHANGELOG generation is based on git commits since the last tag. If there are no new commits, the workflow should inform the user and stop.
-- Always verify the generated CHANGELOG entries make sense — raw commit messages may need rewriting for clarity.
-- If the version was already bumped (e.g. you're on a `release/vX.Y.Z` branch), skip the `npm version` step and use the existing version.
-
-## Version Touchpoints Checklist
-
-| File                          | Field/Pattern                                               |
-| ----------------------------- | ----------------------------------------------------------- |
-| `package.json`                | `"version": "X.Y.Z"`                                        |
-| `open-sse/package.json`       | `"version": "X.Y.Z"`                                        |
-| `electron/package.json`       | `"version": "X.Y.Z"`                                        |
-| `docs/reference/openapi.yaml` | `version: X.Y.Z`                                            |
-| `llm.txt`                     | `**Current version:** X.Y.Z` and `## Key Features (vX.Y.Z)` |
-| `CHANGELOG.md`                | `## [X.Y.Z] — YYYY-MM-DD`                                   |

.claude/commands/capture-release-evidences-cc.md

@@ -1,51 +0,0 @@
----
-description: Automatically run a browser-automation agent to visually validate all new UI features from the current release and capture evidence WebP recordings of the changes.
----
-
-# Capture Release Evidences Workflow
-
-Use this workflow to automatically drive a browser-automation agent to explore the newly deployed or locally running application and record evidence of the UI changes introduced in the latest release.
-
-> **Tool mapping note (v3.8):** This workflow references a `browser_subagent` tool that was specific to an earlier agent runtime. In Claude Code, substitute with the available browser MCP tools (e.g. `mcp__claude-in-chrome__*`) for navigation/screenshots, plus the `Write` tool for saving artifacts. The high-level steps below remain the same regardless of which browser-automation surface is used.
-
-## Prerequisites
-
-- OmniRoute must be actively running and accessible (e.g. locally at `http://localhost:20128` or on the Local VPS at `http://192.168.0.15:20128`).
-- The user must provide the target URL to be tested, or default to `http://192.168.0.15:20128`.
-
-## Workflow Steps
-
-### 1. Identify Target Features
-
-Review the `CHANGELOG.md` for the latest version to map out the new UI elements. For example:
-
-- **CLI Tools Settings**
-- **New Provider/Model Listings (e.g., Gemini 3.1, Qoder PAT)**
-- **New Feature Modals**
-
-### 2. Run the Browser Subagent
-
-For each identified feature, invoke the `browser_subagent` using the `default_api:browser_subagent` tool.
-**Important Task Guidelines for the Subagent:**
-
-- `TaskName`: Give it a clear name like "Validate CLIProxyAPI Tool Tab".
-- `TaskSummary`: "Navigate to the CLI Tools tab and verify the new Integration settings."
-- `Task`: Provide unambiguous instructions for the subagent, such as: "Navigate to http://192.168.0.15:20128/dashboard. Click on the 'Settings' or 'CLI Tools' nav link. Scroll down to find the CLIProxyAPI integration card. Hover over it to trigger UI state. Verify the components render correctly and exit."
-- `RecordingName`: Ensure it describes the feature (e.g. `v3_4_5_cli_proxy_api`). This is required and strictly automatically saved as a WebP artifacts video by the system.
-
-_(Note: The `browser_subagent` automatically creates a WebP recording named by the `RecordingName` parameter. No additional tools for screenshots are needed.)_
-
-### 3. Generate Report Artifact
-
-After the `browser_subagent` finishes its sessions, generate a final Markdown artifact (using `Write` and `IsArtifact=true`) to present the recordings inline to the user using the `![caption](/absolute/path/to/media.webp)` syntax.
-
-### Example Invocation
-
-\```json
-{
-"TaskName": "Validating Qoder PAT Configuration UI",
-"TaskSummary": "Validates the Qoder provider configuration modal",
-"Task": "Go to http://192.168.0.15:20128/dashboard. Click on the 'Providers' tab. Find 'Qoder' in the list. Click 'Add Token' or 'Configure'. Type 'test_token' and submit. Return when done.",
-"RecordingName": "qoder_pat_ui_validation"
-}
-\```

.claude/commands/deploy-vps-akamai-cc.md

@@ -1,39 +0,0 @@
----
-description: Deploy the latest OmniRoute code to the Akamai VPS (69.164.221.35)
----
-
-# Deploy to Akamai VPS Workflow
-
-Deploy OmniRoute to the Akamai VPS using `npm pack + scp` + PM2.
-
-**Akamai VPS:** `69.164.221.35`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Akamai VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-```

.claude/commands/deploy-vps-both-cc.md

@@ -1,49 +0,0 @@
----
-description: Deploy the latest OmniRoute code to BOTH the Akamai VPS and the Local VPS
----
-
-# Deploy to VPS (Both) Workflow
-
-Deploy OmniRoute to the production VPSs using `npm pack + scp` + PM2.
-
-**Akamai VPS:** `69.164.221.35`
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-**PM2 entry:** `/usr/lib/node_modules/omniroute/app/server.js`
-
-> [!IMPORTANT]
-> The npm registry rejects packages > 100MB, so deployment uses **npm pack + scp**.
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to both VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@69.164.221.35:/tmp/ && scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'AKAMAI HTTP %{http_code}\n' http://69.164.221.35:20128/
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.claude/commands/deploy-vps-local-cc.md

@@ -1,39 +0,0 @@
----
-description: Deploy the latest OmniRoute code to the Local VPS (192.168.0.15)
----
-
-# Deploy to Local VPS Workflow
-
-Deploy OmniRoute to the Local VPS using `npm pack + scp` + PM2.
-
-**Local VPS:** `192.168.0.15`
-**Process manager:** PM2 (`omniroute`)
-**Port:** `20128`
-
-## Steps
-
-### 1. Build + pack locally
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-```
-
-### 2. Copy to Local VPS and install
-
-// turbo-all
-
-```bash
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-```
-
-```bash
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-```
-
-### 3. Verify the deployment
-
-```bash
-curl -s -o /dev/null -w 'LOCAL HTTP %{http_code}\n' http://192.168.0.15:20128/
-```

.claude/commands/generate-release-cc.md

@@ -1,362 +0,0 @@
----
-description: Create a new release, bump version up to the .10 patch threshold, update changelog, and manage Pull Requests
----
-
-# Generate Release Workflow
-
-Bump version, finalize CHANGELOG, commit, open a **PR to main** and wait for user confirmation before tagging, publishing, and deploying.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.8.10` → `3.9.0`.
-
-> **🔴 SINGLE BRANCH RULE**: The `release/vX.Y.Z` branch is the **ONLY** development branch for the entire release cycle. ALL work — bug fixes, feature implementations, PR integrations, issue resolutions — MUST be committed directly on this branch. Never create separate `fix/`, `feat/`, or topic branches. When running `/resolve-issues`, `/implement-features`, or `/review-prs`, always work on the current release branch.
-
----
-
-## ⚠️ Two-Phase Flow
-
-```
-Phase 1 (automated): bump → docs → i18n → commit → push → open PR
-  ↕  🛑 STOP: Notify user, wait for PR confirmation
-Phase 2 (post-merge): tag → publish → GitHub release → Docker → deploy
-```
-
-**NEVER push directly to main or create tags before the user confirms the PR.**
-
----
-
-## Phase 0: Security Verification (MANDATORY)
-
-Before creating the release, you must ensure the codebase and supply chain are secure and free of known vulnerabilities.
-
-1. **Run Local Dependencies Audit:**
-
-   ```bash
-   npm audit
-   ```
-
-   _Fix any `high` or `critical` vulnerabilities identified._
-
-2. **Check GitHub CodeQL & Dependabot Alerts:**
-   Navigate to the repository's **Security** tab on GitHub, or use the project's `vulnerability-scanner` skill to analyze active alerts. Ensure all static analysis findings (e.g., prototype pollution, insecure randomness, ReDoS, shell injections) are addressed and logically committed on a target branch.
-
----
-
-## Phase 1: Pre-Merge
-
-### 1. Create release branch
-
-```bash
-git checkout -b release/v3.x.y
-```
-
-### 2. Determine and sync version
-
-Check current version in `package.json`:
-
-```bash
-grep '"version"' package.json
-```
-
-> **🔴 BRANCH-VERSION PARITY RULE**: The logical version in `package.json` MUST exactly match the release branch name. For example, if you are on `release/v3.7.0`, the version in `package.json` MUST be `3.7.0`.
->
-> - If this is the FIRST time generating a release for a new minor/major branch (e.g., bumping from 3.6.9 to 3.7.0), you MUST ensure the version is bumped to match the new branch logic.
-> - If you are just bumping a patch on the current branch (e.g., 3.6.9 to 3.6.10), use:
->   `npm version patch --no-git-tag-version`
-
-> **⚠️ ATOMIC COMMIT RULE — Version bump MUST happen before committing feature files.**
->
-> **CORRECT order:**
->
-> 1. `npm version patch --no-git-tag-version` ← bump first
-> 2. implement features / fix bugs
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **OR if features are already staged:**
->
-> 1. implement features (do NOT commit yet)
-> 2. `npm version patch --no-git-tag-version` ← bump before committing
-> 3. `git add -A && git commit -m "chore(release): v3.x.y — all changes in ONE commit"`
->
-> **NEVER do this (creates version mismatch in git history):**
->
-> - ~~commit features → then bump version → commit package.json separately~~
->
-> This ensures that `git show v3.x.y` always contains both code changes and the version bump together.
-> The GitHub release tag will point to a commit that includes ALL changes for that version.
-
-### 3. Regenerate lock file (REQUIRED after version bump)
-
-**Mandatory** — skipping causes `@swc/helpers` lock mismatch and CI failures:
-
-```bash
-npm install
-```
-
-### 4. Finalize CHANGELOG.md
-
-> **🔴 NO MIXUPS RULE**: Ensure you do NOT mix the backlog of the previous version with the new one. The new version section must ONLY contain the features and fixes for the current release.
-
-Replace the `[Unreleased]` header with the new version and date.
-Keep an empty `## [Unreleased]` section above it, separated by a horizontal rule (`---`).
-
-```markdown
-## [Unreleased]
-
----
-
-## [3.7.0] — 2026-04-19
-
-### ✨ New Features
-
-- ...
-
-### 🐛 Bug Fixes
-
-- ...
-
----
-
-## [3.6.9] — 2026-04-19
-```
-
-### 5. Update openapi.yaml version ⚠️ MANDATORY
-
-> **CI will fail** if `docs/reference/openapi.yaml` version ≠ `package.json` version (`check:docs-sync` enforces this).
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ openapi.yaml → $VERSION"
-
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-# Re-run install to assert the workspace lockfile is updated
-npm install
-```
-
-### 6. Update README.md and i18n docs
-
-Manually perform these documentation updates (there is no `/update-docs` slash command — it was deprecated in v3.8):
-
-- Update feature table rows and "What's new in vX.Y.Z" section in `README.md`
-- Sync feature changes to all 40 language `docs/i18n/*/README.md` files (use the same row edits across each translated README)
-- Update the relevant `docs/<AREA>.md` if architecture or counts changed (e.g. `docs/frameworks/MCP-SERVER.md` when MCP tools change)
-- Re-run `npm run check:docs-sync` and `npm run check:docs-all` to catch drift
-
-### 7. Run tests
-
-// turbo
-
-```bash
-npm test
-```
-
-All tests must pass before creating the PR.
-
-### 8. Stage, commit, and push
-
-// turbo-all
-
-```bash
-git add -A
-git commit -m "chore(release): v3.x.y — summary of changes"
-git push origin release/v3.x.y
-```
-
-### 9. Open PR to main
-
-### 9. Open PR to main
-
-// turbo
-
-```bash
-VERSION=$(node -p "require('./package.json').version")
-
-# Extract the exact changelog entry for this version from the root CHANGELOG.md
-awk "/^## \\[$VERSION\\]/{flag=1; print; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md > /tmp/changelog_body.txt
-
-# Append test status and next steps
-echo "" >> /tmp/changelog_body.txt
-echo "### Tests" >> /tmp/changelog_body.txt
-echo "- All tests pass" >> /tmp/changelog_body.txt
-echo "" >> /tmp/changelog_body.txt
-echo "### ⚠️ After merging: run Phase 2 steps to tag, publish, and deploy." >> /tmp/changelog_body.txt
-
-gh pr create \
-  --repo diegosouzapw/OmniRoute \
-  --base main \
-  --head release/v$VERSION \
-  --title "Release v$VERSION" \
-  --body-file /tmp/changelog_body.txt
-```
-
-### 10. 🛑 STOP — Notify User & Await PR Confirmation
-
-**This is a mandatory stop point.** Present the report in the final response and stop. Do not continue to the next phase until the user explicitly approves.
-
-Inform the user:
-
-- PR URL
-- Summary of changes
-- Test results
-- List of files changed
-
-**DO NOT proceed to Phase 2 until the user confirms the PR looks good and merges it.**
-
----
-
-## Phase 2: Post-Merge Validation (Local VPS)
-
-> Run these steps only AFTER the user has merged the PR into `main` and all CI jobs have passed.
-
-### 11. Deploy to Local VPS for Final Validation (MANDATORY)
-
-Before cutting the official git tag and publishing to the world, deploy the `main` branch to the Local VPS for a final homologation test.
-
-```bash
-git checkout main
-git pull origin main
-
-# Build and pack locally
-cd /home/diegosouzapw/dev/proxys/OmniRoute && rm -f omniroute-*.tgz && rm -rf .next/cache app/.next/cache && npm run build:cli && rm -rf app/logs app/coverage app/.git app/.app-build-backup* && npm pack --ignore-scripts
-
-# Deploy to LOCAL VPS (192.168.0.15)
-scp omniroute-*.tgz root@192.168.0.15:/tmp/
-ssh root@192.168.0.15 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Local done'"
-
-# Verify
-curl -s -o /dev/null -w "LOCAL:  HTTP %{http_code}\n" http://192.168.0.15:20128/
-```
-
-### 12. 🛑 STOP — Notify User & Await Final OK
-
-**This is a mandatory stop point.**
-Inform the user that the `main` branch is now running on the Local VPS.
-Wait for the user to manually test and give the **OK**.
-**DO NOT proceed to Phase 3 until the user confirms the local deploy is stable.**
-
----
-
-## Phase 3: Official Launch
-
-> Run these steps only AFTER the user gives the final OK from the Phase 2 local validation.
-
-### 13. Create Git Tag and GitHub Release (MANDATORY)
-
-// turbo
-
-```bash
-git checkout main
-git pull origin main
-VERSION=$(node -p "require('./package.json').version")
-
-# Extracts the changelog section for this version
-NOTES=$(awk "/^## \\[$VERSION\\]/{flag=1; next} /^---/{if(flag) {flag=0; exit}} flag" CHANGELOG.md | sed -e 's/^[[:space:]]*//' -e 's/[[:space:]]*$//')
-if [ -z "$NOTES" ]; then NOTES="OmniRoute v$VERSION Release"; fi
-
-git tag -a "v$VERSION" -m "Release v$VERSION"
-git push origin "v$VERSION"
-gh release create "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES" --target main || gh release edit "v$VERSION" --repo diegosouzapw/OmniRoute --title "v$VERSION" --notes "$NOTES"
-```
-
-### 14. 🐳 Trigger Docker Hub build (MANDATORY — keep npm and Docker in sync)
-
-> **CRITICAL**: Docker Hub and npm MUST always publish the same version.
-> The Docker image is built automatically via GitHub Actions when a new tag is pushed.
-> After pushing the tag in step 13, **verify the workflow runs**:
-
-```bash
-# Verify the Docker workflow triggered
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 3
-
-# Wait for the Docker build to complete (usually 5–10 min)
-gh run watch --repo diegosouzapw/OmniRoute
-```
-
-### 15. Publish to NPM (Optional/Automated)
-
-Normally handled by CI, but if manual publish is required:
-
-```bash
-npm publish
-```
-
-### 16. Deploy to AKAMAI VPS (Production)
-
-Now that the release is officially cut, deploy it to the Akamai VPS.
-
-```bash
-# Deploy to AKAMAI VPS (69.164.221.35)
-scp omniroute-*.tgz root@69.164.221.35:/tmp/
-ssh root@69.164.221.35 "npm install -g /tmp/omniroute-*.tgz --ignore-scripts && cd /usr/lib/node_modules/omniroute/app && npm rebuild better-sqlite3 && pm2 delete omniroute 2>/dev/null; pm2 start /root/.omniroute/ecosystem.config.cjs --update-env && pm2 save && echo '✅ Akamai done'"
-
-# Verify
-curl -s -o /dev/null -w "AKAMAI: HTTP %{http_code}\n" http://69.164.221.35:20128/
-```
-
-## Phase 4: Release Monitoring & Artifact Validation
-
-> After triggering the official release, actively monitor the CI pipelines until all artifacts are successfully generated. If any pipeline fails, stop and apply the necessary corrections before continuing.
-
-### 18. Monitor CI Pipelines
-
-Wait for and verify the successful completion of the following automated jobs:
-
-1. **Docker Hub Publish**
-2. **Electron Build**
-3. **NPM Registry Publish** (Check with `npm info omniroute version`)
-
-```bash
-# Monitor Docker Hub workflow
-gh run list --repo diegosouzapw/OmniRoute --workflow docker-publish.yml --limit 1
-gh run watch <RUN_ID>
-
-# Monitor Electron build
-gh run list --repo diegosouzapw/OmniRoute --workflow electron-release.yml --limit 1
-gh run watch <RUN_ID>
-
-# Verify NPM version
-npm info omniroute version
-```
-
-### 19. Handle Failures (If Any)
-
-If a workflow fails:
-
-- Use `gh run view <RUN_ID> --log-failed` to identify the error.
-- Apply the fix on the `main` branch.
-- If necessary, re-trigger the workflow using `gh workflow run <workflow_name.yml> --repo diegosouzapw/OmniRoute --ref v3.x.y`
-
-### 20. Preserve release branch
-
-```bash
-# Branch is kept for historical purposes. Do not delete.
-```
-
----
-
-## Notes
-
-- Ensure CHANGELOG, README and `docs/*` are current BEFORE this workflow — run `npm run check:docs-all` and `/version-bump` first (there is no `/update-docs` slash command anymore)
-- The `prepublishOnly` script runs `npm run build:cli` automatically during `npm publish`
-- After npm publish, verify with `npm info omniroute version`
-- Lock file sync errors are caused by skipping `npm install` after version bump
-- Use `gh auth switch -u diegosouzapw` if git push fails with wrong account
-
-## Known CI Pitfalls
-
-| CI failure                                                                | Cause                                                              | Fix                                                                    |
-| ------------------------------------------------------------------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------- |
-| `[docs-sync] FAIL - OpenAPI version differs from package.json`            | Skipped step 5 — `docs/reference/openapi.yaml` version not updated | Run step 5 (`sed -i ...`) and commit                                   |
-| `[docs-sync] FAIL - CHANGELOG.md first section must be "## [Unreleased]"` | `## [Unreleased]` missing or not at top of CHANGELOG               | Add `## [Unreleased]\n\n---\n` before the first versioned `## [x.y.z]` |
-| Electron Linux `.deb` build fails (`FpmTarget` error)                     | `fpm` Ruby gem not installed on `ubuntu-latest` runner             | Already fixed in `electron-release.yml` (`gem install fpm` step)       |
-| Docker Hub `502 error writing layer blob`                                 | Transient Docker Hub network error during ARM64 push               | Re-run the Docker publish workflow; no code change needed              |

.claude/commands/issue-triage-cc.md

@@ -1,50 +0,0 @@
----
-description: How to respond to GitHub issues with insufficient information
----
-
-# Issue Triage Workflow
-
-Respond to GitHub issues that need more information before they can be investigated.
-
-## Steps
-
-### 1. Identify issues needing triage
-
-```bash
-gh issue list --state open --limit 20
-```
-
-### 2. Evaluate each issue
-
-Check if the issue has:
-
-- Clear reproduction steps
-- Environment details (OS, Node.js version, OmniRoute version)
-- Error logs/screenshots
-- Expected vs actual behavior
-
-### 3. Respond with triage template
-
-For issues missing information:
-
-```markdown
-Thank you for reporting this issue! To help us investigate, please provide:
-
-1. **OmniRoute version**: (`omniroute --version`)
-2. **Node.js version**: (`node --version`)
-3. **Operating system**: (e.g., Ubuntu 24.04, macOS 15, Windows 11)
-4. **Installation method**: (npm, Docker, source)
-5. **Steps to reproduce**: (exact commands/actions that trigger the issue)
-6. **Error logs**: (paste relevant logs from the console)
-7. **Expected behavior**: (what should happen)
-
-This will help us debug and resolve your issue faster. 🙏
-```
-
-### 4. Label the issue
-
-Add appropriate labels: `needs-info`, `bug`, `enhancement`, `question`, etc.
-
-```bash
-gh issue edit <NUMBER> --add-label "needs-info"
-```

.claude/commands/resolve-issues-cc.md

@@ -1,166 +0,0 @@
----
-description: Fetch all open GitHub issues, analyze bugs, resolve what's possible, triage the rest, wait for user validation, then commit and release
----
-
-# /resolve-issues — Automated Issue Resolution Workflow
-
-## Overview
-
-This workflow fetches all open issues from the project's GitHub repository, classifies them, analyzes bugs, proposes a resolution plan, waits for user validation, and ONLY THEN implements the fixes, commits, and closes the issues on the current release branch (`release/vX.Y.Z`). It does NOT merge or release automatically — the release branch is later merged via PR to main.
-
-> **BRANCH RULE**: All work MUST happen on the current `release/vX.Y.Z` branch. Never create separate `fix/` branches. If no release branch exists yet, create one first using `/generate-release` Phase 1 steps 1–5.
-
-> **⛔ PR PROHIBITION**: If a fix is associated with a contributor's PR, you MUST merge their PR — NEVER close it and re-implement the fix yourself. See `/review-prs` workflow for the full policy. The `gh pr close` command is FORBIDDEN unless the repository owner explicitly requests it.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-// turbo
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch All Open Issues
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh issue list` can be truncated by the tool, silently hiding issues. You MUST use the two-step approach below to guarantee **all** issues are fetched.
-
-**Step 3a — Get Issue numbers only** (small output, never truncated):
-
-- Run: `gh issue list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one issue number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each Issue** (one call per issue):
-
-- For each issue number from step 3a, run:
-  `gh issue view <NUMBER> --repo <owner>/<repo> --json number,title,labels,body,comments,createdAt,author`
-- You may batch these into parallel calls (up to 4 at a time).
-- Sort by oldest first (FIFO).
-
-### 4. Classify Each Issue
-
-For each issue, determine its type:
-
-- **Bug** — Has `bug` label, or body contains error messages, stack traces, "doesn't work", "broken", "crash", "error"
-- **Feature Request** — Has `enhancement`/`feature` label, or body describes new functionality
-- **Question** — Has `question` label, or is asking "how to" something
-- **Other** — Anything else
-
-Focus ONLY on **Bugs** for resolution. Feature requests and questions should be skipped with a note in the final report.
-
-### 5. Deep-Read Each Bug Issue (One-by-One Analysis)
-
-**IMPORTANT**: Read each bug issue thoroughly, one at a time, before moving to the next. This is NOT a batch process — each issue needs focused attention.
-
-#### 5a. Understand the Problem
-
-For each bug issue, perform the full analysis:
-
-1. **Read the entire body** — including Description, Steps to Reproduce, Expected/Actual Behavior, Error Logs, and Screenshots
-2. **Read ALL comments** — including bot triage comments (Kilo, etc.) and owner/community responses. Pay attention to:
-   - Whether someone already responded with a fix
-   - Whether a community member confirmed the issue is resolved
-   - Whether the issue was marked as duplicate by a bot. **WARNING: DO NOT blindly trust bot duplicate labels (e.g., kilo-duplicate). Bots make mistakes. You MUST read the full conversation and do your own independent analysis to determine if it is truly a duplicate or a distinct bug.**
-3. **Identify the claimed error** — extract the exact error message, status code, and provider/model involved
-
-#### 5b. Check Information Sufficiency
-
-Verify the issue contains enough to act on:
-
-- [ ] Clear description of the problem
-- [ ] Steps to reproduce OR error logs
-- [ ] Provider/model/version information
-- [ ] Expected vs actual behavior
-
-#### 5c. Determine Issue Disposition
-
-For each bug, classify into one of 5 actions:
-
-| Disposition                  | When to Apply                                                                                                          | Action                                                  |
-| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
-| **✅ CLOSE — Already Fixed** | Owner responded with fix + no user follow-up, OR community confirmed fix                                               | Close with comment citing which version fixed it        |
-| **✅ CLOSE — Duplicate**     | You have independently verified the issue is a duplicate (do NOT rely solely on bot flags) + user provides no new info | Close referencing the original issue                    |
-| **✅ CLOSE — Stale**         | We requested logs/info > 7 days ago with no reply                                                                      | Close thanking the user, invite to reopen if needed     |
-| **📝 RESPOND — Needs Info**  | Issue is real but missing critical reproduction details                                                                | Comment asking for specifics per `/issue-triage`        |
-| **📝 RESPOND — User Config** | Error is caused by unsupported env (Node version, wrong model path, missing API enablement)                            | Comment explaining the user-side fix                    |
-| **🔧 FIX — Code Change**     | Root cause is confirmed in the codebase                                                                                | Research, propose solution in report, wait for approval |
-
-#### 5d. For "FIX — Code Change" Issues
-
-Before coding, perform deep source analysis to formulate a plan:
-
-1. **Search the codebase** — `grep_search` for error strings, relevant function names, affected files
-2. **Search the web** — for upstream API changes, SDK updates, or breaking changes that explain the bug
-3. **Read the full source file** — don't rely on grep snippets; understand the surrounding logic
-4. **Verify the root cause** — confirm the bug is reproducible based on the code, not just a user misconfiguration
-5. **Formulate a proposed solution** — detail the exact files and lines you will change and how you will solve it.
-6. **Create an Implementation Plan file** — write your proposed solution to `_tasks/features-vX.Y.Z/<ISSUE_NUMBER>-<short-description>.plan.md` (e.g. `_tasks/features-v3.7.6/1810-auto-restore-probe-failed-db.plan.md`) where `vX.Y.Z` is the current branch version. The plan should contain an Overview, Pre-Implementation Checklist, and detailed Implementation Steps (Files, Changes).
-7. **DO NOT modify the codebase yet** — wait for user approval on your report and plan first.
-
-#### 5e. For "RESPOND" Issues
-
-Post a substantive comment that:
-
-- Acknowledges the specific error they reported
-- Explains the likely root cause
-- Provides concrete steps to resolve (version upgrade, env var fix, model path correction)
-- Asks for follow-up info if needed
-
-**Do NOT post generic template responses.** Every comment should reference the user's specific error messages and environment.
-
-### 6. Generate Report & Wait for Validation
-
-Present a summary report to the user detailing your proposed actions. For any bugs that need fixing, explicitly explain your proposed solution (files to change and logic) and point out that it will be implemented on the release branch (`release/vX.Y.Z`) after approval.
-
-| Issue | Title | Status        | Proposed Action / Version                 |
-| ----- | ----- | ------------- | ----------------------------------------- |
-| #N    | Title | ✅ Close      | Already fixed / duplicate (explain why)   |
-| #N    | Title | 🔧 Propose    | Explanation of the code fix to be applied |
-| #N    | Title | 📝 Respond    | Guidance comment to be posted             |
-| #N    | Title | ❓ Needs Info | Triage comment to be posted               |
-| #N    | Title | ⏭️ Skip       | Feature request / not a bug               |
-
-> **⚠️ IMPORTANT**: Do NOT implement code changes, commit, push, or close issues at this step.
-> Wait for the user to review the proposed fixes and respond with **OK** before proceeding.
-
-- If the user says **OK** or approves → Proceed to step 7
-- If the user requests changes → Adjust the proposed solution and present the report again
-- If the user rejects → Revert any accidental changes and stop
-
-### 7. Implement Fixes, Run Tests & Commit (only after user approval)
-
-After the user validates and gives the OK:
-
-1. **Implement the fixes** — modify the codebase according to the approved plan.
-2. **Run tests** — `npm run test:all` (or the specific test file) to ensure 100% pass.
-3. **Update CHANGELOG.md** with all new bug fix entries.
-4. **Commit** each fix individually on the release branch with message format: `fix: <description> (#<issue_number>)`.
-5. **Push** the release branch: `git push origin release/vX.Y.Z`.
-6. **Close resolved issues immediately**. For each issue that was marked as Fixed, run:
-   `gh issue close <NUMBER> --repo <owner>/<repo> --comment "Thank you for reporting! This issue has been fixed and will be included in the next release (vX.Y.Z)."`
-7. Likewise, close `Duplicate` issues referencing the original, close `Needs Info` if stale, and post the required comments.
-8. If the project runs automatic releases or needs a PR, proceed to run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user).
-
-If NO fixes were committed, skip closing and source control steps and just conclude the workflow.

.claude/commands/review-discussions-cc.md

@@ -1,120 +0,0 @@
----
-description: Read all open GitHub Discussions, summarize them, respond to pending ones, and create issues from actionable feature requests
----
-
-# /review-discussions — GitHub Discussions Review & Response Workflow
-
-## Overview
-
-This workflow reads all open GitHub Discussions, generates a categorized summary, identifies which ones need a response, drafts and posts replies, and optionally creates issues from actionable feature requests. It follows the same flow used for Issues but adapted for the Discussions forum.
-
-> **Tool mapping note (v3.8):** Where steps below say `browser_subagent` (an earlier-runtime tool), in Claude Code use the `gh` CLI via the `Bash` tool — `gh api graphql` for reading discussions and `gh api graphql -F query=...` mutations for posting comments. `WebFetch` is acceptable for read-only HTML scraping when GraphQL is overkill, but prefer `gh` for any write actions.
-
-// turbo-all
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-- Parse the owner and repo name from the URL
-
-### 2. Fetch All Open Discussions
-
-- Use `WebFetch` to fetch `https://github.com/<owner>/<repo>/discussions`
-- Parse the discussion list to get all discussion titles, IDs, authors, categories, and dates
-- For each discussion, fetch the individual page to read the full content and all comments/replies
-
-### 3. Summarize All Discussions
-
-For each discussion, extract:
-
-- **Title** and **#Number**
-- **Author** (GitHub username)
-- **Category** (Announcements, General, Ideas, Q&A, Show and tell)
-- **Date** created
-- **Summary** of the original post (1-2 sentences)
-- **Comments count** and key participants
-- **Your previous response** (if any)
-- **Pending action** — whether a response or follow-up is needed
-
-### 4. Present Summary Report to User
-
-Present the full summary to the user organized by category, using a table:
-
-| #   | Category | Title | Author | Date   | Status            |
-| --- | -------- | ----- | ------ | ------ | ----------------- |
-| #N  | Ideas    | Title | @user  | Mar 23 | ⚠️ Needs response |
-| #N  | Q&A      | Title | @user  | Mar 9  | ✅ Answered       |
-| #N  | General  | Title | @user  | Mar 19 | ⚠️ Needs response |
-
-Highlight:
-
-- **⚠️ Needs response** — No reply from maintainer, or a follow-up comment was left unanswered
-- **✅ Answered** — Maintainer already responded
-- **🐛 Bug reported** — A bug was mentioned that needs tracking
-- **💡 Actionable** — Contains a concrete feature request that could become an issue
-
-### 5. Draft & Post Responses
-
-For each discussion that needs a response, draft a reply following these guidelines:
-
-#### Response Style
-
-- **Friendly and professional** — Start with "Hey @username!"
-- **Acknowledge the contribution** — Thank the user for their input
-- **Be specific** — Reference existing features, settings, or dashboard pages if the feature already exists
-- **Provide workarounds** — If the request isn't implemented yet, suggest current alternatives
-- **Commit to action** — If the request is valid, state that you'll open an issue or add it to the roadmap
-- **Keep it concise** — 3-5 paragraphs max
-
-#### Posting via Browser
-
-- Use `browser_subagent` to navigate to each discussion and post the comment
-- **IMPORTANT**: When typing text in GitHub comment boxes via the browser, use only plain ASCII characters:
-  - Use regular hyphens `-` instead of em-dashes
-  - Use `->` instead of arrow symbols
-  - Do NOT use emoji Unicode characters (the browser keyboard may fail on them)
-  - Use `**bold**` and `\`code\`` markdown formatting
-- Click the green "Comment" button (or "Reply" for threaded replies) after typing
-- Verify the comment was posted by checking the page shows the new comment
-
-### 6. Create Issues from Actionable Feature Requests
-
-For discussions that contain concrete, actionable feature requests:
-
-1. Ask the user which ones should become issues
-2. For each approved request, create a GitHub issue via `browser_subagent`:
-   - Navigate to `https://github.com/<owner>/<repo>/issues/new`
-   - **Title**: `<Feature Name> - <Short description>`
-   - **Body** should include:
-     - `## Feature Request` header
-     - `**Source:** Discussion #N by @author`
-     - `## Problem` — What limitation the user hit
-     - `## Proposed Solution` — How it could work
-     - `### Implementation Ideas` — Technical approach
-     - `### Current Workarounds` — What users can do today
-     - `## Additional Context` — Links to related issues/discussions
-   - Add `enhancement` label
-   - Click "Submit new issue" / "Create"
-3. After creation, go back to the original discussion and post a comment linking to the new issue:
-   - "I've opened Issue #N to track this feature request. Follow along there for updates!"
-
-### 7. Final Report
-
-Present a final summary to the user:
-
-| Discussion | Action Taken                       |
-| ---------- | ---------------------------------- |
-| #N — Title | Responded with workarounds         |
-| #N — Title | Responded + created Issue #N       |
-| #N — Title | Already answered, no action needed |
-| #N — Title | Responded to follow-up comment     |
-
-## Notes
-
-- This workflow is **interactive** — always present the summary and wait for user approval before posting responses or creating issues
-- If the user says "pode responder" (or similar approval), proceed with posting all drafted responses
-- For discussions in non-English languages, respond in the same language as the original post
-- Always reference specific dashboard paths, config options, or code files when explaining existing features
-- When a discussion reveals a bug, note it separately from feature requests

.claude/commands/review-prs-cc.md

@@ -1,256 +0,0 @@
----
-description: Analyze open Pull Requests from the project's GitHub repository, generate a critical report, and optionally implement approved changes
----
-
-# /review-prs — PR Review & Analysis Workflow
-
-## ⛔ ABSOLUTE PROHIBITION — Read Before Anything Else
-
-> **NEVER close a contributor's PR if you intend to use ANY of their code, ideas, or fixes.**
->
-> **NEVER manually integrate contributor code into a release branch and then close their PR.**
->
-> These actions are **STRICTLY FORBIDDEN** under all circumstances:
->
-> 1. ❌ Closing a PR and cherry-picking/copying its code into a release branch
-> 2. ❌ Closing a PR "because of conflicts" and re-implementing the same fix yourself
-> 3. ❌ Closing a PR and committing a "similar" solution inspired by it
-> 4. ❌ Using `gh pr close` on any PR whose content was or will be used
->
-> **Why**: Closing a PR after taking the contributor's work means they get ZERO credit on GitHub — no "Merged" badge, no contribution graph entry, no public record. This is effectively stealing their contribution. An audit found this happened to **37 PRs** in the past.
->
-> **The ONLY acceptable flow**: Resolve conflicts IN the contributor's branch, push fixes TO their branch, then merge THEIR PR via `gh pr merge`. See Step 7 and Step 8 for the exact procedure.
->
-> **When to close a PR**: ONLY when the user (repository owner) explicitly requests it, OR when the PR is clearly spam/malicious, OR when the author themselves asks to close it. In ALL other cases, leave it open.
-
-## Overview
-
-This workflow fetches all open PRs from the project's GitHub repository, performs a critical analysis of each one, generates a detailed report, and waits for user approval before proceeding with implementation. **All improvements are committed on the current release branch** (`release/vX.Y.Z`).
-
-> **BRANCH RULE**: PRs are ALWAYS merged into the current `release/vX.Y.Z` branch, NEVER directly into `main`. The release branch acts as a staging area — only after all PRs are integrated and tests pass does the release branch get merged into `main` via the `/generate-release` workflow.
-
-## Steps
-
-### 1. Identify the GitHub Repository
-
-- Read `package.json` to get the repository URL, or use the git remote origin URL
-  // turbo
-- Run: `git -C <project_root> remote get-url origin` to extract the owner/repo
-
-### 2. Ensure Release Branch Exists
-
-// turbo
-
-Before doing any work, ensure you are on the current release branch:
-
-```bash
-# Check current branch
-git branch --show-current
-
-# If on main, determine next version and create the release branch
-VERSION=$(node -p "require('./package.json').version")
-# Bump patch: e.g. 3.3.11 → 3.3.12
-NEXT=$(node -p "const [a,b,c]=('$VERSION').split('.').map(Number); c>=9?a+'.'+(b+1)+'.0':a+'.'+b+'.'+(c+1)")
-git checkout -b release/v$NEXT
-npm version patch --no-git-tag-version
-npm install
-```
-
-If already on a `release/vX.Y.Z` branch, continue working there.
-
-### 3. Fetch Open Pull Requests
-
-// turbo-all
-
-**⚠️ CRITICAL**: The JSON output of `gh pr list` can be truncated by the tool, silently hiding PRs. You MUST use the two-step approach below to guarantee **all** PRs are fetched.
-
-**Step 3a — Get PR numbers only** (small output, never truncated):
-
-- Run: `gh pr list --repo <owner>/<repo> --state open --limit 500 --json number --jq '.[].number'`
-- This outputs one PR number per line. Count them and confirm total.
-
-**Step 3b — Fetch full metadata for each PR** (one call per PR):
-
-- For each PR number from step 3a, run:
-  `gh pr view <NUMBER> --repo <owner>/<repo> --json number,title,author,headRefName,baseRefName,body,createdAt,additions,deletions,files`
-- You may batch these into parallel calls (up to 4 at a time).
-
-**Step 3c — Fetch diffs for each PR** (one call per PR, saved to /tmp):
-
-- For each PR number, run:
-  `gh pr diff <NUMBER> --repo <owner>/<repo> > /tmp/pr<NUMBER>.diff`
-- Then read each diff file with the `Read` tool.
-
-- For each open PR, collect:
-  - PR number, title, author, branch, number of commits, date
-  - PR description/body
-  - Files changed (diff)
-  - Existing review comments (from bots or humans)
-
-**Verification**: Confirm the count of PRs analyzed matches the count from step 3a before proceeding.
-
-### 3.5 Redirect PR Base Branches to Release Branch
-
-// turbo-all
-
-**⚠️ CRITICAL**: Contributors typically open PRs targeting `main`. Before analyzing or merging, redirect ALL open PRs to target the current release branch instead.
-
-```bash
-# Get the current release branch name
-RELEASE_BRANCH=$(git branch --show-current)  # e.g. release/v3.5.4
-
-# For each open PR that targets main, change its base to the release branch
-for PR_NUM in $(gh pr list --repo <owner>/<repo> --state open --json number,baseRefName --jq '.[] | select(.baseRefName == "main") | .number'); do
-  echo "Redirecting PR #$PR_NUM → $RELEASE_BRANCH"
-  gh pr edit "$PR_NUM" --repo <owner>/<repo> --base "$RELEASE_BRANCH"
-done
-```
-
-This ensures:
-
-1. PRs merge into the release branch, not directly into `main`
-2. Merge conflict detection is accurate against the release branch
-3. The release branch accumulates all changes before the final merge to `main`
-4. If the release branch doesn't exist on remote yet, push it first: `git push origin $RELEASE_BRANCH`
-
-### 4. Analyze Each PR — For each open PR, perform the following analysis:
-
-#### 4a. Feature Assessment
-
-- **Does it make sense?** Evaluate if the feature fills a real gap or solves a valid problem
-- **Alignment** — Check if it aligns with the project's architecture and roadmap
-- **Complexity** — Assess if the scope is reasonable or if it should be split
-
-#### 4b. Code Quality Review
-
-- Check for code duplication
-- Evaluate error handling patterns (consistent with existing codebase?)
-- Check naming conventions and code style
-- Verify TypeScript types (any `any` usage, missing types?)
-
-#### 4c. Security Review
-
-- Check for missing authentication/authorization on new endpoints
-- Check for injection vulnerabilities (URL params, SQL, XSS)
-- Verify input validation on all user-controlled data
-- Check for hardcoded secrets or credentials
-
-#### 4d. Architecture Review
-
-- Does the change follow existing patterns?
-- Are there any breaking changes to public APIs?
-- Is the database schema affected? Migration needed?
-- Impact on performance (N+1 queries, missing indexes?)
-
-#### 4e. Test Coverage
-
-- Does the PR include tests?
-- Are edge cases covered?
-- Would existing tests break?
-
-#### 4f. Cross-Layer (Global) Analysis
-
-Perform a **global impact assessment** to verify whether the PR changes are complete across all layers of the application:
-
-- **Backend → Frontend check**: If the PR adds or modifies backend-only resources (new endpoints, services, data models), evaluate whether corresponding frontend changes are missing:
-  - Does a new endpoint require a new screen/page in the dashboard?
-  - Should there be a new action button, menu item, or navigation link?
-  - Are there new data fields that should be displayed or editable in the UI?
-  - Does a new feature need a toggle, configuration panel, or status indicator?
-- **Frontend → Backend check**: If the PR adds frontend elements, verify the backend support exists:
-  - Are the required API endpoints implemented?
-  - Is the data model sufficient for the new UI components?
-- **Cross-cutting concerns**: Check shared layers (types, DTOs, validation schemas, routes, middleware) for completeness
-- **Document gaps** — If missing layers are detected, list them as **IMPORTANT** issues in the report with concrete suggestions for what should be added
-
-### 5. Generate Report — Create a markdown report for each PR including:
-
-- **PR Summary** — What it does, files affected, commit count
-- **Improvements/Benefits** — Numbered list with impact level (HIGH/MEDIUM/LOW)
-- **Risks & Issues** — Categorized as CRITICAL / IMPORTANT / MINOR
-- **Scoring Table** — Rate across: Feature Relevance, Code Quality, Security, Robustness, Tests
-- **Verdict** — Ready to merge? With mandatory vs optional fixes
-- **Next Steps** — What will happen if approved
-
-### 6. Present to User
-
-- Show the report in the final response and stop. This is a mandatory checkpoint awaiting explicit user approval before continuing.
-- Wait for user decision:
-  - **Approved** → Proceed to step 7
-  - **Approved with changes** → Implement the fixes and corrections before merging
-  - **Rejected** → Close the PR or leave a review comment
-
-### 7. Pre-Merge Fixes & CI Green-Lighting (if approved)
-
-> **⚠️ Fixes and Conflict Resolutions MUST be pushed back to the PR branch before merging.** We want the PR itself to be green and fully valid before it integrates.
-
-- **Sync latest fixes & Resolve Conflicts:** Merge the current `release` branch into the PR branch. If there are merge conflicts, you MUST resolve them inside the author's PR branch. NEVER resolve conflicts by closing their PR and doing the work in a separate branch, as this steals credit from the original author.
-- **Implement improvements:** Apply the required fixes identified in the analysis directly on the PR branch (e.g., adding missing API routes, fixing SSRF, applying comments from other agents).
-- **Pushing changes to PR branches:**
-
-  ```bash
-  # Checkout the PR locally
-  gh pr checkout <NUMBER>
-
-  # Apply fixes, commit your changes
-  git commit -m "chore: apply review suggestions and missing layers"
-
-  # Attempt to push directly to the PR branch
-  git push
-  ```
-
-- **Fallback (ONLY for external forks without maintainer edit access):**
-  Using `cherry-pick` instead of fixing the contributor's PR directly is a **LAST RESORT**. You MUST ALWAYS attempt to `git push` your fixes to their branch first.
-  **ONLY if `git push` explicitly fails with a permission/access error** (meaning the contributor unchecked "Allow edits from maintainers" or it's a locked fork), you may use `git cherry-pick` to bring their changes into the release branch and fix the issues locally.
-  Even then, ensure you preserve the contributor's authorship (`git commit --author="Contributor Name <email>"` if creating new commits).
-  Once you have integrated their work into the release branch, **DO NOT close their PR**. Leave it open so the contributor retains credit. Under NO CIRCUMSTANCES should you use `gh pr close`.
-
-- Run the project's test suite locally to verify nothing breaks:
-  // turbo
-- Run: `npm test` or equivalent test command
-
-### 8. Merge into Release Branch (NEVER CLOSE!)
-
-> **⚠️ CRITICAL**: NEVER use `gh pr close` for a PR whose idea or code was accepted. Closing a PR in a contributor's face after taking their idea—or closing it just because it had conflicts—is unacceptable.
-> You MUST ALWAYS resolve conflicts and apply fixes ON THE AUTHOR'S PR BRANCH (unless explicitly locked from edits), and then merge the PR using GitHub so the contributor gets the official "Merged" badge and proper credit on their profile. **Do not use cherry-pick just because it is "easier" than resolving conflicts on their branch.**
-
-Even if the PR had severe conflicts or required significant architectural adjustments, you MUST:
-
-1. Resolve any conflicts and apply the fixes directly to their PR branch (as detailed in step 7) or use cherry-picking into the release branch.
-2. If you managed to fix their branch, merge it into the release branch using the GitHub CLI:
-   `gh pr merge <NUMBER> --repo <owner>/<repo> --squash --body "Integrated into release/vX.Y.Z"`
-3. If you had to use cherry-picking because you couldn't push to their branch, DO NOT close the PR. GitHub will sometimes auto-detect the cherry-picked commits and mark it as Merged. If it doesn't, leave it open. The repository owner will handle it. NEVER run `gh pr close`.
-
-In ALL cases:
-
-- Post a **thank-you comment** on the PR via the GitHub API before or immediately after merging.
-- The message should:
-  - Thank the author by name/username for their contribution.
-  - Explain what was adjusted or improved (if we pushed fixes to their branch or cherry-picked).
-  - Note it will be included in the upcoming release.
-  - Be friendly, professional, and encouraging.
-
-> **⚠️ MANDATORY CHANGELOG CREDIT**: When cherry-picking is used (because the PR branch couldn't be pushed to or `gh pr merge` failed), the contributor does NOT get the automatic GitHub "Merged" badge. In this case, you MUST compensate by adding an explicit entry to `CHANGELOG.md` in the `[Unreleased]` section with `(#PR_NUMBER — thanks @username)` format. This ensures the contributor gets public credit in the release notes even if GitHub doesn't auto-detect the cherry-pick. This is NOT optional — skipping it effectively erases the contributor's work from the release record.
-
-### 9. Sync Local Release Branch
-
-After merging PRs, sync the local release branch to include the new changes:
-
-```bash
-git fetch origin
-git pull origin release/vX.Y.Z
-```
-
-### 10. Continue or Finalize
-
-After processing all approved PRs:
-
-- If more PRs remain, go back to step 7
-- When all PRs are processed, **update CHANGELOG.md** on the release branch with all new entries
-- Run **test coverage** to verify the gate (≥75% statements/lines/functions, ≥70% branches — measured ~82%):
-  ```bash
-  npm run test:coverage
-  ```
-- Fix any test regressions introduced by merged PRs
-- Run `/generate-release` workflow Phase 1 steps 7–10 (tests → commit → push → open PR to main → wait for user)
-- The `/generate-release` workflow handles the final merge from `release/vX.Y.Z` → `main`

.claude/commands/version-bump-cc.md

@@ -1,341 +0,0 @@
----
-description: Bump version, auto-generate CHANGELOG from git commits, update all versioned files, and refresh root + docs/ documentation to reflect the current project state
----
-
-# Version Bump Workflow
-
-Automatically bump the project version, generate CHANGELOG entries from git history since the last tag, update every file that references the version, and refresh project documentation to reflect the current state.
-
-> **VERSION RULE: Always use PATCH bumps (3.x.y → 3.x.y+1)**
-> NEVER use `npm version minor` or `npm version major`.
-> Always use: `npm version patch --no-git-tag-version`
-> The threshold rule: when `y` reaches 10, bump to `3.(x+1).0` — e.g. `3.4.10` → `3.5.0`.
-
----
-
-## Phase 1: Determine Version
-
-### 1. Read current version and last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-CURRENT_VERSION=$(node -p "require('./package.json').version")
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
-CURRENT_BRANCH=$(git branch --show-current)
-echo "Current version: $CURRENT_VERSION"
-echo "Last tag: $LAST_TAG"
-echo "Current branch: $CURRENT_BRANCH"
-```
-
-### 2. Calculate new version
-
-Apply the patch bump rule:
-
-- If the current patch number is `9`, the new version is `3.(minor+1).0`
-- Otherwise, increment patch: `3.x.y` → `3.x.(y+1)`
-
-If the version was ALREADY bumped (e.g. you are on a release branch and package.json already has the new version), **skip the npm version bump** and use the existing version.
-
-### 3. Bump package.json (if needed)
-
-// turbo
-
-```bash
-# Only if version hasn't been bumped yet
-npm version patch --no-git-tag-version
-```
-
-Or for threshold (y=10):
-
-```bash
-# Manual threshold bump
-VERSION="3.X.0"  # compute manually
-npm version "$VERSION" --no-git-tag-version
-```
-
----
-
-## Phase 2: Generate CHANGELOG from Git History
-
-### 4. Collect commits since last tag
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null)
-echo "=== Commits since $LAST_TAG ==="
-git log "$LAST_TAG"..HEAD --pretty=format:"%h %s" --no-merges | head -100
-echo ""
-echo "=== Merge commits ==="
-git log "$LAST_TAG"..HEAD --merges --pretty=format:"%h %s" | head -50
-```
-
-### 5. Classify commits and generate CHANGELOG section
-
-Analyze each commit message and classify into categories based on the conventional-commit prefix and content:
-
-| Category            | Patterns                                         |
-| ------------------- | ------------------------------------------------ |
-| ✨ New Features     | `feat:`, `feat(*):`                              |
-| 🐛 Bug Fixes        | `fix:`, `fix(*):`                                |
-| ⚠️ Breaking Changes | `BREAKING CHANGE`, `!:` suffix                   |
-| 🛠️ Maintenance      | `chore:`, `refactor:`, `perf:`, `build:`         |
-| 🧪 Tests            | `test:`, `tests:`                                |
-| 📝 Documentation    | `docs:`                                          |
-| 🔒 Security         | `security:`, CVE references, vulnerability fixes |
-| 🌍 i18n             | translation updates, locale changes              |
-
-For each category with entries, create a markdown section with descriptive bullet points. Use the commit messages but rewrite them to be human-readable and descriptive (not raw commit messages).
-
-**If a commit references a PR number** (e.g. `#880`, `PR #885`), include it in the description.
-
-### 6. Update CHANGELOG.md
-
-Replace the `## [Unreleased]` section content with the generated entries, then add the new versioned section:
-
-```markdown
-## [Unreleased]
-
----
-
-## [NEW_VERSION] — YYYY-MM-DD
-
-### ✨ New Features
-
-- **Feature name:** Description (#PR)
-
-### 🐛 Bug Fixes
-
-- **Fix name:** Description (#PR)
-
-### 🛠️ Maintenance
-
-- **Item:** Description
-
----
-
-## [PREVIOUS_VERSION] — YYYY-MM-DD
-
-...
-```
-
-The date must be today's date in `YYYY-MM-DD` format.
-
----
-
-## Phase 3: Sync Version Across All Files
-
-### 7. Update workspace package.json files and openapi.yaml
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-
-# Update docs/reference/openapi.yaml version
-sed -i "s/  version: .*/  version: $VERSION/" docs/reference/openapi.yaml
-echo "✓ docs/reference/openapi.yaml → $VERSION"
-
-# Update workspace packages (open-sse, electron)
-for dir in electron open-sse; do
-  if [ -d "$dir" ] && [ -f "$dir/package.json" ]; then
-    (cd "$dir" && npm version "$VERSION" --no-git-tag-version --allow-same-version > /dev/null)
-    echo "✓ $dir/package.json → $VERSION"
-  fi
-done
-
-echo "✓ All workspace packages synced to $VERSION"
-```
-
-### 8. Update llm.txt version references
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-OLD_VERSION_PATTERN='[0-9]\+\.[0-9]\+\.[0-9]\+'
-
-# Update "Current version:" line
-sed -i "s/\*\*Current version:\*\* $OLD_VERSION_PATTERN/**Current version:** $VERSION/" llm.txt
-
-# Update "Key Features (vX.Y.Z)" header
-sed -i "s/## Key Features (v$OLD_VERSION_PATTERN)/## Key Features (v$VERSION)/" llm.txt
-
-echo "✓ llm.txt → $VERSION"
-```
-
-### 9. Regenerate lock file
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm install
-echo "✓ Lock file regenerated"
-```
-
----
-
-## Phase 4: Update Root Documentation
-
-Based on the CHANGELOG entries generated in Phase 2, review and update these root-level files if relevant changes warrant updates:
-
-### 10. Review and update root documentation files
-
-For each file below, read the current content and determine if the CHANGELOG entries require any updates. Only modify files where substantive changes have occurred:
-
-| File              | When to update                                                                                                              |
-| ----------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `README.md`       | New providers, major features, stats changes (test count, provider count), badges, installation instructions, feature table |
-| `AGENTS.md`       | Architecture changes, new modules, new commands, new providers, new services/handlers/executors                             |
-| `CONTRIBUTING.md` | Dev workflow changes, new tooling, test infrastructure changes                                                              |
-| `SECURITY.md`     | Security fixes, new auth mechanisms, vulnerability disclosures                                                              |
-| `llm.txt`         | Provider count changes, new features, architecture changes                                                                  |
-
-**Update rules:**
-
-- **README.md**: Update provider count, test count, feature highlights table, badges if any numbers changed. If a new provider was added, add it to the provider table. If a major feature was added, add it to the features section.
-- **AGENTS.md**: If new architecture components (handlers, executors, services, DB modules) were added, update the Architecture section. If new commands were added, update the Build/Test table.
-- **SECURITY.md**: Add new vulnerability fixes or security improvements to the relevant section.
-- **llm.txt**: Update provider count, feature list, version references.
-
-### 11. Review and update docs/ files (excluding i18n/)
-
-For each file in `docs/` (excluding `docs/i18n/`), review if CHANGELOG changes affect it:
-
-| File                                          | When to update                                                     |
-| --------------------------------------------- | ------------------------------------------------------------------ |
-| `docs/reference/API_REFERENCE.md`             | New API endpoints, changed request/response formats                |
-| `docs/architecture/ARCHITECTURE.md`           | New modules, new services, changed data flow                       |
-| `docs/architecture/CODEBASE_DOCUMENTATION.md` | New files, architectural changes, module reorganization            |
-| `docs/architecture/REPOSITORY_MAP.md`         | New folders / files / one-line descriptions                        |
-| `docs/reference/CLI-TOOLS.md`                 | New CLI tool integrations, config format changes                   |
-| `docs/guides/USER_GUIDE.md`                   | UX changes, new dashboard pages, settings changes                  |
-| `docs/reference/PROVIDER_REFERENCE.md`        | New providers (regenerate via `scripts/gen-provider-reference.ts`) |
-| `docs/frameworks/MCP-SERVER.md`               | New MCP tools, changed tool signatures, scope changes              |
-| `docs/frameworks/A2A-SERVER.md`               | New A2A skills, protocol changes                                   |
-| `docs/frameworks/AGENT_PROTOCOLS_GUIDE.md`    | New external agent protocols supported                             |
-| `docs/frameworks/CLOUD_AGENT.md`              | Cloud agent additions (codex-cloud, devin, jules) or API changes   |
-| `docs/architecture/AUTHZ_GUIDE.md`            | New route classifications, policy changes                          |
-| `docs/security/GUARDRAILS.md`                 | New guardrails registered, priority/order changes                  |
-| `docs/security/COMPLIANCE.md`                 | Audit log / retention / no-log policy changes                      |
-| `docs/frameworks/SKILLS.md`                   | Skill framework / registry / built-in skill changes                |
-| `docs/frameworks/MEMORY.md`                   | Memory pipeline / extraction / injection / Qdrant changes          |
-| `docs/frameworks/EVALS.md`                    | Evaluation framework changes, new evaluators                       |
-| `docs/frameworks/WEBHOOKS.md`                 | New webhook events, payload schema changes                         |
-| `docs/routing/REASONING_REPLAY.md`            | Reasoning capture/replay pipeline changes                          |
-| `docs/routing/AUTO-COMBO.md`                  | Routing changes, new strategies, scoring weight changes            |
-| `docs/architecture/RESILIENCE_GUIDE.md`       | Circuit breaker / cooldown / lockout behavior changes              |
-| `docs/security/STEALTH_GUIDE.md`              | TLS / CLI fingerprint changes                                      |
-| `docs/ops/TUNNELS_GUIDE.md`                   | Cloudflare tunnel feature changes                                  |
-| `docs/guides/ELECTRON_GUIDE.md`               | Electron build / signing / packaging changes                       |
-| `docs/guides/TROUBLESHOOTING.md`              | New known issues, resolved problems                                |
-| `docs/ops/RELEASE_CHECKLIST.md`               | Process changes                                                    |
-| `docs/ops/COVERAGE_PLAN.md`                   | Coverage gate adjustments, target metrics                          |
-| `docs/reference/openapi.yaml`                 | Already updated in step 7                                          |
-
-**Only update files where the CHANGELOG entries directly affect the documented content.** Do NOT update files just to bump a version number — only when the documented behavior, features, or architecture has actually changed.
-
----
-
-## Phase 5: Verify
-
-### 12. Run lint check
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm run lint
-```
-
-### 13. Run tests
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-npm test
-```
-
-### 14. Verify version sync across all files
-
-// turbo
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-VERSION=$(node -p "require('./package.json').version")
-echo "Expected version: $VERSION"
-echo ""
-
-echo "--- package.json ---"
-grep '"version"' package.json | head -1
-
-echo "--- open-sse/package.json ---"
-grep '"version"' open-sse/package.json | head -1
-
-echo "--- electron/package.json ---"
-[ -f electron/package.json ] && grep '"version"' electron/package.json | head -1
-
-echo "--- docs/reference/openapi.yaml ---"
-grep "  version:" docs/reference/openapi.yaml | head -1
-
-echo "--- llm.txt ---"
-grep "Current version:" llm.txt
-
-echo "--- CHANGELOG.md (first versioned entry) ---"
-grep "^## \[" CHANGELOG.md | head -2
-```
-
-### 15. 🛑 STOP — Present Summary to User
-
-**STOP** and present a summary to the user including:
-
-- Old version → New version
-- CHANGELOG entries generated
-- Files modified
-- Test results
-- Any documentation updates made
-
-**Wait for the user to confirm before committing.**
-
----
-
-## Phase 6: Commit (only after user approval)
-
-### 16. Stage and commit
-
-// turbo-all
-
-```bash
-cd /home/diegosouzapw/dev/proxys/OmniRoute
-git add -A
-VERSION=$(node -p "require('./package.json').version")
-git commit -m "chore(release): bump to v$VERSION — changelog, docs, version sync"
-```
-
----
-
-## Notes
-
-- This workflow does **NOT** create tags, releases, or deploy. Use `/generate-release` for the full release cycle after this.
-- This workflow does **NOT** update `docs/i18n/` translations. Translation updates are handled manually or via release tooling — the `/update-i18n` command does not currently exist as a Claude Code slash command.
-- The CHANGELOG generation is based on git commits since the last tag. If there are no new commits, the workflow should inform the user and stop.
-- Always verify the generated CHANGELOG entries make sense — raw commit messages may need rewriting for clarity.
-- If the version was already bumped (e.g. you're on a `release/vX.Y.Z` branch), skip the `npm version` step and use the existing version.
-
-## Version Touchpoints Checklist
-
-| File                          | Field/Pattern                                               |
-| ----------------------------- | ----------------------------------------------------------- |
-| `package.json`                | `"version": "X.Y.Z"`                                        |
-| `open-sse/package.json`       | `"version": "X.Y.Z"`                                        |
-| `electron/package.json`       | `"version": "X.Y.Z"`                                        |
-| `docs/reference/openapi.yaml` | `version: X.Y.Z`                                            |
-| `llm.txt`                     | `**Current version:** X.Y.Z` and `## Key Features (vX.Y.Z)` |
-| `CHANGELOG.md`                | `## [X.Y.Z] — YYYY-MM-DD`                                   |

.dockerignore

@@ -9,6 +9,7 @@
 # Dependencies and build output
 node_modules
 .next
+.build
 out
 build
 dist
@@ -41,20 +42,18 @@ blob-report
 # Issue #2348: The Dashboard Docs viewer reads markdown from `/app/docs` at
 # runtime. The previous `docs/*` block hid every file except openapi.yaml,
 # so the in-product help screen failed with ENOENT for every page.
-# We now keep the English markdown tree but drop the bulky assets
-# (translations, screenshots, raster diagrams) that account for ~45 MB
+# We now keep the English markdown tree plus the docs assets imported by MDX
+# during `next build`, while still dropping the bulky translated docs and
+# extra raster diagram sources that account for most of the docs footprint
 # of the ~50 MB docs directory. The Docs viewer reads the default-locale
 # (English) sources at runtime, so translations are not required in the
 # container image.
 docs/i18n/**
-docs/screenshots/**
-docs/diagrams/exported/**
 docs/diagrams/**/*.png
 docs/diagrams/**/*.jpg
 docs/diagrams/**/*.jpeg
 docs/diagrams/**/*.gif
 docs/diagrams/**/*.webp
-docs/diagrams/**/*.svg
 # Note: `*.md` matches the root only (Go filepath.Match does not cross /),
 # so nested docs/**/*.md is implicitly kept without a re-include rule.
 *.md
@@ -78,6 +77,8 @@ bun.lock
 # Agent config
 .agents
 .gemini
+.claude
+.source
 
 # Misc
 llm.txt
@@ -124,3 +125,4 @@ app.__qa_backup/
 .worktrees
 .next-playwright/
 cloud/
+electron/dist-electron

.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.sh]
+indent_size = 4

.env.homolog.example

@@ -0,0 +1,9 @@
+# Homologação E2E real — copie para .env.homolog (NUNCA commitar o real)
+HOMOLOG_BASE_URL=http://192.168.0.15:20128
+# Senha de management do dashboard da VPS (a mesma do /login)
+HOMOLOG_ADMIN_PASSWORD=
+# Deixe vazio: a suíte cria uma API key efêmera via admin e revoga no fim.
+# Só preencha para depurar uma camada isolada com uma key fixa.
+HOMOLOG_API_KEY=
+# Tier crítico (chat real, max_tokens=5). Demais providers: só validação de catálogo.
+HOMOLOG_CRITICAL_PROVIDERS=openai,anthropic,gemini,codex,grok,glm,deepseek,openrouter

.github/FUNDING.yml

@@ -0,0 +1,5 @@
+# Funding links for OmniRoute — rendered as the "Sponsor" button on GitHub.
+# Docs: https://docs.github.com/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository
+github: diegosouzapw
+# Additional platforms (uncomment and fill in before enabling):
+# custom: ["https://omniroute.online/donate"]

.github/actions/npm-ci-retry/action.yml

@@ -0,0 +1,29 @@
+name: npm ci with retry
+description: Run npm ci with retries for transient registry/network failures.
+runs:
+  using: composite
+  steps:
+    - shell: bash
+      run: |
+        set -euo pipefail
+
+        max_attempts=3
+        delay_seconds=20
+
+        for attempt in $(seq 1 "$max_attempts"); do
+          if [ "$attempt" -gt 1 ]; then
+            echo "npm ci attempt $attempt/$max_attempts after transient failure"
+          fi
+
+          if npm ci; then
+            exit 0
+          fi
+
+          exit_code=$?
+          if [ "$attempt" -eq "$max_attempts" ]; then
+            exit "$exit_code"
+          fi
+
+          sleep "$delay_seconds"
+          delay_seconds=$((delay_seconds * 2))
+        done

.github/dependabot.yml

@@ -24,6 +24,29 @@ updates:
         update-types: ["version-update:semver-major"]
       - dependency-name: "eslint-config-next"
         update-types: ["version-update:semver-major"]
+      # typescript majors are peer-blocked by typescript-eslint, which pins a hard
+      # upper bound (8.64.0 → peerDependencies.typescript ">=4.8.4 <6.1.0"). A TS 7
+      # bump therefore violates the peer and takes down the whole toolchain at once —
+      # #7068 grouped it with 6 harmless bumps and turned Build + Lint + Quality Ratchet
+      # + Unit (6/8, 8/8) + Integration (1/2, 2/2) + dast-smoke red in one shot, blocking
+      # the innocuous updates riding along with it. Un-ignore once typescript-eslint
+      # widens the peer, and migrate TS majors intentionally (own PR, own CI run).
+      - dependency-name: "typescript"
+        update-types: ["version-update:semver-major"]
+      # jscpd v5 is a Rust rewrite (native binary, no Node.js programmatic API).
+      # scripts/check/check-duplication.mjs is deliberately pinned to jscpd@4 (it
+      # parses jscpd-report.json against a frozen baseline). A v5 major would break
+      # the duplication gate — migrate the gate intentionally, not via dependabot.
+      - dependency-name: "jscpd"
+        update-types: ["version-update:semver-major"]
+      # @huggingface/transformers is HARD-PINNED at 3.5.2 (exact, no caret) — FROZEN.
+      # It is load-bearing for the LLMLingua ONNX compression engine (open-sse/services/
+      # compression/engines/llmlingua/ — worker.ts pins @huggingface/transformers@3.5.2)
+      # and for local memory embeddings (src/lib/memory/embedding/transformersLocal.ts),
+      # and was VPS-validated at 3.5.2 (#4014). 4.x breaks both, and even 3.x minors must
+      # be re-validated on the VPS — so freeze ALL auto-bumps (no update-types = ignore
+      # every version). Migrate it intentionally, not via dependabot (#4050).
+      - dependency-name: "@huggingface/transformers"
 
   - package-ecosystem: "github-actions"
     directory: "/"

.github/workflows/build-fork.yml

@@ -1,23 +1,36 @@
-name: Build Fork Image (ghcr.io)
+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
-  packages: write
+
+env:
+  IMAGE_NAME: ghcr.io/kang-heewon/omniroute
 
 jobs:
   build:
-    name: Build and Push to ghcr.io
+    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@v6
+        uses: actions/checkout@v7
         with:
-          ref: main
+          persist-credentials: false
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v4
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v4
@@ -29,14 +42,30 @@ jobs:
           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
+          platforms: linux/amd64,linux/arm64
           push: true
-          tags: |
-            ghcr.io/gi99lin/omniroute:latest
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
           cache-from: type=gha
           cache-to: type=gha,mode=max

.github/workflows/claude-code-review.yml

@@ -1,43 +0,0 @@
-name: Claude Code Review
-
-on:
-  pull_request:
-    types: [opened, synchronize, ready_for_review, reopened]
-    # Optional: Only run on specific file changes
-    # paths:
-    #   - "src/**/*.ts"
-    #   - "src/**/*.tsx"
-    #   - "src/**/*.js"
-    #   - "src/**/*.jsx"
-
-jobs:
-  claude-review:
-    # Optional: Filter by PR author
-    # if: |
-    #   github.event.pull_request.user.login == 'external-contributor' ||
-    #   github.event.pull_request.user.login == 'new-developer' ||
-    #   github.event.pull_request.author_association == 'FIRST_TIME_CONTRIBUTOR'
-
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      pull-requests: read
-      issues: read
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          fetch-depth: 1
-
-      - name: Run Claude Code Review
-        id: claude-review
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          plugin_marketplaces: "https://github.com/anthropics/claude-code.git"
-          plugins: "code-review@claude-code-plugins"
-          prompt: "/code-review:code-review ${{ github.repository }}/pull/${{ github.event.pull_request.number }}"
-          # See https://github.com/anthropics/claude-code-action/blob/main/docs/usage.md
-          # or https://code.claude.com/docs/en/cli-reference for available options

.github/workflows/claude.yml

@@ -10,6 +10,10 @@ on:
   pull_request_review:
     types: [submitted]
 
+# Least-privilege default: no token permissions at the top level; the `claude` job
+# grants exactly what it needs below (Scorecard TokenPermissions).
+permissions: {}
+
 jobs:
   claude:
     if: |
@@ -26,8 +30,9 @@ jobs:
       actions: read # Required for Claude to read CI results on PRs
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
+          persist-credentials: false
           fetch-depth: 1
 
       - name: Run Claude Code

.github/workflows/codeql.yml

@@ -0,0 +1,31 @@
+name: CodeQL
+# OWNER ACTION REQUIRED before enabling auto-triggers: advanced CodeQL conflicts with
+# GitHub "default setup" — the analyze step fails with "CodeQL analyses from advanced
+# configurations cannot be processed when the default setup is enabled". Switch repo
+# Settings → Code security → CodeQL from Default to Advanced, THEN restore the
+# push/pull_request/schedule triggers below. Until then this only runs on manual dispatch
+# so it never produces a red check on PRs. (The codeqlAlerts ratchet keeps working via the
+# default setup's alerts in the meantime.)
+on:
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  analyze:
+    name: Analyze (javascript-typescript)
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+      contents: read
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
+      - uses: github/codeql-action/init@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 # v4.37.0
+        with:
+          languages: javascript-typescript
+          queries: security-extended
+      - uses: github/codeql-action/analyze@99df26d4f13ea111d4ec1a7dddef6063f76b97e9 # v4.37.0
+        with:
+          category: "/language:javascript-typescript"

.github/workflows/dast-smoke.yml

@@ -0,0 +1,65 @@
+name: DAST smoke (PR)
+on:
+  pull_request:
+    branches: ["main", "release/**"]
+permissions:
+  contents: read
+jobs:
+  dast-smoke:
+    runs-on: ubuntu-latest
+    # ADVISORY while this new gate matures (repo convention: advisory -> blocking).
+    # Flip to blocking (remove continue-on-error) once it's proven stable across a few PRs.
+    continue-on-error: true
+    # Build CLI bundle alone varies 6-11min on GitHub-hosted runners (3 consecutive
+    # timeouts observed on 2026-07-14 with the old 12min cap killing schemathesis
+    # mid-run) — 25min leaves real headroom for the actual DAST steps.
+    timeout-minutes: 25
+    env:
+      JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-api-key-secret-with-sufficient-length-aaaa
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: Build CLI bundle
+        run: npm run build:cli
+      - name: Start OmniRoute
+        env:
+          PORT: "20128"
+          INJECTION_GUARD_MODE: block
+        run: |
+          node dist/server.js > server.log 2>&1 &
+          echo $! > server.pid
+          for _ in $(seq 1 30); do
+            if curl -sf http://localhost:20128/api/monitoring/health >/dev/null; then echo up; break; fi
+            sleep 2
+          done
+      - uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405 # v6.2.0
+        with:
+          python-version: "3.12"
+      - run: pip install schemathesis
+      - name: Schemathesis smoke (high-risk endpoints, blocking)
+        run: |
+          schemathesis run docs/openapi.yaml --url http://localhost:20128 \
+            --include-path-regex '^/v1/(chat/completions|models)$|^/api/(auth|keys)' \
+            --max-examples 8 --workers 4 --checks all --max-response-time 30 \
+            --request-timeout 20 --suppress-health-check all --no-color
+      - name: promptfoo injection-guard (blocking)
+        env:
+          OMNIROUTE_URL: http://localhost:20128
+          OMNIROUTE_API_KEY: not-needed-blocked-before-upstream
+        run: npx --yes promptfoo@latest eval -c promptfooconfig.yaml --no-cache
+      - name: Stop server
+        if: always()
+        run: kill "$(cat server.pid)" || true
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        if: always()
+        with:
+          name: dast-smoke-logs
+          path: server.log
+          retention-days: 7

.github/workflows/deploy-vps.yml

@@ -17,27 +17,82 @@ jobs:
     name: Deploy OmniRoute to VPS
     runs-on: ubuntu-latest
     steps:
+      - name: Check VPS SSH reachability from runner
+        id: reach
+        env:
+          # Pass the host via env (never interpolate a secret straight into the
+          # script body) so /dev/tcp gets a shell variable, not inlined text.
+          VPS_HOST: ${{ secrets.VPS_HOST }}
+        run: |
+          set -uo pipefail
+          # A GitHub-hosted runner can only deploy when it can actually open a TCP
+          # connection to the VPS SSH port. The Local VPS lives on a private LAN and
+          # the Akamai host firewalls :22 to known IPs, so the runner is routinely
+          # unable to reach it (`dial tcp ***:22: i/o timeout`). Treat "unreachable
+          # from the runner" as a SKIP — the real deploys are run manually from an
+          # allowed network via the deploy-vps-local / deploy-vps-akamai skills — so
+          # an unreachable host no longer red-fails every release/push pipeline.
+          # When the host IS reachable, the deploy step below still runs in full and
+          # its health gate surfaces any genuine deploy failure.
+          if timeout 15 bash -c 'exec 3<>"/dev/tcp/${VPS_HOST}/22"' 2>/dev/null; then
+            echo "reachable=true" >> "$GITHUB_OUTPUT"
+            echo "✅ VPS_HOST:22 reachable from the runner — proceeding with deploy."
+          else
+            echo "reachable=false" >> "$GITHUB_OUTPUT"
+            echo "::warning title=Auto-deploy skipped::VPS_HOST:22 is not reachable from this GitHub runner (private LAN / firewalled). Deploy manually with the deploy-vps-local or deploy-vps-akamai skill."
+          fi
+
       - name: Deploy via SSH
+        if: steps.reach.outputs.reachable == 'true'
         uses: appleboy/ssh-action@v1
-        continue-on-error: true
         with:
           host: ${{ secrets.VPS_HOST }}
           username: ${{ secrets.VPS_USER }}
           key: ${{ secrets.VPS_SSH_KEY }}
           port: 22
-          timeout: 30s
-          command_timeout: 5m
+          timeout: 60s
+          command_timeout: 15m
           script: |
-            echo "=== Updating OmniRoute ==="
-            npm install -g omniroute@latest 2>&1
-            INSTALLED_VERSION=$(omniroute --version 2>/dev/null || echo "unknown")
-            echo "Installed version: $INSTALLED_VERSION"
+            set -euo pipefail
 
-            echo "=== Restarting PM2 ==="
-            pm2 restart omniroute || pm2 start omniroute --name omniroute -- --port 20128
+            echo "=== Updating OmniRoute ==="
+            npm install -g omniroute@latest
+            INSTALLED_VERSION=$(omniroute --version 2>/dev/null | tr -d '[:space:]' || echo "unknown")
+            echo "Installed CLI version: $INSTALLED_VERSION"
+
+            # Recreate the PM2 process instead of `pm2 restart`. A bare restart
+            # re-runs whatever script path was saved earlier; after the build-output
+            # reorg (app/ -> dist/, .next -> .build/next) a process pinned to the old
+            # app/server-ws.mjs path can no longer start, and the node process dies
+            # while PM2 still reports "online" — so the box never binds :20128.
+            # Always launch via the `omniroute` bin so .env is loaded and the dist/
+            # layout is resolved correctly.
+            echo "=== (Re)creating PM2 process via bin ==="
+            pm2 delete omniroute 2>/dev/null || true
+            pm2 start omniroute --name omniroute -- --port 20128
             pm2 save
 
-            echo "=== Health Check ==="
-            sleep 3
-            curl -sf http://localhost:20128/api/settings > /dev/null && echo "✅ OmniRoute is healthy" || echo "❌ Health check failed"
+            # Health gate: fail the deploy unless the box actually reports healthy.
+            # Poll /api/monitoring/health for "status":"healthy" (a deeper signal than
+            # a static page 200 — it confirms the app booted, not just that a port is
+            # bound). Boot can take a while after a native-module/build-layout change,
+            # so poll up to ~3min before giving up.
+            echo "=== Health Check (gates the deploy) ==="
+            ok=0
+            for i in $(seq 1 36); do
+              BODY=$(curl -sf -m 5 http://localhost:20128/api/monitoring/health 2>/dev/null || true)
+              if printf '%s' "$BODY" | grep -q '"status":"healthy"'; then
+                ok=1
+                echo "✅ /api/monitoring/health -> healthy (attempt $i) — version $INSTALLED_VERSION"
+                break
+              fi
+              echo "… not healthy yet (attempt $i/36), retrying in 5s"
+              sleep 5
+            done
+            if [ "$ok" != "1" ]; then
+              echo "❌ Health check failed — /api/monitoring/health never reported healthy after ~3min"
+              echo "--- recent PM2 logs ---"
+              pm2 logs omniroute --lines 40 --nostream || true
+              exit 1
+            fi
             echo "=== Deploy complete ==="

.github/workflows/docker-publish.yml

@@ -8,33 +8,148 @@ on:
       - "v*"
     paths-ignore:
       - ".github/workflows/**"
+  # Use 'released' instead of 'published' so editing/re-publishing old releases
+  # does NOT re-trigger this workflow. 'released' fires only on the initial
+  # release publication (and pre-release → release transition).
   release:
-    types: [published]
+    types: [released]
   workflow_dispatch:
     inputs:
       version:
-        description: "Version tag to build (e.g. 2.6.0)"
+        description: "Version tag to build (e.g. 3.8.4)"
         required: true
         type: string
+      promote_latest:
+        description: "Also tag :latest (only if this is the highest semver)"
+        required: false
+        type: boolean
+        default: false
 
+# Least-privilege default: read-only at the top level; the build and merge jobs that
+# push to GHCR grant packages: write themselves (Scorecard TokenPermissions).
 permissions:
   contents: read
-  packages: write
 
 jobs:
-  docker:
-    name: Build and Push Docker (multi-arch)
+  prepare:
+    name: Resolve Docker release metadata
     runs-on: ubuntu-latest
+    outputs:
+      version: ${{ steps.version.outputs.version }}
+      promote_latest: ${{ steps.version.outputs.promote_latest }}
+      skip: ${{ steps.version.outputs.skip }}
     env:
       IMAGE_NAME: diegosouzapw/omniroute
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
+          persist-credentials: false
           ref: ${{ github.event_name == 'workflow_dispatch' && format('refs/tags/v{0}', inputs.version) || '' }}
+          # Need full tag history for semver comparison when deciding :latest.
+          fetch-depth: 0
 
-      - name: Set up QEMU (for multi-arch builds)
-        uses: docker/setup-qemu-action@v4
+      - name: Resolve version, latest-promotion, and skip flag
+        id: version
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          REF_NAME: ${{ github.ref_name }}
+          REF_TYPE: ${{ github.ref_type }}
+          INPUT_VERSION: ${{ inputs.version }}
+          PROMOTE_INPUT: ${{ inputs.promote_latest }}
+        run: |
+          set -euo pipefail
+
+          # 1) Resolve version string from the trigger (all inputs come via env).
+          case "$EVENT_NAME" in
+            workflow_dispatch)
+              VERSION="${INPUT_VERSION#v}"
+              ;;
+            push)
+              if [ "$REF_TYPE" = "tag" ]; then
+                VERSION="${REF_NAME#v}"
+              else
+                # Push to main → build & tag as `main` only. Never touch :latest.
+                VERSION="main"
+              fi
+              ;;
+            release)
+              VERSION="${REF_NAME#v}"
+              ;;
+            *)
+              VERSION="${REF_NAME#v}"
+              ;;
+          esac
+          # Sanity-check: only allow [A-Za-z0-9._-] in VERSION (defense in depth).
+          if ! printf '%s' "$VERSION" | grep -qE '^[A-Za-z0-9._-]+$'; then
+            echo "Refusing to use unsafe VERSION value: $VERSION" >&2
+            exit 1
+          fi
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+
+          # 2) Decide whether to promote :latest.
+          PROMOTE="false"
+          if [ "$VERSION" = "main" ]; then
+            PROMOTE="false"
+          elif printf '%s' "$VERSION" | grep -qE -- '-(rc|alpha|beta|pre|next)'; then
+            echo "Pre-release identifier detected — skipping :latest."
+            PROMOTE="false"
+          elif [ "$EVENT_NAME" = "workflow_dispatch" ]; then
+            PROMOTE="${PROMOTE_INPUT:-false}"
+          else
+            git fetch --tags --quiet || true
+            # Decide via the extracted helper, which folds VERSION into the
+            # candidate set so the result is independent of git-tag sync timing
+            # on `release` events (#5301). Without that, the freshly-created tag
+            # is often not yet visible here and :latest stays a release behind.
+            PROMOTE=$(git tag -l 'v[0-9]*' | bash scripts/ci/should-promote-latest.sh "$VERSION")
+            if [ "$PROMOTE" != "true" ]; then
+              echo "Version $VERSION is not the highest stable semver. Not promoting :latest."
+            fi
+          fi
+          echo "promote_latest=$PROMOTE" >> "$GITHUB_OUTPUT"
+
+          # 3) Skip if this exact version is already published in Docker Hub.
+          #    `main` is always rebuilt (mutable floating tag).
+          SKIP="false"
+          if [ "$VERSION" != "main" ]; then
+            if docker manifest inspect "diegosouzapw/omniroute:${VERSION}" >/dev/null 2>&1; then
+              echo "Image diegosouzapw/omniroute:${VERSION} already exists on Docker Hub — skipping rebuild."
+              SKIP="true"
+            fi
+          fi
+          echo "skip=$SKIP" >> "$GITHUB_OUTPUT"
+
+          echo "Publishing diegosouzapw/omniroute:$VERSION (promote_latest=$PROMOTE, skip=$SKIP)"
+
+  build:
+    name: Build Docker (${{ matrix.platform }})
+    needs: prepare
+    if: needs.prepare.outputs.skip != 'true'
+    runs-on: ${{ matrix.runner }}
+    permissions:
+      contents: read
+      packages: write
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - platform: linux/amd64
+            runner: ubuntu-24.04
+            arch: amd64
+          - platform: linux/arm64
+            runner: ubuntu-24.04-arm
+            arch: arm64
+    env:
+      IMAGE_NAME: diegosouzapw/omniroute
+      GHCR_IMAGE_NAME: ghcr.io/diegosouzapw/omniroute
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          ref: ${{ github.event_name == 'workflow_dispatch' && format('refs/tags/v{0}', inputs.version) || '' }}
+          fetch-depth: 0
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v4
@@ -52,41 +167,238 @@ jobs:
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
-      - name: Extract version from release tag or input
-        id: version
-        run: |
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            VERSION="${{ inputs.version }}"
-          else
-            VERSION="${GITHUB_REF_NAME}"
-            VERSION="${VERSION#v}"
-          fi
-          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
-          echo "Publishing Docker image: $IMAGE_NAME:$VERSION"
-
-      - name: Build and push multi-arch image
+      - name: Build and push platform image by digest
+        id: build
         uses: docker/build-push-action@v7
         with:
           context: .
           target: runner-base
-          platforms: linux/amd64,linux/arm64
-          push: true
+          platforms: ${{ matrix.platform }}
+          outputs: type=image,push-by-digest=true,name-canonical=true,push=true
           tags: |
-            ${{ env.IMAGE_NAME }}:${{ steps.version.outputs.version }}
-            ${{ env.IMAGE_NAME }}:latest
-            ghcr.io/diegosouzapw/omniroute:${{ steps.version.outputs.version }}
-            ghcr.io/diegosouzapw/omniroute:latest
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+            ${{ env.IMAGE_NAME }}
+            ${{ env.GHCR_IMAGE_NAME }}
+          cache-from: type=gha,scope=docker-${{ matrix.arch }}
+          cache-to: type=gha,scope=docker-${{ matrix.arch }},mode=max
           no-cache: false
         env:
           DOCKER_BUILDKIT_INLINE_CACHE: 1
 
-      - name: Inspect image
+      - name: Build and push WEB platform image by digest
+        id: build-web
+        uses: docker/build-push-action@v7
+        with:
+          context: .
+          target: runner-web
+          platforms: ${{ matrix.platform }}
+          outputs: type=image,push-by-digest=true,name-canonical=true,push=true
+          tags: |
+            ${{ env.IMAGE_NAME }}
+            ${{ env.GHCR_IMAGE_NAME }}
+          cache-from: type=gha,scope=docker-web-${{ matrix.arch }}
+          cache-to: type=gha,scope=docker-web-${{ matrix.arch }},mode=max
+          no-cache: false
+        env:
+          DOCKER_BUILDKIT_INLINE_CACHE: 1
+
+      - name: Export digests
+        env:
+          DIGEST_BASE: ${{ steps.build.outputs.digest }}
+          DIGEST_WEB: ${{ steps.build-web.outputs.digest }}
         run: |
-          docker buildx imagetools inspect "${{ env.IMAGE_NAME }}:${{ steps.version.outputs.version }}"
+          set -euo pipefail
+          mkdir -p /tmp/digests/base /tmp/digests/web
+          touch "/tmp/digests/base/${DIGEST_BASE#sha256:}"
+          touch "/tmp/digests/web/${DIGEST_WEB#sha256:}"
+
+      - name: Upload base digests
+        uses: actions/upload-artifact@v7
+        with:
+          name: digests-base-${{ matrix.arch }}
+          path: /tmp/digests/base/*
+          if-no-files-found: error
+          retention-days: 1
+
+      - name: Upload web digests
+        uses: actions/upload-artifact@v7
+        with:
+          name: digests-web-${{ matrix.arch }}
+          path: /tmp/digests/web/*
+          if-no-files-found: error
+          retention-days: 1
+
+  merge:
+    name: Publish multi-arch manifests
+    needs:
+      - prepare
+      - build
+    if: needs.prepare.outputs.skip != 'true'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+      security-events: write
+    env:
+      IMAGE_NAME: diegosouzapw/omniroute
+      GHCR_IMAGE_NAME: ghcr.io/diegosouzapw/omniroute
+      VERSION: ${{ needs.prepare.outputs.version }}
+      PROMOTE_LATEST: ${{ needs.prepare.outputs.promote_latest }}
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          ref: ${{ github.event_name == 'workflow_dispatch' && format('refs/tags/v{0}', inputs.version) || '' }}
+          fetch-depth: 0
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v4
+
+      - name: Login to Docker Hub
+        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
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Download base digests
+        uses: actions/download-artifact@v8
+        with:
+          pattern: digests-base-*
+          path: /tmp/digests/base
+          merge-multiple: true
+
+      - name: Download web digests
+        uses: actions/download-artifact@v8
+        with:
+          pattern: digests-web-*
+          path: /tmp/digests/web
+          merge-multiple: true
+
+      - name: Create Docker Hub manifest
+        run: |
+          set -euo pipefail
+
+          create_manifest() {
+            local image="$1" suffix="$2" dir="$3"
+            local tags=(-t "${image}:${VERSION}${suffix}")
+            if [ "$PROMOTE_LATEST" = "true" ]; then
+              tags+=(-t "${image}:latest${suffix}")
+            fi
+            local refs=()
+            while IFS= read -r digest_file; do
+              refs+=("${image}@sha256:$(basename "$digest_file")")
+            done < <(find "$dir" -type f | sort)
+            if [ "${#refs[@]}" -eq 0 ]; then
+              echo "No image digests in $dir" >&2
+              exit 1
+            fi
+            docker buildx imagetools create "${tags[@]}" "${refs[@]}"
+          }
+
+          create_manifest "${IMAGE_NAME}" "" /tmp/digests/base
+          create_manifest "${IMAGE_NAME}" "-web" /tmp/digests/web
+
+      - name: Create GHCR manifest
+        run: |
+          set -euo pipefail
+
+          create_manifest() {
+            local image="$1" suffix="$2" dir="$3"
+            local tags=(-t "${image}:${VERSION}${suffix}")
+            if [ "$PROMOTE_LATEST" = "true" ]; then
+              tags+=(-t "${image}:latest${suffix}")
+            fi
+            local refs=()
+            while IFS= read -r digest_file; do
+              refs+=("${image}@sha256:$(basename "$digest_file")")
+            done < <(find "$dir" -type f | sort)
+            if [ "${#refs[@]}" -eq 0 ]; then
+              echo "No image digests in $dir" >&2
+              exit 1
+            fi
+            docker buildx imagetools create "${tags[@]}" "${refs[@]}"
+          }
+
+          create_manifest "${GHCR_IMAGE_NAME}" "" /tmp/digests/base
+          create_manifest "${GHCR_IMAGE_NAME}" "-web" /tmp/digests/web
+
+      - name: Inspect image
+        if: needs.prepare.outputs.version != 'main'
+        run: |
+          docker buildx imagetools inspect "${IMAGE_NAME}:${VERSION}"
+
+      - name: Generate CycloneDX SBOM (image, advisory)
+        if: needs.prepare.outputs.version != 'main'
+        continue-on-error: true
+        uses: anchore/sbom-action@v0
+        with:
+          image: ${{ env.GHCR_IMAGE_NAME }}:${{ env.VERSION }}
+          format: cyclonedx-json
+          output-file: sbom-image.cdx.json
+          artifact-name: sbom-image.cdx.json
+
+      # Visibility scan: reports HIGH + CRITICAL into the SARIF (Security tab) but
+      # never blocks (exit-code 0). The blocking gate below narrows to CRITICAL.
+      #
+      # ignore-unfixed mirrors the blocking gate: the Security tab must surface only
+      # ACTIONABLE vulnerabilities — ones with a published fix we can pull by rebuilding
+      # on a patched base or bumping the dep. Without it the advisory upload floods the
+      # tab with unfixable base-image OS CVEs (Debian trixie packages with no upstream
+      # patch yet, overwhelmingly local-only and not reachable from the proxy request
+      # surface), which is noise an operator cannot act on. trivyignores points at the
+      # repo-root .trivyignore so accepted-risk fixable CVEs have one auditable home.
+      # See docs/security/SUPPLY_CHAIN.md.
+      - name: Trivy image scan (SARIF, advisory)
+        if: needs.prepare.outputs.version != 'main'
+        continue-on-error: true
+        uses: aquasecurity/trivy-action@ed142fd0673e97e23eac54620cfb913e5ce36c25 # v0.36.0
+        with:
+          image-ref: ${{ env.GHCR_IMAGE_NAME }}:${{ env.VERSION }}
+          format: sarif
+          output: trivy-results.sarif
+          severity: HIGH,CRITICAL
+          ignore-unfixed: true
+          trivyignores: .trivyignore
+          exit-code: "0"
+
+      # BLOCKING gate (v3.8.27 cycle-end): fail the release on a CRITICAL CVE in the
+      # published image. Narrowed to severity CRITICAL (HIGH stays visible in the
+      # SARIF step above, not blocking). ignore-unfixed:true so an unfixable base-image
+      # CVE with no upstream patch does not red the release (reduces false-blocks);
+      # a fixable CRITICAL still blocks. Per docs/security/SUPPLY_CHAIN.md. NB: Trivy
+      # scans against a CVE DB that grows continuously — a newly-disclosed CRITICAL on
+      # an unchanged base image can red this gate; the fix is to rebuild on a patched
+      # base, bump the dep, or add a justified .trivyignore entry (see the CVE-variance
+      # note in docs/security/SUPPLY_CHAIN.md).
+      - name: Trivy CRITICAL gate (blocking)
+        if: needs.prepare.outputs.version != 'main'
+        uses: aquasecurity/trivy-action@ed142fd0673e97e23eac54620cfb913e5ce36c25 # v0.36.0
+        with:
+          image-ref: ${{ env.GHCR_IMAGE_NAME }}:${{ env.VERSION }}
+          format: table
+          severity: CRITICAL
+          ignore-unfixed: true
+          exit-code: "1"
+
+      - name: Upload Trivy SARIF to Security tab
+        if: needs.prepare.outputs.version != 'main'
+        continue-on-error: true
+        uses: github/codeql-action/upload-sarif@v4
+        with:
+          sarif_file: trivy-results.sarif
+          category: trivy-image
 
       - name: Update Docker Hub description
+        # Only refresh README/description when we actually promote :latest
+        # (avoids overwriting from main pushes or back-fill builds).
+        if: needs.prepare.outputs.promote_latest == 'true'
         uses: peter-evans/dockerhub-description@v5
         with:
           username: ${{ secrets.DOCKERHUB_USERNAME }}

.github/workflows/electron-release.yml

@@ -11,43 +11,56 @@ on:
         required: true
         type: string
 
+# Least-privilege default: read-only at the top level; each job grants the writes it
+# needs (build/release upload assets, publish-npm forwards npm provenance / packages
+# to the reusable workflow) — Scorecard TokenPermissions.
 permissions:
-  contents: write
-  id-token: write
-  packages: write
+  contents: read
 
 jobs:
   validate:
     name: Validate version
     runs-on: ubuntu-latest
+    permissions:
+      contents: read
     outputs:
       version: ${{ steps.validate.outputs.version }}
     steps:
       - name: Checkout code
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
+          persist-credentials: false
           fetch-depth: 0
 
       - name: Validate version format
         id: validate
+        env:
+          # Pass workflow context via env (never interpolate ${{ ... }} straight
+          # into the run: script body) so the shell receives variables, not
+          # inlined text — zizmor template-injection mitigation. INPUT_VERSION is
+          # the operator-supplied value and is regex-validated below before use.
+          EVENT_NAME: ${{ github.event_name }}
+          INPUT_VERSION: ${{ inputs.version }}
         run: |
-          if [[ "${{ github.event_name }}" == "push" ]]; then
+          if [[ "$EVENT_NAME" == "push" ]]; then
             VERSION="${GITHUB_REF#refs/tags/}"
           else
-            VERSION="${{ inputs.version }}"
+            VERSION="$INPUT_VERSION"
           fi
 
           if [[ ! "$VERSION" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
             echo "Error: Invalid version format. Expected: v1.6.8"
             exit 1
           fi
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
           echo "✓ Valid version: $VERSION"
 
   build:
     name: Build Electron (${{ matrix.platform }})
     needs: validate
     runs-on: ${{ matrix.runner }}
+    permissions:
+      contents: write # electron-builder may publish artifacts with GH_TOKEN
     strategy:
       fail-fast: false
       matrix:
@@ -71,7 +84,9 @@ jobs:
             deb_ext: .deb
 
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
       - name: Setup Node
         uses: actions/setup-node@v6
         with:
@@ -79,7 +94,7 @@ jobs:
           cache: npm
 
       - name: Cache node_modules
-        uses: actions/cache@v5
+        uses: actions/cache@v6.1.0
         with:
           path: node_modules
           key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}
@@ -99,17 +114,23 @@ jobs:
           # that cause EPERM errors during Next.js standalone build glob scans.
           # Create a clean temp profile directory to avoid this.
           mkdir -p "$RUNNER_TEMP/home"
-          echo "USERPROFILE=$RUNNER_TEMP/home" >> $GITHUB_ENV
+          echo "USERPROFILE=$RUNNER_TEMP/home" >> "$GITHUB_ENV"
 
       - name: Build Next.js standalone
         env:
           JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+          NODE_OPTIONS: "--max_old_space_size=6144"
         run: npm run build
 
       - name: Sync version in electron/package.json
         shell: bash
+        env:
+          # Pass the validated version via env (never interpolate ${{ ... }}
+          # straight into the run: script body) — zizmor template-injection
+          # mitigation. Already regex-validated (^v[0-9]+\.[0-9]+\.[0-9]+$) in
+          # the `validate` job, so it cannot carry shell metacharacters.
+          VERSION: ${{ needs.validate.outputs.version }}
         run: |
-          VERSION="${{ needs.validate.outputs.version }}"
           VERSION_NO_V="${VERSION#v}"
           node -e "
             const fs = require('fs');
@@ -135,9 +156,16 @@ jobs:
 
       - name: Smoke packaged Electron app
         if: matrix.platform != 'linux'
-        # Windows CI: requestSingleInstanceLock() fails due to USERPROFILE
-        # sanitization needed for the build step. Smoke is best-effort there.
-        continue-on-error: ${{ matrix.platform == 'windows' }}
+        # Best-effort smoke on Windows + macos-arm64:
+        #  - Windows: requestSingleInstanceLock() fails due to USERPROFILE
+        #    sanitization needed for the build step.
+        #  - macos-arm64: the headless GitHub arm64 runner crashes Electron's GPU
+        #    process (gpu_process_host exit_code=15 → network service crash →
+        #    "No rendezvous client, terminating process"), so the app can't bind
+        #    127.0.0.1:20128 in time. The identical bundle is smoke-gated on
+        #    macos-intel + linux, so packaging is still verified per-OS; we don't
+        #    let the arm64 runner's GPU flakiness block the desktop release.
+        continue-on-error: ${{ matrix.platform == 'windows' || matrix.platform == 'macos-arm64' }}
         env:
           ELECTRON_SMOKE_TIMEOUT_MS: 60000
           ELECTRON_SMOKE_STREAM_LOGS: "1"
@@ -173,6 +201,12 @@ jobs:
               [ -f "$file" ] && cp "$file" "../../release-assets/OmniRoute.exe" && break
             done
           fi
+          # electron-updater manifests (latest.yml / latest-mac.yml / latest-linux.yml)
+          # must be published alongside the installers, or autoUpdater fails with
+          # "Cannot find latest.yml in the latest release artifacts" (#6766).
+          for file in latest*.yml; do
+            [ -f "$file" ] && cp "$file" ../../release-assets/
+          done
 
       - name: Upload artifacts
         uses: actions/upload-artifact@v7
@@ -184,10 +218,13 @@ jobs:
     name: Create Release
     needs: [validate, build]
     runs-on: ubuntu-latest
+    permissions:
+      contents: write # softprops/action-gh-release creates the GitHub Release
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
         with:
+          persist-credentials: false
           fetch-depth: 0
 
       - name: Download all artifacts
@@ -197,14 +234,20 @@ jobs:
           merge-multiple: true
 
       - name: Create source archives
+        env:
+          # Pass the validated version via env (never interpolate ${{ ... }}
+          # straight into the run: script body) — zizmor template-injection
+          # mitigation. Already regex-validated (^v[0-9]+\.[0-9]+\.[0-9]+$) in
+          # the `validate` job, so it cannot carry shell metacharacters.
+          VERSION: ${{ needs.validate.outputs.version }}
         run: |
           # Create source code archives (excluding dev dependencies and build artifacts)
-          export TARBALL="OmniRoute-${{ needs.validate.outputs.version }}.source.tar.gz"
-          export ZIPBALL="OmniRoute-${{ needs.validate.outputs.version }}.source.zip"
+          export TARBALL="OmniRoute-${VERSION}.source.tar.gz"
+          export ZIPBALL="OmniRoute-${VERSION}.source.zip"
 
           # Use git archive for clean source export
-          git archive --format=tar.gz --prefix=OmniRoute-${{ needs.validate.outputs.version }}/ HEAD -o "release-assets/$TARBALL"
-          git archive --format=zip --prefix=OmniRoute-${{ needs.validate.outputs.version }}/ HEAD -o "release-assets/$ZIPBALL"
+          git archive --format=tar.gz --prefix="OmniRoute-${VERSION}/" HEAD -o "release-assets/$TARBALL"
+          git archive --format=zip --prefix="OmniRoute-${VERSION}/" HEAD -o "release-assets/$ZIPBALL"
 
           echo "✓ Created source archives:"
           ls -lh "release-assets/$TARBALL" "release-assets/$ZIPBALL"
@@ -226,6 +269,7 @@ jobs:
             release-assets/*.AppImage
             release-assets/*.deb
             release-assets/*.blockmap
+            release-assets/*.yml
             release-assets/*.source.tar.gz
             release-assets/*.source.zip
         env:
@@ -234,6 +278,14 @@ jobs:
   publish-npm:
     name: Publish to npm
     needs: [validate, release]
+    permissions:
+      # Must be `write`, not `read`: this job calls the reusable npm-publish.yml whose
+      # `publish` job needs `contents: write` (gh release upload — attach the SBOM, #3874).
+      # A reusable workflow's job cannot request more permission than the caller grants,
+      # so a `read` here makes GitHub reject the run at startup (startup_failure).
+      contents: write
+      id-token: write # npm provenance (forwarded to the reusable workflow)
+      packages: write # publish to npm.pkg.github.com
     uses: ./.github/workflows/npm-publish.yml
     with:
       version: ${{ needs.validate.outputs.version }}

.github/workflows/lock-released-branch.yml

@@ -0,0 +1,125 @@
+name: Lock released branch
+
+# Two responsibilities (defense in depth — Hard Rule #18 enforcement):
+#
+# 1. `on: release: published` — when a GitHub Release publishes tag v3.X.Y,
+#    apply branch protection (lock_branch + enforce_admins) to release/v3.X.Y
+#    so no further commits can land on a shipped version. To reopen later:
+#      gh api -X DELETE repos/<owner>/<repo>/branches/release/<tag>/protection
+#
+# 2. `on: push: branches: ['release/v*']` — verify that no push lands on a
+#    release/* branch whose matching tag already exists. This is the preventive
+#    guard: if the lock didn't apply (workflow bug, missing PAT, race), this
+#    job FAILS the push run so the operator gets paged immediately.
+#
+# `permissions:` cannot grant the `Administration` scope to GITHUB_TOKEN — that
+# scope only exists on PATs. Set BRANCH_LOCK_TOKEN as a repo secret pointing to
+# a PAT/fine-grained token with `Administration: read & write`. Without it, the
+# lock step will fail loudly (which is what we want — silent failure caused the
+# v3.8.3 incident on 2026-05-26 where 6 commits landed post-release).
+
+on:
+  release:
+    types: [published]
+  push:
+    branches:
+      - "release/v*"
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Tag of the released version (e.g. v3.8.2)"
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  # ─────────────────────────────────────────────────────────────────────────
+  # Job 1 — Lock the release branch when a Release is published.
+  # ─────────────────────────────────────────────────────────────────────────
+  lock-branch:
+    if: github.event_name == 'release' || github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Lock release/<tag> branch
+        env:
+          # Administration scope is required to PUT branch protection. Default
+          # GITHUB_TOKEN cannot do this — operator must provision BRANCH_LOCK_TOKEN.
+          GH_TOKEN: ${{ secrets.BRANCH_LOCK_TOKEN }}
+          TAG: ${{ github.event.release.tag_name || inputs.tag }}
+          REPO: ${{ github.repository }}
+        run: |
+          set -euo pipefail
+
+          if [ -z "${GH_TOKEN}" ]; then
+            echo "::error::BRANCH_LOCK_TOKEN secret is not set. Create a PAT with Administration:write and add it as repo secret."
+            exit 1
+          fi
+          if [ -z "${TAG}" ]; then
+            echo "::error::No tag provided; cannot determine release branch."
+            exit 1
+          fi
+
+          BRANCH="release/${TAG}"
+          echo "Target branch: ${BRANCH} (repo: ${REPO})"
+
+          if ! gh api "repos/${REPO}/branches/${BRANCH}" >/dev/null 2>&1; then
+            echo "::warning::Branch ${BRANCH} not found — nothing to lock."
+            exit 0
+          fi
+
+          echo "Applying lock_branch protection to ${BRANCH}..."
+          gh api -X PUT "repos/${REPO}/branches/${BRANCH}/protection" --input - <<'JSON'
+          {
+            "required_status_checks": null,
+            "enforce_admins": true,
+            "required_pull_request_reviews": null,
+            "restrictions": null,
+            "lock_branch": true,
+            "allow_force_pushes": false,
+            "allow_deletions": false
+          }
+          JSON
+
+          LOCKED=$(gh api "repos/${REPO}/branches/${BRANCH}/protection" \
+            --jq '.lock_branch.enabled')
+          if [ "${LOCKED}" != "true" ]; then
+            echo "::error::Failed to confirm lock on ${BRANCH} (lock_branch=${LOCKED})."
+            exit 1
+          fi
+          echo "✅ ${BRANCH} is now locked (read-only)."
+
+  # ─────────────────────────────────────────────────────────────────────────
+  # Job 2 — Preventive guard: fail if a push lands on release/vX.Y.Z whose
+  # tag already exists. This catches the case where the lock didn't apply
+  # (PAT missing, race window, workflow bug) and pages the operator.
+  # ─────────────────────────────────────────────────────────────────────────
+  guard-no-push-after-release:
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    steps:
+      - name: Reject push if matching release tag exists
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          REPO: ${{ github.repository }}
+          REF: ${{ github.ref_name }}
+        run: |
+          set -euo pipefail
+
+          # Extract version from ref: release/v3.8.3 -> v3.8.3
+          if [[ ! "${REF}" =~ ^release/(v[0-9]+\.[0-9]+\.[0-9]+)$ ]]; then
+            echo "Ref ${REF} does not match release/vX.Y.Z — nothing to guard."
+            exit 0
+          fi
+          TAG="${BASH_REMATCH[1]}"
+          echo "Checking if tag ${TAG} already exists on ${REPO}..."
+
+          if gh api "repos/${REPO}/git/refs/tags/${TAG}" >/dev/null 2>&1; then
+            echo "::error::Hard Rule #18 violation — push to ${REF} but tag ${TAG} is already released."
+            echo "::error::Hotfixes for a released version must go on a NEW branch: release/v$(echo "${TAG#v}" | awk -F. '{$3=$3+1; print $1"."$2"."$3}' OFS=.)"
+            echo "::error::To undo this push: revert the offending commits, or contact an admin to lock the branch if it wasn't already."
+            exit 1
+          fi
+
+          echo "✅ No release tag for ${TAG} yet — push is OK."

.github/workflows/mutation-redundancy.yml

@@ -0,0 +1,63 @@
+name: Mutation Redundancy (disableBail, on-demand)
+# One-off measurement to UNBLOCK R1 (test-redundancy prune). The nightly mutation run
+# (nightly-mutation.yml) bails on the first kill, so `killedBy` lists only the FIRST
+# killer — 🟠 redundant is understated and 🟢 unique overstated (see the caveat in
+# scripts/quality/mutation-radiography.mjs). This workflow re-runs the SAME combo +
+# chatCore leaf batches with stryker.disablebail.json (disableBail:true, incremental:false)
+# so `killedBy` lists EVERY killer. Feed the uploaded reports to
+# `node scripts/quality/mutation-radiography.mjs --candidates mutation-nobail-*/mutation.json`
+# to get the accurate R1 prune-candidate list (🔴 empty ∪ 🟠 redundant) for human review.
+#
+# Batches mirror the nightly's leaf decomposition (d/e/f/g/h/i) rather than 2 mega-batches:
+# disableBail is MORE expensive than bail (it never stops early), and Stryker only writes
+# mutation.json on a SUCCESSFUL finish — a batch cancelled at the cap produces NO data — so
+# smaller batches each fit the 300min headroom and run in parallel. auth/accountFallback and
+# the security quartet are out of scope: R1 targets the combo/chatCore leaves.
+on:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  stryker-nobail:
+    name: Stryker disableBail (batch ${{ matrix.batch.name }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        batch:
+          - name: d
+            mutate: "open-sse/services/combo/comboStructure.ts,open-sse/services/combo/autoStrategy.ts,open-sse/services/combo/validateQuality.ts"
+          - name: e
+            mutate: "open-sse/services/combo/shadowRouting.ts,open-sse/services/combo/targetSorters.ts,open-sse/services/combo/comboPredicates.ts,open-sse/services/combo/rrState.ts,open-sse/services/combo/comboData.ts"
+          - name: f
+            mutate: "open-sse/services/combo/quotaScoring.ts,open-sse/services/combo/quotaStrategies.ts"
+          - name: g
+            mutate: "open-sse/handlers/chatCore/comboContextCache.ts,open-sse/handlers/chatCore/idempotency.ts,open-sse/handlers/chatCore/passthroughHelpers.ts,open-sse/handlers/chatCore/responseHeaders.ts,open-sse/handlers/chatCore/sanitization.ts,open-sse/handlers/chatCore/upstreamTimeouts.ts"
+          - name: h
+            mutate: "open-sse/handlers/chatCore/headers.ts,open-sse/handlers/chatCore/logTruncation.ts,open-sse/handlers/chatCore/memoryExtraction.ts,open-sse/handlers/chatCore/nonStreamingSse.ts,open-sse/handlers/chatCore/passthroughToolNames.ts,open-sse/handlers/chatCore/executorHelpers.ts"
+          - name: i
+            mutate: "open-sse/handlers/chatCore/telemetryHelpers.ts,open-sse/handlers/chatCore/memorySkillsInjection.ts,open-sse/handlers/chatCore/semanticCache.ts"
+    timeout-minutes: 300
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: Run Stryker (disableBail)
+        env:
+          BATCH_MUTATE: ${{ matrix.batch.mutate }}
+        run: npx stryker run --config-file stryker.disablebail.json --mutate "$BATCH_MUTATE"
+      - name: Upload mutation report
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: mutation-nobail-${{ matrix.batch.name }}
+          path: reports/mutation/
+          if-no-files-found: warn
+          retention-days: 14

.github/workflows/nightly-compat.yml

@@ -0,0 +1,126 @@
+name: Nightly Node Compat
+
+# Plano mestre testes+CI (Eixo D2, aprovado 2026-07-04): as matrizes de compatibilidade
+# Node 24/26 custavam ~28% de CADA run do CI pesado (2 execuções completas da suíte por
+# sync da release-PR) para pegar uma classe de quebra que raramente nasce num PR típico.
+# Elas rodam aqui 1×/dia contra o tip da release ativa (mesmo alvo do nightly-release-green)
+# e continuam obrigatórias no gate de release via workflow_dispatch do ci.yml se preciso.
+# fail-fast desligado: numa quebra queremos saber TODAS as versões afetadas de uma vez.
+
+on:
+  schedule:
+    - cron: "47 6 * * *" # 06:47 UTC diário — slot distinto dos demais nightlies
+  workflow_dispatch:
+    inputs:
+      branch:
+        description: "Branch to validate (default: highest release/vX.Y.Z)"
+        required: false
+        type: string
+
+permissions:
+  contents: read
+  issues: write
+
+concurrency:
+  group: nightly-compat
+  cancel-in-progress: true
+
+jobs:
+  resolve-branch:
+    name: Resolve active release branch
+    runs-on: ubuntu-latest
+    outputs:
+      target: ${{ steps.branch.outputs.target }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - name: Resolve active release branch
+        id: branch
+        env:
+          INPUT_BRANCH: ${{ github.event.inputs.branch }}
+        run: |
+          set -euo pipefail
+          if [ -n "${INPUT_BRANCH:-}" ]; then
+            TARGET="$INPUT_BRANCH"
+          else
+            TARGET=$(git for-each-ref --format='%(refname:short)' 'refs/remotes/origin/release/v*' \
+              | sed 's#origin/##' \
+              | sort -t/ -k2 -V \
+              | tail -1)
+          fi
+          case "$TARGET" in
+            release/v[0-9]*.[0-9]*.[0-9]*) ;;
+            *) echo "Refusing non-canonical branch name: $TARGET"; exit 1 ;;
+          esac
+          echo "target=$TARGET" >> "$GITHUB_OUTPUT"
+
+  compat-build-26:
+    name: Node 26 Compatibility Build
+    runs-on: ubuntu-latest
+    timeout-minutes: 25
+    needs: resolve-branch
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ needs.resolve-branch.outputs.target }}
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "26"
+          cache: npm
+      - uses: ./.github/actions/npm-ci-retry
+      - run: npm run build
+
+  compat-tests:
+    name: Node ${{ matrix.node }} Compat Tests (${{ matrix.shard }}/4)
+    runs-on: ubuntu-latest
+    timeout-minutes: 25
+    needs: resolve-branch
+    strategy:
+      fail-fast: false
+      matrix:
+        node: [24, 26]
+        shard: [1, 2, 3, 4]
+    env:
+      JWT_SECRET: ci-nightly-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-nightly-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+      TEST_SHARD: ${{ matrix.shard }}/4
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ needs.resolve-branch.outputs.target }}
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ matrix.node }}
+          cache: npm
+      - uses: ./.github/actions/npm-ci-retry
+      - run: npm run check:node-runtime
+      - run: npm run test:unit:ci:shard
+
+  report:
+    name: Open / update tracking issue on failure
+    runs-on: ubuntu-latest
+    if: ${{ !cancelled() && (needs.compat-tests.result == 'failure' || needs.compat-build-26.result == 'failure') }}
+    needs: [resolve-branch, compat-build-26, compat-tests]
+    permissions:
+      issues: write
+    steps:
+      - name: Open or update issue
+        env:
+          GH_TOKEN: ${{ github.token }}
+          TARGET: ${{ needs.resolve-branch.outputs.target }}
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: |
+          set -euo pipefail
+          TITLE="🌙 nightly-compat: Node 24/26 failures on $TARGET"
+          EXISTING=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open --search "$TITLE in:title" --json number --jq '.[0].number')
+          BODY="Nightly Node-compat run failed on \`$TARGET\`: $RUN_URL — triage which Node version/shard broke (fail-fast off, all versions reported)."
+          if [ -n "$EXISTING" ]; then
+            gh issue comment "$EXISTING" --repo "$GITHUB_REPOSITORY" --body "$BODY"
+          else
+            gh issue create --repo "$GITHUB_REPOSITORY" --title "$TITLE" --body "$BODY"
+          fi

.github/workflows/nightly-llm-security.yml

@@ -0,0 +1,102 @@
+name: Nightly LLM Security
+on:
+  schedule:
+    - cron: "53 5 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  promptfoo-guard:
+    name: promptfoo — injection guard (block mode, no secret)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with: { node-version: "24", cache: npm }
+      - run: npm ci
+      - name: Build CLI bundle
+        env: { JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation }
+        run: npm run build:cli
+      - name: Start OmniRoute (block mode)
+        env:
+          JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+          PORT: "20128"
+          INJECTION_GUARD_MODE: block
+        run: |
+          node dist/server.js > server.log 2>&1 &
+          echo $! > server.pid
+          for i in $(seq 1 30); do
+            if curl -sf http://localhost:20128/api/monitoring/health >/dev/null; then echo up; break; fi
+            sleep 2
+          done
+      - name: promptfoo guard-validation
+        run: npx --yes promptfoo@latest eval -c promptfooconfig.yaml --no-cache
+        env:
+          OMNIROUTE_URL: http://localhost:20128
+          OMNIROUTE_API_KEY: not-needed-blocked-before-upstream
+      - name: Stop server
+        if: always()
+        run: kill "$(cat server.pid)" || true
+
+  garak:
+    name: garak probes (skip without provider secret)
+    runs-on: ubuntu-latest
+    # NOTE: the `secrets` context is NOT available in a job-level `if:` — referencing
+    # it there makes GitHub reject the file on push (startup_failure on every push).
+    # Map the secret into a job-level env and gate each step on a presence check, so
+    # the job stays green and simply skips the probes when the secret is absent.
+    env:
+      PROMPTFOO_PROVIDER_KEY: ${{ secrets.PROMPTFOO_PROVIDER_KEY }}
+    steps:
+      - name: Gate on provider secret
+        id: gate
+        run: |
+          if [ -n "$PROMPTFOO_PROVIDER_KEY" ]; then
+            echo "run=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "run=false" >> "$GITHUB_OUTPUT"
+            echo "::notice::PROMPTFOO_PROVIDER_KEY not set — skipping garak probes (advisory)."
+          fi
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+        if: steps.gate.outputs.run == 'true'
+      - uses: actions/setup-node@v6
+        if: steps.gate.outputs.run == 'true'
+        with: { node-version: "24", cache: npm }
+      - run: npm ci
+        if: steps.gate.outputs.run == 'true'
+      - name: Build CLI bundle
+        if: steps.gate.outputs.run == 'true'
+        env: { JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation }
+        run: npm run build:cli
+      - name: Start OmniRoute
+        if: steps.gate.outputs.run == 'true'
+        env:
+          JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+          PORT: "20128"
+        run: |
+          node dist/server.js > server.log 2>&1 &
+          echo $! > server.pid
+          for i in $(seq 1 30); do
+            if curl -sf http://localhost:20128/api/monitoring/health >/dev/null; then echo up; break; fi
+            sleep 2
+          done
+      - uses: actions/setup-python@v6
+        if: steps.gate.outputs.run == 'true'
+        with: { python-version: "3.12" }
+      - run: pip install garak
+        if: steps.gate.outputs.run == 'true'
+      - name: garak limited probes
+        if: steps.gate.outputs.run == 'true'
+        env:
+          OPENAI_API_KEY: ${{ secrets.PROMPTFOO_PROVIDER_KEY }}
+          OPENAI_BASE_URL: http://localhost:20128/v1
+        run: garak --model_type openai --model_name gpt-4o-mini --probes promptinject,dan,leakreplay --report_prefix garak-omniroute || true
+      - name: Stop server
+        if: always() && steps.gate.outputs.run == 'true'
+        run: kill "$(cat server.pid)" || true

.github/workflows/nightly-mutation.yml

@@ -0,0 +1,163 @@
+name: Nightly Mutation
+on:
+  schedule:
+    - cron: "17 3 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  stryker:
+    name: Stryker mutation (batch ${{ matrix.batch.name }} — advisory)
+    runs-on: ubuntu-latest
+    # Mutation testing is expensive. History of the budget:
+    #   - Full 8-module set TIMED OUT at the 180min cap (run 27705123780 = exactly 180min).
+    #     The two god-files chatCore.ts/combo.ts dominated ~2/3 of the mutants and were
+    #     removed from stryker.conf.json `mutate`.
+    #   - The remaining 6 modules in 3 batches: auth.ts and accountFallback.ts are large; the
+    #     a (auth+publicCreds) and b (accountFallback+error) batches still ran near the 180min
+    #     cap (the perTest dry-run over ~130 covering test files is itself costly), so the two
+    #     big modules are now ISOLATED into their own batches (a=auth, b=accountFallback).
+    #   - Onda 3 / Fase 9 T5 re-add: combo.ts was split into 11 leaves; the 8 well-covered
+    #     combo/* leaves are back in `mutate` (covered by the 24 combo-*.test.ts), grouped into
+    #     2 batches (d=heavy, e=light). After #4204 (D7b) merged, the reset-aware quota pair
+    #     quotaScoring/quotaStrategies was added as batch f. A covering-test audit then added the
+    #     6 chatCore/* leaves with direct unit coverage as batch g. A follow-up then wrote dedicated
+    #     unit tests for 6 more leaves and added them as batch h. A final follow-up added dedicated
+    #     tests (no mock.module — fetch-override + crafted inputs + temp-DATA_DIR) for telemetryHelpers
+    #     + memorySkillsInjection + semanticCache (its cache-HIT block now has a setCachedResponse
+    #     fixture) as batch i — ALL 15/15 chatCore leaves are now mutated. See
+    #     _mutate_godfiles_excluded_comment in stryker.conf.json.
+    # 9 PARALLEL batches, each overriding the mutate set via `--mutate` (Stryker 9 CLI:
+    # `-m, --mutate <comma-list>`; the conf's `mutate[]` remains the local-run default/union).
+    #   - Cold-seeding budget (per-batch `timeout-minutes: ${{ matrix.batch.timeout || 180 }}`):
+    #     a COLD run must COMPLETE once to write stryker-incremental.json (Stryker writes it only on
+    #     a successful finish); a job cancelled at the cap writes nothing, so the next run is cold
+    #     again — an infinite never-seeds loop. actions/cache is also branch-scoped, so each branch
+    #     (incl. release) must seed its OWN cache via a run with enough headroom. Measured cold runs
+    #     Measured cold totals (run 27801802713, extrapolated from the % at the 180/350 cancel point):
+    #     auth ~375min (2301 mutants — EXCEEDS the 360min job max even isolated), accountFallback
+    #     ~358min (1441), the c security quartet ~348min (1163), d ~197min (1316), g=142, h=132, e=66,
+    #     f=45, i=33. The widely-covered modules blow the budget because the tap-runner re-runs every
+    #     covering test file per mutant (a perTest fixed cost over ~138 test files, times thousands of
+    #     mutants). A flat timeout bump cannot rescue auth (>360min max) — so the three over-budget
+    #     batches are SPLIT so each half fits: auth->a1/a2 and accountFallback->b1/b2 by mutation range
+    #     (`file:startLine-endLine`), the c quartet->c1/c2 by module pair. Splitting also seeds each
+    #     sub-batch's own incremental cache, after which nightlies re-test only changed mutants.
+    # Full coverage every night in parallel; wall-clock = the slowest batch's cold run until seeded.
+    # Runs at stryker concurrency=4 with per-process DATA_DIR isolation
+    # (tests/_setup/isolateDataDir.ts) — see _concurrency_comment in stryker.conf.json.
+    strategy:
+      fail-fast: false
+      matrix:
+        batch:
+          # Per-batch `timeout` (minutes) tiers the cold-seeding budget by measured cost; batches
+          # without the key default to 180. Cold-run profiling (run 27801802713) showed the
+          # widely-covered modules need FAR more than the 180 cap because the tap-runner re-runs every
+          # covering test file per mutant: auth ~375min (2301 mutants, EXCEEDS the 360min GitHub job
+          # max even isolated), accountFallback ~358min, the c security quartet ~348min — none fit a
+          # single job. So auth/accountFallback are split by MUTATION RANGE (`file:startLine-endLine`,
+          # ~half the mutants each) into a1/a2, b1/b2; the c quartet is split by MODULE pair into
+          # c1/c2. d (3 combo modules, ~197min) stays whole. Split-heavy batches get 300min headroom
+          # for their cold seeding run; once each batch completes once and writes
+          # stryker-incremental.json, later runs re-test only changed mutants and finish far faster.
+          # g/h (142/132min cold) keep a 240 buffer; e/f/i (33-66min) keep the 180 default.
+          - name: a1
+            mutate: "src/sse/services/auth.ts:1-1109"
+            timeout: 300
+          - name: a2
+            mutate: "src/sse/services/auth.ts:1110-2218"
+            timeout: 300
+          - name: b1
+            mutate: "open-sse/services/accountFallback.ts:1-863"
+            timeout: 300
+          - name: b2
+            mutate: "open-sse/services/accountFallback.ts:864-1726"
+            timeout: 300
+          - name: c1
+            mutate: "src/server/authz/routeGuard.ts,src/shared/utils/circuitBreaker.ts"
+            timeout: 300
+          - name: c2
+            mutate: "open-sse/utils/error.ts,open-sse/utils/publicCreds.ts"
+            timeout: 300
+          - name: d
+            mutate: "open-sse/services/combo/comboStructure.ts,open-sse/services/combo/autoStrategy.ts,open-sse/services/combo/validateQuality.ts"
+            timeout: 300
+          - name: e
+            mutate: "open-sse/services/combo/shadowRouting.ts,open-sse/services/combo/targetSorters.ts,open-sse/services/combo/comboPredicates.ts,open-sse/services/combo/rrState.ts,open-sse/services/combo/comboData.ts"
+          - name: f
+            mutate: "open-sse/services/combo/quotaScoring.ts,open-sse/services/combo/quotaStrategies.ts"
+          - name: g
+            mutate: "open-sse/handlers/chatCore/comboContextCache.ts,open-sse/handlers/chatCore/idempotency.ts,open-sse/handlers/chatCore/passthroughHelpers.ts,open-sse/handlers/chatCore/responseHeaders.ts,open-sse/handlers/chatCore/sanitization.ts,open-sse/handlers/chatCore/upstreamTimeouts.ts"
+            timeout: 240
+          - name: h
+            mutate: "open-sse/handlers/chatCore/headers.ts,open-sse/handlers/chatCore/logTruncation.ts,open-sse/handlers/chatCore/memoryExtraction.ts,open-sse/handlers/chatCore/nonStreamingSse.ts,open-sse/handlers/chatCore/passthroughToolNames.ts,open-sse/handlers/chatCore/executorHelpers.ts"
+            timeout: 240
+          - name: i
+            mutate: "open-sse/handlers/chatCore/telemetryHelpers.ts,open-sse/handlers/chatCore/memorySkillsInjection.ts,open-sse/handlers/chatCore/semanticCache.ts"
+    # Per-batch budget: split-heavy batches (a1/a2/b1/b2/c1/c2/d) override to 300min, g/h to 240min;
+    # the rest default to 180min. `matrix.batch.timeout` is null for batches without the key -> `|| 180`.
+    # NOTE: a1+a2 both mutate auth.ts (disjoint line ranges) and b1+b2 both mutate accountFallback.ts;
+    # when merging the per-batch mutation.json for radiography/scores, same-file mutants from sibling
+    # ranges must be UNIONED (scripts/check/check-mutation-ratchet.mjs::measureMutationScores and
+    # scripts/quality/mutation-radiography.mjs both merge per file).
+    timeout-minutes: ${{ matrix.batch.timeout || 180 }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: Restore Stryker incremental cache
+        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
+        with:
+          path: reports/mutation/stryker-incremental.json
+          key: stryker-incremental-${{ matrix.batch.name }}-${{ github.run_id }}
+          restore-keys: stryker-incremental-${{ matrix.batch.name }}-
+      - name: Run Stryker (advisory)
+        id: stryker
+        continue-on-error: true
+        env:
+          BATCH_MUTATE: ${{ matrix.batch.mutate }}
+        run: npx stryker run --mutate "$BATCH_MUTATE"
+      - name: Upload mutation report
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: mutation-report-${{ matrix.batch.name }}
+          path: reports/mutation/
+          if-no-files-found: warn
+          retention-days: 14
+
+  # Aggregation gate (T3): each split batch emits a PARTIAL view of a mutated file
+  # (auth.ts lives in a1+a2, accountFallback in b1+b2), so a PER-BATCH ratchet would
+  # only ever see half a file vs the whole-file baseline. This job runs AFTER every
+  # batch, downloads all reports, and ratchets the MERGED per-module scores
+  # (check-mutation-ratchet UNIONS same-file mutants across reports) against the
+  # dedicatedGate `mutationScore.*` floors in quality-baseline.json (seeded ~2pt below
+  # the first full measurement). Blocking: a module dropping below its floor fails the
+  # run. Missing reports (e.g. an artifact-upload flake) are skipped, never failed.
+  mutation-ratchet:
+    name: Mutation score ratchet (blocking)
+    needs: stryker
+    if: always()
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+      - name: Download all mutation reports
+        uses: actions/download-artifact@v8
+        with:
+          pattern: mutation-report-*
+          path: reports/all
+      - name: Ratchet merged per-module mutation scores
+        run: node scripts/check/check-mutation-ratchet.mjs reports/all/*/mutation.json --ratchet

.github/workflows/nightly-property.yml

@@ -0,0 +1,35 @@
+name: Nightly Property Discovery
+on:
+  schedule:
+    - cron: "0 6 * * *"
+  workflow_dispatch:
+permissions:
+  contents: read
+  issues: write
+jobs:
+  property-random-seed:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: fast-check random seed (high runs)
+        id: prop
+        run: FC_SEED=random FC_NUM_RUNS=2000 npm run test:property
+      - name: Open issue on failure
+        if: failure()
+        uses: actions/github-script@v9
+        with:
+          script: |
+            await github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title: "Nightly property-test failure (Fase 8 B)",
+              body: "fast-check found a counterexample with a random seed. Check the run logs for the reproducible seed + minimal case, then add it as a fixture.\n\nRun: " + context.serverUrl + "/" + context.repo.owner + "/" + context.repo.repo + "/actions/runs/" + context.runId,
+              labels: ["quality-gate-finding"],
+            });

.github/workflows/nightly-release-green.yml

@@ -0,0 +1,303 @@
+name: Release-Green (continuous)
+
+# Solution D — continuous, NON-BLOCKING drift signal for the active release branch.
+#
+# WHY: the full gate (ci.yml) only runs on the release PR (PR → main), so reds
+# accrue silently on release/** and explode — in layers — at release time. This
+# workflow reproduces the release-equivalent validation on the release branch and,
+# when there are HARD failures, opens/updates a single tracking issue.
+#
+# WS5.1 (v3.8.49 quality plan) — two modes:
+#   push to release/v* (code paths) → --quick (fast HARD gates, ~5-8min). Catches the
+#     captain's direct pushes (sync-back — the one ungated write path) AND the merged
+#     COMBINATION right after every PR merge, attributing the offending push range in
+#     the issue. Base-red MTTD drops from ≤24h to ≤~15min after the offending push.
+#   schedule (3×/day) → full --with-build --full-ci (the deep sweep incl. build+suites).
+#
+# It is NOT a required status check and never touches a contributor PR — it only
+# reports. Ratchet drift (eslint warnings / cognitive-complexity / file-size) is
+# expected mid-cycle and is reported but never raises the alarm on its own; only
+# real defects (typecheck / lint errors / unit / vitest / db-rules / public-creds /
+# package-artifact) flip the issue open.
+
+on:
+  push:
+    branches: ["release/v*", "main"]
+    paths:
+      - "src/**"
+      - "open-sse/**"
+      - "bin/**"
+      - "electron/**"
+      - "scripts/**"
+      - "tests/**"
+      - "config/**"
+      - "package.json"
+      - "package-lock.json"
+      - "tsconfig*.json"
+  schedule:
+    - cron: "23 5 * * *" # full sweep — off-peak, distinct from other nightlies
+    - cron: "23 12 * * *" # full sweep — midday (WS5.1: 3×/day instead of 1×)
+    - cron: "23 18 * * *" # full sweep — evening
+  workflow_dispatch:
+    inputs:
+      branch:
+        description: "Release branch to validate (default: highest release/vX.Y.Z)"
+        required: false
+        type: string
+
+permissions:
+  contents: read
+  issues: write
+
+concurrency:
+  # push storms during merge campaigns collapse to the newest commit per branch;
+  # scheduled full sweeps keep their own single lane.
+  group: release-green-${{ github.event_name }}-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  OMNIROUTE_SKIP_SYSTEM_TRUST: "1"
+
+jobs:
+  release-green:
+    name: Validate active release branch
+    # On a push, only run for release/* pushes — a push to main is handled by the
+    # main-green job below. Schedule/dispatch always run (they validate the highest release).
+    if: ${{ github.event_name != 'push' || startsWith(github.ref_name, 'release/') }}
+    # Dynamic runner: with USE_VPS_RUNNER=true (release window / on-demand pre-flight)
+    # this runs on the dedicated VPS runner — clean env (no operator OMNIROUTE_API_KEY,
+    # no local noauth CLIs => zero machine-specific false positives) and no contention.
+    # Nightly cron normally finds the var false (VM off) and falls back to hosted.
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && fromJSON('["self-hosted","omni-release"]')) || 'ubuntu-latest' }}
+    env:
+      JWT_SECRET: ci-nightly-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-nightly-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+
+      - name: Resolve active release branch
+        id: branch
+        env:
+          INPUT_BRANCH: ${{ github.event.inputs.branch }}
+          EVENT_NAME: ${{ github.event_name }}
+          PUSHED_REF: ${{ github.ref_name }}
+        run: |
+          set -euo pipefail
+          if [ -n "${INPUT_BRANCH:-}" ]; then
+            TARGET="$INPUT_BRANCH"
+          elif [ "$EVENT_NAME" = "push" ]; then
+            # validate exactly what was pushed, not the highest branch
+            TARGET="$PUSHED_REF"
+          else
+            # highest release/vX.Y.Z by semver among remote branches
+            TARGET=$(git for-each-ref --format='%(refname:short)' 'refs/remotes/origin/release/v*' \
+              | sed 's#origin/##' \
+              | sort -t/ -k2 -V \
+              | tail -1)
+          fi
+          if [ -z "$TARGET" ]; then echo "No release/v* branch found"; exit 1; fi
+          # Strict format guard — reject anything that isn't release/vX.Y.Z (blocks
+          # ref/command injection via the workflow_dispatch input).
+          if ! printf '%s' "$TARGET" | grep -qE '^release/v[0-9]+\.[0-9]+\.[0-9]+$'; then
+            echo "Refusing non-canonical branch name: $TARGET"; exit 1
+          fi
+          echo "target=$TARGET" >> "$GITHUB_OUTPUT"
+          echo "Active release branch: $TARGET"
+
+      - name: Checkout the release branch
+        env:
+          TARGET: ${{ steps.branch.outputs.target }}
+        run: |
+          set -euo pipefail
+          git checkout "$TARGET"
+          git log -1 --oneline
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+
+      - uses: ./.github/actions/npm-ci-retry
+
+      - name: Release-green validation (full)
+        id: validate
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+        run: |
+          set +e
+          # --hermetic: scrub live-test trigger vars (self-hosted runner may carry
+          # operator env; hosted ignores the unknown flag before #6300 lands).
+          # push → --quick: fast HARD gates only (~5-8min), per-merge signal.
+          # schedule/dispatch → --with-build --full-ci: ALSO run every static gate from
+          # ci.yml's gate jobs (lint, quality-gate, quality-extended, docs-sync-strict,
+          # pr-test-policy) + build + full suites. PRs into release/** only get the
+          # fast-gates, so these accrue silently and explode in layers on the release PR
+          # (v3.8.46: 11 static base-reds leaked).
+          if [ "$EVENT_NAME" = "push" ]; then
+            MODE="--quick"
+          else
+            MODE="--with-build --full-ci"
+          fi
+          echo "[release-green] mode: $MODE (event: $EVENT_NAME)"
+          # shellcheck disable=SC2086 — MODE is an intentional flag list
+          node scripts/quality/validate-release-green.mjs --json --hermetic $MODE \
+            1> release-green.json 2> release-green.log
+          echo "exit=$?" >> "$GITHUB_OUTPUT"
+          echo "------- report -------"
+          cat release-green.log
+
+      - name: Open / update tracking issue on HARD failure
+        if: steps.validate.outputs.exit != '0'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          TARGET: ${{ steps.branch.outputs.target }}
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+          EVENT_NAME: ${{ github.event_name }}
+          BEFORE_SHA: ${{ github.event.before }}
+          AFTER_SHA: ${{ github.event.after }}
+        run: |
+          set -euo pipefail
+          TITLE="🔴 Release branch not green: ${TARGET}"
+          {
+            echo "The **release-green** validation found HARD failures on \`${TARGET}\`."
+            echo "These are real defects that would block the release PR — fix them in the"
+            echo "originating PR branch (via co-authorship), not by demanding it from contributors."
+            echo ""
+            echo "**Run:** ${RUN_URL} (mode: ${EVENT_NAME})"
+            # WS5.1 attribution: on push events the offending change IS this push's range
+            # (one merge per push in the normal queue), so name it — no bisect needed.
+            if [ "$EVENT_NAME" = "push" ] && [ -n "${BEFORE_SHA:-}" ] && \
+               git cat-file -e "$BEFORE_SHA" 2>/dev/null; then
+              echo ""
+              echo "**Offending push range** (\`${BEFORE_SHA:0:9}..${AFTER_SHA:0:9}\`):"
+              echo '```'
+              git log --no-decorate --oneline "${BEFORE_SHA}..${AFTER_SHA}" | head -20
+              echo '```'
+            fi
+            echo ""
+            echo '```'
+            sed -n '/──────── verdict ────────/,$p' release-green.log || tail -40 release-green.log
+            echo '```'
+            echo ""
+            echo "_Ratchet drift (eslint warnings / cognitive-complexity / file-size) listed above is expected mid-cycle and is rebaselined at release — it is NOT a contributor concern and did not, on its own, open this issue._"
+          } > issue-body.md
+
+          EXISTING=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open \
+            --search "in:title $TITLE" --json number --jq '.[0].number' 2>/dev/null || echo "")
+          if [ -n "$EXISTING" ]; then
+            gh issue comment "$EXISTING" --repo "$GITHUB_REPOSITORY" --body-file issue-body.md
+            echo "Updated existing issue #$EXISTING"
+          else
+            gh issue create --repo "$GITHUB_REPOSITORY" --title "$TITLE" --body-file issue-body.md
+          fi
+
+      - name: Upload report artifact
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: release-green-report
+          path: |
+            release-green.json
+            release-green.log
+          if-no-files-found: ignore
+
+  # Companion arm for `main`. Under the parallel-cycle model, main only receives merged
+  # work at the release squash — so a gate/infra fix that lands only on release leaves
+  # main red the whole cycle, and repo-wide gates (CodeQL alert count, ratchet baselines)
+  # turn EVERY PR into main red on a check unrelated to its diff. This detects that and
+  # opens a "🔴 main not green" tracking issue. The PREVENTION is the companion-PR reflex
+  # (Hard Rule #21 area / _shared/merge-gates.md §8); this is the automated backstop.
+  main-green:
+    name: Validate main branch
+    # On a push, only run for a push to main — a push to release/* is handled by
+    # release-green above. Schedule/dispatch always run (they also sweep main).
+    if: ${{ github.event_name != 'push' || github.ref_name == 'main' }}
+    runs-on: ${{ (vars.USE_VPS_RUNNER == 'true' && fromJSON('["self-hosted","omni-release"]')) || 'ubuntu-latest' }}
+    env:
+      JWT_SECRET: ci-nightly-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-nightly-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: main # literal — no injection surface; scheduled runs default to the repo default branch (a release/v*), so pin main explicitly
+          fetch-depth: 0
+          persist-credentials: false
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+
+      - uses: ./.github/actions/npm-ci-retry
+
+      - name: Main-green validation
+        id: validate
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+        run: |
+          set +e
+          # push (a merge into main) → --quick fast HARD gates; schedule/dispatch → full sweep.
+          if [ "$EVENT_NAME" = "push" ]; then
+            MODE="--quick"
+          else
+            MODE="--with-build --full-ci"
+          fi
+          echo "[main-green] mode: $MODE (event: $EVENT_NAME)"
+          # shellcheck disable=SC2086 — MODE is an intentional flag list
+          node scripts/quality/validate-release-green.mjs --json --hermetic $MODE \
+            1> main-green.json 2> main-green.log
+          echo "exit=$?" >> "$GITHUB_OUTPUT"
+          echo "------- report -------"
+          cat main-green.log
+
+      - name: Open / update tracking issue on HARD failure
+        if: steps.validate.outputs.exit != '0'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+          EVENT_NAME: ${{ github.event_name }}
+        run: |
+          set -euo pipefail
+          TITLE="🔴 main branch not green"
+          {
+            echo "The **main-green** validation found HARD failures on \`main\`."
+            echo ""
+            echo "Because \`main\` only receives merged work at the release squash, a gate/infra"
+            echo "fix that landed only on the release branch leaves \`main\` broken for the whole"
+            echo "cycle — and repo-wide gates (CodeQL alert count, ratchet baselines) then turn"
+            echo "**every open PR into main** red on a check unrelated to its diff. The fix is a"
+            echo "companion PR \`--base main\` carrying the release-side fix (see"
+            echo "\`_shared/merge-gates.md\` §8), NOT chasing each contributor PR."
+            echo ""
+            echo "**Run:** ${RUN_URL} (mode: ${EVENT_NAME})"
+            echo ""
+            echo '```'
+            sed -n '/──────── verdict ────────/,$p' main-green.log || tail -40 main-green.log
+            echo '```'
+            echo ""
+            echo "_Ratchet drift (eslint warnings / cognitive-complexity / file-size) is expected mid-cycle and did NOT, on its own, open this issue._"
+          } > issue-body.md
+
+          EXISTING=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open \
+            --search "in:title $TITLE" --json number --jq '.[0].number' 2>/dev/null || echo "")
+          if [ -n "$EXISTING" ]; then
+            gh issue comment "$EXISTING" --repo "$GITHUB_REPOSITORY" --body-file issue-body.md
+            echo "Updated existing issue #$EXISTING"
+          else
+            gh issue create --repo "$GITHUB_REPOSITORY" --title "$TITLE" --body-file issue-body.md
+          fi
+
+      - name: Upload report artifact
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: main-green-report
+          path: |
+            main-green.json
+            main-green.log
+          if-no-files-found: ignore

.github/workflows/nightly-resilience.yml

@@ -0,0 +1,110 @@
+name: Nightly Resilience
+on:
+  schedule:
+    - cron: "41 4 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  heap:
+    name: Heap-growth gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - run: npm run test:heap
+
+  chaos:
+    name: Resilience chaos (fault injection)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - run: npm run test:chaos
+
+  k6-soak:
+    name: k6 load/soak
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: Build CLI bundle
+        env:
+          JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+        run: npm run build:cli
+      - name: Start OmniRoute (background)
+        env:
+          JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+          PORT: "20128"
+        run: |
+          node dist/server.js > server.log 2>&1 &
+          echo $! > server.pid
+          for i in $(seq 1 30); do
+            if curl -sf http://localhost:20128/api/monitoring/health >/dev/null; then echo "server up"; break; fi
+            sleep 2
+          done
+      - name: Install k6
+        uses: grafana/setup-k6-action@v1
+      - name: Run k6 soak
+        run: k6 run tests/load/k6-soak.js
+        env:
+          BASE_URL: http://localhost:20128
+          SOAK_DURATION: "3m"
+          SOAK_VUS: "10"
+      - name: Stop server
+        if: always()
+        run: kill "$(cat server.pid)" || true
+
+  a11y:
+    name: A11y axe (nightly, freeze-and-alert)
+    runs-on: ubuntu-latest
+    # The Playwright webServer (`start` mode) builds Next via build-next-isolated.mjs and
+    # boots the standalone server itself (waits on /api/monitoring/health, 15min webServer
+    # timeout). Unlike the per-PR test-e2e job, this nightly job has no pre-built artifact,
+    # so it self-builds — hence the generous job timeout. REQUIRE_AXE=1 makes the suite run
+    # the real axe analysis (the 4 page tests are gated to nightly so per-PR e2e stays fast)
+    # and makes the meta-test fail loudly if @axe-core/playwright ever goes missing.
+    timeout-minutes: 30
+    env:
+      JWT_SECRET: ci-test-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-test-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+      REQUIRE_AXE: "1"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+          cache: npm
+      - run: npm ci
+      - name: Cache Playwright browsers
+        uses: actions/cache@v6.1.0
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-chromium-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
+          restore-keys: playwright-chromium-${{ runner.os }}-
+      - run: npx playwright install --with-deps chromium
+      - name: Run axe a11y suite (self-building webServer)
+        run: npx playwright test tests/e2e/a11y.spec.ts

.github/workflows/nightly-schemathesis.yml

@@ -0,0 +1,72 @@
+name: Nightly Schemathesis
+on:
+  schedule:
+    - cron: "23 4 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  schemathesis:
+    name: Schemathesis — OpenAPI contract fuzz (advisory)
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with: { node-version: "24", cache: npm }
+      - run: npm ci
+      - name: Build CLI bundle
+        env: { JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation }
+        run: npm run build:cli
+      - name: Start OmniRoute (background)
+        env:
+          JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
+          PORT: "20128"
+        run: |
+          node dist/server.js > server.log 2>&1 &
+          echo $! > server.pid
+          for i in $(seq 1 30); do
+            if curl -sf http://localhost:20128/api/monitoring/health >/dev/null; then echo "server up"; break; fi
+            sleep 2
+          done
+      - uses: actions/setup-python@v6
+        with: { python-version: "3.12" }
+      - name: Install schemathesis
+        run: pip install schemathesis
+      - name: Schemathesis contract fuzz (advisory)
+        # Advisory gate: never fails the job. `continue-on-error` covers a crash of the
+        # step itself; `|| true` covers schemathesis exiting non-zero when it finds spec
+        # violations / upstream 500s — both are expected here (most /v1 endpoints proxy an
+        # upstream that has no provider configured in CI). The point of the nightly is to
+        # PROVE the contract is fuzzable and surface regressions, not to gate the build.
+        continue-on-error: true
+        run: |
+          schemathesis run docs/openapi.yaml \
+            --url http://localhost:20128 \
+            --max-examples 20 \
+            --workers 4 \
+            --checks all \
+            --max-response-time 30 \
+            --request-timeout 30 \
+            --suppress-health-check all \
+            --report junit \
+            --report-junit-path schemathesis-report/junit.xml \
+            --no-color \
+            || true
+      - name: Stop server
+        if: always()
+        run: kill "$(cat server.pid)" || true
+      - name: Upload schemathesis report
+        if: always()
+        uses: actions/upload-artifact@v7
+        with:
+          name: schemathesis-report
+          path: |
+            schemathesis-report/
+            server.log
+          if-no-files-found: warn
+          retention-days: 14

.github/workflows/npm-publish.yml

@@ -1,8 +1,11 @@
 name: Publish to npm
 
 on:
+  # 'released' (not 'published') so editing/re-publishing old releases does NOT
+  # re-trigger this workflow. Pairs with the semver guard below as defense in
+  # depth against accidental dist-tag clobbering by old releases.
   release:
-    types: [published]
+    types: [released]
   workflow_dispatch:
     inputs:
       version:
@@ -10,13 +13,23 @@ on:
         required: true
         type: string
       tag:
-        description: "npm dist-tag (latest / next)"
+        description: "npm dist-tag (auto / latest / next / historic)"
         required: false
-        default: "latest"
+        default: "auto"
         type: choice
         options:
+          - auto
           - latest
           - next
+          - historic
+      publish_mode:
+        description: "staged = npm stage publish (owner approves with 2FA after the staged boot-verify); direct = legacy immediate publish (emergency fallback only)"
+        required: false
+        default: "staged"
+        type: choice
+        options:
+          - staged
+          - direct
   workflow_call:
     inputs:
       version:
@@ -24,18 +37,19 @@ on:
         required: true
         type: string
       tag:
-        description: "npm dist-tag (latest / next)"
+        description: "npm dist-tag (auto / latest / next / historic)"
         required: false
-        default: "latest"
+        default: "auto"
         type: string
     secrets:
       NPM_TOKEN:
         required: true
 
+# Least-privilege default: read-only at the top level; each publish job grants the
+# id-token (npm provenance) / packages (GitHub Packages) writes it needs (Scorecard
+# TokenPermissions).
 permissions:
   contents: read
-  id-token: write
-  packages: write
 
 env:
   NPM_PUBLISH_NODE_VERSION: "24"
@@ -43,10 +57,18 @@ env:
 jobs:
   publish:
     runs-on: ubuntu-latest
-    environment: NPM_TOKEN
+    permissions:
+      contents: write # gh release upload (attach SBOM to the GitHub Release)
+      id-token: write # npm provenance
+      packages: write # publish to npm.pkg.github.com
     steps:
       - name: Checkout
-        uses: actions/checkout@v6
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          # Need full tag history to compare against highest semver when
+          # deciding whether this release should claim dist-tag `latest`.
+          fetch-depth: 0
 
       - name: Setup Node.js
         uses: actions/setup-node@v6
@@ -57,77 +79,263 @@ jobs:
       - name: Install dependencies (skip scripts to avoid heavy build)
         run: npm install --ignore-scripts --no-audit --no-fund
 
-      - name: Resolve version and dist-tag
+      - name: Resolve version, dist-tag and skip flag
         id: resolve
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          REF_NAME: ${{ github.ref_name }}
+          INPUT_VERSION: ${{ inputs.version }}
+          INPUT_TAG: ${{ inputs.tag }}
         run: |
-          VERSION="${{ inputs.version }}"
-          TAG="${{ inputs.tag }}"
+          set -euo pipefail
 
-          if [ -z "$VERSION" ]; then
-            if [ "${{ github.event_name }}" = "release" ]; then
-              VERSION="${GITHUB_REF_NAME}"
-            fi
+          # 1) Resolve VERSION from the trigger (all inputs come via env).
+          VERSION="${INPUT_VERSION:-}"
+          if [ -z "$VERSION" ] && [ "$EVENT_NAME" = "release" ]; then
+            VERSION="$REF_NAME"
+          fi
+          VERSION="${VERSION#v}"
+          if ! printf '%s' "$VERSION" | grep -qE '^[0-9]+\.[0-9]+\.[0-9]+([.-][A-Za-z0-9.-]+)?$'; then
+            echo "Refusing to publish unsafe VERSION value: $VERSION" >&2
+            exit 1
           fi
 
-          # Strip v prefix if present
-          VERSION="${VERSION#v}"
-
-          # Default dist-tag logic
-          if [ -z "$TAG" ]; then
-            if [[ "$VERSION" == *-* ]]; then
+          # 2) Resolve dist-tag.
+          #    - explicit 'latest'/'next'/'historic' is honored
+          #    - 'auto' (or empty): pre-release identifiers → 'next';
+          #      stable versions → 'latest' only if VERSION is the highest
+          #      stable semver among `v*` tags (otherwise → 'historic').
+          REQUESTED_TAG="${INPUT_TAG:-auto}"
+          TAG="$REQUESTED_TAG"
+          if [ "$TAG" = "auto" ] || [ -z "$TAG" ]; then
+            if printf '%s' "$VERSION" | grep -qE -- '-(rc|alpha|beta|pre|next)'; then
               TAG="next"
             else
-              TAG="latest"
+              git fetch --tags --quiet || true
+              HIGHEST=$(git tag -l 'v[0-9]*' | sed 's/^v//' | grep -vE -- '-(rc|alpha|beta|pre|next)' | sort -V | tail -1 || echo "")
+              if [ -n "$HIGHEST" ] && [ "$VERSION" = "$HIGHEST" ]; then
+                TAG="latest"
+              else
+                echo "Version $VERSION is not the highest semver tag (highest=${HIGHEST:-<none>}). Using dist-tag 'historic' to avoid clobbering @latest."
+                TAG="historic"
+              fi
             fi
           fi
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-          echo "tag=$TAG" >> $GITHUB_OUTPUT
-          echo "📦 Publishing omniroute@$VERSION with tag=$TAG"
+
+          # 3) Skip-if-already-published. NOTE: do NOT pass `--silent` to
+          #    `npm view` — it suppresses stdout and breaks the grep, which
+          #    caused old releases (3.2.8) to be re-published and steal
+          #    dist-tag `latest`. See incident notes in CHANGELOG.
+          PUBLISHED="$(npm view "omniroute@${VERSION}" version 2>/dev/null || true)"
+          SKIP="false"
+          if [ "$PUBLISHED" = "$VERSION" ]; then
+            echo "⚠️ omniroute@${VERSION} is already on npm — skipping publish."
+            SKIP="true"
+          fi
+
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          echo "tag=$TAG"          >> "$GITHUB_OUTPUT"
+          echo "skip=$SKIP"        >> "$GITHUB_OUTPUT"
+          echo "📦 Resolved omniroute@$VERSION dist-tag=$TAG skip=$SKIP"
 
       - name: Sync package.json version
+        if: steps.resolve.outputs.skip != 'true'
+        env:
+          VERSION: ${{ steps.resolve.outputs.version }}
         run: |
-          npm version "${{ steps.resolve.outputs.version }}" --no-git-tag-version --allow-same-version
+          npm version "$VERSION" --no-git-tag-version --allow-same-version
 
       - name: Build CLI bundle (standalone app)
+        if: steps.resolve.outputs.skip != 'true'
         env:
           JWT_SECRET: ci-build-secret-with-sufficient-length-for-validation
         run: npm run build:cli
 
       - name: Validate npm package artifact
+        if: steps.resolve.outputs.skip != 'true'
         run: npm run check:pack-artifact
 
-      - name: Publish to npm
-        run: |
-          VERSION="${{ steps.resolve.outputs.version }}"
-          TAG="${{ steps.resolve.outputs.tag }}"
-          # Check if this version is already published — skip instead of failing with E403
-          if npm view "omniroute@${VERSION}" version --silent 2>/dev/null | grep -q "^${VERSION}$"; then
-            echo "⚠️ Version ${VERSION} is already published on npm — skipping."
-            exit 0
-          fi
-          if [ "$TAG" = "latest" ]; then
-            npm publish --access public
-          else
-            npm publish --access public --tag "$TAG"
-          fi
-          echo "✅ Published omniroute@$VERSION (tag: $TAG)"
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - name: Generate CycloneDX SBOM (npm)
+        if: steps.resolve.outputs.skip != 'true'
+        run: npx @cyclonedx/cyclonedx-npm --ignore-npm-errors --output-format JSON --output-file sbom-npm.cdx.json
 
-      - name: Publish to GitHub Packages
-        run: |
-          VERSION="${{ steps.resolve.outputs.version }}"
-          TAG="${{ steps.resolve.outputs.tag }}"
+      - name: Upload SBOM (npm) as workflow artifact
+        if: steps.resolve.outputs.skip != 'true'
+        uses: actions/upload-artifact@v7
+        with:
+          name: sbom-npm
+          path: sbom-npm.cdx.json
+          if-no-files-found: error
 
-          echo "Configuring for GitHub Packages..."
-          echo "//npm.pkg.github.com/:_authToken=${{ secrets.GITHUB_TOKEN }}" > .npmrc
-          npm pkg set name="@diegosouzapw/omniroute"
-
-          if [ "$TAG" = "latest" ]; then
-            npm publish --registry=https://npm.pkg.github.com || echo "⚠️ Version ${VERSION} might already be published on GitHub."
-          else
-            npm publish --registry=https://npm.pkg.github.com --tag "$TAG" || echo "⚠️ Version ${VERSION} might already be published on GitHub."
-          fi
-          echo "✅ Action finished for GitHub Packages"
+      - name: Attach SBOM to GitHub Release
+        if: steps.resolve.outputs.skip != 'true' && github.event_name == 'release'
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          TAG: ${{ github.ref_name }}
+        run: gh release upload "$TAG" sbom-npm.cdx.json --clobber
+
+      # WS1.2/WS1.3 (#7065 class): the artifact that is about to be published must
+      # BOOT. build:cli already assembled dist/ above; this packs+installs+boots the
+      # real tarball and fails the publish before anything reaches the registry.
+      - name: Boot-smoke the tarball before ANY publish
+        if: steps.resolve.outputs.skip != 'true'
+        run: npm run check:pack-boot
+
+      # 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
+      # human gate to AFTER the proof instead of before it. Requires npm >= 11.15
+      # (staged publishing GA 2026-05-22). publish_mode=direct is the emergency
+      # fallback (legacy immediate publish) via workflow_dispatch.
+      - name: Ensure npm supports staged publishing
+        if: steps.resolve.outputs.skip != 'true' && (github.event_name != 'workflow_dispatch' || inputs.publish_mode != 'direct')
+        run: |
+          set -euo pipefail
+          CUR=$(npm --version)
+          if ! node -e "const [a,b]='$(npm --version)'.split('.').map(Number); process.exit(a>11||(a===11&&b>=15)?0:1)"; then
+            # Pinned exact version (supply-chain: never float @latest in the publish
+            # job); bump deliberately when a newer npm is required.
+            echo "npm $CUR < 11.15 — installing pinned npm 11.15.0 for staged publishing"
+            npm install -g --ignore-scripts npm@11.15.0
+          fi
+          npm --version
+
+      - name: Publish to npm (staged — owner approves with 2FA)
+        if: steps.resolve.outputs.skip != 'true' && (github.event_name != 'workflow_dispatch' || inputs.publish_mode != 'direct')
+        env:
+          VERSION: ${{ steps.resolve.outputs.version }}
+          TAG: ${{ steps.resolve.outputs.tag }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          set -euo pipefail
+          # Always pass --tag explicitly. Defense in depth: even if VERSION is
+          # accidentally an older release, the historic tag will NOT claim `@latest`.
+          npm stage publish --provenance --access public --tag "$TAG"
+          {
+            echo "## 📦 omniroute@$VERSION STAGED (not yet installable)"
+            echo ""
+            echo "The exact bytes are parked on the registry. To release them:"
+            echo '```'
+            echo "npm stage list omniroute            # find the stage id"
+            echo "npm stage approve <id>              # owner 2FA — THE publish"
+            echo '```'
+            echo "To verify the staged bytes first: npm stage download <id> → run"
+            echo "scripts/check/check-pack-boot.mjs against them (see RELEASE_CHECKLIST)."
+            echo "To discard: npm stage reject <id>."
+          } >> "$GITHUB_STEP_SUMMARY"
+          echo "✅ Staged omniroute@$VERSION (dist-tag=$TAG) — awaiting owner 'npm stage approve'"
+
+      - name: Publish to npm (DIRECT — emergency fallback)
+        if: steps.resolve.outputs.skip != 'true' && github.event_name == 'workflow_dispatch' && inputs.publish_mode == 'direct'
+        env:
+          VERSION: ${{ steps.resolve.outputs.version }}
+          TAG: ${{ steps.resolve.outputs.tag }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          set -euo pipefail
+          npm publish --provenance --access public --tag "$TAG"
+          echo "✅ Published omniroute@$VERSION (dist-tag=$TAG) [DIRECT mode]"
+
+      - name: Publish to GitHub Packages
+        if: steps.resolve.outputs.skip != 'true'
+        env:
+          VERSION: ${{ steps.resolve.outputs.version }}
+          TAG: ${{ steps.resolve.outputs.tag }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          set -euo pipefail
+          echo "Configuring for GitHub Packages..."
+          echo "//npm.pkg.github.com/:_authToken=${GITHUB_TOKEN}" > .npmrc
+          npm pkg set name="@diegosouzapw/omniroute"
+          npm publish --registry=https://npm.pkg.github.com --tag "$TAG" \
+            || echo "⚠️ omniroute@${VERSION} might already be published on GitHub Packages."
+          echo "✅ Action finished for GitHub Packages"
+
+  publish-opencode-plugin:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      id-token: write # npm provenance
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+          # Full history needed for auto-bump: git diff against previous release tag
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.NPM_PUBLISH_NODE_VERSION }}
+          registry-url: https://registry.npmjs.org
+
+      - name: Auto-bump plugin version if plugin changed since last release
+        id: bump
+        working-directory: "@omniroute/opencode-plugin"
+        env:
+          CURRENT_TAG: ${{ github.ref_name }}
+        run: |
+          set -euo pipefail
+
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          PKG_NAME=$(node -p "require('./package.json').name")
+
+          # 1) Skip if current version is not yet published (no bump needed)
+          PUBLISHED="$(npm view "${PKG_NAME}@${PKG_VERSION}" version 2>/dev/null || true)"
+          if [ "$PUBLISHED" != "$PKG_VERSION" ]; then
+            echo "✅ ${PKG_NAME}@${PKG_VERSION} is new — no bump needed."
+            echo "bumped=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          # 2) Find the previous release tag (exclude the current one)
+          PREV_TAG=$(git tag -l 'v*' --sort=-version:refname \
+            | grep -v "^${CURRENT_TAG}$" | head -1 || echo "")
+          if [ -z "$PREV_TAG" ]; then
+            echo "No previous tag to compare — skipping bump."
+            echo "bumped=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          # 3) Check if plugin dir actually changed since that tag
+          if git diff --quiet "$PREV_TAG" -- "@omniroute/opencode-plugin/"; then
+            echo "⏭️ No plugin changes since $PREV_TAG — nothing to publish."
+            echo "bumped=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          # 4) Auto-bump patch version
+          npm version patch --no-git-tag-version --allow-same-version
+          NEW_VERSION=$(node -p "require('./package.json').version")
+          echo "bumped=true" >> "$GITHUB_OUTPUT"
+          echo "📦 Auto-bumped ${PKG_NAME} from ${PKG_VERSION} to ${NEW_VERSION}"
+
+      - name: Install plugin dependencies
+        working-directory: "@omniroute/opencode-plugin"
+        run: npm install --no-audit --no-fund
+
+      - name: Build plugin
+        working-directory: "@omniroute/opencode-plugin"
+        run: npm run clean && npm run build
+
+      - name: Test plugin
+        working-directory: "@omniroute/opencode-plugin"
+        run: npm test
+
+      - name: Publish @omniroute/opencode-plugin to npm
+        working-directory: "@omniroute/opencode-plugin"
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          set -euo pipefail
+          PKG_VERSION=$(node -p "require('./package.json').version")
+          PKG_NAME=$(node -p "require('./package.json').name")
+          # Same hardened skip-check as the main job (no --silent flag).
+          PUBLISHED="$(npm view "${PKG_NAME}@${PKG_VERSION}" version 2>/dev/null || true)"
+          if [ "$PUBLISHED" = "$PKG_VERSION" ]; then
+            echo "⚠️ ${PKG_NAME}@${PKG_VERSION} is already published on npm — skipping."
+            exit 0
+          fi
+          npm publish --provenance --access public --ignore-scripts
+          echo "✅ Published ${PKG_NAME}@${PKG_VERSION}"

.github/workflows/opencode-plugin-ci.yml

@@ -0,0 +1,66 @@
+name: opencode-plugin CI
+
+on:
+  push:
+    branches: [main, release/v3.8.2]
+    paths:
+      - "@omniroute/opencode-plugin/**"
+  pull_request:
+    branches: [main, release/v3.8.2]
+    paths:
+      - "@omniroute/opencode-plugin/**"
+    types: [opened, synchronize, reopened, ready_for_review]
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+defaults:
+  run:
+    working-directory: "@omniroute/opencode-plugin"
+
+jobs:
+  test:
+    name: Test (Node ${{ matrix.node }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        node: ["22", "24"]
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ matrix.node }}
+          cache: npm
+          cache-dependency-path: "@omniroute/opencode-plugin/package-lock.json"
+      - run: npm install --no-audit --no-fund
+      - run: npm run build
+      - run: npm test
+
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: "22"
+          cache: npm
+          cache-dependency-path: "@omniroute/opencode-plugin/package-lock.json"
+      - run: npm install --no-audit --no-fund
+      - run: npm run build
+      - uses: actions/upload-artifact@v7
+        with:
+          name: opencode-plugin-dist
+          path: "@omniroute/opencode-plugin/dist"
+          retention-days: 7

.github/workflows/opencode-provider-ci.yml

@@ -32,8 +32,10 @@ jobs:
       matrix:
         node: ["20", "22", "24"]
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
         with:
           node-version: ${{ matrix.node }}
           cache: npm
@@ -46,15 +48,17 @@ jobs:
     runs-on: ubuntu-latest
     needs: test
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
         with:
           node-version: "20"
           cache: npm
           cache-dependency-path: "@omniroute/opencode-provider/package-lock.json"
       - run: npm ci
       - run: npm run build
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: opencode-provider-dist
           path: "@omniroute/opencode-provider/dist"

.github/workflows/quality.yml

@@ -0,0 +1,354 @@
+name: Quality Gates
+
+on:
+  pull_request:
+    branches: ["release/**"]
+    types: [opened, synchronize, reopened, ready_for_review]
+  workflow_dispatch:
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+env:
+  # CI must never mutate the runner's OS trust store (2026-07-05: a cert-flow
+  # test installed a fake PEM on a persistent self-hosted runner and broke all
+  # system TLS). Belt-and-suspenders with tests/_setup/isolateDataDir.ts.
+  OMNIROUTE_SKIP_SYSTEM_TRUST: "1"
+  CI_NODE_VERSION: "24"
+
+jobs:
+  # Same classifier as ci.yml (scripts/quality/classify-pr-changes.mjs) so PR→release
+  # path filters share existence reasons: code / docs / i18n / workflow.
+  changes:
+    name: Change Classification
+    runs-on: ubuntu-latest
+    outputs:
+      code: ${{ steps.classify.outputs.code }}
+      docs: ${{ steps.classify.outputs.docs }}
+      i18n: ${{ steps.classify.outputs.i18n }}
+      workflow: ${{ steps.classify.outputs.workflow }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+          fetch-depth: 0
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+      - id: classify
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          BASE_SHA: ${{ github.event.pull_request.base.sha }}
+          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+        run: |
+          if [ "$EVENT_NAME" != "pull_request" ]; then
+            {
+              echo "code=true"
+              echo "docs=true"
+              echo "i18n=true"
+              echo "workflow=true"
+            } >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          git diff --name-only "$BASE_SHA" "$HEAD_SHA" > changed-files.txt
+          node scripts/quality/classify-pr-changes.mjs changed-files.txt >> "$GITHUB_OUTPUT"
+
+  # Docs/OpenAPI contract gates only — existence reason is doc accuracy + route refs.
+  # Split out of fast-gates so pure-docs PRs skip typecheck/unit while still validating docs.
+  docs-gates:
+    name: Docs Gates (fast-path)
+    needs: changes
+    if: ${{ github.event_name != 'pull_request' || ((github.event.pull_request.draft == false || startsWith(github.head_ref, 'mergify/merge-queue/')) && (needs.changes.outputs.docs == 'true' || needs.changes.outputs.code == 'true')) }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      # One walk of src/app/api for openapi-routes + docs-symbols (both still fail independently).
+      - run: npm run check:api-docs-refs
+      - name: Docs accuracy (fabricated-docs + i18n mirrors, strict)
+        run: npm run check:docs-all
+
+  fast-gates:
+    name: Fast Quality Gates
+    needs: changes
+    # Code surface only — pure docs/i18n PRs skip this bag (docs-gates covers docs).
+    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 (same rule as ci.yml): use the self-hosted VPS pool only when the
+    # 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.
+    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:
+      JWT_SECRET: ci-lint-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-lint-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      - name: Restore ESLint file cache
+        uses: actions/cache@v6
+        with:
+          path: |
+            .eslintcache
+            .eslintcache-complexity
+          key: eslint-${{ runner.os }}-${{ hashFiles('eslint.config.mjs', 'eslint.complexity-ratchets.config.mjs', 'config/quality/eslint-suppressions.json', 'package-lock.json') }}
+          restore-keys: |
+            eslint-${{ runner.os }}-
+      - run: npm run check:provider-consistency
+      - run: npm run check:fetch-targets
+      # docs-all / openapi-routes / docs-symbols live in docs-gates (path-filtered).
+      - run: npm run check:deps
+      - run: npm run check:file-size
+      - run: npm run check:error-helper
+      - run: npm run check:migration-numbering
+      - run: npm run check:public-creds
+      - run: npm run check:db-rules
+      - run: npm run check:known-symbols
+      - run: npm run check:route-guard-membership
+      - run: npm run check:test-discovery
+      - run: npm run check:test-runner-api
+      # Guards tap.testFiles drift: a covering unit test absent from stryker.conf.json
+      # tap.testFiles makes its module's mutants survive on a cold nightly-mutation run,
+      # false-failing the blocking mutationScore ratchet. See check-mutation-test-coverage.mjs.
+      - run: npm run check:mutation-test-coverage
+      - run: npm run check:any-budget:t11
+      # Build-scope guard: fails if worktrees/cruft leak into the tsconfig include
+      # scope (would OOM `next build`). Instant. See incident 2026-06-25 / #5031.
+      - run: npm run check:build-scope
+      # Pack-policy (unexpected-files allowlist) WITHOUT a build — catches a stray file
+      # leaking into the npm tarball (v3.8.36: 6 ops bin/*.sh) per-PR instead of only on
+      # the release PR's heavy Package Artifact job.
+      - run: npm run check:pack-policy
+      # 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
+      - name: Typecheck (core)
+        run: npm run typecheck:core
+      # #7033: dashboard-scoped typecheck gate — src/app/(dashboard) TSX is not
+      # covered by typecheck:core's curated allowlist. See check-dashboard-typecheck.mjs.
+      - name: Typecheck (dashboard)
+        run: npm run check:dashboard-typecheck
+      # WS4.2 (v3.8.49 plan): TypeScript 7 native-compiler SHADOW — advisory only.
+      # TS7 went GA 2026-07-08 with 8-12x type-check speedups; its Compiler API only
+      # arrives in 7.1, so typescript-eslint / type-coverage / Stryker stay on 6.x
+      # (the hybrid is the officially documented pattern). Isolated npx on purpose:
+      # installing an alias package could collide node_modules/.bin/tsc with 6.x.
+      # Promote to the blocking gate after ~1 week of parity with the step above.
+      - name: Typecheck (core) — TS7 native shadow (advisory)
+        continue-on-error: true
+        run: |
+          RC=0
+          START=$(date +%s)
+          npx -y -p typescript@7 tsc --pretty false -p tsconfig.typecheck-core.json || RC=$?
+          echo "[ts7-shadow] exit=$RC elapsed=$(( $(date +%s) - START ))s — the 6.x step above stays authoritative"
+          exit $RC
+      # TIA: build the impact map at runtime (gitignored, ~21MB) and run only the
+      # unit tests impacted by this PR's changed files. On hub/unmapped changes the
+      # selector returns __RUN_ALL__ — full-suite authority is the parallel
+      # `fast-unit` 4-shard job (test:unit:ci:shard; was 2-shard, #6781), NOT an
+      # unsharded re-run here. Stacking unsharded test:unit:ci on top of fast-unit
+      # doubled wall time (~16 min extra on ubuntu-latest) without extra coverage.
+      #
+      # BLOCKING for the *impacted subset* (flipped 2026-06-17). Fail-safe full
+      # coverage remains required via `Unit Tests fast-path` (fast-unit).
+      - name: Impacted unit tests (TIA subset; blocking)
+        env:
+          GITHUB_BASE_REF: ${{ github.base_ref }}
+        run: |
+          git fetch --no-tags origin "$GITHUB_BASE_REF" || true
+          node scripts/quality/build-test-impact-map.mjs
+          SEL="$(node scripts/quality/select-impacted-tests.mjs)"
+          if [ -z "$SEL" ]; then echo "No source/test changes — skipping unit tests"; exit 0; fi
+          # CI runners are 4-vCPU; run at --test-concurrency=4 (matching the ci.yml unit
+          # job) rather than test:unit's local-tuned concurrency=20. Oversubscribing the
+          # runner makes timing-sensitive tests (db-backup, upstream-timeout, ...) flake,
+          # which must not happen on a blocking gate. DATA_DIR isolation keeps the parallel
+          # run race-free regardless of concurrency.
+          if echo "$SEL" | grep -q "__RUN_ALL__"; then
+            echo "Fail-safe: __RUN_ALL__ — deferring FULL unit suite to fast-unit (4-shard)."
+            echo "Not re-running unsharded test:unit:ci here (duplicate of fast-unit coverage)."
+            exit 0
+          fi
+          echo "Running impacted tests:"; echo "$SEL"
+          mapfile -t FILES <<< "$SEL"
+          # Loader parity with test:unit:ci:shard (#6787): tests/unit/dashboard/** runs
+          # under `--import tsx` (CJS transform — required for ESM-only deep imports like
+          # @lobehub/icons/es/* reached via lobeProviderIcons.ts); everything else under
+          # `--import tsx/esm`. A single tsx/esm invocation false-reds every dashboard
+          # module-shape test the impact map selects ("Unexpected token 'export'").
+          DASH=(); REST=()
+          for f in "${FILES[@]}"; do
+            case "$f" in
+              tests/unit/dashboard/*) DASH+=("$f") ;;
+              *) REST+=("$f") ;;
+            esac
+          done
+          RC=0
+          if [ ${#REST[@]} -gt 0 ]; then
+            node --import tsx/esm --import ./open-sse/utils/setupPolyfill.ts --import ./tests/_setup/isolateDataDir.ts --test --test-force-exit --test-concurrency=4 "${REST[@]}" || RC=$?
+          fi
+          if [ ${#DASH[@]} -gt 0 ]; then
+            node --import tsx --import ./open-sse/utils/setupPolyfill.ts --import ./tests/_setup/isolateDataDir.ts --test --test-force-exit --test-concurrency=4 "${DASH[@]}" || RC=$?
+          fi
+          exit $RC
+
+  fast-vitest:
+    name: Vitest (fast-path)
+    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).
+    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
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      # WS5.2/5.3: JUnit feeds Trunk Flaky Tests — the fast-path runs on EVERY PR,
+      # which is where flaky-detection volume actually comes from (ci.yml's heavy
+      # jobs only run on the release PR). Advisory upload, own-origin only.
+      - run: npm run test:vitest -- --reporter=default --reporter=junit --outputFile.junit=trunk-junit/vitest-fastpath.xml
+      - name: Upload test results to Trunk (advisory)
+        if: ${{ always() && (github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository) }}
+        continue-on-error: true
+        uses: trunk-io/analytics-uploader@385f1ccdf345b4532dc4b6c665dd432b702b8e28 # v2.1.2
+        with:
+          junit-paths: trunk-junit/**/*.xml
+          org-slug: omniroute
+          token: ${{ secrets.TRUNK_TOKEN }}
+
+  fast-unit:
+    name: Unit Tests fast-path (${{ matrix.shard }}/4)
+    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).
+    # This is the heaviest fast-path job; 4-way sharding (was 2, #6781) halves the
+    # 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.
+    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:
+        shard: [1, 2, 3, 4]
+    env:
+      JWT_SECRET: ci-lint-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-lint-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      # QW-d: fonte única — o mesmo npm script do CI pesado/local. Fecha dois drifts do
+      # comando inline antigo: os dirs `memory` e `usage` estavam FORA do glob (testes
+      # silenciosamente não rodavam no fast path) e o setupPolyfill não era importado.
+      - run: npm run test:unit:ci:shard
+        env:
+          TEST_SHARD: ${{ matrix.shard }}/4
+
+  # ── Pacote 4 (plano mestre testes+CI, aprovado 2026-07-04) ─────────────────────────
+  # No-new-warnings por PR via ESLint bulk suppressions nativo (>=9.24). O baseline
+  # config/quality/eslint-suppressions.json congela as violações EXISTENTES por
+  # arquivo+regra; qualquer warning NOVO aparece e o --max-warnings 0 falha o job — o
+  # drift de +41/+88 warnings por ciclo passa a morrer no PR que o introduz, em vez de
+  # ser rebaselinado às cegas na release. Aperto do baseline (na reconciliação da
+  # release): npx eslint . --prune-suppressions --suppressions-location config/quality/eslint-suppressions.json
+  #
+  # Princípio Zero: bloqueante SÓ para branches internas (as campanhas/sessões são a
+  # origem do drift). PR de FORK roda em modo report (continue-on-error → o job fica
+  # verde com anotação; a campanha /green-prs aplica o fix via co-autoria — o
+  # contribuidor NUNCA é bloqueado nem cobrado).
+  lint-guard:
+    name: No new ESLint warnings
+    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') }}
+    runs-on: ubuntu-latest
+    continue-on-error: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == true }}
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+      - uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      - name: Restore ESLint file cache
+        uses: actions/cache@v6
+        with:
+          path: |
+            .eslintcache
+            .eslintcache-complexity
+          key: eslint-${{ runner.os }}-${{ hashFiles('eslint.config.mjs', 'eslint.complexity-ratchets.config.mjs', 'config/quality/eslint-suppressions.json', 'package-lock.json') }}
+          restore-keys: |
+            eslint-${{ runner.os }}-
+      - 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
+
+  # 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
+  # bullets vizinhos/seções inteiras (incidente #6193, 2026-07-05: 212 linhas /
+  # 130 bullets); o checkout de PR é refs/pull/N/merge, então comparar contra a
+  # base detecta o eat ANTES do merge. (2) SKILL.md gerado stale vs o catálogo de
+  # agent-skills (#6186 mergeou um id de catálogo sem rodar o gerador → 8 reds de
+  # integration invisíveis até a release).
+  #
+  # Princípio Zero: bloqueante SÓ para branches internas; PR de FORK roda em modo
+  # report (continue-on-error) — a campanha corrige via co-autoria, o contribuidor
+  # nunca é bloqueado.
+  merge-integrity:
+    name: Merge integrity (changelog + generated skills)
+    # Always on non-draft PRs — CHANGELOG/skills can break on docs-only merges too.
+    if: ${{ github.event_name != 'pull_request' || (github.event.pull_request.draft == false || startsWith(github.head_ref, 'mergify/merge-queue/')) }}
+    runs-on: ubuntu-latest
+    continue-on-error: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.fork == true }}
+    env:
+      JWT_SECRET: ci-lint-secret-with-sufficient-length-for-validation
+      API_KEY_SECRET: ci-lint-api-key-secret-long
+      DISABLE_SQLITE_AUTO_BACKUP: "true"
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7
+        with:
+          fetch-depth: 0
+          persist-credentials: false
+      - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6
+        with:
+          node-version: ${{ env.CI_NODE_VERSION }}
+          cache: npm
+      - run: npm ci
+      - name: CHANGELOG integrity (nenhum bullet da base pode sumir no merge-result)
+        run: npm run check:changelog-integrity
+      - name: Agent-skills generator sync (SKILL.md gerado ≡ catálogo)
+        run: npm run check:agent-skills-sync

.github/workflows/scorecard.yml

@@ -0,0 +1,40 @@
+name: OpenSSF Scorecard
+on:
+  branch_protection_rule:
+  schedule:
+    - cron: "27 7 * * 1"
+  push:
+    branches: ["main"]
+
+permissions: read-all
+
+jobs:
+  analysis:
+    name: Scorecard analysis
+    runs-on: ubuntu-latest
+    permissions:
+      # security-events: write removed — Scorecard findings are advisory and no longer
+      # uploaded to the code-scanning Security tab (they are supply-chain/posture scores,
+      # not code vulnerabilities, and drowned out real CodeQL alerts). The run still
+      # produces the OpenSSF badge (publish_results) and a downloadable SARIF artifact.
+      id-token: write
+      contents: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+        with:
+          persist-credentials: false
+
+      - name: Run analysis
+        uses: ossf/scorecard-action@v2.4.3
+        with:
+          results_file: results.sarif
+          results_format: sarif
+          publish_results: true
+
+      - name: Upload artifact
+        uses: actions/upload-artifact@v7
+        with:
+          name: SARIF file
+          path: results.sarif
+          retention-days: 5

.github/workflows/semgrep.yml

@@ -0,0 +1,29 @@
+name: semgrep
+on:
+  pull_request:
+    branches: ["main", "release/**"]
+  push:
+    branches: ["main"]
+permissions:
+  contents: read
+jobs:
+  semgrep:
+    runs-on: ubuntu-latest
+    container:
+      image: semgrep/semgrep
+    steps:
+      - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          persist-credentials: false
+      - name: Run semgrep (advisory)
+        continue-on-error: true
+        run: |
+          semgrep scan --config p/owasp-top-ten --config p/secrets \
+            --sarif --output semgrep.sarif --metrics off || true
+          python -c "import json; d=json.load(open('semgrep.sarif')); print('semgrepFindings=%d' % len(d['runs'][0]['results']))" || echo "semgrepFindings=SKIP"
+      - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        if: always()
+        with:
+          name: semgrep-sarif
+          path: semgrep.sarif
+          retention-days: 14

.github/workflows/wiki-sync.yml

@@ -0,0 +1,69 @@
+name: Wiki Sync
+
+# Keeps the GitHub wiki in sync with docs/ on every release that lands on main.
+# The wiki has no native generator and historically drifts (it sat at "212+ providers /
+# 14 strategies / 37 MCP tools" while code was at 226 / 15 / 87, and new docs like
+# SUPPLY_CHAIN never appeared). This runs scripts/docs/sync-wiki.mjs, which:
+#   - ADDS any docs/ page missing from the wiki (curated; internal reports excluded),
+#   - syncs the four cover-page counts on Home.md.
+# It does NOT overwrite existing wiki pages by default: several docs sources still carry
+# stale counts (e.g. ARCHITECTURE.md says "177 providers" while the wiki cover is 226),
+# so blind overwrite would regress the wiki. Full content parity (--update-existing) is
+# gated on regenerating those sources first.
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "docs/**"
+      - "README.md"
+      - "AGENTS.md"
+      - "src/shared/constants/routingStrategies.ts"
+      - "config/i18n.json"
+      - "open-sse/mcp-server/server.ts"
+      - "scripts/docs/sync-wiki.mjs"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+concurrency:
+  group: wiki-sync
+  cancel-in-progress: false
+
+jobs:
+  sync-wiki:
+    name: Sync wiki with docs
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repo
+        uses: actions/checkout@v7
+
+      - name: Setup Node
+        uses: actions/setup-node@v6
+        with:
+          node-version: "24"
+
+      - name: Clone wiki
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          REPO: ${{ github.repository }}
+        run: |
+          git clone "https://x-access-token:${GH_TOKEN}@github.com/${REPO}.wiki.git" wiki
+
+      - name: Sync wiki (add missing pages + cover counts)
+        run: node scripts/docs/sync-wiki.mjs --wiki-dir wiki
+
+      - name: Commit & push if changed
+        run: |
+          cd wiki
+          if [ -n "$(git status --porcelain)" ]; then
+            git config user.name "github-actions[bot]"
+            git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+            git add -A
+            git commit -m "docs(wiki): auto-sync pages + cover counts with docs"
+            git push
+            echo "Wiki updated."
+          else
+            echo "Wiki already in sync — nothing to push."
+          fi

.gitignore

@@ -4,12 +4,42 @@
 .omnivscodeagent/
 omnirouteCloud/
 omnirouteSite/
+_cache/
+_ideia/
+_mono_repo/
+_references/
+_tasks/
+.agents/**
+.claude/**
+.gemini/**
+.config/**
+.data/**
+.logs/**
+.tests/**
+.coverage/**
+coverage/
+.dist/**
+.next/**
+.build/**
+.out/**
+
+# Stryker mutation testing — ephemeral sandbox + generated reports (never commit)
+.stryker-tmp/
+reports/mutation/
+stryker-output-*.json
+
+
+# Memory Bank and Cursor rules (local-only AI agent context)
+memory-bank/
+.cursor/rules/core.mdc
+.cursor/rules/memory-bank.mdc
 
 # Claude Code local state — runtime files only; shared commands at .claude/commands/ are tracked
 .claude/scheduled_tasks.lock
 .claude/scheduled_tasks/
 .claude/sessions/
 .claude/state.json
+.claude/settings.local.json
 
 # Root-level underscore-prefixed directories (private/draft — never commit)
 /_*/
@@ -19,32 +49,19 @@ docs/new-features/
 
 # dependencies
 node_modules/
-/.pnp
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/versions
-.data/
-.next-playwright/
-
-# testing
-coverage/
-coverage**
-
-# next.js
-.next/
-/out/
-
-# production
-/build
-/app
-cloud/*
-
-# misc
+# Also ignore a root node_modules SYMLINK (worktree setups symlink it from the main
+# checkout). The trailing-slash pattern above only matches a directory, so without this
+# a symlink named node_modules could be staged by `git add -A` and committed.
+/node_modules
+*.map
 .DS_Store
-*.pem
+
+# Obsidian sync plugin — committed for community distribution
+!obsidian-plugin/
+obsidian-plugin/node_modules/
+
+# Serena AI assistant config (local-only tool, not project code)
+.serena/
 
 # debug
 npm-debug.log*
@@ -55,6 +72,10 @@ yarn-error.log*
 # env files (can opt-in for committing if needed)
 .env*
 !.env.example
+!.env.homolog.example
+# Provider API keys (never commit)
+*.api-key
+.nvidia-api-key
 
 # vercel
 .vercel
@@ -97,15 +118,22 @@ clipr/
 app.log
 *.tgz
 .gh-discussions.json
+deploy.sh
+docker-compose.minimal.yml
+
 
 # Backup directories
 app.__qa_backup/
 .app-build-backup-*/
+backup/
 
-# Production standalone build (created by scripts/prepublish.mjs)
-# Conflicts with Next.js App Router detection in dev (root app/ shadows src/app/)
-# npm publish still includes it via package.json "files" field
-/app/
+# Build intermediates (.build/) and shippable standalone (dist/).
+# These are fully reproducible from source; never committed.
+# Layer 1: Next.js now writes to .build/next (was .next); assembled bundle → dist/
+# (Previously /app/ was the standalone output; renamed to /dist/ in Layer 1.)
+/.build/
+/dist/
+/.next/
 
 # Electron
 electron/dist-electron/
@@ -120,9 +148,6 @@ vscode-extension/
 *.sqlite-wal
 *.sqlite-journal
 
-# Compiled npm-package build artifact (not source, should not be in git)
-/app
-
 # IDEA
 .idea/
 
@@ -137,6 +162,11 @@ typescript
 
 # Superpowers plans/specs (internal tooling, not project code)
 docs/superpowers/
+# Superpowers visual-companion brainstorm mockups (ephemeral)
+.superpowers/
+
+# TIA test-impact map — generated at runtime in CI (build-test-impact-map.mjs), never committed (~21MB)
+config/quality/test-impact-map.json
 
 # GitNexus local index
 .gitnexus
@@ -151,8 +181,8 @@ bun.lock
 # Private environment variables for .http-client
 http-client.private.env.json
 
-# Feature-triage ephemeral artifact (regenerated each run)
-_ideia/_triage.json
+# Note: _ideia/ (feature-triage drafts) is fully covered by the /_*/ rule above
+# and kept as a separate local-only git repo. Never committed to OmniRoute.
 
 # i18n audit artifact (generated by scripts/i18n/audit-dashboard-pages.mjs)
 scripts/i18n/_audit.json
@@ -161,5 +191,61 @@ scripts/i18n/_pending-keys.json
 # Private workflow / skill / command implementations
 # These contain proprietary multi-phase logic and should not be committed
 .agents/workflows/implement-features-ag.md
+.agents/workflows/port-upstream-features-ag.md
+.agents/workflows/port-upstream-issues-ag.md
 .agents/skills/implement-features/
 .claude/commands/implement-features-cc.md
+.claude/commands/port-upstream-features-cc.md
+.claude/commands/port-upstream-issues-cc.md
+.claude/worktrees/
+.codegraph/
+
+# Fumadocs generated source
+.source/
+
+# AI agent local settings and configs
+.agents/
+.antigravitycli/
+.claude/
+
+# PR Reviews and local feedback files
+pr_reviews*.json
+
+#hidden local data directories (never commit)
+.local-data/
+.data-dev/
+/.junie/
+
+# internal setup prompts with personal credentials — never commit
+CODEX-SETUP-PROMPT.md
+# Quality ratchet — métricas efêmeras (baseline commitado em config/quality/; métricas não)
+config/quality/quality-metrics.json
+
+# Runtime logs (diretório local, nunca versionado)
+/logs/
+-home-diegosouzapw-dev-automações-bots-yt-downloader-20260504 .txt
+-home-diegosouzapw-dev-automações-bots-yt-downloader-20260410 .txt
+docs/prompts/AGENT-OWNERSHIP-PROTOCOL.omniroute.md
+docs/prompts/AGENT-OWNERSHIP-PROTOCOL.md
+docs/prompts/AGENT-OWNERSHIP-PROTOCOL.omniroute-mim.md
+docs/prompts/AGENT-OWNERSHIP-PROTOCOL.omniroute-mid.md
+omniroute.md
+
+# mise configuration
+mise.toml
+_artifacts/
+.claude-flow/
+
+# ESLint file cache (npm run lint --cache / complexity ratchets)
+.eslintcache
+.eslintcache-complexity
+
+
+# CI/local quality artifacts (eslint-results.json, etc.)
+.artifacts/
+
+# Homologation E2E suite (npm run homolog) — real-environment credentials + report output
+.env.homolog
+tests/homolog/.auth/
+tests/homolog/ui/.auth/
+homolog-report/

.gitleaks.toml

@@ -0,0 +1,89 @@
+# .gitleaks.toml — Configuração do gitleaks para OmniRoute
+# Task 7.18 — PLANO-QUALITY-GATES-FASE7.md
+#
+# Estende as regras padrão do gitleaks com allowlists específicas do projeto.
+#
+# INSTRUÇÕES para allowlists:
+#   Findings legítimos (fixtures de teste, creds OAuth públicas já cobertas pelo
+#   check-public-creds.mjs, valores de exemplo em docs) devem ser registrados abaixo
+#   em [[allowlist]] com um comentário explicativo obrigatório.
+#
+#   NÃO adicione uma entrada de allowlist sem justificativa. Cada entrada é revisada
+#   a cada release (stale-enforcement). Regra: se o finding é um valor real que o
+#   sistema usa em produção, é um verdadeiro positivo — não allowliste, corrija.
+#
+# Referência: docs/security/PUBLIC_CREDS.md (credenciais OAuth públicas conhecidas)
+#             CLAUDE.md Hard Rule #11 (resolvePublicCred obrigatório)
+
+# Herdar TODAS as regras padrão do gitleaks. ATENÇÃO: um config customizado
+# SEM [extend].useDefault = true (e sem [[rules]] próprias) resulta em ZERO
+# regras — o gitleaks SUBSTITUI o ruleset padrão pelo arquivo, não o estende
+# automaticamente. Sem esta seção, `gitleaks --config .gitleaks.toml` nunca
+# detecta nada (todo finding vira 0), tornando o gate inerte. Com useDefault,
+# a allowlist abaixo é aplicada POR CIMA das ~170 regras padrão.
+[extend]
+  useDefault = true
+
+# Para desabilitar uma regra específica, usar:
+# [[rules]]
+#   id = "rule-id"
+#   [rules.allowlist]
+#     description = "..."
+
+# ---------------------------------------------------------------------------
+# Allowlist global do projeto
+# Entradas aqui são ignoradas em TODAS as varreduras.
+# ---------------------------------------------------------------------------
+[allowlist]
+  description = "OmniRoute project-level allowlist — fixtures, test vectors, public OAuth creds"
+
+  # Paths a ignorar completamente (node_modules, builds, etc.)
+  paths = [
+    '''node_modules''',
+    '''\.next''',
+    '''dist''',
+    '''\.git''',
+    '''coverage''',
+    '''\.nyc_output''',
+  ]
+
+  # Commits específicos a ignorar (ex: commit que introduziu fixtures de teste)
+  # commits = []
+
+  # Regexes de stopwords — linhas que contêm estes padrões são ignoradas.
+  # Usar apenas para falsos positivos comprovados com justificativa abaixo.
+  # stopwords = []
+
+  # Regexes de targets (paths de arquivos) que podem ser allowlistados por regra.
+  # Ver [[allowlist]] por-regra abaixo para granularidade.
+
+# ---------------------------------------------------------------------------
+# Allowlist por-regra (adicionar conforme necessário durante o stale review)
+# ---------------------------------------------------------------------------
+#
+# Exemplo (REMOVER / SUBSTITUIR por entradas reais quando necessário):
+#
+# [[rules]]
+#   # Allowlistar fixtures de teste que contêm tokens OAuth de exemplo/inválidos
+#   # Adicionado: 2026-06-13 | Revisar em: v3.9.0 | Justificativa: valores não-reais de teste
+#   id = "github-fine-grained-pat"
+#   [rules.allowlist]
+#     description = "Test fixture PATs — valores sintéticos, não funcionais"
+#     paths = [
+#       '''tests/fixtures/''',
+#       '''tests/unit/''',
+#     ]
+#
+
+[[rules]]
+  # Falsos-positivos comprovados do generic-api-key — zerados em 2026-07-13 (WS6/D3,
+  # plano v3.8.49). Revisar em v3.9.0. Nenhum é credencial: dois são NOMES DE CAMPO
+  # de métricas de latência; o terceiro é o valor PÚBLICO de um beta header da API
+  # da Anthropic (documentado publicamente, não é segredo).
+  id = "generic-api-key"
+  [rules.allowlist]
+    description = "Field names + public Anthropic beta-header value (não são segredos)"
+    regexes = [
+      '''latencyP\d{2}Ms''',
+      '''interleaved-thinking-2025-05-14''',
+    ]

.husky/pre-commit

@@ -5,20 +5,9 @@ if ! command -v npx >/dev/null 2>&1; then
   exit 0
 fi
 
+# Cheap, deterministic local gates (re-enabled). Slower checks (i18n drift,
+# openapi coverage/security-tiers, env-doc sync) run in CI to keep commits fast.
 npx lint-staged
 node scripts/check/check-docs-sync.mjs
 npm run check:any-budget:t11
-
-# Strict env-doc sync (FASE 2)
-node scripts/check/check-env-doc-sync.mjs
-
-# CLI i18n consistency check — all t() keys must exist in en.json (FASE 8.3)
-node scripts/check/check-cli-i18n.mjs
-
-# i18n docs drift advisory (FASE 5) — warn-only on pre-commit; CI enforces strict.
-node scripts/i18n/check-translation-drift.mjs --warn || \
-  echo "⚠️  i18n drift detected. Run 'npm run i18n:run' to update locale mirrors."
-
-# i18n UI coverage advisory (FASE 6) — pre-commit warns; CI enforces strict.
-node scripts/i18n/check-ui-keys-coverage.mjs --threshold=80 || \
-  echo "⚠️  UI i18n coverage below 80% for at least one locale."
+node scripts/check/check-tracked-artifacts.mjs

.husky/pre-push

@@ -1,8 +1,15 @@
 #!/usr/bin/env sh
-#if ! command -v npm >/dev/null 2>&1; then
-#  echo "⚠️  npm not found in PATH — skipping pre-push hooks"
-#  echo "   Run 'npm test' manually before pushing."
-#  exit 0
-#fi
+# .husky/pre-push — intentionally light.
+# any-budget + tracked-artifacts already run on pre-commit; re-running them on
+# every push only doubles local wall time for the same existence reason (CI still
+# enforces both). Keep this hook as a PATH/npm sanity check + reminder.
+# Intentionally excludes test:unit / typecheck (slow; covered by CI).
 
-#npm run test:unit
+if ! command -v npm >/dev/null 2>&1; then
+  echo "⚠️  npm not found in PATH — skipping pre-push hooks"
+  echo "   Run 'npm run check:any-budget:t11 && npm run check:tracked-artifacts' manually before pushing."
+  exit 0
+fi
+
+# No-op success: real local gates live in pre-commit; CI owns the rest.
+exit 0

.i18n-state.json

@@ -1,219 +0,0 @@
-{
-  "sources": {
-    "CLAUDE.md": {
-      "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-      "locales": {
-        "pt-BR": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "6ed62a4b8e85b48db9dbd3c5f00cec0a423742dd4ac518ff0206d6bf1732e714",
-          "updated_at": "2026-05-18T22:01:38.515Z"
-        },
-        "az": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "b3da42c255bf9d70ac862ae083ad2c15193dfcd69407db70bb452bc03b735283",
-          "updated_at": "2026-05-18T21:47:44.228Z"
-        },
-        "bn": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "cbb9eb8a552e7f6ceb0d45fdd115db2d88e90c420944f27fdfce8a461603c50a",
-          "updated_at": "2026-05-18T21:48:17.508Z"
-        },
-        "ar": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "179543e6015946c2409a72ad87519c71a86086982fa573061a9d958675face59",
-          "updated_at": "2026-05-18T21:48:47.676Z"
-        },
-        "cs": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "ee2d587bb968619c4791ee7fa75909f40aa1d6fb5e97c293f8ff2ac4bc22167c",
-          "updated_at": "2026-05-18T21:51:04.860Z"
-        },
-        "da": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "4672b5643ab8f9adfcf8a14199c127dcc54380ed4cbaccd3d946f0db25fbead3",
-          "updated_at": "2026-05-18T21:51:13.777Z"
-        },
-        "de": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "1a36bebb379ff38306b0e850d2460f4cd9c5bc70b8b1f7ef9c42b84c833e22cd",
-          "updated_at": "2026-05-18T21:51:16.409Z"
-        },
-        "es": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "269c2b0842485060471ff2a7179fd16cc40273e7c8d27f28477d8724a1333b26",
-          "updated_at": "2026-05-18T21:51:22.611Z"
-        },
-        "fa": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "8b4603ebc4875f4af2ca67c571282038f566dce5b62d17caa361c0ec879c2bea",
-          "updated_at": "2026-05-18T21:52:38.812Z"
-        },
-        "fi": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "16a3a0b0df89e37808d7567e502944fb6792e14eb8c61e4b474b0fe79b310d63",
-          "updated_at": "2026-05-18T21:52:44.086Z"
-        },
-        "fr": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "1a8bb2fdc17927047842bf6806787e9cea83d8f2912bc0291836574af877cde1",
-          "updated_at": "2026-05-18T21:52:44.715Z"
-        },
-        "he": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "446414fae3f108ec2ac0fea09d826fab6a6dcfe2189e33f63d0068d7ffe945b2",
-          "updated_at": "2026-05-18T21:54:06.000Z"
-        },
-        "hi": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "24ce173a1252a9849917324395ae5712e7d03d98ab9e9119a98c12c405e5fd96",
-          "updated_at": "2026-05-18T21:54:16.102Z"
-        },
-        "gu": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "4d49e4be59a029c9407ca023a7f7ef21533e2ccf9c1b857a84eec0d5c1e0b1eb",
-          "updated_at": "2026-05-18T21:55:11.836Z"
-        },
-        "hu": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "85881f57fc6a606e122466a368b159f3b7f6a8f0fa90aa7fe039f0127e436d44",
-          "updated_at": "2026-05-18T21:55:54.603Z"
-        },
-        "id": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "e970c79fe15c9f78745b1b53e5eed3b8914641a0a3f81ce2b5207a21dd850d4e",
-          "updated_at": "2026-05-18T21:56:05.289Z"
-        },
-        "in": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "9127b1ab7c33307a62ba12adc36ae0f70809b1ff21cd562b0d2f4c52ba5aae0d",
-          "updated_at": "2026-05-18T21:56:08.126Z"
-        },
-        "it": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "949279fa3953e26345303fdb0defb959d722cfd8e0858a2fd1353384bdee2d66",
-          "updated_at": "2026-05-18T21:56:31.825Z"
-        },
-        "ja": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "e2eec56e1fa368594e32e6184defc91bccf6b086f84de8a03774efa3b4b21cc7",
-          "updated_at": "2026-05-18T21:57:34.374Z"
-        },
-        "mr": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "c795db0cde7b51a434a5bf06384fbec09073a2b7418fb0dddd90fa12f46fb7e1",
-          "updated_at": "2026-05-18T21:58:25.858Z"
-        },
-        "ko": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "8d3f5cfda2ad3ce01e882cf2008de9f2106279e0f3a180cd8fa70280870b9761",
-          "updated_at": "2026-05-18T21:58:25.863Z"
-        },
-        "ms": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "f2e13499c45cea20bcf178eac842ba923859bcc25822c6b4b9cf627512f3cce9",
-          "updated_at": "2026-05-18T21:58:33.906Z"
-        },
-        "nl": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "81f851a5aff422692c62fd65c1289598bfc779f8ca02af7083215a0d0cf42575",
-          "updated_at": "2026-05-18T21:59:16.560Z"
-        },
-        "phi": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "bf3fb36abd19f82bb296fe9fada413368b06b60d7931c352ebd1da8c3ff2c9fa",
-          "updated_at": "2026-05-18T21:59:52.998Z"
-        },
-        "no": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "3263bf8e5287023b7e50f1a2e65c069b2a3719cbf58b1454e451b19ac56b2c93",
-          "updated_at": "2026-05-18T22:00:47.607Z"
-        },
-        "pl": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "549129cf48c266b953b13e32efdbd8b7ba09848d68f76a984471c8f3b7c15338",
-          "updated_at": "2026-05-18T22:01:03.762Z"
-        },
-        "ro": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "6391e37e4289f64b4e58a2922f42d0163f50dd836f55dbad1aa2d39020c27a68",
-          "updated_at": "2026-05-18T22:02:54.102Z"
-        },
-        "ru": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "6aa38bc3c3c835bcd5ddf37d9a1ed29bf57d3234ee910f87c92b1363254ad4e6",
-          "updated_at": "2026-05-18T22:02:57.045Z"
-        },
-        "pt": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "3a15114c2839e513ce1983571ab7ac312856a29f1284a49d80eba3860b06b3ed",
-          "updated_at": "2026-05-18T22:03:11.851Z"
-        },
-        "sk": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "d7bf32867f17562967d0af5b78ae4c71abd4af3c7523128b041739dd9b02131b",
-          "updated_at": "2026-05-18T22:04:00.222Z"
-        },
-        "sw": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "ae3337d4ef14ab15a25a60f2d74db80be8b2e82cdb3911f9a92b22fa5fd5395b",
-          "updated_at": "2026-05-18T22:04:46.376Z"
-        },
-        "sv": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "36f1ca81330f13a3489523711dcf9b3a051518164345dfefc3097dbc1459e1b3",
-          "updated_at": "2026-05-18T22:05:02.302Z"
-        },
-        "ta": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "12f7f379ca9970a561aa71a56f58734f6d454bf47f99bc240e52c2943aa585bb",
-          "updated_at": "2026-05-18T22:05:29.419Z"
-        },
-        "te": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "7334cc88818d46644f138e8c5aee8045346cc6a9e98f597bd616ff8de02d17e9",
-          "updated_at": "2026-05-18T22:06:17.933Z"
-        },
-        "tr": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "7284ba38f5a9b81f70926c923870f6ee1d29e9e34e7074a087e5ad9812794c91",
-          "updated_at": "2026-05-18T22:07:15.730Z"
-        },
-        "th": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "b300d8668da2de9dd5e3c80b3a6d138b677662965be6c1459dcc145fbe88c062",
-          "updated_at": "2026-05-18T22:07:44.472Z"
-        },
-        "ur": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "c2dfcb2125306a21b293a054f72d0946af4c9f29058fb679bcca3fbda7608a5a",
-          "updated_at": "2026-05-18T22:08:34.169Z"
-        },
-        "vi": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "ece90f91f228a0c504e4537d55e951b48763cafc14531a81dfc42d8a1ad45771",
-          "updated_at": "2026-05-18T22:09:55.405Z"
-        },
-        "zh-CN": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "780e02b27f556c748090474ad9081d8b3fd92018b14329407ac54a8f7e27688b",
-          "updated_at": "2026-05-18T22:10:23.922Z"
-        },
-        "uk-UA": {
-          "source_hash": "951d6ba25c4ced12e53f5dead589013135b827a1ed908a6dc5c5e5dcc3cc96cb",
-          "target_hash": "9a7a645713fb8b23de2a1a9b24317376a7a83fee994830bb81a2889e34efc0ee",
-          "updated_at": "2026-05-18T22:18:32.917Z"
-        }
-      }
-    },
-    "docs/architecture/ARCHITECTURE.md": {
-      "source_hash": "a065bbff5e461cca6cd1a81d2923626040548c3b3af98ecb2a69a99709bd8059",
-      "locales": {
-        "pt-BR": {
-          "source_hash": "a065bbff5e461cca6cd1a81d2923626040548c3b3af98ecb2a69a99709bd8059",
-          "target_hash": "7ee10dc8cba2668fd279af64ecca3a1760e974b6dc9672aee81e69c63ee41175",
-          "updated_at": "2026-05-20T05:34:41.826Z"
-        }
-      }
-    }
-  }
-}

.markdownlint.json

@@ -0,0 +1,14 @@
+{
+  "_comment": "Advisory markdown lint for docs/ + root *.md. Rules that conflict with the existing doc style (heavy inline HTML, long lines, centered headings) are disabled so the gate stays signal-not-noise. Run: npm run lint:md",
+  "default": true,
+  "MD013": false,
+  "MD033": false,
+  "MD041": false,
+  "MD024": { "siblings_only": true },
+  "MD026": false,
+  "MD036": false,
+  "MD040": false,
+  "MD029": false,
+  "MD007": { "indent": 2 },
+  "MD046": false
+}

.mergify.yml

@@ -0,0 +1,55 @@
+# Mergify merge queue — WS3.4/D5 of the v3.8.49 quality/velocity master plan.
+#
+# WHY: ~85-100 active PR authors/month and 300+ PRs/week peaks, all merged by ONE
+# identity. The manual merge-train validated batches by hand; this queue automates
+# it with batching + automatic batch bisection (a red batch of N costs ~log2(N)
+# revalidations instead of N). Mergify Open Source plan: free, unlimited, public repo.
+#
+# GOVERNANCE (non-negotiable, mirrors CLAUDE.md Hard Rules #21/#22 + the owner's
+# pre-merge ⭐ gate):
+#   • A PR enters the queue ONLY via the `queue` label — applied by the owner (or a
+#     session acting for the owner) AFTER the pre-merge ⭐ report/decision. The label
+#     IS the merge approval; Mergify only executes it.
+#   • During a release-freeze (open issue labeled `release-freeze`), do NOT label PRs
+#     targeting the frozen branch — the freeze is a human-honored coordination signal
+#     the queue cannot see. Retarget to the active release/vX+1 first (Hard Rule #21).
+#   • Never label a PR another session is actively working (Hard Rule #22b).
+#   • 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.
+
+queue_rules:
+  - name: release
+    # Any current or future release branch — the reason GitHub's native queue was
+    # rejected (no wildcard support on personal-account repos).
+    queue_conditions:
+      - base~=^release/v\d+\.\d+\.\d+$
+      - label=queue
+      - -draft
+      - -conflict
+    # "Everything that ran is green, nothing still running, AND the always-on
+    # anchor check succeeded" — robust to the path-filtered fast-gates (docs-only
+    # PRs skip code jobs; matrix shard names vary) while never fail-open: a PR with
+    # zero checks cannot vacuously merge, because `Merge integrity` runs on EVERY
+    # non-draft PR (quality.yml) and must be an affirmative success. Review approval
+    # 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:
+      - "#check-failure=0"
+      - "#check-pending=0"
+      - "#check-success>=1"
+      - check-success=Merge integrity (changelog + generated skills)
+    # 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
+
+pull_request_rules:
+  - name: clean up the queue label after merge
+    conditions:
+      - merged
+    actions:
+      label:
+        remove:
+          - queue

.npmignore

@@ -9,6 +9,16 @@ app/vscode-extension/
 **/db.json
 
 # Source code (pre-built app/ is published instead)
+#
+# NOTE (#3578 / #3821-review): package.json "files" is the source of truth for what
+# ships. It now allowlists the backend source closure the MCP server needs at runtime
+# (open-sse/, src/lib, src/server, ...) and OVERRIDES the broad src/ + open-sse/ excludes
+# below — npm honors files[] over .npmignore for inclusion. These lines are kept only as
+# intent/back-stop: if files[] is ever trimmed back to specific paths, they must NOT be
+# allowed to re-hide the MCP closure (that would silently reintroduce the --mcp
+# ERR_MODULE_NOT_FOUND #3578 fixed). The closure gate in
+# tests/unit/mcp-published-files-closure-3578.test.ts asserts the real `npm pack` output
+# in both directions (closure present + zero test files), catching such a regression.
 src/
 open-sse/
 docs/
@@ -18,6 +28,17 @@ images/
 logs/
 scripts/
 
+# Co-located tests must never ship even when their parent dir is allowlisted by files[].
+# (Primary guard is the "!**/*.test.*" negations in package.json files[]; this is defense
+# in depth for any nested dir the allowlist pulls in.)
+**/__tests__/
+**/*.test.ts
+**/*.test.tsx
+**/*.test.js
+**/*.test.mjs
+**/*.spec.ts
+**/*.spec.tsx
+
 # Config/dev files
 *.md
 !README.md

.npmrc

@@ -2,3 +2,13 @@
 # Keeping peer auto-install disabled prevents npm from pulling @lobehub/ui/mermaid
 # back into the tree and reopening npm audit findings for unused packages.
 legacy-peer-deps=true
+
+# Network resilience: enlarge npm's fetch retry budget so a transient registry
+# socket reset (ECONNRESET) mid-download retries instead of failing the job.
+# npm defaults to only 2 retries with short timeouts; `npm ci` in
+# electron-release.yml hit ECONNRESET during v3.8.41 publish. Applies to every
+# CI workflow (electron / docker / unit) and local installs.
+fetch-retries=5
+fetch-retry-factor=4
+fetch-retry-mintimeout=20000
+fetch-retry-maxtimeout=120000

.prettierignore

@@ -0,0 +1,5 @@
+# Long reference tables are manually aligned; formatting the whole file causes noisy diffs.
+docs/reference/ENVIRONMENT.md
+
+# Dense auto-generated free-tier budget rows (one object per line) — prettier multi-line expand blows past file-size cap 800.
+open-sse/config/freeModelCatalog.data.ts

.semgrep/rules/cli-no-sqlite.yaml

@@ -1,31 +0,0 @@
-rules:
-  - id: cli-no-sqlite-direct
-    patterns:
-      - pattern: new Database(...)
-    paths:
-      include:
-        - "/bin/**"
-      exclude:
-        - "/bin/cli/sqlite.mjs"
-    message: >
-      Direct SQLite access in bin/ is banned. Use src/lib/db/* helpers or
-      withRuntime() from bin/cli/runtime.mjs. See CLAUDE.md hard rule #5 and
-      bin/cli/CONVENTIONS.md.
-    languages: [js]
-    severity: ERROR
-
-  - id: cli-no-raw-sql
-    patterns:
-      - pattern: $DB.prepare("INSERT INTO ...")
-      - pattern: $DB.prepare("DELETE FROM ...")
-      - pattern: $DB.prepare("UPDATE $TABLE SET ...")
-    paths:
-      include:
-        - "/bin/**"
-      exclude:
-        - "/bin/cli/sqlite.mjs"
-    message: >
-      Raw SQL in bin/ is banned. Use src/lib/db/* helpers. See CLAUDE.md
-      hard rule #5 and bin/cli/CONVENTIONS.md.
-    languages: [js]
-    severity: ERROR

.size-limit.json

@@ -0,0 +1,22 @@
+[
+  {
+    "name": "CLI entry (omniroute.mjs)",
+    "path": "bin/omniroute.mjs",
+    "limit": "15 KB"
+  },
+  {
+    "name": "MCP server entry (mcp-server.mjs)",
+    "path": "bin/mcp-server.mjs",
+    "limit": "5 KB"
+  },
+  {
+    "name": "Node runtime support (nodeRuntimeSupport.mjs)",
+    "path": "bin/nodeRuntimeSupport.mjs",
+    "limit": "8 KB"
+  },
+  {
+    "name": "Reset password entry (reset-password.mjs)",
+    "path": "bin/reset-password.mjs",
+    "limit": "6 KB"
+  }
+]

.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
+};

.trivyignore

@@ -0,0 +1,22 @@
+# .trivyignore — accepted-risk suppressions for the container image scan
+#
+# Policy (see docs/security/SUPPLY_CHAIN.md):
+#   - The Trivy steps in .github/workflows/docker-publish.yml run with
+#     `ignore-unfixed: true`, so vulnerabilities WITHOUT a published fix are
+#     already excluded from both the blocking CRITICAL gate and the advisory
+#     Security-tab upload. You do NOT need an entry here for an unfixable
+#     base-image OS CVE — it will not be reported.
+#   - This file is the single auditable home for the rare case where a *fixable*
+#     CVE must be temporarily accepted (e.g. the upstream fix is not yet in the
+#     pinned base tag, or the affected package/binary is provably unreachable
+#     from the proxy request surface and rebuilding now is not justified).
+#
+# Format — one CVE id per line, each with a justification comment and, where
+# possible, an expiry, e.g.:
+#   # CVE-XXXX-YYYY — <why accepted>; revisit on next base-image bump (YYYY-MM-DD)
+#   CVE-XXXX-YYYY
+#
+# Keep this list SHORT and reviewed every release. Prefer fixing (rebuild on a
+# patched base / bump the dep) over suppressing. Stale entries are debt.
+#
+# (No accepted-risk suppressions at present — ignore-unfixed covers the noise.)

.vale.ini

@@ -0,0 +1,15 @@
+# Advisory prose lint for OmniRoute docs (Vale — https://vale.sh).
+# Warning-first: surfaces vague language, passive voice, and terminology drift without
+# blocking CI. The Microsoft style is pulled by the CI step (vale sync / vale-action).
+# Project terms live in the OmniRoute vocabulary so they never read as misspellings.
+StylesPath = .vale/styles
+MinAlertLevel = warning
+Packages = Microsoft
+Vocab = OmniRoute
+
+[*.md]
+BasedOnStyles = Vale, Microsoft
+
+# Code-heavy reference docs and auto-generated catalogs are noisy under prose rules.
+[docs/reference/PROVIDER_REFERENCE.md]
+BasedOnStyles = Vale

.vale/styles/Vocab/OmniRoute/accept.txt

@@ -0,0 +1,50 @@
+OmniRoute
+combo
+combos
+[Cc]ombo
+[Aa]uto-[Cc]ombo
+MCP
+A2A
+ACP
+RTK
+Caveman
+Troglodita
+Qdrant
+FTS5
+SQLite
+LowDB
+OAuth
+PKCE
+SSE
+JSON-RPC
+LKGP
+P2C
+Antigravity
+Codex
+Kiro
+Qoder
+Pollinations
+LongCat
+Cerebras
+DeepSeek
+Groq
+Cline
+OpenCode
+Termux
+Electron
+Fumadocs
+Notion
+Obsidian
+WebDAV
+IPv4
+IPv6
+SOCKS5
+loopback
+backoff
+changelog
+i18n
+locale
+locales
+roadmap
+[Ww]ildcard
+upstream

.vscode/launch.json

@@ -1,31 +0,0 @@
-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Debug Dev Server",
-      "type": "node",
-      "request": "launch",
-      "runtimeExecutable": "${env:HOME}/.nvm/versions/node/v22.22.2/bin/node",
-      "program": "${workspaceFolder}/scripts/run-next.mjs",
-      "args": ["dev"],
-      "console": "integratedTerminal",
-      "skipFiles": ["<node_internals>/**", "node_modules/**"]
-    },
-    {
-      "name": "Debug Prod Server",
-      "type": "node",
-      "request": "launch",
-      "program": "${workspaceFolder}/scripts/run-next.mjs",
-      "args": ["start"],
-      "console": "integratedTerminal",
-      "skipFiles": ["<node_internals>/**", "node_modules/**"]
-    },
-    {
-      "name": "Attach to Running Server",
-      "type": "node",
-      "request": "attach",
-      "port": 9229,
-      "skipFiles": ["<node_internals>/**", "node_modules/**"]
-    }
-  ]
-}

.vscode/settings.json

@@ -1,4 +1,5 @@
 {
+  "workbench.sideBar.location": "left",
   "css.lint.unknownAtRules": "ignore",
   "sonarlint.rules": {
     "css:S4662": {
@@ -18,32 +19,124 @@
     }
   },
   "git.ignoreLimitWarning": true,
+
+  // ─── Git: não adicionar os ~44 repos aninhados (9 worktrees + _references/* +
+  // _mono_repo/* + _ideia/_tasks/.agents) ao Source Control. Era a causa do
+  // "validando muito": um git status + watcher por repo. Só o repo raiz fica. ───
+  "git.autoRepositoryDetection": false,
+  "git.repositoryScanMaxDepth": 0,
+  "git.detectSubmodules": false,
+  "git.autofetch": false,
+  "git.autorefresh": true,
+
+  // ─── Performance: não seguir o symlink de node_modules criado pelas worktrees ───
+  // As worktrees em .worktrees/ apontam node_modules para o checkout principal;
+  // sem isto a busca atravessa o symlink mesmo com node_modules excluído.
+  "search.followSymlinks": false,
+
+  // ─── TypeScript server (monorepo grande: ~6,6k arquivos rastreados, Next.js 16) ───
+  "typescript.tsserver.maxTsServerMemory": 4096,
+  "typescript.disableAutomaticTypeAcquisition": true,
+  "typescript.tsc.autoDetect": "off",
+  "npm.autoDetect": "off",
+  // O tsserver tem o próprio watcher (independente de files.watcherExclude).
+  // excludeDirectories evita que ele vigie as árvores pesadas.
+  "typescript.tsserver.watchOptions": {
+    "excludeDirectories": [
+      "**/node_modules",
+      "**/.next",
+      "**/.build",
+      "**/dist",
+      "**/coverage",
+      "**/.worktrees",
+      "**/.claude/worktrees",
+      "**/electron",
+      "**/_references",
+      "**/_mono_repo",
+      "**/_tasks"
+    ]
+  },
+
+  // Para esconder os diretórios gerados da árvore do Explorer, descomente:
+  // (MANTIDO comentado — o dono precisa ver _references/_mono_repo/_tasks na árvore.
+  //  A performance é resolvida por watcherExclude + search.exclude + tsserver, sem
+  //  precisar escondê-los do Explorer.)
   // "files.exclude": {
+  //   "**/.worktrees": true,
+  //   "**/coverage": true,
+  //   "**/dist": true,
+  //   "**/.build": true,
+  //   "**/.next": true,
   //   "**/_references": true,
   //   "**/_mono_repo": true,
-  //   "**/electron": true,
-  //   "**/node_modules": true,
-  //   "**/.next": true,
-  //   "**/coverage": true,
-  //   "**/omniroute-*.tgz": true,
-  //   "**/_tasks": true
+  //   "**/_tasks": true,
+  //   "**/omniroute-*.tgz": true
   // },
   "files.watcherExclude": {
-    "**/_references/**": true,
-    "**/_mono_repo/**": true,
-    "**/electron/**": true,
+    "**/.git/objects/**": true,
+    "**/.git/subtree-cache/**": true,
     "**/node_modules/**": true,
     "**/.next/**": true,
+    "**/.build/**": true,
+    "**/dist/**": true,
+    "**/build/**": true,
+    "**/out/**": true,
     "**/coverage/**": true,
-    "**/_tasks/**": true
+    "**/.coverage/**": true,
+    "**/.nyc_output/**": true,
+    "**/.cache/**": true,
+    "**/.turbo/**": true,
+    "**/.swc/**": true,
+    "**/.stryker-tmp/**": true,
+    "**/stryker-output-*/**": true,
+    "**/playwright-report/**": true,
+    "**/test-results/**": true,
+    "**/.worktrees/**": true,
+    "**/.claude/worktrees/**": true,
+    "**/electron/**": true,
+    "**/_references/**": true,
+    "**/_mono_repo/**": true,
+    "**/_tasks/**": true,
+    "**/logs/**": true,
+    "**/*.tgz": true,
+    "**/*.tsbuildinfo": true,
+    "**/OmniRoute-*/**": true,
+    "**/*-merge-*/**": true,
+    "**/*-worktree-*/**": true,
+    "**/*-issues-*/**": true,
+    "**/*-reorg*/**": true
   },
   "search.exclude": {
-    "**/_references": true,
-    "**/_mono_repo": true,
-    "**/electron": true,
     "**/node_modules": true,
     "**/.next": true,
+    "**/.build": true,
+    "**/dist": true,
+    "**/build": true,
+    "**/out": true,
     "**/coverage": true,
-    "**/_tasks": true
+    "**/.coverage": true,
+    "**/.nyc_output": true,
+    "**/.cache": true,
+    "**/.turbo": true,
+    "**/.swc": true,
+    "**/.stryker-tmp": true,
+    "**/stryker-output-*": true,
+    "**/playwright-report": true,
+    "**/test-results": true,
+    "**/.worktrees": true,
+    "**/.claude/worktrees": true,
+    "**/electron": true,
+    "**/_references": true,
+    "**/_mono_repo": true,
+    "**/_tasks": true,
+    "**/logs": true,
+    "**/*.tgz": true,
+    "**/*.tsbuildinfo": true,
+    "**/package-lock.json": true,
+    "**/OmniRoute-*": true,
+    "**/*-merge-*": true,
+    "**/*-worktree-*": true,
+    "**/*-issues-*": true,
+    "**/*-reorg*": true
   }
 }

.zizmor.yml

@@ -0,0 +1,104 @@
+# .zizmor.yml — zizmor security audit configuration
+# https://github.com/woodruffw/zizmor
+#
+# zizmor audits GitHub Actions workflows for security anti-patterns:
+#   • Unpinned third-party actions (supply-chain risk)
+#   • Script injection via ${{ github.* }} in run: steps
+#   • pull_request_target misuse (allows untrusted code to reach secrets)
+#   • Excessive permissions / overly broad GITHUB_TOKEN scopes
+#   • Cache poisoning via actions/cache with unguarded keys
+#   • … 20+ additional audits
+#
+# MOTIVATION (2026-03 incident): the trivy-action/LiteLLM supply-chain attack
+# exploited exactly the kind of pull_request_target misconfiguration that zizmor
+# detects statically. OmniRoute's npm/Docker/Electron publish workflows are high-
+# value targets that warrant proactive audit.
+#
+# BASELINE STRATEGY: this file starts with an EMPTY ignores list. As zizmor is
+# first run against the existing workflows, findings will be reviewed:
+#   • True positives → fix the workflow (preferred)
+#   • Accepted risk  → add an entry below with a justification comment
+# This enforces the same stale-enforcement discipline as other allowlists in
+# this project: every ignore requires human sign-off and is subject to review
+# at each release cycle.
+#
+# RATCHET: zizmorFindings metric in quality-baseline.json (direction: down)
+# starts advisory; current baseline is frozen at first green run; new findings
+# must be remediated or explicitly ignored here.
+
+# ── Global settings ──────────────────────────────────────────────────────────
+# Uncomment to pin to a specific minimum severity level.
+# min-severity: low       # low | medium | high | critical (default: low = all)
+
+# ── Per-rule ignores ─────────────────────────────────────────────────────────
+# zizmor ≥1.0 replaced the old top-level `ignores:` list with a `rules:` map
+# keyed by audit id. Per-rule config lives under `rules.<audit-id>.ignore`,
+# where each entry is `filename` or `filename:line` (line optional, column
+# further-optional). See: https://docs.zizmor.sh/configuration/
+#
+# Format:
+#   rules:
+#     <zizmor-audit-id>:          # e.g. "unpinned-uses", "template-injection"
+#       ignore:
+#         - <workflow-filename>            # ignore this audit across the file
+#         - <workflow-filename>:<line>     # or scope to a specific line
+#
+# Example (do not uncomment without real justification):
+#
+#   rules:
+#     unpinned-uses:
+#       # actions/checkout@v6 is pinned at the major-version tag intentionally:
+#       # GitHub-managed first-party action; SHA pinning buys little against a
+#       # GitHub-side compromise and adds significant maintenance burden.
+#       ignore:
+#         - ci.yml
+
+# Every entry below is an explicit, justified ignore (same stale-review
+# discipline as the other allowlists in this project). New ignores require a
+# per-rule entry with a justification comment.
+rules:
+  dangerous-triggers:
+    # deploy-vps.yml uses `on: workflow_run` (after "Publish to Docker Hub").
+    # zizmor flags workflow_run as "almost always used insecurely", but this one
+    # is guarded and not exploitable:
+    #   • The deploy job is gated on `github.event.workflow_run.conclusion ==
+    #     'success'` (deploy-vps.yml job `if:`, L15), so it only runs after a
+    #     successful, trusted upstream run — never on a forked/PR-triggered
+    #     failure.
+    #   • It does NOT checkout or execute untrusted code: the deploy runs over SSH
+    #     using repository secrets; there is no `actions/checkout` of an attacker
+    #     ref in the privileged context.
+    # Accepted risk, re-review at the next release cycle (added 2026-06-15).
+    ignore:
+      - deploy-vps.yml
+
+  cache-poisoning:
+    # zizmor's cache-poisoning audit flags `actions/setup-node` (cache: npm) and
+    # `actions/cache` steps that populate a cache which a later artifact-publishing
+    # job could consume — the attack is: a fork PR seeds a poisoned cache that a
+    # trusted publish run then restores and ships. None of the four entries below
+    # are exploitable in that way:
+    #
+    #   • electron-release.yml / npm-publish.yml — PUBLISH workflows that trigger
+    #     ONLY on trusted events: `push: tags v*` + `workflow_dispatch` (electron)
+    #     and `release: [released]` + `workflow_dispatch` + `workflow_call`
+    #     (npm). They NEVER run on a `pull_request` from a fork, so an untrusted
+    #     ref can never populate the npm/node_modules cache they restore. The
+    #     cache key is `hashFiles('package-lock.json')` / `runner.os-node-…`, a
+    #     first-party, lockfile-pinned key on trusted events.
+    #
+    #   • opencode-plugin-ci.yml / opencode-provider-ci.yml — CI-only workflows
+    #     (lint/test of the two opencode packages). They DO run on `pull_request`,
+    #     but (a) they publish NO artifacts — there is no downstream publish job
+    #     that restores their cache, and (b) GitHub Actions cache is branch-scoped:
+    #     a fork-PR run writes to a PR-isolated cache that base-branch / release
+    #     runs cannot read. The `cache: npm` here only speeds up `npm ci` within
+    #     the same ephemeral CI run.
+    #
+    # Accepted risk (first-party caching on trusted/isolated events), re-review at
+    # the next release cycle (added 2026-06-16).
+    ignore:
+      - electron-release.yml
+      - npm-publish.yml
+      - opencode-plugin-ci.yml
+      - opencode-provider-ci.yml

@omniroute/opencode-plugin/.gitignore

@@ -0,0 +1,4 @@
+node_modules
+dist
+*.log
+.DS_Store

@omniroute/opencode-plugin/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 OmniRoute contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

@omniroute/opencode-plugin/README.md

@@ -0,0 +1,296 @@
+# @omniroute/opencode-plugin
+
+> **Recommended way to use OmniRoute with OpenCode.** Pulls a live model catalog from `/v1/models` (including `-low`/`-medium`/`-high`/`-thinking` variants as first-class IDs), aggregates combos via `/api/combos` using a least-common-denominator capability/limit join, sanitizes Gemini tool schemas in flight, and supports multiple side-by-side OmniRoute instances out of the box.
+
+## Why this and not `@omniroute/opencode-provider`?
+
+`@omniroute/opencode-provider` is the legacy config-generator package — it writes a frozen `provider.omniroute` block into `opencode.json` with a **hardcoded list of 8 models** ([`OMNIROUTE_DEFAULT_OPENCODE_MODELS`](https://github.com/diegosouzapw/OmniRoute/blob/main/%40omniroute/opencode-provider/src/index.ts#L48-L56)). It works on the CLI but in the **OpenCode Desktop / Web** builds (Tauri / Electron) the runtime re-runs the model picker and the static block surfaces only a few of those — and they drift behind the live OmniRoute catalog.
+
+This plugin solves that by:
+
+- Fetching `/v1/models` and `/api/combos` **at OpenCode startup, in Node.js** — no CORS, no WebView restrictions
+- Emitting the provider block **dynamically** in the plugin's `config`/`provider` hook — so `opencode.json` only needs the plugin entry, not a static `provider.omniroute`
+- Re-fetching on a configurable TTL (default 5 min), so new models / combo changes in the OmniRoute UI appear without restarting OpenCode
+- Computing `limit.context` for combos as `min(member.context_length)` from the live catalog (no more `null` values that cause 4K-token truncation)
+- **Auto-pickup of `interleaved` capability** for thinking models (merged via PR #3138)
+
+**If you only have the legacy `opencode-provider` block in your `opencode.json`, replace it with a single plugin entry.** No other config changes required — the same `auth.json` API key works.
+
+## Install
+
+The plugin ships **pre-built inside the `omniroute` npm package** since v3.8.23.
+If you have OmniRoute installed, the plugin is already on disk:
+
+```sh
+# 1. One command — copy the plugin into OpenCode and update opencode.json
+omniroute setup opencode --auth
+
+# 2. Follow the interactive prompt to enter your OmniRoute API key
+# 3. Restart OpenCode — /models lists the full live catalog
+```
+
+The `--auth` flag runs `opencode auth login --provider omniroute` automatically.
+Use `--base-url` to point at a non-default OmniRoute address:
+
+```sh
+omniroute setup opencode --base-url https://or.example.com --auth
+```
+
+### What it does
+
+1. Locates the bundled plugin inside the omniroute installation
+2. Copies `dist/` + `package.json` to `~/.config/opencode/plugins/omniroute/`
+3. Writes/updates `opencode.json` with the plugin entry (idempotent, replaces legacy entries)
+4. (With `--auth`) runs `opencode auth login` so the API key is stored
+
+Re-run any time to update the plugin or change the base URL. Older entries for
+`@omniroute/opencode-provider` or the legacy `opencode-omniroute-auth` package are
+automatically cleaned up.
+
+### Manual install (without omniroute CLI)
+
+If you cannot run `omniroute setup opencode` (local dev, CI, air-gapped), reference
+the built artifact directly:
+
+```sh
+cd @omniroute/opencode-plugin && npm run build && npm pack
+# then extract into ~/.config/opencode/plugins/omniroute-opencode-plugin/
+```
+
+And add the entry to `opencode.json` manually (see Quick Start below).
+
+Peer dep: `@opencode-ai/plugin` (managed by your OpenCode install).
+
+## Quick start (single instance, manual)
+
+```jsonc
+// opencode.json
+{
+  "$schema": "https://opencode.ai/config.json",
+  "plugin": [
+    [
+      "./plugins/omniroute-opencode-plugin/dist/index.js",
+      {
+        "providerId": "omniroute",
+        "baseURL": "https://or.example.com",
+      },
+    ],
+  ],
+}
+```
+
+```sh
+opencode auth login --provider omniroute
+# prompts for the OmniRoute API key, writes to ~/.local/share/opencode/auth.json
+```
+
+> ⚠ Use the `--provider` flag explicitly. `opencode auth login omniroute` is parsed as a positional `url` argument by current OC releases (≤1.15.5) and fails with `fetch() URL is invalid`. Tracked upstream.
+
+Restart OpenCode. `/models` lists the full live catalog. Variants (`-low`, `-medium`, `-high`, `-thinking`) and combos appear as first-class IDs — OmniRoute is the source of truth, no client-side synthesis.
+
+## Multi-instance (prod + preprod side-by-side)
+
+> ⚠ OC ≤1.15.5 dedupes plugin loads by absolute module path. Two `plugin:` entries pointing at the same `dist/index.js` collapse into one (last-listed options win). Workaround: install the plugin twice into separate directories so each entry resolves to a distinct module file. v0.2.x will introduce an `instances: [...]` shape that registers N providers from a single load.
+
+### Dual-install workaround (works today on OC ≤1.15.5)
+
+Pack the plugin once, extract it twice into named directories, then point each `plugin:` entry at its own copy:
+
+```sh
+# 1. Build + pack the plugin (run from the plugin worktree)
+cd /path/to/OmniRoute/@omniroute/opencode-plugin
+npm run build
+npm pack
+# produces omniroute-opencode-plugin-0.1.0.tgz
+
+# 2. Extract one copy per OmniRoute endpoint
+mkdir -p ~/.config/opencode/plugins/omniroute-opencode-plugin-prod
+mkdir -p ~/.config/opencode/plugins/omniroute-opencode-plugin-preprod
+tar -xzf omniroute-opencode-plugin-0.1.0.tgz -C ~/.config/opencode/plugins/omniroute-opencode-plugin-prod    --strip-components=1
+tar -xzf omniroute-opencode-plugin-0.1.0.tgz -C ~/.config/opencode/plugins/omniroute-opencode-plugin-preprod --strip-components=1
+```
+
+Then in `~/.config/opencode/opencode.json` reference each directory by absolute path:
+
+```jsonc
+{
+  "$schema": "https://opencode.ai/config.json",
+  "plugin": [
+    [
+      "./plugins/omniroute-opencode-plugin-prod/dist/index.js",
+      {
+        "providerId": "omniroute",
+        "displayName": "OmniRoute",
+        "baseURL": "https://or.example.com",
+      },
+    ],
+    [
+      "./plugins/omniroute-opencode-plugin-preprod/dist/index.js",
+      {
+        "providerId": "omniroute-preprod",
+        "displayName": "OmniRoute Preprod",
+        "baseURL": "https://or-preprod.example.com",
+      },
+    ],
+  ],
+}
+```
+
+Paths are relative to `~/.config/opencode/`. Each entry now resolves to a distinct module file, so OC loads them as two separate plugin instances. Authenticate each:
+
+```sh
+opencode auth login --provider omniroute
+opencode auth login --provider omniroute-preprod
+```
+
+Each entry gets its own provider id, its own model picker entry, its own slot in `auth.json`, and its own TTL cache. Closures are isolated per plugin instance — no cross-talk.
+
+### After publish (`@omniroute/opencode-plugin` npm)
+
+Once the package is published, the dual-install becomes two `npm install --prefix` commands instead of `tar -xzf`:
+
+```sh
+mkdir -p ~/.config/opencode/plugins/omniroute-opencode-plugin-prod
+mkdir -p ~/.config/opencode/plugins/omniroute-opencode-plugin-preprod
+npm install --prefix ~/.config/opencode/plugins/omniroute-opencode-plugin-prod    @omniroute/opencode-plugin
+npm install --prefix ~/.config/opencode/plugins/omniroute-opencode-plugin-preprod @omniroute/opencode-plugin
+```
+
+`opencode.json` paths become `./plugins/omniroute-opencode-plugin-prod/node_modules/@omniroute/opencode-plugin/dist/index.js` (and the preprod equivalent).
+
+## Features
+
+| Feature                                     | What it does                                                                                                                                                                                                                                                                                                                                                                                                | Hook                         |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
+| Dynamic `/v1/models`                        | Pulls live catalog (455+ entries on prod) on each refresh, TTL-cached                                                                                                                                                                                                                                                                                                                                       | `provider.models`            |
+| Variants pass-through                       | `-low`/`-medium`/`-high`/`-thinking` ship as first-class IDs from OmniRoute (no client synthesis)                                                                                                                                                                                                                                                                                                           | `provider.models`            |
+| Combo LCD aggregation                       | Combos appear with intersected capabilities + min context/output across members                                                                                                                                                                                                                                                                                                                             | `provider.models` + `config` |
+| `combo/<slug>` namespace + `Combo: ` prefix | Combos surface under `combo/claude-primary` (not the upstream UUID) and the picker shows `Combo: claude-primary` so they stand apart from raw provider/model pairs                                                                                                                                                                                                                                          | both hooks                   |
+| Nice names + cost                           | `/api/pricing/models` display names AND `/api/pricing` per-million-token cost overlaid onto the live catalog                                                                                                                                                                                                                                                                                                | both hooks                   |
+| Canonical-twin dedup + alias-fallback       | `/v1/models` exposes the same upstream model under both short alias (`cc/claude-opus-4-7`) and canonical name (`claude/claude-opus-4-7`); the plugin drops the canonical twin when an alias twin exists (no duplicate rows in the picker) and reverse-maps canonical → alias to pick up enrichment for short aliases (`dg/nova-3 → Deepgram - Nova 3`) that `/api/pricing/models` only indexes by canonical | both hooks                   |
+| Compression pipeline tags                   | Combo names get tagged with their compression pipeline (e.g. `Combo: claude-primary [rtk🟡 → caveman🟠]`) when `features.compressionMetadata: true`. Intensity tokens render as a traffic-light emoji: 🟢 lite/minimal · 🟡 standard · 🟠 aggressive/full · 🔴 ultra                                                                                                                                        | both hooks                   |
+| Provider-tag prefix                         | Prepend short upstream-provider label to enriched names (e.g. `Claude - Claude Opus 4.7` vs `Kiro - Claude Opus 4.7`, `GHM - GPT 5`) so same-id models routed via different upstream connections group visibly in the picker (default-on, opt-out via `features.providerTag: false`)                                                                                                                        | both hooks                   |
+| Usable-only filter                          | Filter to providers with at least one healthy connection in `/api/providers` (opt-in via `features.usableOnly`)                                                                                                                                                                                                                                                                                             | both hooks                   |
+| Disk-cache fallback                         | Last-known-good catalog persisted to disk; hydrates on a cold start when `/v1/models` is unreachable (default-on, opt-out via `features.diskCache: false`)                                                                                                                                                                                                                                                  | `config`                     |
+| Bearer injection + suffix-spoof guard       | Adds `Authorization` on baseURL-matched requests only                                                                                                                                                                                                                                                                                                                                                       | `auth.loader.fetch`          |
+| Gemini schema sanitization                  | Strips `$schema`/`$ref`/`additionalProperties` for `gemini-*`/`google-vertex-gemini/*`                                                                                                                                                                                                                                                                                                                      | `auth.loader.fetch` wrap     |
+| Multi-instance                              | Each plugin entry binds to its own `providerId`; closures isolated                                                                                                                                                                                                                                                                                                                                          | factory                      |
+| Config-hook shim                            | OC ≤1.15.5 fallback: writes static catalog into `config.provider[id]` (config hook is the only one that fires in `serve` mode on these versions)                                                                                                                                                                                                                                                            | `config`                     |
+
+## Plugin options
+
+| Option          | Type     | Default                                    | Description                                                |
+| --------------- | -------- | ------------------------------------------ | ---------------------------------------------------------- |
+| `providerId`    | `string` | `"omniroute"`                              | OpenCode provider id; must be unique across plugin entries |
+| `displayName`   | `string` | `"OmniRoute"` or `OmniRoute (<id>)`        | Label in the OC UI                                         |
+| `modelCacheTtl` | `number` | `300000` (5 min)                           | `/v1/models` TTL in ms                                     |
+| `baseURL`       | `string` | resolved from `auth.json` after `/connect` | Override OmniRoute base URL                                |
+| `features`      | `object` | see below                                  | Feature toggles (all opt-in/out, defaults preserve v0.1.0) |
+
+### `features` block
+
+Every field is optional. Defaults mirror v0.1.0 behaviour so existing `opencode.json` files do not need to change.
+
+| Feature               | Type      | Default | What it does                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| --------------------- | --------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `combos`              | `boolean` | `true`  | Discover `/api/combos` and surface them as pseudo-models with LCD capabilities. Combos are keyed under the `combo/<slug>` namespace and labelled `Combo: <name>` in the model picker so they're distinguishable from raw provider/model pairs.                                                                                                                                                                                                                                                                                                                               |
+| `enrichment`          | `boolean` | `true`  | Pull display names from `/api/pricing/models` AND per-million-token pricing (`input`, `output`, `cached` → `cacheRead`, `cache_creation` → `cacheWrite`) from `/api/pricing`, then overlay both onto the live catalog (so the UI shows `Claude 4.7 Opus` with `cost.input: 5`, `cost.output: 25` instead of raw IDs and zeroed cost).                                                                                                                                                                                                                                        |
+| `compressionMetadata` | `boolean` | `false` | Pull `/api/context/combos` so combo names get tagged with their compression pipeline, e.g. `Combo: claude-primary [rtk🟡 → caveman🟠]`. Intensity tokens render as traffic-light emoji (🟢 lite/minimal · 🟡 standard · 🟠 aggressive/full · 🔴 ultra) so the picker advertises "how compressed" each combo is at a glance.                                                                                                                                                                                                                                                  |
+| `providerTag`         | `boolean` | `true`  | Prepend a short upstream-provider label to the enriched display name with `" - "` separator, so `cc/claude-opus-4-7 → Claude - Claude Opus 4.7` differs visibly from `kr/claude-opus-4-7 → Kiro - Claude Opus 4.7` in the OC TUI model picker. Label resolution: use `/api/pricing/models[<alias>].name` verbatim when ≤8 chars (e.g. `Claude`, `Kiro`, `Codex`, `Qwen`), otherwise fall back to `UPPER(alias)` (e.g. `GitHub Models` → `GHM`, `Gemini` → `GEMINI`). Idempotent. Combos intentionally skipped (the `Combo: ` prefix already conveys multi-upstream). |
+| `usableOnly`          | `boolean` | `false` | Read `/api/providers` and filter the catalog to providers that have at least one connection with `isActive: true` AND `testStatus: 'active'`. Subtract-filter semantics: providers unknown to BOTH the pricing-models catalog AND the connection table pass through (so synthetic prefixes like `agentrouter/*` survive). On fetch failure the filter is disabled for the refresh — never hides the whole catalog.                                                                                                                                                           |
+| `diskCache`           | `boolean` | `true`  | Persist the last successful `/v1/models` + `/api/combos` + enrichment + connections + compression snapshot to `${OPENCODE_DATA_DIR ?? ~/.local/share/opencode}/plugins/omniroute-<providerId>.json`. On a subsequent cold start where `/v1/models` throws (network down / IP whitelist drop / 5xx) the static block hydrates from the snapshot so OC's model picker survives offline. Soft-fail on read/write — never blocks publishing.                                                                                                                                     |
+| `geminiSanitization`  | `boolean` | `true`  | Strip `$schema`/`$ref`/`additionalProperties` from tool params when the model id matches `gemini`                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `mcpAutoEmit`         | `boolean` | `false` | Auto-write an `mcp.<providerId>` remote entry into the OC config pointing at `<baseURL>/api/mcp/stream` with the resolved Bearer token                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `mcpToken`            | `string`  | _unset_ | Optional separate Bearer for the auto-emitted MCP entry. Falls back to the provider's `apiKey` (from `auth.json`) when unset                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `fetchInterceptor`    | `boolean` | `true`  | Inject `Authorization: Bearer` + default `Content-Type` on every outbound request targeting `baseURL` (suffix-spoof guarded)                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+
+#### Example — enrichment + compression tags + MCP auto-emit
+
+```jsonc
+{
+  "plugin": [
+    [
+      "@omniroute/opencode-plugin",
+      {
+        "providerId": "omniroute",
+        "baseURL": "https://or.example.com",
+        "features": {
+          "combos": true,
+          "enrichment": true,
+          "compressionMetadata": true,
+          "mcpAutoEmit": true,
+        },
+      },
+    ],
+  ],
+}
+```
+
+With `mcpAutoEmit: true`, the plugin synthesises an `mcp.omniroute` entry equivalent to a manual:
+
+```jsonc
+"mcp": {
+  "omniroute": {
+    "type": "remote",
+    "url": "https://or.example.com/api/mcp/stream",
+    "enabled": true,
+    "headers": { "Authorization": "Bearer <apiKey-from-auth.json>" }
+  }
+}
+```
+
+If you want a narrower-scoped Bearer for MCP (different from the chat/inference key), set `features.mcpToken`. Operator overrides win: if you already set `mcp.omniroute` in `opencode.json`, the plugin will not overwrite it.
+
+#### Example — production-leaning defaults (clean picker, offline resilience)
+
+```jsonc
+{
+  "plugin": [
+    [
+      "@omniroute/opencode-plugin",
+      {
+        "providerId": "omniroute",
+        "baseURL": "https://or.example.com",
+        "features": {
+          "combos": true,
+          "enrichment": true,
+          "compressionMetadata": true,
+          "usableOnly": true,
+          "diskCache": true,
+        },
+      },
+    ],
+  ],
+}
+```
+
+- `usableOnly: true` drops models whose canonical provider has no healthy connection in your OmniRoute instance — your `/models` picker stays focused on what you can actually call.
+- `diskCache: true` (default) writes a snapshot to `${OPENCODE_DATA_DIR}/plugins/omniroute-<providerId>.json` on every healthy refresh. On a cold start where `/v1/models` is unreachable (laptop offline, IP whitelist drop), the snapshot hydrates the static block so OC still shows the catalog instead of a stub.
+- `compressionMetadata: true` annotates combo display names with their pipeline using traffic-light emoji for intensity (e.g. `Combo: claude-primary [rtk🟡 → caveman🟠]`) so the picker advertises which compression each combo applies and how heavy it is at a glance. Palette: 🟢 lite/minimal · 🟡 standard · 🟠 aggressive/full · 🔴 ultra. Unknown intensities fall through to raw text (`[rtk:custom-thing]`) so the plugin never hides a value OmniRoute knows but the plugin doesn't.
+- `providerTag: true` (default) prepends a short upstream-provider label so the picker shows `Claude - Claude Opus 4.7` for `cc/claude-opus-4-7`, `Kiro - Claude Opus 4.7` for `kr/claude-opus-4-7`, and `GHM - GPT 5` for `ghm/gpt-5` (slot.name `GitHub Models` > 8 chars → abbreviated). Critical when the same model id is sold through multiple upstream connections with different cost/auth/rate-limit profiles. Set to `false` to keep the pre-v3.8.3 unsuffixed format.
+
+## Comparison vs `@omniroute/opencode-provider`
+
+[`@omniroute/opencode-provider`](https://github.com/diegosouzapw/OmniRoute/tree/main/%40omniroute/opencode-provider) is the existing config-generator package — it writes a frozen `provider.<id>` block into `opencode.json` at build time. This plugin is the runtime integration.
+
+|                   | `@omniroute/opencode-plugin` (this) | `@omniroute/opencode-provider`    |
+| ----------------- | ----------------------------------- | --------------------------------- |
+| Type              | OC plugin                           | Config generator (CLI/build-time) |
+| Models            | Live from `/v1/models`              | Frozen at scaffold                |
+| Combos            | LCD-aggregated live                 | None                              |
+| Gemini sanitize   | Yes                                 | N/A                               |
+| OC UI integration | `/connect`, `/models`               | None                              |
+| Multi-instance    | Native                              | Manual                            |
+
+Both can coexist; pick the one that fits your environment.
+
+## Requirements
+
+- Node `>=22.22.3` (per `engines.node`); tested on Node 22 and 24.
+- OpenCode: verified end-to-end against `opencode@1.15.5` with `@opencode-ai/plugin@1.15.6`.
+- OC plugin peer (`@opencode-ai/plugin`) `>=1.14.49` for the full feature set (provider hook surfaces models in `/models`). On `<=1.14.48`, the plugin falls back to its `config` hook, writing a static catalog snapshot into `config.provider[id]` so models still appear.
+- The plugin uses the OC v1 plugin shape (`default: { id, server }`) — older OC releases that only walk named exports will reject it. Stay on OC ≥1.15.
+
+## License
+
+MIT. See [LICENSE](./LICENSE).

@omniroute/opencode-plugin/package.json

@@ -0,0 +1,73 @@
+{
+  "name": "@omniroute/opencode-plugin",
+  "version": "0.2.0",
+  "description": "OpenCode plugin for the OmniRoute AI Gateway. Drives dynamic model discovery, /connect auth flow, and multi-instance OmniRoute providers via the official @opencode-ai/plugin contract.",
+  "type": "module",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    },
+    "./runtime": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "tsup",
+    "clean": "rm -rf dist",
+    "test": "node --import tsx/esm --test tests/scaffold.test.ts tests/auth.test.ts tests/options-schema.test.ts tests/multi-instance.test.ts tests/fetch-interceptor.test.ts tests/provider.test.ts tests/gemini-sanitize.test.ts tests/combos.test.ts tests/config-shim.test.ts tests/features.test.ts tests/usable-combo.test.ts tests/disk-snapshot-perms.test.ts tests/fork-features.test.ts tests/auto-combo-context.test.ts tests/provider-id-routing.test.ts",
+    "prepublishOnly": "npm run clean && npm run build && npm test"
+  },
+  "keywords": [
+    "omniroute",
+    "opencode",
+    "opencode-plugin",
+    "ai-sdk",
+    "openai-compatible",
+    "provider",
+    "gemini",
+    "combos",
+    "mcp"
+  ],
+  "author": "OmniRoute contributors",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/diegosouzapw/OmniRoute.git",
+    "directory": "@omniroute/opencode-plugin"
+  },
+  "bugs": {
+    "url": "https://github.com/diegosouzapw/OmniRoute/issues"
+  },
+  "homepage": "https://github.com/diegosouzapw/OmniRoute/tree/main/%40omniroute/opencode-plugin#readme",
+  "engines": {
+    "node": ">=22.22.3"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "peerDependencies": {
+    "@opencode-ai/plugin": "*"
+  },
+  "dependencies": {
+    "zod": "^4.4.3"
+  },
+  "devDependencies": {
+    "@opencode-ai/plugin": "^1.15.6",
+    "@types/node": "^22.19.19",
+    "tsup": "^8.5.1",
+    "tsx": "^4.22.3",
+    "typescript": "^5.9.3"
+  },
+  "overrides": {
+    "esbuild": "^0.28.1"
+  }
+}

@omniroute/opencode-plugin/src/logger.ts

@@ -0,0 +1,74 @@
+/**
+ * Structured logger for the OmniRoute plugin.
+ *
+ * Levels: error < warn < info < debug
+ * Default: warn (matches current console.warn behavior)
+ * Set via features.logLevel in plugin options.
+ */
+
+export type LogLevel = "error" | "warn" | "info" | "debug";
+
+const LEVEL_ORDER: Record<LogLevel, number> = {
+  error: 0,
+  warn: 1,
+  info: 2,
+  debug: 3,
+};
+
+const TAG = "[omniroute-plugin]";
+
+function shouldLog(current: LogLevel, target: LogLevel): boolean {
+  return LEVEL_ORDER[current] >= LEVEL_ORDER[target];
+}
+
+let _level: LogLevel = "warn";
+
+export function setLogLevel(level: LogLevel): void {
+  _level = level;
+}
+
+export function getLogLevel(): LogLevel {
+  return _level;
+}
+
+function fmt(level: LogLevel, msg: string, tag?: string): string {
+  const prefix = tag ? `${TAG}${tag}` : TAG;
+  return `${prefix} [${level.toUpperCase()}] ${msg}`;
+}
+
+export const logger = {
+  error(msg: string, ...args: unknown[]): void {
+    if (shouldLog(_level, "error")) console.error(fmt("error", msg), ...args);
+  },
+  warn(msg: string, ...args: unknown[]): void {
+    if (shouldLog(_level, "warn")) console.warn(fmt("warn", msg), ...args);
+  },
+  info(msg: string, ...args: unknown[]): void {
+    if (shouldLog(_level, "info")) console.warn(fmt("info", msg), ...args);
+  },
+  debug(msg: string, ...args: unknown[]): void {
+    if (shouldLog(_level, "debug")) console.warn(fmt("debug", msg), ...args);
+  },
+  /** Always emit regardless of level (for critical init breadcrumbs). */
+  always(msg: string, ...args: unknown[]): void {
+    console.warn(TAG, msg, ...args);
+  },
+
+  // ── Tagged child loggers ──────────────────────────────────────────────
+  child(tag: string) {
+    return {
+      error: (msg: string, ...args: unknown[]) =>
+        shouldLog(_level, "error") &&
+        console.error(fmt("error", msg, tag), ...args),
+      warn: (msg: string, ...args: unknown[]) =>
+        shouldLog(_level, "warn") &&
+        console.warn(fmt("warn", msg, tag), ...args),
+      info: (msg: string, ...args: unknown[]) =>
+        shouldLog(_level, "info") &&
+        console.warn(fmt("info", msg, tag), ...args),
+      debug: (msg: string, ...args: unknown[]) =>
+        shouldLog(_level, "debug") &&
+        console.warn(fmt("debug", msg, tag), ...args),
+    };
+  },
+};

@omniroute/opencode-plugin/src/naming.ts

@@ -0,0 +1,301 @@
+/**
+ * Universal model naming template for the OmniRoute plugin.
+ *
+ * Naming pipeline:
+ *   [tag] <provider-label><separator><display-name><suffix>
+ *
+ *   [Free] <provider> - <name> · <budget>     ← free model
+ *   Auto: <variant> (<N>p)                     ← auto combo
+ *   Combo: <name>                              ← DB combo
+ *   <provider> - <name>                        ← regular model
+ */
+
+// ── Constants ────────────────────────────────────────────────────────────
+
+/** Separator between provider label and model display name. */
+export const PROVIDER_TAG_SEPARATOR = " - ";
+
+/** Threshold beyond which providerDisplayName is abbreviated. */
+const PROVIDER_LABEL_MAX_CHARS = 12;
+
+/** Aliases longer than this get title-case instead of UPPER. */
+const ALIAS_UPPER_MAX_CHARS = 5;
+
+// ── Auto Combo Types ─────────────────────────────────────────────────────
+
+export type AutoVariant =
+  | "coding"
+  | "fast"
+  | "cheap"
+  | "offline"
+  | "smart"
+  | "lkgp";
+
+export const AUTO_VARIANTS: AutoVariant[] = [
+  "coding",
+  "fast",
+  "cheap",
+  "offline",
+  "smart",
+  "lkgp",
+];
+
+export const AUTO_VARIANT_DESCRIPTIONS: Record<
+  AutoVariant | "default",
+  string
+> = {
+  default: "Best provider via scoring",
+  coding: "Quality-first for code tasks",
+  fast: "Latency-optimized routing",
+  cheap: "Cost-optimized routing",
+  offline: "Offline-friendly providers",
+  smart: "Quality-first with exploration",
+  lkgp: "Last-Known-Good-Provider routing",
+};
+
+// ── Free Model Types ─────────────────────────────────────────────────────
+
+export type FreeModelFreeType =
+  | "recurring-daily"
+  | "recurring-monthly"
+  | "recurring-credit"
+  | "one-time-initial"
+  | "keyless"
+  | "discontinued";
+
+// ── Provider Label ────────────────────────────────────────────────────────
+
+/**
+ * Title-case a long, lowercase-looking alias.
+ * `antigravity` → `Antigravity`
+ */
+function titleCaseAlias(alias: string): string {
+  if (alias.length === 0) return alias;
+  return alias.charAt(0).toUpperCase() + alias.slice(1).toLowerCase();
+}
+
+/**
+ * Pick the short label for an upstream provider.
+ *
+ * Rules:
+ *   1. Trim `providerDisplayName`. If ≤12 chars → use verbatim.
+ *   2. Alias ≤5 chars → UPPER(alias). Alias >5 → titleCase.
+ *   3. Neither → undefined.
+ */
+export function shortProviderLabel(
+  enrichment:
+    | { providerDisplayName?: string; providerAlias?: string }
+    | undefined,
+): string | undefined {
+  if (!enrichment) return undefined;
+  const raw =
+    typeof enrichment.providerDisplayName === "string"
+      ? enrichment.providerDisplayName.trim()
+      : "";
+  if (raw.length > 0 && raw.length <= PROVIDER_LABEL_MAX_CHARS) return raw;
+  const alias =
+    typeof enrichment.providerAlias === "string"
+      ? enrichment.providerAlias.trim()
+      : "";
+  if (alias.length > 0) {
+    return alias.length <= ALIAS_UPPER_MAX_CHARS
+      ? alias.toUpperCase()
+      : titleCaseAlias(alias);
+  }
+  // Long displayName with no alias to fall back on: keep the long label
+  // rather than dropping the provider prefix entirely.
+  return raw.length > 0 ? raw : undefined;
+}
+
+// ── Free Label ────────────────────────────────────────────────────────────
+
+/**
+ * Normalise display name so free-tier models get a consistent `[Free] ` prefix.
+ *
+ * "GPT-4.1 (Free)"          → "[Free] GPT-4.1"
+ * "DeepSeek V4 Flash Free"  → "[Free] DeepSeek V4 Flash"
+ * "Claude Opus 4.7"         → "Claude Opus 4.7"  (unchanged)
+ */
+export function normaliseFreeLabel(name: string): string {
+  // Bounded whitespace quantifiers ({0,8}/{1,8}) avoid the polynomial-ReDoS
+  // backtracking that unbounded \s* before an anchored \s*$ would allow on
+  // attacker-influenced display names. 8 covers any realistic label spacing.
+  const cleaned = name
+    .replace(/\s{0,8}\(free\)\s{0,8}$/i, "")
+    .replace(/[\s-]{1,8}free\s{0,8}$/i, "")
+    .trim();
+  const wasFree = cleaned.length < name.trim().length;
+  if (!wasFree) return name;
+  return `[Free] ${cleaned}`;
+}
+
+// ── Free Budget Formatting ────────────────────────────────────────────────
+
+function fmtTokens(n: number): string {
+  if (n >= 1e9) return (n / 1e9).toFixed(1).replace(/\.0$/, "") + "B";
+  if (n >= 1e6) return (n / 1e6).toFixed(1).replace(/\.0$/, "") + "M";
+  if (n >= 1e3) return (n / 1e3).toFixed(1).replace(/\.0$/, "") + "K";
+  return String(n);
+}
+
+/**
+ * Format a free model budget into a short human-readable suffix.
+ *
+ * recurring-daily   → "25M tokens/day"
+ * recurring-monthly → "25M tokens/month"
+ * recurring-credit  → "10M credits"
+ * one-time-initial  → "1M credits (one-time)"
+ * keyless           → "(keyless)"
+ * discontinued      → "(discontinued)"
+ */
+export function formatFreeBudget(params: {
+  freeType: FreeModelFreeType;
+  monthlyTokens?: number;
+  creditTokens?: number;
+}): string {
+  const { freeType, monthlyTokens = 0, creditTokens = 0 } = params;
+
+  switch (freeType) {
+    case "recurring-daily":
+      return `${fmtTokens(monthlyTokens)} tokens/day`;
+    case "recurring-monthly":
+      return `${fmtTokens(monthlyTokens)} tokens/month`;
+    case "recurring-credit":
+      return `${fmtTokens(creditTokens)} credits`;
+    case "one-time-initial":
+      return `${fmtTokens(creditTokens)} credits (one-time)`;
+    case "keyless":
+      return "(keyless)";
+    case "discontinued":
+      return "(discontinued)";
+    default:
+      return "";
+  }
+}
+
+// ── Auto Combo Naming ─────────────────────────────────────────────────────
+
+/**
+ * Format auto combo display name.
+ *
+ * "Auto: Coding (4p)"
+ * "Auto: Default (6p)"
+ * "Auto" (no candidate count when unknown)
+ */
+export function formatAutoComboName(
+  variant: AutoVariant | undefined,
+  candidateCount?: number,
+): string {
+  const label = variant
+    ? variant.charAt(0).toUpperCase() + variant.slice(1)
+    : "Default";
+  const count =
+    typeof candidateCount === "number" && candidateCount > 0
+      ? ` (${candidateCount}p)`
+      : "";
+  return `Auto: ${label}${count}`;
+}
+
+/**
+ * Build the model ID for an auto combo entry.
+ * "auto/coding", "auto/fast", "auto" (default).
+ */
+export function autoComboModelId(variant: AutoVariant | undefined): string {
+  return variant ? `auto/${variant}` : "auto";
+}
+
+// ── Universal Display Name Builder ────────────────────────────────────────
+
+export interface ModelDisplayNameParams {
+  /** Raw model ID (e.g. "cc/claude-sonnet-4-6"). */
+  rawId: string;
+  /** Enrichment display name (e.g. "Claude Sonnet 4.6"). */
+  enrichmentName?: string;
+  /** Provider tag enrichment. */
+  providerAlias?: string;
+  /** Human-readable upstream provider label. */
+  providerDisplayName?: string;
+  /** Whether model is free tier. */
+  isFree?: boolean;
+  /** Free model budget info. */
+  freeType?: FreeModelFreeType;
+  /** Monthly token budget (for recurring free models). */
+  monthlyTokens?: number;
+  /** Credit token budget (for credit-based free models). */
+  creditTokens?: number;
+  /** Whether this is a combo entry (skip provider tag). */
+  isCombo?: boolean;
+  /** Whether this is an auto combo entry. */
+  isAutoCombo?: boolean;
+  /** Auto combo variant. */
+  autoVariant?: AutoVariant;
+  /** Auto combo candidate count. */
+  autoCandidateCount?: number;
+}
+
+/**
+ * Build the final display name following the universal template.
+ *
+ * Priority:
+ *   1. Auto combo → "Auto: <variant> (<N>p)"
+ *   2. DB combo → "Combo: <name>"
+ *   3. Free + enrichment + provider tag → "[Free] <label> - <name> · <budget>"
+ *   4. Free + enrichment → "[Free] <name> · <budget>"
+ *   5. Free + raw → "[Free] <rawId> · <budget>"
+ *   6. Enrichment + provider tag → "<label> - <name>"
+ *   7. Enrichment only → "<name>"
+ *   8. Raw fallback → normaliseFreeLabel(rawId)
+ */
+export function buildModelDisplayName(params: ModelDisplayNameParams): string {
+  // Auto combos
+  if (params.isAutoCombo) {
+    return formatAutoComboName(params.autoVariant, params.autoCandidateCount);
+  }
+
+  // Determine base name — strip any existing free suffix first
+  const rawBase =
+    params.enrichmentName && params.enrichmentName.trim().length > 0
+      ? params.enrichmentName
+      : params.rawId;
+  const cleanedBase = rawBase
+    .replace(/\s*\(free\)\s*$/i, "")
+    .replace(/[\s-]+free\s*$/i, "")
+    .trim();
+  const wasFree = cleanedBase.length < rawBase.trim().length;
+  const isFree = !!params.isFree || wasFree;
+
+  let baseName = cleanedBase;
+
+  // Provider tag (skip for combos)
+  if (!params.isCombo) {
+    const label = shortProviderLabel({
+      providerDisplayName: params.providerDisplayName,
+      providerAlias: params.providerAlias,
+    });
+    if (label) {
+      const prefix = `${label}${PROVIDER_TAG_SEPARATOR}`;
+      if (!baseName.startsWith(prefix)) {
+        baseName = `${prefix}${baseName}`;
+      }
+    }
+  }
+
+  // Prepend [Free] if applicable (AFTER provider tag for correct ordering)
+  if (isFree) {
+    baseName = `[Free] ${baseName}`;
+  }
+
+  // Free budget suffix
+  if (isFree && params.freeType) {
+    const budget = formatFreeBudget({
+      freeType: params.freeType,
+      monthlyTokens: params.monthlyTokens,
+      creditTokens: params.creditTokens,
+    });
+    if (budget) {
+      baseName = `${baseName} · ${budget}`;
+    }
+  }
+
+  return baseName;
+}

@omniroute/opencode-plugin/tests/auth.test.ts

@@ -0,0 +1,147 @@
+/**
+ * T-02 auth-hook contract tests.
+ *
+ * Covers the `createOmniRouteAuthHook(opts)` factory and its loader behaviour
+ * against every Auth flavor (`api`, `oauth`, null, empty key). Validates the
+ * multi-instance fix: provider id flows from plugin options, not a module
+ * constant.
+ */
+
+import test from "node:test";
+import assert from "node:assert/strict";
+import { createOmniRouteAuthHook } from "../src/index.js";
+
+test("createOmniRouteAuthHook: default providerId is 'omniroute'", () => {
+  const hook = createOmniRouteAuthHook();
+  assert.equal(hook.provider, "opencode-omniroute");
+});
+
+test("createOmniRouteAuthHook: custom providerId binds to hook.provider (multi-instance)", () => {
+  const hook = createOmniRouteAuthHook({ providerId: "omniroute-preprod" });
+  assert.equal(hook.provider, "opencode-omniroute-preprod");
+});
+
+test("createOmniRouteAuthHook: methods[0] is type 'api' with label including displayName", () => {
+  const hook = createOmniRouteAuthHook();
+  assert.equal(Array.isArray(hook.methods), true);
+  assert.equal(hook.methods.length, 1);
+  const m = hook.methods[0];
+  assert.equal(m.type, "api");
+  assert.equal(m.label, "OmniRoute API Key");
+
+  const custom = createOmniRouteAuthHook({ providerId: "omniroute-preprod" });
+  assert.equal(custom.methods[0].label, "OmniRoute (opencode-omniroute-preprod) API Key");
+});
+
+test("createOmniRouteAuthHook: prompts[0] uses key='apiKey' per @opencode-ai/plugin contract", () => {
+  // NOTE: spec referenced `name: "apiKey"`; the official
+  // @opencode-ai/plugin@1.15.6 prompt shape uses `key` + `message` (no
+  // `name`/`label`/`mask` fields). Asserting against the real type contract.
+  const hook = createOmniRouteAuthHook();
+  const m = hook.methods[0];
+  assert.equal(m.type, "api");
+  // narrow: api method may carry prompts
+  const prompts = "prompts" in m ? m.prompts : undefined;
+  assert.ok(Array.isArray(prompts) && prompts.length === 1, "expected one prompt");
+  const p = prompts![0];
+  assert.equal(p.type, "text");
+  assert.equal((p as { key: string }).key, "apiKey");
+  assert.ok(
+    typeof (p as { message: string }).message === "string" &&
+      (p as { message: string }).message.includes("omniroute"),
+    "prompt message should mention provider id"
+  );
+});
+
+test("loader: valid api auth → {apiKey} when no baseURL option (T-04: fetch omitted)", async () => {
+  // T-04 changed the loader return shape: without a resolvable baseURL the
+  // interceptor cannot gate-keep requests, so the loader falls back to
+  // apiKey-only and the AI-SDK uses its default fetch. See fetch-interceptor
+  // tests for the wired-fetch branches.
+  const hook = createOmniRouteAuthHook();
+  assert.ok(hook.loader, "loader must be defined");
+  const result = await hook.loader!(
+    async () => ({ type: "api", key: "sk-test" }) as never,
+    {} as never
+  );
+  assert.deepEqual(result, { apiKey: "sk-test" });
+});
+
+test("loader: valid api auth → {apiKey, baseURL, fetch} when baseURL option set (T-04)", async () => {
+  const hook = createOmniRouteAuthHook({ baseURL: "https://or.example.com/v1" });
+  const result = await hook.loader!(
+    async () => ({ type: "api", key: "sk-x" }) as never,
+    {} as never
+  );
+  assert.equal((result as { apiKey: string }).apiKey, "sk-x");
+  assert.equal((result as { baseURL: string }).baseURL, "https://or.example.com/v1");
+  assert.equal(
+    typeof (result as { fetch?: unknown }).fetch,
+    "function",
+    "T-04: loader must wire fetch interceptor when baseURL resolves"
+  );
+});
+
+test("loader: features.fetchInterceptor=false AND geminiSanitization=false → no custom fetch (flags honored)", async () => {
+  // Regression: both fetch-layer flags were documented + schema-validated but
+  // silently ignored. Disabling both must fall back to the SDK default fetch.
+  const hook = createOmniRouteAuthHook({
+    baseURL: "https://or.example.com/v1",
+    features: { fetchInterceptor: false, geminiSanitization: false },
+  });
+  const result = await hook.loader!(
+    async () => ({ type: "api", key: "sk-x" }) as never,
+    {} as never
+  );
+  assert.deepEqual(result, { apiKey: "sk-x", baseURL: "https://or.example.com/v1" });
+  assert.equal(
+    (result as { fetch?: unknown }).fetch,
+    undefined,
+    "both flags off must omit the custom fetch"
+  );
+});
+
+test("loader: features.fetchInterceptor=false but geminiSanitization=true → fetch still wired (sanitizer only)", async () => {
+  const hook = createOmniRouteAuthHook({
+    baseURL: "https://or.example.com/v1",
+    features: { fetchInterceptor: false, geminiSanitization: true },
+  });
+  const result = await hook.loader!(
+    async () => ({ type: "api", key: "sk-x" }) as never,
+    {} as never
+  );
+  assert.equal(
+    typeof (result as { fetch?: unknown }).fetch,
+    "function",
+    "geminiSanitization alone must still provide a fetch wrapper"
+  );
+});
+
+test("loader: null/undefined auth → {} (no creds yet, OC surfaces /connect)", async () => {
+  const hook = createOmniRouteAuthHook();
+  const r1 = await hook.loader!(async () => null as never, {} as never);
+  assert.deepEqual(r1, {});
+  const r2 = await hook.loader!(async () => undefined as never, {} as never);
+  assert.deepEqual(r2, {});
+});
+
+test("loader: oauth-flavored auth → {} (wrong method type, ignored)", async () => {
+  const hook = createOmniRouteAuthHook();
+  const result = await hook.loader!(
+    async () =>
+      ({
+        type: "oauth",
+        refresh: "r",
+        access: "a",
+        expires: 0,
+      }) as never,
+    {} as never
+  );
+  assert.deepEqual(result, {});
+});
+
+test("loader: api auth with empty key → {} (empty creds rejected)", async () => {
+  const hook = createOmniRouteAuthHook();
+  const result = await hook.loader!(async () => ({ type: "api", key: "" }) as never, {} as never);
+  assert.deepEqual(result, {});
+});

@omniroute/opencode-plugin/tests/auto-combo-context.test.ts

@@ -0,0 +1,74 @@
+/**
+ * TDD regression — auto combos must never advertise `limit.context: 0`.
+ *
+ * opencode's overflow guard (packages/opencode/src/session/overflow.ts)
+ * short-circuits when `model.limit.context === 0`:
+ *
+ *   if (input.model.limit.context === 0) return false  // never overflow
+ *
+ * so a zero context silently DISABLES opencode's smart auto-compaction for
+ * auto combos. The session then grows unbounded until OmniRoute's
+ * server-side purifyHistory() destructively drops old messages — the
+ * "coding agent keeps forgetting things" bug.
+ *
+ * Fix under test: mapAutoComboToStaticEntry consumes the context_length /
+ * max_output_tokens now served by GET /api/combos/auto, and falls back to a
+ * safe positive default (128000 / 8192) for older servers that do not send
+ * the fields yet.
+ */
+import test from "node:test";
+import assert from "node:assert/strict";
+
+import { mapAutoComboToStaticEntry } from "../src/index.ts";
+import type { OmniRouteRawAutoCombo } from "../src/index.ts";
+
+test("uses server-provided context_length and max_output_tokens", () => {
+  const raw = {
+    id: "auto/coding",
+    name: "Auto Coding",
+    variant: "coding",
+    candidateCount: 5,
+    context_length: 1048576,
+    max_output_tokens: 65536,
+  } as OmniRouteRawAutoCombo;
+
+  const entry = mapAutoComboToStaticEntry(raw);
+  assert.equal(entry.limit?.context, 1048576);
+  assert.equal(entry.limit?.output, 65536);
+});
+
+test("falls back to a safe positive default when the server omits limits (old servers)", () => {
+  const raw = {
+    id: "auto",
+    name: "Auto",
+    candidateCount: 3,
+  } as OmniRouteRawAutoCombo;
+
+  const entry = mapAutoComboToStaticEntry(raw);
+  assert.ok(
+    typeof entry.limit?.context === "number" && entry.limit.context > 0,
+    `context must be a positive number (never 0 — zero disables opencode auto-compaction), got ${entry.limit?.context}`
+  );
+  assert.ok(
+    typeof entry.limit?.output === "number" && entry.limit.output > 0,
+    `output must be a positive number, got ${entry.limit?.output}`
+  );
+});
+
+test("ignores non-positive server values and keeps the safe fallback", () => {
+  const raw = {
+    id: "auto/fast",
+    name: "Auto Fast",
+    variant: "fast",
+    candidateCount: 2,
+    context_length: 0,
+    max_output_tokens: -1,
+  } as OmniRouteRawAutoCombo;
+
+  const entry = mapAutoComboToStaticEntry(raw);
+  assert.ok(
+    typeof entry.limit?.context === "number" && entry.limit.context > 0,
+    "zero/negative server values must not propagate"
+  );
+  assert.ok(typeof entry.limit?.output === "number" && entry.limit.output > 0);
+});

@omniroute/opencode-plugin/tests/combos.test.ts

@@ -0,0 +1,711 @@
+/**
+ * T-05 combo-discovery contract tests.
+ *
+ * Covers:
+ *   - `defaultOmniRouteCombosFetcher(baseURL, apiKey, timeoutMs?)`
+ *     — envelope tolerance (`{combos: [...]}` and bare array), non-2xx errors.
+ *   - `mapComboToModelV2(combo, members, providerId, baseURL)`
+ *     — LCD policy across capabilities, limits, modalities; defensive
+ *       posture on empty members; nice-name preference.
+ *   - `createOmniRouteProviderHook(opts, deps)` extension
+ *     — combos merged into the models map; collision resolution (combo
+ *       wins, warn-once); soft-fail when the combos fetcher throws;
+ *       combos cached + reused under the same TTL key as models.
+ *
+ * Mocking strategy mirrors `provider.test.ts`: both fetchers are
+ * dependency-injected at hook construction, no `fetch` monkey-patch.
+ */
+
+import test from "node:test";
+import assert from "node:assert/strict";
+import {
+  createOmniRouteProviderHook,
+  defaultOmniRouteCombosFetcher,
+  mapComboToModelV2,
+  type OmniRouteCombosFetcher,
+  type OmniRouteModelsFetcher,
+  type OmniRouteRawCombo,
+  type OmniRouteRawModelEntry,
+} from "../src/index.js";
+
+// ────────────────────────────────────────────────────────────────────────────
+// Fixtures
+// ────────────────────────────────────────────────────────────────────────────
+
+const MODEL_PRIMARY: OmniRouteRawModelEntry = {
+  id: "claude-primary",
+  capabilities: {
+    tool_calling: true,
+    reasoning: true,
+    vision: true,
+    thinking: true,
+    temperature: true,
+  },
+  context_length: 200_000,
+  max_output_tokens: 64_000,
+  max_input_tokens: 180_000,
+  input_modalities: ["text", "image"],
+  output_modalities: ["text"],
+};
+
+const MODEL_SECONDARY: OmniRouteRawModelEntry = {
+  id: "claude-secondary",
+  capabilities: {
+    tool_calling: true,
+    reasoning: false,
+    vision: true,
+    thinking: false,
+    temperature: true,
+  },
+  context_length: 100_000,
+  max_output_tokens: 32_000,
+  max_input_tokens: 96_000,
+  input_modalities: ["text", "image"],
+  output_modalities: ["text"],
+};
+
+const MODEL_NO_TOOLS: OmniRouteRawModelEntry = {
+  id: "gemini-3-flash",
+  capabilities: { tool_calling: false, reasoning: false, vision: false, thinking: false },
+  context_length: 1_000_000,
+  max_output_tokens: 8_192,
+  input_modalities: ["text"],
+  output_modalities: ["text"],
+};
+
+const COMBO_CLAUDE_TIER: OmniRouteRawCombo = {
+  id: "combo-claude-tier",
+  name: "Claude Tier",
+  strategy: "priority",
+  models: [
+    { id: "s1", kind: "model", model: "claude-primary", weight: 100 },
+    { id: "s2", kind: "model", model: "claude-secondary", weight: 80 },
+  ],
+};
+
+// ────────────────────────────────────────────────────────────────────────────
+// Helpers
+// ────────────────────────────────────────────────────────────────────────────
+
+function stubModelsFetcher(
+  payload: OmniRouteRawModelEntry[]
+): OmniRouteModelsFetcher & { callCount: () => number } {
+  let n = 0;
+  const f: OmniRouteModelsFetcher = async () => {
+    n++;
+    return payload;
+  };
+  return Object.assign(f, { callCount: () => n });
+}
+
+function stubCombosFetcher(
+  payload: OmniRouteRawCombo[]
+): OmniRouteCombosFetcher & { callCount: () => number; callsBy: () => Array<[string, string]> } {
+  let n = 0;
+  const calls: Array<[string, string]> = [];
+  const f: OmniRouteCombosFetcher = async (baseURL, apiKey) => {
+    n++;
+    calls.push([baseURL, apiKey]);
+    return payload;
+  };
+  return Object.assign(f, {
+    callCount: () => n,
+    callsBy: () => calls,
+  });
+}
+
+function failingCombosFetcher(
+  err = new Error("boom")
+): OmniRouteCombosFetcher & { callCount: () => number } {
+  let n = 0;
+  const f: OmniRouteCombosFetcher = async () => {
+    n++;
+    throw err;
+  };
+  return Object.assign(f, { callCount: () => n });
+}
+
+const apiAuth = (key: string): unknown => ({ type: "api", key });
+
+// Capture console.warn invocations for the duration of a callback, then
+// restore the original. Needed because the collision + soft-fail paths
+// emit warnings we want to assert on.
+async function withWarnCapture<T>(
+  fn: (warnings: Array<{ args: unknown[] }>) => Promise<T>
+): Promise<{ result: T; warnings: Array<{ args: unknown[] }> }> {
+  const original = console.warn;
+  const warnings: Array<{ args: unknown[] }> = [];
+  console.warn = (...args: unknown[]) => {
+    warnings.push({ args });
+  };
+  try {
+    const result = await fn(warnings);
+    return { result, warnings };
+  } finally {
+    console.warn = original;
+  }
+}
+
+// ────────────────────────────────────────────────────────────────────────────
+// defaultOmniRouteCombosFetcher — envelope tolerance + error surfacing
+// ────────────────────────────────────────────────────────────────────────────
+
+test("defaultOmniRouteCombosFetcher: parses {combos:[…]} envelope", async () => {
+  const originalFetch = globalThis.fetch;
+  globalThis.fetch = (async (input: unknown) => {
+    const url = typeof input === "string" ? input : (input as { url: string }).url;
+    assert.equal(url, "https://or.example.com/api/combos");
+    return new Response(
+      JSON.stringify({
+        combos: [
+          { id: "c1", name: "Combo One", strategy: "priority", models: [] },
+          { id: "c2", name: "Combo Two", strategy: "weighted", models: [] },
+        ],
+      }),
+      { status: 200, headers: { "Content-Type": "application/json" } }
+    );
+  }) as typeof fetch;
+  try {
+    const combos = await defaultOmniRouteCombosFetcher("https://or.example.com", "sk-test");
+    assert.equal(combos.length, 2);
+    assert.equal(combos[0].id, "c1");
+    assert.equal(combos[1].id, "c2");
+  } finally {
+    globalThis.fetch = originalFetch;
+  }
+});
+
+test("defaultOmniRouteCombosFetcher: parses bare array envelope", async () => {
+  const originalFetch = globalThis.fetch;
+  globalThis.fetch = (async () => {
+    return new Response(JSON.stringify([{ id: "c1" }, { id: "c2" }, { not_an_id: 42 }]), {
+      status: 200,
+    });
+  }) as typeof fetch;
+  try {
+    const combos = await defaultOmniRouteCombosFetcher("https://or.example.com/v1", "sk-test");
+    // Strip /v1 before /api/combos, AND filter out entries with no string id.
+    assert.equal(combos.length, 2);
+    assert.equal(combos[0].id, "c1");
+    assert.equal(combos[1].id, "c2");
+  } finally {
+    globalThis.fetch = originalFetch;
+  }
+});
+
+test("defaultOmniRouteCombosFetcher: strips trailing /v1 before /api/combos", async () => {
+  const originalFetch = globalThis.fetch;
+  let observedUrl = "";
+  globalThis.fetch = (async (input: unknown) => {
+    observedUrl = typeof input === "string" ? input : (input as { url: string }).url;
+    return new Response(JSON.stringify({ combos: [] }), { status: 200 });
+  }) as typeof fetch;
+  try {
+    await defaultOmniRouteCombosFetcher("https://or.example.com/v1/", "sk-test");
+    assert.equal(observedUrl, "https://or.example.com/api/combos");
+  } finally {
+    globalThis.fetch = originalFetch;
+  }
+});
+
+test("defaultOmniRouteCombosFetcher: throws on non-2xx with status code in message", async () => {
+  const originalFetch = globalThis.fetch;
+  globalThis.fetch = (async () => {
+    return new Response(JSON.stringify({ error: "Invalid token" }), {
+      status: 403,
+      statusText: "Forbidden",
+    });
+  }) as typeof fetch;
+  try {
+    await assert.rejects(
+      async () => {
+        await defaultOmniRouteCombosFetcher("https://or.example.com", "sk-bad");
+      },
+      (err: unknown) => {
+        const msg = err instanceof Error ? err.message : String(err);
+        assert.match(msg, /403/, "status code must appear in message");
+        assert.match(msg, /\/api\/combos/, "url must appear in message");
+        return true;
+      }
+    );
+  } finally {
+    globalThis.fetch = originalFetch;
+  }
+});
+
+test("defaultOmniRouteCombosFetcher: throws when apiKey missing", async () => {
+  await assert.rejects(
+    async () => defaultOmniRouteCombosFetcher("https://or.example.com", ""),
+    /apiKey required/
+  );
+});
+
+test("defaultOmniRouteCombosFetcher: throws when baseURL missing", async () => {
+  await assert.rejects(
+    async () => defaultOmniRouteCombosFetcher("", "sk-test"),
+    /baseURL required/
+  );
+});
+
+// ────────────────────────────────────────────────────────────────────────────
+// mapComboToModelV2 — LCD semantics
+// ────────────────────────────────────────────────────────────────────────────
+
+test("mapComboToModelV2: empty members → capabilities all false (defensive)", () => {
+  const m = mapComboToModelV2(
+    { id: "combo-empty", name: "Empty Combo" },
+    [],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m.id, "combo-empty");
+  assert.equal(m.name, "Empty Combo");
+  assert.equal(m.capabilities.temperature, false);
+  assert.equal(m.capabilities.reasoning, false);
+  assert.equal(m.capabilities.attachment, false);
+  assert.equal(m.capabilities.toolcall, false);
+  assert.equal(m.capabilities.input.text, false);
+  assert.equal(m.capabilities.output.text, false);
+  assert.equal(m.limit.context, 0);
+  assert.equal(m.limit.output, 0);
+  assert.equal(m.limit.input, undefined);
+  assert.deepEqual(m.cost, { input: 0, output: 0, cache: { read: 0, write: 0 } });
+});
+
+test("mapComboToModelV2: all members reasoning=true → combo reasoning=true", () => {
+  const m = mapComboToModelV2(
+    { id: "c", models: [] },
+    [
+      MODEL_PRIMARY,
+      {
+        ...MODEL_PRIMARY,
+        id: "p2",
+        capabilities: { ...MODEL_PRIMARY.capabilities, thinking: false, reasoning: true },
+      },
+    ],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m.capabilities.reasoning, true);
+});
+
+test("mapComboToModelV2: any member reasoning=false → combo reasoning=false", () => {
+  const m = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_NO_TOOLS], // gemini-3-flash has reasoning:false, thinking:false
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m.capabilities.reasoning, false);
+});
+
+test("mapComboToModelV2: limit.context is min of members'", () => {
+  const m = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_SECONDARY, MODEL_NO_TOOLS],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  // min(200_000, 100_000, 1_000_000) = 100_000
+  assert.equal(m.limit.context, 100_000);
+  // min(64_000, 32_000, 8_192) = 8_192
+  assert.equal(m.limit.output, 8_192);
+});
+
+test("mapComboToModelV2: limit.input only emitted when EVERY member declares one", () => {
+  const m1 = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_SECONDARY],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  // Both declare max_input_tokens → limit.input = min(180000, 96000)
+  assert.equal(m1.limit.input, 96_000);
+
+  const m2 = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_NO_TOOLS], // gemini-3-flash doesn't declare max_input_tokens
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m2.limit.input, undefined);
+});
+
+test("mapComboToModelV2: nice name preferred from combo.name", () => {
+  const m1 = mapComboToModelV2(
+    { id: "combo-x", name: "Pretty Name" },
+    [MODEL_PRIMARY],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m1.name, "Pretty Name");
+
+  // Falls back to id when name is absent or empty.
+  const m2 = mapComboToModelV2(
+    { id: "combo-y" },
+    [MODEL_PRIMARY],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m2.name, "combo-y");
+
+  const m3 = mapComboToModelV2(
+    { id: "combo-z", name: "   " },
+    [MODEL_PRIMARY],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m3.name, "combo-z");
+});
+
+test("mapComboToModelV2: attachment AND vision flag both honored across members", () => {
+  // MODEL_PRIMARY: vision=true; MODEL_SECONDARY: vision=true → combo attachment=true
+  const yes = mapComboToModelV2(
+    { id: "c1", models: [] },
+    [MODEL_PRIMARY, MODEL_SECONDARY],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(yes.capabilities.attachment, true);
+
+  // Add a member with no vision/attachment → AND collapses to false
+  const no = mapComboToModelV2(
+    { id: "c2", models: [] },
+    [MODEL_PRIMARY, MODEL_NO_TOOLS],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(no.capabilities.attachment, false);
+});
+
+test("mapComboToModelV2: modalities AND'd across members", () => {
+  const m = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_SECONDARY], // both have text+image
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m.capabilities.input.text, true);
+  assert.equal(m.capabilities.input.image, true);
+  assert.equal(m.capabilities.input.audio, false);
+
+  // Add a text-only member → image collapses to false.
+  const m2 = mapComboToModelV2(
+    { id: "c", models: [] },
+    [MODEL_PRIMARY, MODEL_NO_TOOLS],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m2.capabilities.input.text, true);
+  assert.equal(m2.capabilities.input.image, false);
+});
+
+test("mapComboToModelV2: api block matches providerId + baseURL", () => {
+  const m = mapComboToModelV2(
+    { id: "c" },
+    [MODEL_PRIMARY],
+    "omniroute-preprod",
+    "https://or-preprod.example.com/v1"
+  );
+  assert.equal(m.providerID, "omniroute-preprod");
+  assert.equal(m.api.id, "openai-compatible");
+  assert.equal(m.api.url, "https://or-preprod.example.com/v1");
+  assert.equal(m.api.npm, "@ai-sdk/openai-compatible");
+  assert.equal(m.status, "active");
+});
+
+test("mapComboToModelV2: explicit member temperature=false drops combo temperature=false", () => {
+  const tempFalse: OmniRouteRawModelEntry = {
+    id: "no-temp",
+    capabilities: { tool_calling: true, temperature: false },
+    context_length: 100_000,
+    max_output_tokens: 8_000,
+    input_modalities: ["text"],
+    output_modalities: ["text"],
+  };
+  const m = mapComboToModelV2(
+    { id: "c" },
+    [MODEL_PRIMARY, tempFalse],
+    "omniroute",
+    "https://or.example.com/v1"
+  );
+  assert.equal(m.capabilities.temperature, false);
+});
+
+// ────────────────────────────────────────────────────────────────────────────
+// createOmniRouteProviderHook — combos merge + collision + soft-fail + cache
+// ────────────────────────────────────────────────────────────────────────────
+
+test("models() returns combo entries merged into the map", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY, MODEL_SECONDARY, MODEL_NO_TOOLS]);
+  const combosFetcher = stubCombosFetcher([COMBO_CLAUDE_TIER]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+  const out = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+
+  // 3 raw models + 1 combo = 4 entries
+  assert.equal(Object.keys(out).length, 4);
+  assert.ok(out["omniroute/claude-primary"]);
+  assert.ok(out["omniroute/claude-secondary"]);
+  assert.ok(out["omniroute/gemini-3-flash"]);
+  assert.ok(out["omniroute/claude-tier"]);
+
+  const combo = out["omniroute/claude-tier"];
+  assert.equal(combo.name, "Claude Tier");
+  assert.equal(combo.providerID, "omniroute");
+  // LCD over claude-primary (200k, reasoning) + claude-secondary (100k, no reasoning)
+  assert.equal(combo.limit.context, 100_000);
+  assert.equal(combo.capabilities.reasoning, false);
+  assert.equal(combo.capabilities.toolcall, true);
+});
+
+test("models(): combo with unknown member ids degrades to all-false LCD posture", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY]); // catalog only has claude-primary
+  const combosFetcher = stubCombosFetcher([
+    {
+      id: "phantom",
+      name: "Phantom Combo",
+      models: [
+        { id: "s1", kind: "model", model: "does-not-exist-1", weight: 50 },
+        { id: "s2", kind: "model", model: "does-not-exist-2", weight: 50 },
+      ],
+    },
+  ]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+  const out = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  assert.ok(out["omniroute/phantom-combo"]);
+  // With zero resolvable members, LCD = all-false (defensive posture).
+  assert.equal(out["omniroute/phantom-combo"].capabilities.toolcall, false);
+  assert.equal(out["omniroute/phantom-combo"].capabilities.reasoning, false);
+  assert.equal(out["omniroute/phantom-combo"].limit.context, 0);
+});
+
+test("models(): hidden combos are excluded from the map", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY]);
+  const combosFetcher = stubCombosFetcher([
+    {
+      id: "visible",
+      name: "Visible",
+      models: [{ id: "s1", kind: "model", model: "claude-primary", weight: 100 }],
+    },
+    {
+      id: "hidden",
+      name: "Hidden",
+      isHidden: true,
+      models: [{ id: "s1", kind: "model", model: "claude-primary", weight: 100 }],
+    },
+  ]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+  const out = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  assert.ok(out["omniroute/visible"]);
+  assert.ok(!out["omniroute/hidden"], "hidden combo must be omitted");
+});
+
+test("models(): combo name exactly matches raw model id → raw deleted, raw deleted, no warn", async () => {
+  // Combo.name === raw model id triggers the dedup deletion. This mirrors
+  // the real OmniRoute payload where /v1/models pre-mirrors combos as
+  // no-slash raw entries whose ids match /api/combos friendly names.
+  const colliderCombo: OmniRouteRawCombo = {
+    id: "uuid-collider",
+    name: "claude-primary", // EXACT match to MODEL_PRIMARY.id
+    models: [{ id: "s1", kind: "model", model: "claude-secondary", weight: 100 }],
+  };
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY, MODEL_SECONDARY]);
+  const combosFetcher = stubCombosFetcher([colliderCombo]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+
+  const { result: out, warnings } = await withWarnCapture(async (_w) => {
+    return hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  });
+
+  // Raw model replaced by combo of the same key; combo now lives at the bare slug.
+  assert.ok(out["omniroute/claude-primary"], "combo surfaces under prefixed key");
+  assert.equal(out["omniroute/claude-primary"].name, "claude-primary");
+
+  // No collision warning fires — dedup makes keys disjoint.
+  const collisionWarns = warnings.filter((w) => {
+    const msg = w.args[0];
+    return typeof msg === "string" && msg.includes("collides");
+  });
+  assert.equal(collisionWarns.length, 0, "no collision warn after dedup");
+});
+
+test("models(): two combos with same slug → second gets disambiguator suffix", async () => {
+  // Both combos slug to `claude` — second must get `claude-<id-prefix>`.
+  const combos: OmniRouteRawCombo[] = [
+    {
+      id: "uuid-a",
+      name: "Claude",
+      models: [{ id: "s", kind: "model", model: "claude-primary", weight: 1 }],
+    },
+    {
+      id: "uuid-b",
+      name: "Claude",
+      models: [{ id: "s", kind: "model", model: "claude-secondary", weight: 1 }],
+    },
+  ];
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    {
+      fetcher: stubModelsFetcher([MODEL_PRIMARY, MODEL_SECONDARY]),
+      combosFetcher: stubCombosFetcher(combos),
+    }
+  );
+
+  const out = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  // First combo gets the bare slug; second gets disambiguated.
+  assert.ok(out["omniroute/claude"], "first combo at prefixed slug");
+  assert.ok(out["omniroute/claude-uuid"], "second combo disambiguated by id prefix");
+});
+
+test("models(): combos fetch fails → falls back to models-only, warn emitted, no throw", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY, MODEL_SECONDARY]);
+  const combosFetcher = failingCombosFetcher(new Error("ECONNRESET"));
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+
+  const { result: out, warnings } = await withWarnCapture(async () => {
+    return hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  });
+
+  // Catalog includes the models but NOT any combo entries.
+  assert.equal(Object.keys(out).length, 2);
+  assert.ok(out["omniroute/claude-primary"]);
+  assert.ok(out["omniroute/claude-secondary"]);
+
+  // Soft-fail warning surfaced.
+  const softFail = warnings.find((w) => {
+    const msg = w.args[0];
+    return typeof msg === "string" && msg.includes("combos fetch failed");
+  });
+  assert.ok(softFail, "soft-fail warning must be emitted on combos fetch error");
+  assert.equal(combosFetcher.callCount(), 1);
+});
+
+test("models(): combos cached + reused within TTL (one combo fetch per TTL window)", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY, MODEL_SECONDARY]);
+  const combosFetcher = stubCombosFetcher([COMBO_CLAUDE_TIER]);
+  let nowMs = 1_000_000;
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1", modelCacheTtl: 60_000 },
+    { fetcher: modelsFetcher, combosFetcher, now: () => nowMs }
+  );
+
+  await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  nowMs += 30_000; // half the TTL
+  const second = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  assert.equal(combosFetcher.callCount(), 1, "combos fetched only once within TTL");
+  assert.equal(modelsFetcher.callCount(), 1, "models fetched only once within TTL");
+  assert.ok(second["omniroute/claude-tier"]);
+});
+
+test("models(): combos refetched after TTL expiry (same key as models)", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY]);
+  const combosFetcher = stubCombosFetcher([COMBO_CLAUDE_TIER]);
+  let nowMs = 1_000_000;
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1", modelCacheTtl: 60_000 },
+    { fetcher: modelsFetcher, combosFetcher, now: () => nowMs }
+  );
+
+  await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  nowMs += 60_001;
+  await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  assert.equal(combosFetcher.callCount(), 2, "combos must refetch past TTL");
+  assert.equal(modelsFetcher.callCount(), 2, "models must refetch past TTL");
+});
+
+test("models(): combos fetcher receives the resolved baseURL + apiKey", async () => {
+  const modelsFetcher = stubModelsFetcher([MODEL_PRIMARY]);
+  const combosFetcher = stubCombosFetcher([COMBO_CLAUDE_TIER]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+  await hook.models!({} as never, { auth: apiAuth("sk-spy") as never });
+  assert.deepEqual(combosFetcher.callsBy()[0], ["https://or.example.com/v1", "sk-spy"]);
+});
+
+test("models(): nested combo-ref context is the min of nested + raw members", async () => {
+  // Top-level combo MASTER-LIGHT has 1 raw model (claude-primary, 200k)
+  // and 2 combo-refs: OldLLM (8k member) and KIRO (32k member). The OLD
+  // plugin would advertise 200k (only the raw model); the fix should
+  // make it advertise 8k (the bottleneck across the member graph).
+  const modelsFetcher = stubModelsFetcher([
+    MODEL_PRIMARY,
+    {
+      id: "oldllm-member-1",
+      context_length: 8_000,
+      max_output_tokens: 4_000,
+      capabilities: {
+        tool_calling: false,
+        reasoning: false,
+        vision: false,
+        thinking: false,
+        temperature: true,
+      },
+      input_modalities: ["text"],
+      output_modalities: ["text"],
+    },
+    {
+      id: "kiro-member-1",
+      context_length: 32_000,
+      max_output_tokens: 8_000,
+      capabilities: {
+        tool_calling: true,
+        reasoning: false,
+        vision: false,
+        thinking: false,
+        temperature: true,
+      },
+      input_modalities: ["text"],
+      output_modalities: ["text"],
+    },
+  ]);
+  const combosFetcher = stubCombosFetcher([
+    {
+      id: "oldllm",
+      name: "OldLLM",
+      models: [{ id: "s1", kind: "model", model: "oldllm-member-1", weight: 100 }],
+    },
+    {
+      id: "kiro",
+      name: "KIRO",
+      models: [{ id: "s1", kind: "model", model: "kiro-member-1", weight: 100 }],
+    },
+    {
+      id: "master-light",
+      name: "MASTER-LIGHT",
+      models: [
+        { id: "r1", kind: "model", model: "claude-primary", weight: 50 },
+        { id: "r2", kind: "combo-ref", comboName: "OldLLM", weight: 25 },
+        { id: "r3", kind: "combo-ref", comboName: "KIRO", weight: 25 },
+      ],
+    },
+  ]);
+  const hook = createOmniRouteProviderHook(
+    { baseURL: "https://or.example.com/v1" },
+    { fetcher: modelsFetcher, combosFetcher }
+  );
+  const out = await hook.models!({} as never, { auth: apiAuth("sk-z") as never });
+  const masterLight = out["omniroute/master-light"];
+  assert.ok(masterLight, "MASTER-LIGHT entry must exist");
+  assert.equal(
+    masterLight.limit.context,
+    8_000,
+    `expected 8_000 (OldLLM bottleneck), got ${masterLight.limit.context}`
+  );
+});

@omniroute/opencode-plugin/tests/disk-snapshot-perms.test.ts

@@ -0,0 +1,66 @@
+/**
+ * Regression test for the disk-snapshot file permissions (release/v3.8.2
+ * review finding C2). The snapshot embeds provider topology + connection
+ * records and lives alongside auth.json (0o600), so it must NOT be readable by
+ * group/other. Before the fix it was written with the default (typically
+ * world-readable 0o644) mode.
+ */
+
+import test from "node:test";
+import assert from "node:assert/strict";
+import fs from "node:fs";
+import os from "node:os";
+import path from "node:path";
+
+import {
+  defaultDiskSnapshotWriter,
+  diskSnapshotPath,
+  type OmniRouteFetchCacheEntry,
+} from "../src/index.js";
+
+function makeEntry(): Omit<OmniRouteFetchCacheEntry, "expiresAt"> {
+  return {
+    rawModels: [],
+    rawCombos: [],
+    rawEnrichment: new Map(),
+    rawCompressionCombos: [],
+    rawConnections: [],
+  };
+}
+
+test("defaultDiskSnapshotWriter writes an owner-only (no group/other) snapshot", async (t) => {
+  // POSIX-only assertion; Windows does not honor numeric file modes.
+  if (process.platform === "win32") {
+    t.skip("file mode semantics are POSIX-only");
+    return;
+  }
+
+  const tmp = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-disk-perms-"));
+  const prevDataDir = process.env.OPENCODE_DATA_DIR;
+  process.env.OPENCODE_DATA_DIR = tmp;
+
+  try {
+    await defaultDiskSnapshotWriter("perm-test", makeEntry());
+
+    const file = diskSnapshotPath("perm-test");
+    assert.ok(fs.existsSync(file), "snapshot file should be written");
+
+    const fileMode = fs.statSync(file).mode & 0o777;
+    assert.equal(
+      fileMode & 0o077,
+      0,
+      `snapshot must not be group/other accessible (got ${fileMode.toString(8)})`
+    );
+
+    const dirMode = fs.statSync(path.dirname(file)).mode & 0o777;
+    assert.equal(
+      dirMode & 0o077,
+      0,
+      `plugins dir must not be group/other accessible (got ${dirMode.toString(8)})`
+    );
+  } finally {
+    if (prevDataDir === undefined) delete process.env.OPENCODE_DATA_DIR;
+    else process.env.OPENCODE_DATA_DIR = prevDataDir;
+    fs.rmSync(tmp, { recursive: true, force: true });
+  }
+});

@omniroute/opencode-plugin/tests/fetch-interceptor.test.ts

@@ -0,0 +1,269 @@
+/**
+ * T-04 fetch-interceptor contract tests.
+ *
+ * Covers `createOmniRouteFetchInterceptor` (URL-prefix gating, header merge,
+ * Content-Type defaulting, input-shape polymorphism) plus the loader
+ * integration that wires it into the AuthHook return shape.
+ *
+ * Strategy: replace `globalThis.fetch` with a closure-based recorder for the
+ * duration of each test (saved-and-restored in try/finally — node:test has
+ * no built-in spy/restore lifecycle). The recorder captures `(input, init)`
+ * as observed by the wrapped global call so we can assert on what was
+ * forwarded after header injection.
+ */
+import test from "node:test";
+import assert from "node:assert/strict";
+import { createOmniRouteAuthHook, createOmniRouteFetchInterceptor } from "../src/index.js";
+
+type FetchCall = { input: Parameters<typeof fetch>[0]; init?: RequestInit };
+
+function installFetchRecorder(response: Response = new Response("ok")) {
+  const calls: FetchCall[] = [];
+  const original = globalThis.fetch;
+  globalThis.fetch = (async (input: any, init?: any) => {
+    calls.push({ input, init });
+    return response;
+  }) as typeof fetch;
+  const restore = () => {
+    globalThis.fetch = original;
+  };
+  return { calls, restore };
+}
+
+const BASE = "https://or.example.com/v1";
+const KEY = "sk-test-fetch";
+
+test("createOmniRouteFetchInterceptor: targets baseURL → Authorization header injected", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(`${BASE}/chat/completions`, {
+      method: "POST",
+      body: JSON.stringify({ x: 1 }),
+    });
+    assert.equal(calls.length, 1);
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: targets baseURL → Authorization OVERRIDES caller-supplied Bearer", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(`${BASE}/chat/completions`, {
+      method: "POST",
+      body: "{}",
+      headers: { Authorization: "Bearer attacker-key" },
+    });
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    // We own the apiKey for this provider — caller-supplied Bearer must lose.
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: targets baseURL + body → Content-Type defaults to application/json", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(`${BASE}/chat/completions`, {
+      method: "POST",
+      body: JSON.stringify({ m: "x" }),
+    });
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Content-Type"), "application/json");
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: caller-set Content-Type is NOT overwritten", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(`${BASE}/v2/whatever`, {
+      method: "POST",
+      body: "raw",
+      headers: { "Content-Type": "text/plain; charset=utf-8" },
+    });
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Content-Type"), "text/plain; charset=utf-8");
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: non-baseURL host → passthrough, no Authorization injected", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f("https://third-party.example.org/v1/chat", {
+      method: "POST",
+      body: "{}",
+      headers: { "X-Caller": "yes" },
+    });
+    const sent = calls[0]!;
+    // Init forwarded verbatim — no header injection.
+    const sentHeaders = new Headers((sent.init as RequestInit | undefined)?.headers);
+    assert.equal(sentHeaders.get("Authorization"), null, "MUST NOT leak apiKey");
+    assert.equal(sentHeaders.get("X-Caller"), "yes");
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: refuses suffix-spoof — `${base}-attacker.evil` does NOT match baseURL", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    // baseURL is `https://or.example.com/v1`. A spoofed
+    // `https://or.example.com/v1-attacker.evil/chat` shares the literal prefix
+    // but is NOT under our origin path — must be treated as passthrough.
+    await f("https://or.example.com/v1-attacker.evil/chat", {
+      method: "POST",
+      body: "{}",
+    });
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit | undefined)?.headers);
+    assert.equal(sentHeaders.get("Authorization"), null);
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: URL object input is handled", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(new URL(`${BASE}/models`), {});
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: Request input is handled (reads .url)", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    const req = new Request(`${BASE}/chat/completions`, {
+      method: "POST",
+      body: JSON.stringify({ a: 1 }),
+      headers: { "X-Caller": "preserved" },
+    });
+    await f(req);
+    const sent = calls[0]!;
+    // The interceptor forwards the original Request as `input` but layers our
+    // headers into the `init`. We assert against the init view since fetch()
+    // resolves headers from init first when both are present.
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+    assert.equal(
+      sentHeaders.get("X-Caller"),
+      "preserved",
+      "Request-attached headers must survive the merge"
+    );
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: trailing slash in baseURL is normalized", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({
+      apiKey: KEY,
+      baseURL: `${BASE}////`,
+    });
+    await f(`${BASE}/models`, {});
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+  } finally {
+    restore();
+  }
+});
+
+test("createOmniRouteFetchInterceptor: GET without body does NOT set Content-Type", async () => {
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const f = createOmniRouteFetchInterceptor({ apiKey: KEY, baseURL: BASE });
+    await f(`${BASE}/models`); // no init at all
+    const sent = calls[0]!;
+    const sentHeaders = new Headers((sent.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+    assert.equal(
+      sentHeaders.get("Content-Type"),
+      null,
+      "Content-Type should only default when a body exists"
+    );
+  } finally {
+    restore();
+  }
+});
+
+// ----------------------------------------------------------------------------
+// loader integration
+// ----------------------------------------------------------------------------
+
+test("loader: returns fetch fn when apiKey + baseURL both present (via opts)", async () => {
+  const hook = createOmniRouteAuthHook({ baseURL: BASE });
+  const result = await hook.loader!(async () => ({ type: "api", key: KEY }) as never, {} as never);
+  assert.equal((result as { apiKey: string }).apiKey, KEY);
+  assert.equal((result as { baseURL: string }).baseURL, BASE);
+  assert.equal(
+    typeof (result as { fetch?: unknown }).fetch,
+    "function",
+    "loader must wire fetch interceptor when baseURL resolves"
+  );
+});
+
+test("loader: returns fetch fn when baseURL is stashed on the auth credential", async () => {
+  // Some auth backends attach baseURL alongside the key (post-/connect flow).
+  // The loader should pick it up even when plugin opts.baseURL is unset.
+  const hook = createOmniRouteAuthHook();
+  const result = await hook.loader!(
+    async () => ({ type: "api", key: KEY, baseURL: BASE }) as never,
+    {} as never
+  );
+  assert.equal((result as { baseURL?: string }).baseURL, BASE);
+  assert.equal(typeof (result as { fetch?: unknown }).fetch, "function");
+});
+
+test("loader: omits fetch fn when baseURL missing (apiKey-only return)", async () => {
+  const hook = createOmniRouteAuthHook(); // no baseURL opt
+  const result = await hook.loader!(async () => ({ type: "api", key: KEY }) as never, {} as never);
+  // Interceptor needs a baseURL to gate-keep; without one, fall back to
+  // apiKey-only and let the SDK use its default fetch.
+  assert.deepEqual(result, { apiKey: KEY });
+});
+
+test("loader integration: wired interceptor actually injects Bearer when invoked", async () => {
+  // End-to-end: pull the fetch fn out of the loader return and exercise it,
+  // proving the wiring matches the standalone interceptor's contract.
+  const { calls, restore } = installFetchRecorder();
+  try {
+    const hook = createOmniRouteAuthHook({ baseURL: BASE });
+    const result = await hook.loader!(
+      async () => ({ type: "api", key: KEY }) as never,
+      {} as never
+    );
+    const wiredFetch = (result as { fetch: typeof fetch }).fetch;
+    await wiredFetch(`${BASE}/v1/models`, {});
+    assert.equal(calls.length, 1);
+    const sentHeaders = new Headers((calls[0]!.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), `Bearer ${KEY}`);
+  } finally {
+    restore();
+  }
+});

@omniroute/opencode-plugin/tests/fork-features.test.ts

@@ -0,0 +1,291 @@
+/**
+ * Tests for the 3 mrmm-fork features backported to @omniroute/opencode-plugin:
+ *
+ *   1. `normaliseFreeLabel` — free-tier model display names get a consistent
+ *      `[Free] ` prefix instead of trailing "(Free)" or ad-hoc "free" words.
+ *
+ *   2. `resolveApiBlock` — per-provider-prefix API format routing. Anthropic
+ *      prefixes (`cc/`, `claude/`, `anthropic/`, `kiro/`, `kr/`) get the
+ *      Anthropic SDK block; everything else gets OpenAI-compat.
+ *
+ *   3. `debugLog` — JSONL request/response capture, gated by
+ *      `features.debugLog` and togglable at runtime via
+ *      `debugLogEnabled/SetEnabled`.
+ */
+import { test } from "node:test";
+import assert from "node:assert/strict";
+
+import {
+  normaliseFreeLabel,
+  resolveApiBlock,
+  DEFAULT_ANTHROPIC_PREFIXES,
+  ensureV1Suffix,
+  debugLogEnabled,
+  debugLogSetEnabled,
+  debugLogClear,
+  debugLogRead,
+  debugLogAppend,
+  createDebugLoggingFetch,
+  DebugLogEntry,
+} from "../src/index.js";
+
+// ── 1. normaliseFreeLabel ────────────────────────────────────────────────────
+
+test("normaliseFreeLabel: '(Free)' suffix becomes [Free] prefix", () => {
+  assert.equal(normaliseFreeLabel("GPT-4.1 (Free)"), "[Free] GPT-4.1");
+});
+
+test("normaliseFreeLabel: trailing ' Free' word becomes [Free] prefix", () => {
+  assert.equal(
+    normaliseFreeLabel("DeepSeek V4 Flash Free"),
+    "[Free] DeepSeek V4 Flash"
+  );
+});
+
+test("normaliseFreeLabel: trailing '-free' (hyphen) becomes [Free] prefix", () => {
+  assert.equal(normaliseFreeLabel("Llama 4 Scout-free"), "[Free] Llama 4 Scout");
+});
+
+test("normaliseFreeLabel: case-insensitive (FREE, Free, free all match)", () => {
+  assert.equal(normaliseFreeLabel("Model A FREE"), "[Free] Model A");
+  assert.equal(normaliseFreeLabel("Model A free"), "[Free] Model A");
+  assert.equal(normaliseFreeLabel("Model A Free"), "[Free] Model A");
+});
+
+test("normaliseFreeLabel: names without 'free' pass through unchanged", () => {
+  assert.equal(normaliseFreeLabel("Claude 4.7 Opus"), "Claude 4.7 Opus");
+  assert.equal(normaliseFreeLabel("GPT-5"), "GPT-5");
+});
+
+test("normaliseFreeLabel: 'free' in the middle of a name is NOT rewritten", () => {
+  // Only trailing/standalone "free" markers count; embedded "freedom" stays
+  assert.equal(
+    normaliseFreeLabel("Freedom Model"),
+    "Freedom Model"
+  );
+});
+
+test("normaliseFreeLabel: empty / whitespace-only inputs are handled", () => {
+  // Empty input returns empty; pure whitespace input passes through (no Free marker)
+  assert.equal(normaliseFreeLabel(""), "");
+  assert.equal(normaliseFreeLabel("   "), "   ");
+});
+
+// ── 2. resolveApiBlock ───────────────────────────────────────────────────────
+
+test("resolveApiBlock: cc/* models get the Anthropic SDK block (no /v1)", () => {
+  const block = resolveApiBlock("cc/claude-opus-4-7", "https://api.example.com");
+  assert.equal(block.id, "anthropic");
+  assert.equal(block.npm, "@ai-sdk/anthropic");
+  assert.equal(block.url, "https://api.example.com"); // NO /v1 suffix
+});
+
+test("resolveApiBlock: claude/*, anthropic/*, kiro/*, kr/* all route to Anthropic", () => {
+  for (const id of [
+    "claude/claude-opus-4-7",
+    "anthropic/claude-sonnet-4",
+    "kiro/claude-sonnet-4-5",
+    "kr/claude-opus-4-6",
+  ]) {
+    const block = resolveApiBlock(id, "https://api.example.com");
+    assert.equal(block.id, "anthropic", `${id} should route to Anthropic`);
+    assert.equal(block.npm, "@ai-sdk/anthropic");
+  }
+});
+
+test("resolveApiBlock: non-Anthropic models get OpenAI-compat with /v1", () => {
+  const block = resolveApiBlock("gpt-4o", "https://api.example.com");
+  assert.equal(block.id, "openai-compatible");
+  assert.equal(block.npm, "@ai-sdk/openai-compatible");
+  assert.equal(block.url, "https://api.example.com/v1");
+});
+
+test("resolveApiBlock: user can override anthropicPrefixes to add custom prefixes", () => {
+  const block = resolveApiBlock("myproxy/claude-opus", "https://api.example.com", {
+    anthropicPrefixes: ["myproxy"],
+  });
+  assert.equal(block.id, "anthropic");
+  assert.equal(block.npm, "@ai-sdk/anthropic");
+});
+
+test("resolveApiBlock: empty anthropicPrefixes forces OpenAI-compat for everything", () => {
+  const block = resolveApiBlock("cc/claude-opus", "https://api.example.com", {
+    anthropicPrefixes: [],
+  });
+  assert.equal(block.id, "openai-compatible");
+});
+
+test("resolveApiBlock: baseURL that already ends in /v1 is not double-suffixed (OpenAI path)", () => {
+  const block = resolveApiBlock("gpt-4o", "https://api.example.com/v1");
+  assert.equal(block.url, "https://api.example.com/v1"); // idempotent
+});
+
+test("resolveApiBlock: model id without '/' uses the id as prefix", () => {
+  const block = resolveApiBlock("claude-opus-4-7", "https://api.example.com");
+  // The whole id is the prefix, which doesn't match "cc"/"claude" etc.
+  // So it falls through to OpenAI-compat.
+  assert.equal(block.id, "openai-compatible");
+});
+
+test("DEFAULT_ANTHROPIC_PREFIXES: contains the canonical Anthropic aliases", () => {
+  assert.deepEqual(DEFAULT_ANTHROPIC_PREFIXES, [
+    "cc",
+    "claude",
+    "anthropic",
+    "kiro",
+    "kr",
+  ]);
+});
+
+test("ensureV1Suffix: idempotent for URLs that already end in /v1", () => {
+  assert.equal(ensureV1Suffix("https://api.example.com/v1"), "https://api.example.com/v1");
+  assert.equal(
+    ensureV1Suffix("https://api.example.com/v1/"),
+    "https://api.example.com/v1" // trailing slash is stripped
+  );
+});
+
+test("ensureV1Suffix: appends /v1 when missing", () => {
+  assert.equal(ensureV1Suffix("https://api.example.com"), "https://api.example.com/v1");
+  assert.equal(ensureV1Suffix("https://api.example.com/"), "https://api.example.com/v1");
+});
+
+// ── 3. debugLog ──────────────────────────────────────────────────────────────
+
+test("debugLog: default state is disabled", () => {
+  debugLogClear("test-provider-disabled-default");
+  assert.equal(debugLogEnabled("test-provider-disabled-default"), false);
+});
+
+test("debugLogSetEnabled + debugLogEnabled: roundtrip", () => {
+  debugLogSetEnabled("test-provider-toggle", true);
+  assert.equal(debugLogEnabled("test-provider-toggle"), true);
+  debugLogSetEnabled("test-provider-toggle", false);
+  assert.equal(debugLogEnabled("test-provider-toggle"), false);
+});
+
+test("debugLogAppend + debugLogRead: roundtrip preserves entry shape", () => {
+  const providerId = "test-provider-readroundtrip";
+  debugLogClear(providerId);
+  const entry: DebugLogEntry = {
+    reqId: "req-1",
+    providerId,
+    ts: 1700000000000,
+    url: "https://api.example.com/v1/chat",
+    method: "POST",
+    reqHeaders: { "content-type": "application/json" },
+    reqBody: { model: "gpt-4o", messages: [] },
+    resStatus: 200,
+    resHeaders: { "content-type": "application/json" },
+    resBody: { choices: [] },
+    durationMs: 42,
+  };
+  debugLogAppend(entry);
+  const read = debugLogRead(providerId, 10);
+  assert.equal(read.length, 1);
+  assert.deepEqual(read[0], entry);
+});
+
+test("createDebugLoggingFetch: passes through when disabled", async () => {
+  const providerId = "test-provider-passthrough";
+  debugLogClear(providerId);
+  debugLogSetEnabled(providerId, false);
+  const calls: unknown[] = [];
+  const inner: typeof fetch = async (input) => {
+    calls.push(input);
+    return new Response("ok", { status: 200 });
+  };
+  const wrapped = createDebugLoggingFetch(inner, providerId, false);
+  const res = await wrapped("https://api.example.com/v1/chat");
+  assert.equal(res.status, 200);
+  assert.equal(calls.length, 1);
+  // No log entry should be written when disabled
+  assert.equal(debugLogRead(providerId).length, 0);
+});
+
+test("createDebugLoggingFetch: captures request/response when enabled", async () => {
+  const providerId = "test-provider-captures";
+  debugLogClear(providerId);
+  const inner: typeof fetch = async () =>
+    new Response(JSON.stringify({ ok: true }), {
+      status: 200,
+      headers: { "content-type": "application/json" },
+    });
+  const wrapped = createDebugLoggingFetch(inner, providerId, true);
+  const res = await wrapped("https://api.example.com/v1/chat", {
+    method: "POST",
+    headers: { "content-type": "application/json" },
+    body: JSON.stringify({ model: "gpt-4o" }),
+  });
+  assert.equal(res.status, 200);
+  const entries = debugLogRead(providerId);
+  assert.equal(entries.length, 1);
+  assert.equal(entries[0].method, "POST");
+  assert.equal(entries[0].resStatus, 200);
+  assert.equal(entries[0].url, "https://api.example.com/v1/chat");
+  assert.deepEqual(entries[0].reqBody, { model: "gpt-4o" });
+});
+
+test("createDebugLoggingFetch: records error without crashing the wrapped fetch", async () => {
+  const providerId = "test-provider-error";
+  debugLogClear(providerId);
+  const inner: typeof fetch = async () => {
+    throw new Error("network down");
+  };
+  const wrapped = createDebugLoggingFetch(inner, providerId, true);
+  await assert.rejects(wrapped("https://api.example.com/v1/chat"), /network down/);
+  const entries = debugLogRead(providerId);
+  assert.equal(entries.length, 1);
+  assert.equal(entries[0].resStatus, null);
+  assert.equal(entries[0].error, "network down");
+});
+
+// ── Regression tests for the 3 HIGH-priority bot review fixes ───────────────
+
+test("createDebugLoggingFetch: URL instance input is captured (not 'undefined')", async () => {
+  const providerId = "test-provider-url-input";
+  debugLogClear(providerId);
+  const inner: typeof fetch = async () =>
+    new Response("ok", { status: 200 });
+  const wrapped = createDebugLoggingFetch(inner, providerId, true);
+  await wrapped(new URL("https://api.example.com/v1/chat"));
+  const entries = debugLogRead(providerId);
+  assert.equal(entries.length, 1);
+  assert.equal(entries[0].url, "https://api.example.com/v1/chat");
+  assert.notEqual(entries[0].url, undefined);
+});
+
+test("createDebugLoggingFetch: Request object input captures URL and headers", async () => {
+  const providerId = "test-provider-request-input";
+  debugLogClear(providerId);
+  const inner: typeof fetch = async () =>
+    new Response("ok", { status: 200 });
+  const wrapped = createDebugLoggingFetch(inner, providerId, true);
+  const req = new Request("https://api.example.com/v1/chat", {
+    method: "POST",
+    headers: { "x-test": "yes" },
+  });
+  await wrapped(req);
+  const entries = debugLogRead(providerId);
+  assert.equal(entries.length, 1);
+  assert.equal(entries[0].url, "https://api.example.com/v1/chat");
+  assert.equal(entries[0].reqHeaders["x-test"], "yes");
+});
+
+test("createDebugLoggingFetch: SSE response is NOT buffered (resBody is the stream marker)", async () => {
+  const providerId = "test-provider-sse";
+  debugLogClear(providerId);
+  const inner: typeof fetch = async () =>
+    new Response("data: hello\n\n", {
+      status: 200,
+      headers: { "content-type": "text/event-stream" },
+    });
+  const wrapped = createDebugLoggingFetch(inner, providerId, true);
+  const res = await wrapped("https://api.example.com/v1/stream");
+  // The response body must remain readable downstream
+  const txt = await res.text();
+  assert.equal(txt, "data: hello\n\n");
+  const entries = debugLogRead(providerId);
+  assert.equal(entries.length, 1);
+  assert.equal(entries[0].resBody, "[stream]", "SSE responses must not be buffered");
+});

@omniroute/opencode-plugin/tests/gemini-sanitize.test.ts

@@ -0,0 +1,410 @@
+/**
+ * T-06 Gemini tool-schema sanitisation contract tests.
+ *
+ * Three layers under test:
+ *   1. `sanitizeGeminiToolSchemas` — pure function; key stripping + clone
+ *      semantics on chat-completion + Responses-API shapes.
+ *   2. `shouldSanitizeForGemini` — model-string detection (liberal).
+ *   3. `createGeminiSanitizingFetch` — wrapper composition; URL gating,
+ *      body-shape polymorphism, streaming-body bypass, fail-open behaviour,
+ *      composition with the T-04 Bearer interceptor.
+ *
+ * Strategy: same posture as fetch-interceptor.test.ts — install a
+ * closure-based fetch recorder; assert on the `(input, init)` observed by
+ * the inner fetch after the sanitising wrapper has had its say.
+ */
+import test from "node:test";
+import assert from "node:assert/strict";
+import {
+  __resetGeminiStreamingWarning,
+  createGeminiSanitizingFetch,
+  createOmniRouteFetchInterceptor,
+  sanitizeGeminiToolSchemas,
+  shouldSanitizeForGemini,
+} from "../src/index.js";
+
+// ────────────────────────────────────────────────────────────────────────────
+// Helpers
+// ────────────────────────────────────────────────────────────────────────────
+
+type FetchCall = { input: Parameters<typeof fetch>[0]; init?: RequestInit };
+
+function recorder(response: Response = new Response("ok")): {
+  fn: typeof fetch;
+  calls: FetchCall[];
+} {
+  const calls: FetchCall[] = [];
+  const fn = (async (input: any, init?: any) => {
+    calls.push({ input, init });
+    return response;
+  }) as typeof fetch;
+  return { fn, calls };
+}
+
+function bodyAsRecord(init: RequestInit | undefined): Record<string, unknown> {
+  const b = init?.body;
+  if (typeof b !== "string") {
+    throw new Error(`expected string body, got ${typeof b}`);
+  }
+  return JSON.parse(b) as Record<string, unknown>;
+}
+
+// Sample tool payloads — small enough to inline, big enough to cover
+// chat-completion + Responses-API + nested properties.
+
+function chatCompletionsWithDollarSchema(): Record<string, unknown> {
+  return {
+    model: "gemini-2.5-pro",
+    tools: [
+      {
+        type: "function",
+        function: {
+          name: "search",
+          parameters: {
+            $schema: "http://json-schema.org/draft-07/schema#",
+            type: "object",
+            additionalProperties: false,
+            properties: {
+              q: { type: "string" },
+            },
+            required: ["q"],
+          },
+        },
+      },
+    ],
+  };
+}
+
+function responsesApiWithRef(): Record<string, unknown> {
+  return {
+    model: "gemini-2.5-flash",
+    tools: [
+      {
+        type: "function",
+        name: "lookup",
+        input_schema: {
+          type: "object",
+          $ref: "#/definitions/Lookup",
+          properties: {
+            id: { type: "string", ref: "Id" },
+          },
+        },
+      },
+    ],
+  };
+}
+
+function nestedPropertiesPayload(): Record<string, unknown> {
+  return {
+    model: "gemini-pro",
+    tools: [
+      {
+        type: "function",
+        function: {
+          name: "deep",
+          parameters: {
+            type: "object",
+            properties: {
+              outer: {
+                type: "object",
+                $schema: "http://json-schema.org/draft-07/schema#",
+                properties: {
+                  inner: {
+                    type: "object",
+                    additionalProperties: true,
+                    $ref: "#/inner",
+                    properties: {
+                      leaf: { type: "string" },
+                    },
+                  },
+                },
+              },
+            },
+          },
+        },
+      },
+    ],
+  };
+}
+
+// ────────────────────────────────────────────────────────────────────────────
+// sanitizeGeminiToolSchemas — pure function
+// ────────────────────────────────────────────────────────────────────────────
+
+test("sanitizeGeminiToolSchemas: strips $schema from top-level", () => {
+  const input = {
+    model: "gemini-2.5-pro",
+    $schema: "http://json-schema.org/draft-07/schema#",
+    tools: [],
+  };
+  const out = sanitizeGeminiToolSchemas(input) as Record<string, unknown>;
+  assert.equal(out.$schema, undefined);
+  assert.equal(out.model, "gemini-2.5-pro");
+});
+
+test("sanitizeGeminiToolSchemas: strips $ref + additionalProperties from tools[].function.parameters", () => {
+  const input = chatCompletionsWithDollarSchema();
+  const out = sanitizeGeminiToolSchemas(input) as Record<string, unknown>;
+  const params = (out.tools as Array<{ function: { parameters: Record<string, unknown> } }>)[0]!
+    .function.parameters;
+  assert.equal(params.$schema, undefined);
+  assert.equal(params.additionalProperties, undefined);
+  // Untouched keys survive.
+  assert.equal(params.type, "object");
+  assert.deepEqual(params.required, ["q"]);
+});
+
+test("sanitizeGeminiToolSchemas: strips nested $schema from properties.x.properties.y", () => {
+  const input = nestedPropertiesPayload();
+  const out = sanitizeGeminiToolSchemas(input) as Record<string, unknown>;
+  const params = (out.tools as Array<{ function: { parameters: Record<string, unknown> } }>)[0]!
+    .function.parameters;
+  const outer = (params.properties as Record<string, Record<string, unknown>>).outer!;
+  const inner = (outer.properties as Record<string, Record<string, unknown>>).inner!;
+  assert.equal(outer.$schema, undefined);
+  assert.equal(inner.$ref, undefined);
+  assert.equal(inner.additionalProperties, undefined);
+  // Leaf still intact.
+  assert.deepEqual(inner.properties, { leaf: { type: "string" } });
+});
+
+test("sanitizeGeminiToolSchemas: handles Responses-API tools[].input_schema shape", () => {
+  const input = responsesApiWithRef();
+  const out = sanitizeGeminiToolSchemas(input) as Record<string, unknown>;
+  const inputSchema = (out.tools as Array<{ input_schema: Record<string, unknown> }>)[0]!
+    .input_schema;
+  assert.equal(inputSchema.$ref, undefined);
+  // Nested `ref` (lowercase) also stripped.
+  const props = inputSchema.properties as Record<string, Record<string, unknown>>;
+  assert.equal(props.id!.ref, undefined);
+  assert.equal(props.id!.type, "string");
+});
+
+test("sanitizeGeminiToolSchemas: leaves payload without tools untouched", () => {
+  const input = { model: "gemini-2.5-pro", messages: [{ role: "user", content: "hi" }] };
+  const out = sanitizeGeminiToolSchemas(input) as Record<string, unknown>;
+  assert.deepEqual(out, input);
+});
+
+test("sanitizeGeminiToolSchemas: does not mutate input (returned object is distinct)", () => {
+  const input = chatCompletionsWithDollarSchema();
+  const beforeJson = JSON.stringify(input);
+  const out = sanitizeGeminiToolSchemas(input);
+  // Input bit-identical to its pre-sanitise serialisation.
+  assert.equal(JSON.stringify(input), beforeJson);
+  // Output is a different reference.
+  assert.notEqual(out, input);
+});
+
+// ────────────────────────────────────────────────────────────────────────────
+// shouldSanitizeForGemini — detection
+// ────────────────────────────────────────────────────────────────────────────
+
+test("shouldSanitizeForGemini: gemini-2.5-pro → true", () => {
+  assert.equal(shouldSanitizeForGemini({ model: "gemini-2.5-pro" }), true);
+});
+
+test("shouldSanitizeForGemini: models/gemini-pro → true", () => {
+  assert.equal(shouldSanitizeForGemini({ model: "models/gemini-pro" }), true);
+});
+
+test("shouldSanitizeForGemini: google-vertex/gemini-1.5-flash → true", () => {
+  assert.equal(shouldSanitizeForGemini({ model: "google-vertex/gemini-1.5-flash" }), true);
+});
+
+test("shouldSanitizeForGemini: gemini/gemini-2.5-pro → true", () => {
+  assert.equal(shouldSanitizeForGemini({ model: "gemini/gemini-2.5-pro" }), true);
+});
+
+test("shouldSanitizeForGemini: claude-sonnet-4 → false", () => {
+  assert.equal(shouldSanitizeForGemini({ model: "claude-sonnet-4" }), false);
+});
+
+test("shouldSanitizeForGemini: payload.model missing → false", () => {
+  assert.equal(shouldSanitizeForGemini({ messages: [] }), false);
+});
+
+test("shouldSanitizeForGemini: payload is null → false", () => {
+  assert.equal(shouldSanitizeForGemini(null), false);
+});
+
+test("shouldSanitizeForGemini: payload.model is non-string → false", () => {
+  assert.equal(shouldSanitizeForGemini({ model: 42 }), false);
+});
+
+// ────────────────────────────────────────────────────────────────────────────
+// createGeminiSanitizingFetch — wrapper
+// ────────────────────────────────────────────────────────────────────────────
+
+const URL_CHAT = "https://or.example.com/v1/chat/completions";
+const URL_RESPONSES = "https://or.example.com/v1/responses";
+const URL_MODELS = "https://or.example.com/v1/models";
+
+test("createGeminiSanitizingFetch: gemini model + chat/completions → tool schemas stripped before forward", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  await wrapped(URL_CHAT, {
+    method: "POST",
+    body: JSON.stringify(chatCompletionsWithDollarSchema()),
+  });
+  assert.equal(rec.calls.length, 1);
+  const forwarded = bodyAsRecord(rec.calls[0]!.init);
+  const params = (
+    forwarded.tools as Array<{ function: { parameters: Record<string, unknown> } }>
+  )[0]!.function.parameters;
+  assert.equal(params.$schema, undefined);
+  assert.equal(params.additionalProperties, undefined);
+});
+
+test("createGeminiSanitizingFetch: non-gemini model + chat/completions → body passed through unchanged", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  const originalBody = JSON.stringify({
+    model: "claude-sonnet-4",
+    tools: [
+      {
+        type: "function",
+        function: {
+          name: "x",
+          parameters: { $schema: "keep-me", type: "object" },
+        },
+      },
+    ],
+  });
+  await wrapped(URL_CHAT, { method: "POST", body: originalBody });
+  // Identity check on body — wrapper must NOT mutate non-Gemini payloads.
+  assert.equal(rec.calls[0]!.init!.body, originalBody);
+});
+
+test("createGeminiSanitizingFetch: gemini model + /v1/models (non-completion endpoint) → body passed through unchanged", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  // GET /v1/models has no body in production; assert that even if a caller
+  // attached a Gemini-shaped body to a non-completion URL, the wrapper
+  // doesn't touch it.
+  const body = JSON.stringify(chatCompletionsWithDollarSchema());
+  await wrapped(URL_MODELS, { method: "POST", body });
+  assert.equal(rec.calls[0]!.init!.body, body);
+});
+
+test("createGeminiSanitizingFetch: gemini model + /responses endpoint → input_schema stripped", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  await wrapped(URL_RESPONSES, {
+    method: "POST",
+    body: JSON.stringify(responsesApiWithRef()),
+  });
+  const forwarded = bodyAsRecord(rec.calls[0]!.init);
+  const schema = (forwarded.tools as Array<{ input_schema: Record<string, unknown> }>)[0]!
+    .input_schema;
+  assert.equal(schema.$ref, undefined);
+});
+
+test("createGeminiSanitizingFetch: gemini model + Request input with body → tool schemas stripped", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  const req = new Request(URL_CHAT, {
+    method: "POST",
+    body: JSON.stringify(chatCompletionsWithDollarSchema()),
+    headers: { "Content-Type": "application/json" },
+  });
+  await wrapped(req);
+  const forwarded = bodyAsRecord(rec.calls[0]!.init);
+  const params = (
+    forwarded.tools as Array<{ function: { parameters: Record<string, unknown> } }>
+  )[0]!.function.parameters;
+  assert.equal(params.$schema, undefined);
+});
+
+test("createGeminiSanitizingFetch: gemini model + ReadableStream body → skipped + warn emitted once", async () => {
+  __resetGeminiStreamingWarning();
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+
+  // Capture console.warn for the duration of this test.
+  const warnings: string[] = [];
+  const originalWarn = console.warn;
+  console.warn = (...args: unknown[]) => {
+    warnings.push(args.map(String).join(" "));
+  };
+
+  try {
+    const stream1 = new ReadableStream({
+      start(controller) {
+        controller.enqueue(new TextEncoder().encode("{}"));
+        controller.close();
+      },
+    });
+    const stream2 = new ReadableStream({
+      start(controller) {
+        controller.enqueue(new TextEncoder().encode("{}"));
+        controller.close();
+      },
+    });
+    // Two streaming calls — only one warn expected.
+    await wrapped(URL_CHAT, { method: "POST", body: stream1 });
+    await wrapped(URL_CHAT, { method: "POST", body: stream2 });
+  } finally {
+    console.warn = originalWarn;
+  }
+
+  // Both calls forwarded to inner fetch with their streams intact.
+  assert.equal(rec.calls.length, 2);
+  // ONE warning total — one-shot latch held.
+  assert.equal(warnings.length, 1);
+  assert.match(warnings[0]!, /streaming Request body, skipping schema strip/);
+});
+
+test("createGeminiSanitizingFetch: invalid JSON body → pass through, no throw", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  // Garbage body must not crash the wrapper.
+  await wrapped(URL_CHAT, { method: "POST", body: "this is not json{{" });
+  assert.equal(rec.calls.length, 1);
+  assert.equal(rec.calls[0]!.init!.body, "this is not json{{");
+});
+
+test("createGeminiSanitizingFetch: empty body → pass through unchanged", async () => {
+  const rec = recorder();
+  const wrapped = createGeminiSanitizingFetch(rec.fn);
+  await wrapped(URL_CHAT, { method: "POST" });
+  assert.equal(rec.calls.length, 1);
+});
+
+test("createGeminiSanitizingFetch: composes correctly with createOmniRouteFetchInterceptor (Bearer + sanitization)", async () => {
+  // Save and replace globalThis.fetch — the Bearer interceptor calls global
+  // fetch when the URL targets its baseURL.
+  const originalFetch = globalThis.fetch;
+  const observed: FetchCall[] = [];
+  globalThis.fetch = (async (input: any, init?: any) => {
+    observed.push({ input, init });
+    return new Response("ok");
+  }) as typeof fetch;
+
+  try {
+    const composed = createGeminiSanitizingFetch(
+      createOmniRouteFetchInterceptor({
+        apiKey: "sk-test",
+        baseURL: "https://or.example.com/v1",
+      })
+    );
+    await composed(URL_CHAT, {
+      method: "POST",
+      body: JSON.stringify(chatCompletionsWithDollarSchema()),
+    });
+
+    assert.equal(observed.length, 1);
+    // Bearer injected (header concern).
+    const sentHeaders = new Headers((observed[0]!.init as RequestInit).headers);
+    assert.equal(sentHeaders.get("Authorization"), "Bearer sk-test");
+    // Schema sanitised (body concern).
+    const forwarded = bodyAsRecord(observed[0]!.init);
+    const params = (
+      forwarded.tools as Array<{ function: { parameters: Record<string, unknown> } }>
+    )[0]!.function.parameters;
+    assert.equal(params.$schema, undefined);
+    assert.equal(params.additionalProperties, undefined);
+  } finally {
+    globalThis.fetch = originalFetch;
+  }
+});

@omniroute/opencode-plugin/tests/multi-instance.test.ts

@@ -0,0 +1,136 @@
+/**
+ * T-08 multi-instance smoke.
+ *
+ * Validates that two `OmniRoutePlugin(input, opts)` invocations with
+ * different `providerId` values coexist without sharing mutable state.
+ * This is the contract that lets opencode.json declare prod + preprod
+ * side by side:
+ *
+ *   "plugin": [
+ *     ["@omniroute/opencode-plugin", {"providerId": "omniroute-prod",    "baseURL": "https://or.example/v1"}],
+ *     ["@omniroute/opencode-plugin", {"providerId": "omniroute-preprod", "baseURL": "https://or-preprod.example/v1"}]
+ *   ]
+ *
+ * Assertions:
+ *   - Each invocation returns its own hooks object (no identity reuse).
+ *   - Each `auth` hook carries its own `provider` matching opts.providerId.
+ *   - Each `auth.methods` array is its own array (not the same reference).
+ *   - Calling the factory twice with IDENTICAL opts still yields two
+ *     independent objects (no instance reuse / no shared closure cache).
+ *   - Mutating one instance's auth hook does NOT bleed into the other.
+ *   - Each instance's loader closure captures its OWN baseURL — no
+ *     last-write-wins module-scope state.
+ */
+
+import test from "node:test";
+import assert from "node:assert/strict";
+import { OmniRoutePlugin } from "../src/index.js";
+
+const fakeInput = {} as Parameters<typeof OmniRoutePlugin>[0];
+
+test("multi-instance: two plugin invocations bind to their own providerId", async () => {
+  const a = await OmniRoutePlugin(fakeInput, {
+    providerId: "omniroute-prod",
+    baseURL: "https://a.example/v1",
+  });
+  const b = await OmniRoutePlugin(fakeInput, {
+    providerId: "omniroute-preprod",
+    baseURL: "https://b.example/v1",
+  });
+
+  assert.equal(a.auth?.provider, "opencode-omniroute-prod");
+  assert.equal(b.auth?.provider, "opencode-omniroute-preprod");
+});
+
+test("multi-instance: hook objects + nested arrays are independent references", async () => {
+  const a = await OmniRoutePlugin(fakeInput, {
+    providerId: "alpha",
+    baseURL: "https://a.example/v1",
+  });
+  const b = await OmniRoutePlugin(fakeInput, {
+    providerId: "bravo",
+    baseURL: "https://b.example/v1",
+  });
+
+  assert.notEqual(a, b, "top-level hooks objects must not be the same reference");
+  assert.notEqual(a.auth, b.auth, "auth hooks must not be the same reference");
+  assert.notEqual(
+    a.auth?.methods,
+    b.auth?.methods,
+    "methods arrays must not be the same reference"
+  );
+});
+
+test("multi-instance: identical opts twice still yield independent objects", async () => {
+  const opts = { providerId: "twin", baseURL: "https://twin.example/v1" };
+  const first = await OmniRoutePlugin(fakeInput, { ...opts });
+  const second = await OmniRoutePlugin(fakeInput, { ...opts });
+
+  assert.notEqual(first, second);
+  assert.notEqual(first.auth, second.auth);
+  assert.notEqual(first.auth?.methods, second.auth?.methods);
+  // Same provider id is fine — what matters is no shared mutable state.
+  assert.equal(first.auth?.provider, "opencode-twin");
+  assert.equal(second.auth?.provider, "opencode-twin");
+});
+
+test("multi-instance: mutating instance A's auth.methods does not affect instance B", async () => {
+  const a = await OmniRoutePlugin(fakeInput, {
+    providerId: "iso-a",
+    baseURL: "https://a.example/v1",
+  });
+  const b = await OmniRoutePlugin(fakeInput, {
+    providerId: "iso-b",
+    baseURL: "https://b.example/v1",
+  });
+
+  const beforeLen = b.auth?.methods?.length ?? 0;
+  // Mutate a's methods array — extend it; b's must be untouched.
+  // We don't know the concrete method shape so push a sentinel cast.
+  a.auth?.methods?.push({ type: "api", label: "sentinel" } as never);
+  assert.equal(b.auth?.methods?.length, beforeLen, "instance B leaked from instance A mutation");
+});
+
+test("multi-instance: loader closures see their own opts (not last-write-wins)", async () => {
+  // Each plugin's loader builds its loader payload from the providerId/baseURL
+  // captured at invocation time. If the factory accidentally shared a closure
+  // (e.g. a module-scope let that the last invocation overwrites), both
+  // loaders would emit the same baseURL. Verify they don't.
+  const a = await OmniRoutePlugin(fakeInput, {
+    providerId: "omniroute-prod",
+    baseURL: "https://prod.example/v1",
+  });
+  const b = await OmniRoutePlugin(fakeInput, {
+    providerId: "omniroute-preprod",
+    baseURL: "https://preprod.example/v1",
+  });
+
+  assert.ok(a.auth?.loader, "instance A must have a loader");
+  assert.ok(b.auth?.loader, "instance B must have a loader");
+
+  const getAuthA = async () => ({ type: "api", key: "sk-prod" }) as never;
+  const getAuthB = async () => ({ type: "api", key: "sk-preprod" }) as never;
+
+  const rA = (await a.auth!.loader!(getAuthA, {} as never)) as Record<string, unknown>;
+  const rB = (await b.auth!.loader!(getAuthB, {} as never)) as Record<string, unknown>;
+
+  assert.equal(rA.apiKey, "sk-prod");
+  assert.equal(rA.baseURL, "https://prod.example/v1");
+  assert.equal(rB.apiKey, "sk-preprod");
+  assert.equal(rB.baseURL, "https://preprod.example/v1");
+});
+
+test("multi-instance: invalid opts on one instance does not poison the other", async () => {
+  // Sequencing: bad opts → good opts. The bad call must throw cleanly; the
+  // good call must still produce a working hooks object. Confirms no
+  // half-built module-level state survives a failed parse.
+  await assert.rejects(
+    () => OmniRoutePlugin(fakeInput, { providerId: "bad id!" } as never),
+    /providerId/
+  );
+  const ok = await OmniRoutePlugin(fakeInput, {
+    providerId: "recovered",
+    baseURL: "https://ok.example/v1",
+  });
+  assert.equal(ok.auth?.provider, "opencode-recovered");
+});