Probe the direct host for Jetpack capability detection, not the proxy

The route-support probe only sent Atomic sites to the direct host; Jetpack
WPCom-REST sites fell through to the WP.com proxy. Since the proxy and the
direct host advertise different route lists (the #22879 premise), Jetpack sites
got the wrong answer. Broaden the predicate to isUsingWpComRestApi &&
!isWPComSimpleSite (Atomic + Jetpack); the proxy is only for minting the
application password.

Author: jkmassel

WordPress/src/main/java/org/wordpress/android/repositories/EditorSettingsRepository.kt

@@ -108,11 +108,12 @@ class EditorSettingsRepository @Inject constructor(
     private suspend fun fetchRouteSupport(
         site: SiteModel
     ): Boolean = try {
-        // For Atomic sites the editor fetches `wp-block-editor/v1/settings`
-        // from the direct host — proxy and direct host can advertise
-        // different route lists, so detection has to probe the direct host
-        // too. See #22879.
-        if (site.isWPComAtomic) {
+        // Atomic and Jetpack-WPCom-REST sites have their own REST host that the editor talks to
+        // directly — the WP.com proxy and the direct host advertise different route lists, so
+        // detection has to probe the direct host too. The proxy is only for minting the application
+        // password. WP.com Simple sites have no direct host (the WP.com REST API *is* their API),
+        // and self-hosted sites are already direct via the configured client. See #22879.
+        if (site.isUsingWpComRestApi && !site.isWPComSimpleSite) {
             fetchRouteSupportViaDirectHostDiscovery(site)
         } else {
             fetchRouteSupportViaConfiguredClient(site)

WordPress/src/test/java/org/wordpress/android/repositories/EditorSettingsRepositoryTest.kt

@@ -229,6 +229,36 @@ class EditorSettingsRepositoryTest : BaseUnitTest() {
             verify(wpApiClientProvider, never()).getWpApiClient(atomicSite)
         }
 
+    @Test
+    fun `jetpack site probes the direct host, not the WP_com proxy`() =
+        runTest {
+            val jetpackSite = SiteModel().apply {
+                id = 7
+                url = "https://jetpack.example.com"
+                // isUsingWpComRestApi via Jetpack, but not Atomic and not WP.com Simple → direct host.
+                setIsJetpackConnected(true)
+                setOrigin(SiteModel.ORIGIN_WPCOM_REST)
+            }
+            mockDiscoverySuccess(
+                siteUrl = jetpackSite.url,
+                hasEditorSettings = true,
+                hasEditorAssets = true
+            )
+            whenever(themeRepository.fetchCurrentTheme(jetpackSite))
+                .thenReturn(buildTheme(isBlockTheme = false))
+
+            val result =
+                repository.fetchEditorCapabilitiesForSite(jetpackSite)
+
+            assertThat(result).isTrue()
+            verify(appPrefsWrapper)
+                .setSiteSupportsEditorSettings(jetpackSite, true)
+            verify(appPrefsWrapper)
+                .setSiteSupportsEditorAssets(jetpackSite, true)
+            // The proxy is only for minting — capability detection goes direct.
+            verify(wpApiClientProvider, never()).getWpApiClient(jetpackSite)
+        }
+
     @Test
     fun `atomic site returns false when discovery fails`() =
         runTest {