31e41eed34
Test-pollution class: runtime_provider is usually imported lazily (inside switch_model's resolution path), so its first import in a pytest worker can happen while a test has hermes_cli.config.load_config patched. The module-level from-import then bound the MagicMock permanently — after the patch exited, every later caller in the process silently read the dead test's config. Live victim: MoA aggregator context-length resolution (resolve_runtime_provider -> AuthError 'Unknown provider custom:example'), making TestMoAContextLength::test_moa_custom_context_configures_compressor_threshold fail whenever it shared a process with TestLocalOllamaModelDiscovery::test_switch_model_on_current_ollama_custom_endpoint_keeps_base_url. Fix: load_config / get_compatible_custom_providers / normalize_extra_headers become late-bound delegates resolving hermes_cli.config attributes at call time. Both patch targets (config.load_config and runtime_provider.load_config) keep working. Regression tests pin the late-binding property and fail if the delegates revert to from-imports (sabotage-verified).