Remove point-in-time HOST2 status from the codebase

Comments asserting a partner is down, being rebuilt or not yet installed are true on the day they are written and wrong afterwards, and nothing prompts anyone to revisit them. Behaviour is described generically; current state belongs in operator memory, not in tracked files.
2026-08-17 15:20:25 -04:00
parent e8ee5b052b
commit 0447fa6f86
11 changed files with 14 additions and 14 deletions
@@ -35,7 +35,7 @@
 //
 //   Served from cache, collected only on a miss.
 //       vv_wd_all() SSHes to every configured partner, so its cost is set by the slowest node
-//       rather than by how much data there is. Measured at 8.3s on this host with HOST2 down —
+//       rather than by how much data there is. Measured at 8.3s on this host with the partner unreachable —
 //       paid by every visitor, every 30 seconds, because the tab polls. The cache check happens
 //       before the heavy include, so a hit costs one file read and no SSH at all.
 //