Repository navigation
fix(docs): validate aggregate provider counts on main - #16809
Merged
Merged
Conversation
Port the #16762 provider-count gate onto main. The live catalog here is 358 providers, so published claims and the stale-claim fixture follow that total.
Prettier realigned two markdown tables in the provider-count port. Update only those English source hashes so the i18n drift gate stays green.
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
diegosouzapw
added a commit
that referenced
this pull request
Oct 19, 2026
Brings main's 4 post-v3.8.51 commits (#16835, #16782, #16809, #16536) into the release ancestry so PR #15083 stops being CONFLICTING and runs CI again. Tree kept identical to the release tip (da38fc4): every main-only change is already on release in a newer form — evaluateComplexityRun() in validate-release-green.mjs, the USE_VPS_BUILD_RUNNER gate in ci.yml and nightly-release-green.yml, ONNXRUNTIME_NODE_INSTALL=skip in npm-ci-retry, the 375-provider counts (main says 358), and the four unit tests whose release versions are supersets of main's. The three main-only changelog.d fragments are dropped on purpose: the reconciler credits those commits from history.
Merged
arashashrafii
pushed a commit
to arashashrafii/OmniRoute
that referenced
this pull request
Oct 24, 2026
…nce#16809) Companion of cheaper-inference#16762 (merge-gates §8). That gate landed on `release/v3.8.52`, where the catalog total is **372**. This PR ports the same validator onto `main`, where `docs/reference/PROVIDER_REFERENCE.md` still records **358**. It does not copy 372 onto main. What changed: - `makeProviderCountValidator` in `scripts/check/check-docs-counts-sync.mjs`, required on `README.md`, `AGENTS.md`, and `llm.txt`, and optional on the secondary docs and skill surfaces. - Aggregate claims the checker flagged now say 358. The versioned snapshot “351 registered providers in OmniRoute v3.8.0” and the chat-model registry denominator stay exempt. - Strict `llm.txt` mirrors (`docs/i18n/*/llm.txt`) get the same `352-provider` → `358-provider` token so `check:docs-sync` stays green. - Other locale mirrors were not retranslated. `.i18n-state.json` records the new English source hashes only. Locale hashes stay on the previous source, so `i18n:check` keeps those as non-blocking stale warnings. - Skill surfaces covered by the new check move 327 → 358: `src/shared/constants/agentSkills.ts`, `skills/README.md`, `skills/omni-auth/SKILL.md`, `skills/omni-providers/SKILL.md`. Prettier also realigned existing tables in `docs/architecture/REPOSITORY_MAP.md` and `docs/frameworks/AGENTBRIDGE.md`. - The regression fixture uses `**349** LLM providers` because 358 is the live total on this branch. Checked locally on this branch: provider-count unit test 10/10, `check-docs-counts-sync` exit 0 with no strict drift, `i18n:check` PASS, `check:docs-sync` PASS. Already at `origin/main` (`fd95f823`). CI was still queued at merge time. Local gates on this branch passed. (cherry picked from commit f295b2e)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion of #16762 (merge-gates §8). That gate landed on
release/v3.8.52, where the catalog total is 372. This PR ports the same validator ontomain, wheredocs/reference/PROVIDER_REFERENCE.mdstill records 358. It does not copy 372 onto main.What changed:
makeProviderCountValidatorinscripts/check/check-docs-counts-sync.mjs, required onREADME.md,AGENTS.md, andllm.txt, and optional on the secondary docs and skill surfaces.llm.txtmirrors (docs/i18n/*/llm.txt) get the same352-provider→358-providertoken socheck:docs-syncstays green..i18n-state.jsonrecords the new English source hashes only. Locale hashes stay on the previous source, soi18n:checkkeeps those as non-blocking stale warnings.src/shared/constants/agentSkills.ts,skills/README.md,skills/omni-auth/SKILL.md,skills/omni-providers/SKILL.md. Prettier also realigned existing tables indocs/architecture/REPOSITORY_MAP.mdanddocs/frameworks/AGENTBRIDGE.md.**349** LLM providersbecause 358 is the live total on this branch.Checked locally on this branch: provider-count unit test 10/10,
check-docs-counts-syncexit 0 with no strict drift,i18n:checkPASS,check:docs-syncPASS.Leave this PR open. Do not squash it into
mainfrom the release train.