fix: health endpoint always 200 so Docker HEALTHCHECK passes on startup

/health was returning 503 when the Hermes gateway hadn't started yet.
Docker HEALTHCHECK uses curl -f which treats 503 as failure, so the
container stayed in "starting" state until the gateway was fully up
(~120s). Combined with start-period=180s, HF Space was stuck at
RUNNING_APP_STARTING indefinitely.

Fix: always return HTTP 200 from /health (gateway status in JSON body).
Reduce start-period to 30s since health server starts in ~2s.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Dockerfile

@@ -97,7 +97,7 @@ ENV HERMES_HOME=/opt/data \
 
 EXPOSE 7861
 
-HEALTHCHECK --interval=30s --timeout=5s --start-period=180s \
+HEALTHCHECK --interval=30s --timeout=5s --start-period=30s \
   CMD curl -fsS http://localhost:7861/health || exit 1
 
 CMD ["/opt/huggingmes/start.sh"]

health-server.js

@@ -566,7 +566,11 @@ const server = http.createServer(async (req, res) => {
 
   if (path === "/health" || path === `${APP_BASE}/health`) {
     const data = await statusPayload();
-    res.writeHead(data.ok ? 200 : 503, { "content-type": "application/json" });
+    // Always 200 — health server up means the app is running.
+    // Gateway readiness is in the JSON body (gateway: true/false).
+    // Returning 503 here caused Docker HEALTHCHECK to fail during gateway
+    // startup, keeping HF Space stuck in RUNNING_APP_STARTING indefinitely.
+    res.writeHead(200, { "content-type": "application/json" });
     res.end(
       JSON.stringify({
         ok: data.ok,