Use guard hostname for realtime and config polling

[hansott]

No description provided.

[aikido-pr-checks]

🟡 Medium - Realtime polling now reuses AIKIDO_ENDPOINT even though it calls a different path contract

This fallback now returns AIKIDO_ENDPOINT, but RealtimeAPI still probes <base>/config while the normal API client uses <base>/api/runtime/.... In deployments that override only AIKIDO_ENDPOINT to point at an API proxy or mock server and omit AIKIDO_REALTIME_ENDPOINT, the poller will now hit 404s on the custom API base instead of the default realtime host. That leaves config and blocked-list refreshes stuck on stale data until a separate realtime endpoint is configured.

Show fix

Suggested change

	return getAikidoAPIEndpoint(token);
	String region = token != null ? token.getRegion() : "EU";
	return switch (region) {
	case "US" -> "https://guard.us.aikido.dev/";
	case "ME" -> "https://guard.me.aikido.dev/";
	case "AU" -> "https://guard.au.aikido.dev/";
	default -> "https://guard.aikido.dev/";
	};

_{More info - Reply on this comment to give feedback or ignore the issue.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!