fix(doctor): recognize vertex provider config

[tianma-if]

What does this PR do?

Fixes hermes doctor diagnostics for the Vertex provider. Doctor now recognizes provider IDs from the model/provider catalog in addition to API-key auth providers, so model.provider: vertex is not reported as unknown.

It also allows Vertex's recommended google/gemini-* model IDs through the vendor-slug check, matching the Vertex setup flow and runtime path.

Related Issue

Fixes #56906

Type of Change

• Bug fix
• Tests
• New feature
• Documentation
• Refactor

Changes

• Extends doctor provider validation with hermes_cli.models._KNOWN_PROVIDER_NAMES.
• Treats catalog-known provider IDs as valid even when resolve_provider_full() has no catalog object for them.
• Adds vertex to the vendor-slug-accepting provider policy.
• Adds a regression case for provider: vertex with default: google/gemini-3-flash-preview.

How to Test

• .venv/bin/python -m pytest tests/hermes_cli/test_doctor.py -q -k "provider_ids_that_catalog_aliases or vertex"
• .venv/bin/python -m pytest tests/hermes_cli/test_doctor.py -q
• .venv/bin/python -m ruff check hermes_cli/doctor.py tests/hermes_cli/test_doctor.py
• scripts/run_tests.sh tests/hermes_cli/test_doctor.py -q
• pytest tests/ -q

Platform: macOS, Python 3.13, local .venv.

[alt-glitch]

This was generated by AI during triage.

Competing-PR cluster for #56906 (hermes doctor false-positives on Vertex). Four open PRs now fix this via distinct mechanisms: #56930 (plugin-registry fallback in providers.py::get_provider, earliest), #56939 (normalize_provider + expanded known set), #56962 (ProviderProfile enumeration in doctor), and this one (#57154, catalog _KNOWN_PROVIDER_NAMES + vendor-slug allow). Related, not duplicates — different code paths. Flagging for a maintainer to pick one (earliest = #56930).

[teknium1]

Thanks for the narrow doctor-path fix. Current main still rejects a configured provider whenever catalog_provider is None in hermes_cli/doctor.py:818-833, and still warns on Vertex's documented google/... model IDs because vertex is absent from providers_accepting_vendor_slugs in hermes_cli/doctor.py:841-858. The setup flow writes provider: vertex at hermes_cli/model_setup_flows.py:2455, while the documentation specifies google/gemini-3-flash-preview at website/docs/integrations/providers.md:398-403.

Problems

• Fixes #56906 is broader than this diff. [Bug]: hermes doctor fails when using the new vertex provider #56906 also reports title generation failing, but commit afe70d643c3b changes only doctor validation and its tests.

Suggested changes

• Use Related to #56906 instead, or address the title-generation symptom separately.

Automated hermes-sweeper review.