manifests: hub 0.117.0 and stale_threshold 45m (R-549, operator ruling A)

Three report cycles instead of two. The chaos-night round-9 measurement: cadence
15m, a failed push retried for ~100 s, a 29m59s gap against a 30m threshold -
one second from paging the operator about a healthy, self-repaired box.
node_down and host_down move to 90m with it (2x). The same release makes the
dashboard's customer status read this value instead of a hardcoded 30m.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

manifests/hub.yaml

@@ -78,7 +78,10 @@ data:
       max_days: 90
       prune_schedule: "04:30"
     alerting:
-      stale_threshold: "30m"
+      # 45m: operator ruling A on R-549 (2026-09-17) - three report cycles, so one failed push
+      # (retried ~100 s, measured 29m59s gap in chaos night round 9) cannot page on a healthy box.
+      # node_down / host_down follow at 2x = 90m.
+      stale_threshold: "45m"
     notifications:
       # Resend API key is NOT stored here. It is injected at runtime from Secret/resend-api
       # via the RESEND_API_KEY env var (see Deployment below). The Secret is created out-of-band
@@ -125,7 +128,7 @@ spec:
     spec:
       containers:
         - name: hub
-          image: gitea.dooplex.hu/admin/felhom-hub:0.116.0
+          image: gitea.dooplex.hu/admin/felhom-hub:0.117.0
           ports:
             - containerPort: 8080
               name: http