fix(agent): short-circuit local server detection for known public provider hosts

[liuhao1024]

What does this PR do?

When using the openai-api provider with the default base URL https://api.openai.com/v1, Hermes sends HTTP GET requests to local-only discovery endpoints (/api/tags, /v1/props, /version) on api.openai.com. These endpoints return 404 Not Found (as expected, since they're not part of the OpenAI API), creating noise in egress logs and monitoring dashboards.

This PR adds a hostname blacklist to detect_local_server_type() to short-circuit detection for known public provider hosts. Local/custom endpoints (localhost, 127.0.0.1, RFC1918 IPs, custom URLs) still probe as expected.

Related Issue

Fixes #61421

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• agent/model_metadata.py: Add hostname check to detect_local_server_type() to short-circuit detection for known public provider hosts (api.openai.com, api.anthropic.com, generativelanguage.googleapis.com)
• tests/agent/test_model_metadata_local_ctx.py: Add TestDetectLocalServerTypePublicProviderShortCircuit test class with 5 regression tests

How to Test

1. Configure Hermes with:

   model:
     provider: openai-api
     default: gpt-5.1
     base_url: "https://api.openai.com/v1"

2. Use Hermes via gateway or CLI to send prompts with images (triggers vision routing)
3. Before fix: Egress logs show 404s to /api/tags, /v1/props, /version on api.openai.com
4. After fix: No probing requests to those endpoints; only normal /v1/... API traffic
5. Run pytest tests/agent/test_model_metadata_local_ctx.py::TestDetectLocalServerTypePublicProviderShortCircuit -v — all 5 tests pass

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/agent/test_model_metadata_local_ctx.py -v and all 39 tests pass
• I've added tests for my changes (5 new tests in TestDetectLocalServerTypePublicProviderShortCircuit)
• I've tested on my platform: macOS 15.2

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — hostname parsing uses stdlib urlparse, works on all platforms
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

[teknium1]

Thanks for addressing the unnecessary discovery traffic. The underlying path remains present on current main: agent/model_metadata.py:704-740 probes the configured URL, and agent/image_routing.py:321-331 can call that detector for an unknown capability.

Problems

• agent/model_metadata.py:690 parses the hostname directly instead of using the existing base_url_hostname() helper. That misses the trailing-dot normalization contract already covered by tests/test_base_url_hostname.py:37-38: https://api.openai.com./v1 will still be probed.

Suggested changes

• Use the already imported base_url_hostname(normalized) at agent/model_metadata.py:690 and add a matching no-request regression case.

Automated hermes-sweeper review.

[teknium1]

Please use the existing base_url_hostname(normalized) helper here. It canonicalizes trailing DNS dots (covered by tests/test_base_url_hostname.py), so https://api.openai.com./v1 is treated as the same OpenAI host and does not retain the probe behavior this change targets.