Connection failures show raw platform error text with formatting artifacts

[pliablepixels]

On Android, a request to an unreachable Ollama server surfaces as:

Ninjii error: failed to connect to /192.168.50.11 (port 11434) ...

The leading / is java.net.InetSocketAddress.toString(), which formats as hostname/literal-address; connecting to a raw IP leaves the hostname half empty. Capacitor uses CapacitorHttpUrlConnection (plain HttpURLConnection, no OkHttp), so this is Android's libcore wording reaching the user verbatim.

resolveQueryError (app/src/lib/query/query-error.ts) special-cases only 401; everything else falls through to t(fallbackKey, { error: message }) with the raw .message interpolated. assistant.error_generic is "Ninjii error: {{error}}", so whatever the platform networking layer says goes straight to the user.

Consequences:

• Untranslatable. {{error}} is always English platform text, in all five locales.
• Platform-dependent. Electron says connect ECONNREFUSED 192.168.50.11:11434, iOS URLSession says Could not connect to the server, and browser fetch says Failed to fetch with no address at all, so web users cannot see which host failed.
• No guidance. Nothing tells the user to check the address or start the server.

This affects every caller of resolveQueryError, not just the assistant: an unreachable ZoneMinder server shows the same string in its error banner.

Fix: carry the address from the request, do not parse it out of the message

lib/http.ts's catch already has fullUrl in scope and rethrows untouched. Stamp the host there, so it is identical on every adapter:

if (httpError.host === undefined) {
  try { httpError.host = new URL(fullUrl).host; } catch { /* relative URL */ }
}

new URL(fullUrl).host gives 192.168.50.11:11434: host and port, no scheme, no path, no stray /.

Detect unreachability structurally rather than by string match: a connection failure never received a response, so it has no status, while an HTTP error does. No regex over four platforms' wordings, which would drift.

Aborts must be excluded so a user cancellation does not render as a connection failure. Note isTimeoutError folds aborts in and is therefore the wrong helper here; isAbortError is the right one.

Result is one localized string with a single variable, which does translate:

Can't reach 192.168.50.11:11434. Check the address in Settings, or that the server is running.

The address stays visible, which is wanted, but comes from the request rather than from platform prose. It also appears on web and iOS, where the platform message currently hides it.

[pliablepixels]

Claude here, assisting @pliablepixels.

Fixed in 65f7a96, pushed to main.

The address now comes from the request rather than the message. lib/http.ts stamps HttpError.host with new URL(fullUrl).host in its catch, the one place that knows what was dialled, so it is identical on every adapter and present even where the platform hides it.

Detection is structural: no status means no response was ever received, while an HTTP error always has one. No matching on the four platform wordings, which would have drifted. Aborts are excluded via isAbortError so a user cancelling is not told the server is unreachable.

What users see now, on any platform:

Can't reach 192.168.50.11:11434. Check the address in Settings, or that the server is running.

The address stays visible, which was the requirement, but as clean host:port with no scheme, path, or InetSocketAddress artifacts. It also now appears on web and iOS, where the platform message gave no address at all.

Eight tests: two pinning that the host is stamped on both connection failures and non-2xx errors, six covering all four platform wordings resolving identically, the caller fallbackKey being outranked, aborts left alone, and a missing host falling through unchanged.

common.cannot_reach_host added to all five locales. 07-api-and-data-fetching.rst documents the four-adapter wording table, why the check is structural rather than textual, and why isTimeoutError is the wrong helper here.

Gates: 3051 passed, 0 failed, build and all three blocking lints clean.