fix: surface streamed load failures inline

The streamed loaders on bookmarks, collections, library, search, and the
collection detail page swallowed only ApiError into their in-band `error`
field and re-threw anything else. A raw network failure (a non-ApiError
TypeError from fetch) therefore escaped the `{#await}` to SvelteKit's
generic error page. On the collection detail page a content-load failure
showed a misleading "this collection is empty", and on search a failed
results query showed a false "no matches" because the streamed `error`
was never rendered.

Fold non-ApiError failures into the same in-band `error` so every
transient blip renders as an inline message, add a `contentError` branch
to the collection detail grid, and render the search results `error` in
both result views.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

frontend/src/routes/library/+page.ts

@@ -51,10 +51,11 @@ export const load: PageLoad = async () => {
                 if (e instanceof ApiError && e.status === 401) {
                     return { ...empty, authenticated: false };
                 }
-                if (e instanceof ApiError) {
-                    return { ...empty, error: e.message };
-                }
-                throw e;
+                // An HTTP error or a raw network failure (a non-ApiError
+                // TypeError) renders inline rather than escaping to the
+                // framework error page for a transient API blip.
+                const message = e instanceof ApiError ? e.message : 'Something went wrong.';
+                return { ...empty, error: message };
             }
         })()
     };