deploy: searxng on 9563, not 8080

8080 is taken several times over on this box, and the container name is the
only thing addressing it, so the port is ours to pick.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

deploy/README.md

@@ -81,7 +81,7 @@ no query leaves the LAN again. The shipped shape:
 
 ```json
 "search": {
-  "url": "http://searxng:8080",
+  "url": "http://searxng:9563",
   "max_results": 4,
   "snippet_runes": 1500,
   "language": "auto",

deploy/mavend.json

@@ -46,11 +46,12 @@
     "The instance must have `json` in search.formats (settings.yml); a stock",
     "SearXNG answers 403 to format=json and every search then fails. It is",
     "addressed by container name, so it needs the same maven_default",
-    "attachment kiwix has. No instance reachable ⇒ she falls through to the",
+    "attachment kiwix has, and it must listen on 9563: 8080 is taken several",
+    "times over on this box. No instance reachable ⇒ she falls through to the",
     "ZIMs and never says the search failed."
   ],
   "search": {
-    "url": "http://searxng:8080",
+    "url": "http://searxng:9563",
     "max_results": 4,
     "snippet_runes": 1500,
     "language": "auto",

internal/config/config.go

@@ -1119,7 +1119,7 @@ const (
 // Only the query string leaves the box. Notes, facts, the persona block and the
 // history are never part of a request; internal/websearch cannot read the store.
 type SearchConfig struct {
-	// URL — base address of the SearXNG instance, e.g. "http://searxng:8080".
+	// URL — base address of the SearXNG instance, e.g. "http://searxng:9563".
 	// Empty ⇒ the whole block is normalised to nil and the source stays off.
 	//
 	// The instance needs `search.formats` to include `json` in its settings.yml.

internal/websearch/searxng.go

@@ -80,7 +80,7 @@ type Options struct {
 	Timeout time.Duration
 }
 
-// New makes a client for a SearXNG base URL like http://searxng:8080.
+// New makes a client for a SearXNG base URL like http://searxng:9563.
 //
 // The instance must have the JSON format enabled (`search.formats: [html,
 // json]` in its settings.yml); a stock install answers 403 to format=json and