fix(status): treat customHealthCheck 'unconfigured' results consistently

Two paths produced status: 'unconfigured' on the system status dashboard
but they wrote the human-readable reason to different fields:

  - Manifest requiredConfigKeys (MBTA, TfL, OTP, TransitLand, DB RIS, …)
    → wrapper writes the reason to `url` (rendered muted gray).
  - Custom ctx.registerHealthCheck (only Swiss currently)
    → wrapper forwards `error` straight through, and the dashboard
      renders any `error` in red regardless of status.

So 'Swiss API key not configured' was the only red 'not configured'
line on the page while every other one was gray.

Normalize at the wrapper: when a custom check returns 'unconfigured'
with an error message, hoist the message into `url` and clear `error`.
Now custom checks behave like manifest checks for missing config —
red is reserved for actual failures (status: 'down').

Author: Medformatik

apps/api/src/services/integration-health.ts

@@ -98,14 +98,20 @@ async function executeSingleHealthCheck(
     const start = Date.now();
     try {
       const result = await integration.customHealthCheck();
+      // Normalize the unconfigured-with-message shape to match the
+      // manifest `requiredConfigKeys` path: surface the reason in `url`
+      // (rendered muted gray) rather than `error` (rendered red), so the
+      // status dashboard treats missing config consistently regardless of
+      // which path produced it.
+      const isUnconfigured = result.status === "unconfigured";
       return {
         id,
         name,
         category,
-        url: hc.url ?? "",
+        url: isUnconfigured && result.error ? result.error : (hc.url ?? ""),
         status: result.status,
         responseTime: result.responseTime ?? Date.now() - start,
-        error: result.error,
+        error: isUnconfigured ? undefined : result.error,
       };
     } catch (err) {
       return {