# Part A - R-549, operator ruling A: the quiet-box alarm waits three report cycles
# Deployed 2026-09-17 ~08:22Z. Manifest commit 06334e164c51; hub image 0.117.0.

## ArgoCD, verified by revision and image - not by the rollout message
  before sync: OutOfSync rev=06334e164c519a9926e868c23e6bda2f58f915cc
  after:       Synced, health Healthy, rev == manifest HEAD: YES
  image:       gitea.dooplex.hu/admin/felhom-hub:0.117.0
  NOTE: `rollout status` printed "successfully rolled out" while the new pod was still 0/1 ready.
        Readiness was waited for separately (ready=true at 08:22:51Z).

## The live ConfigMap
  stale_threshold: "45m"

## THE PROOF - the running hub's own startup lines (these fields did not exist before v0.117.0)
  2026/09/17 10:22:34 [INFO] Staleness checker initialized: 2 ok, 0 stale, 2 down (node_stale after 45m0s, node_down after 1h30m0s)
  2026/09/17 10:22:34 [INFO] Host staleness checker initialized: 2 ok, 0 stale, 0 down (stale/down left unseeded → first Check emits; host_stale after 45m0s, host_down after 1h30m0s)
  (log times are the pod's local CEST; 10:22 CEST = 08:22Z)

## Hub serving: https://hub.felhom.eu/healthz -> 200
