configure anonymous SearXNG provider defaults

docs/Dankclaw/SearXNG.md

@@ -61,9 +61,29 @@ valkey:
   url: "valkey://searxng-valkey:6379/0"
 
 outgoing:
-  request_timeout: 4.0
-  max_request_timeout: 12.0
+  request_timeout: 5.0
+  max_request_timeout: 15.0
   retries: 1                     # avoid amplifying upstream 429/CAPTCHA responses
+
+# Anonymous, bounded default aggregation. Disabled engines remain configured
+# for explicit/on-demand selection; see SearXNG Providers for the policy.
+engines:
+  - name: bing
+    disabled: false
+    weight: 2
+    paging: false
+    timeout: 5.0
+  - name: duckduckgo
+    disabled: false
+    weight: 2
+    paging: false
+    timeout: 5.0
+  - name: google cse
+    disabled: true
+  - name: brave
+    disabled: true
+  - name: startpage
+    disabled: true
 ```
 
 ## Volumes
@@ -100,9 +120,12 @@ The current request policy allows a modest amount of VPN latency (`4.0s` per
 request, `12.0s` maximum) while limiting retries to one. This can recover slow
 providers, but it cannot fix an upstream CAPTCHA or 429 caused by the shared
 VPN exit IP. SearXNG queries all ~50 upstream engines from one Gluetun VPN exit
-IP. The rate-sensitive engines (Google, DuckDuckGo) then answer with reCAPTCHA / 429,
-and SearXNG **suspends** the offending engine for hours to days, which is what
-shows up as "Google went unavailable". This is upstream, not local.
+IP. The rate-sensitive engines (Google, DuckDuckGo) then answer with reCAPTCHA / 429.
+The default provider policy therefore favors anonymous Bing and DuckDuckGo,
+disables observed CAPTCHA/429 providers from normal aggregation, and disables
+pagination to reduce upstream request volume. SearXNG **suspends** offending
+engines for hours to days, which is what shows up as "Google went unavailable".
+This is upstream, not local.
 
 Fixes (cheapest first): tune the `outgoing` block (`request_timeout`,
 `retry_on_http_error`, `suspended_times`), duplicate the `google` engine under a