d5d0613778
Under gateway.multiplex_profiles the primary gateway's in-process ticker fires satellite-profile jobs and delivers through the primary's live adapters (#69377) — the satellite home intentionally holds no platform credentials (its own token would be a duplicate_credential fatal). _preflight_check_delivery loads the gateway config of the job's OWN home, so a profile_routes-routed platform reads as unconnected there and the job is permanently blocked before any LLM call with a misleading "not connected" error (#97476). When the own-home config reports a platform unconnected, consult the primary home's profile_routes: an enabled route matching the platform that points at the profile currently being served means delivery is the primary gateway's to make — pass the check. The primary config.yaml is read directly (both top-level and nested gateway. forms) instead of via load_gateway_config() so no primary platform config leaks into the satellite process's environment. Lookup failures and missing configs fail closed (the block stands).