[maheswari-pinneti]

Summary

• Describe the user-facing or operational change.

Related Issues

• Closes #
• Related to #

Validation

Choose the change type and focused loop from the
Contribution Golden Path. The full unit suite,
Vitest, the 60% coverage gate, and the production build all run in CI on this PR (#8329):

• Change type: provider / routing / UI / i18n / CLI / DB / build-deploy / other
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR
• SonarQube is temporarily opt-in while the private project has no quota; it is not a PR gate.

Tests Added Or Updated

• List every changed or added automated test file.
• If no production code changed, state that here.

Coverage Notes

• If this PR changes src/, open-sse/, electron/, or bin/, explain which tests cover the change.
• If coverage moved down in any touched file, explain why and what follow-up task will recover it.

Reviewer Notes

• Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about.

[maheswari-pinneti]

Hi, PR #13347 (docs: sync provider count to 358) is currently showing “Action required — workflow is awaiting approval from a maintainer.”

Could you please approve the Quality Gates workflow so the CI checks can run?

Thank you!

[diegosouzapw]

You had the right number — 358 is indeed the live count. It landed on the tip via a parallel
maintainer sweep (#13216) a little before this PR could be merged, so README/AGENTS.md/llm.txt
already carry 358 everywhere today. Closing as already covered — good catch though, the count
genuinely needed the bump.

Triage note: this is the review recommendation — the close itself happens only after the maintainer's per-PR sign-off (and, where a superseding PR is named, after it has landed). Nothing is being closed by this comment.