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.

Plugin/unraid/Tools/api_cache_writer.php

@@ -149,7 +149,7 @@ vv_cache_write('arrs', $arrs);
 
 // ── Watchdog payload ──────────────────────────────────────────────────────────
 // Here for the same reason as the other two: vv_wd_all() SSHes to every partner, which cost 8.3s
-// on this host with HOST2 down, and the Watchdog tab polls every 30 seconds. Collected off the
+// on this host with the partner unreachable, and the Watchdog tab polls every 30 seconds. Collected off the
 // request path it is paid once a minute by cron instead of by whoever has the tab open.
 require_once $_base . '/include/watchdog.php';
 vv_cache_write('watchdog', vv_wd_all());

Plugin/unraid/api/rsync.php

@@ -150,7 +150,7 @@ $history  = [];
 // cleanup, docker updates — and run on their schedule whether or not RSYNC_ENABLED is true. So the
 // page could report a healthy 56-minute "daily sync" for a subsystem that had not run in a month,
 // which is exactly what it was doing: the last entry here is 2026-07-16, the day the global gate
-// was closed for the HOST2 rebuild.
+// was closed.
 //
 // Deliberately outside the 30-day cutoff. The last transfer is 29 days old as this is written and
 // would have dropped out of the window within days, taking the page from a wrong answer to no

Plugin/unraid/api/watchdog.php

@@ -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.
 //

Plugin/unraid/include/ai_memory_learn.php

@@ -194,7 +194,7 @@ function vv_ai_mem_append(string $text): array {
 // Takes one line back out of the learned slot. The counterpart to vv_ai_mem_append(), and the
 // reason a decided proposal can be changed at all: without this, "accepted" was a one-way door
 // and the only way out was editing mem_learned.md by hand. An accepted line joins every future
-// prompt, and a fact that is true today — HOST2 is offline — becomes actively wrong the day it
+// prompt, and a fact that is true today — a host is unreachable — becomes actively wrong the day it
 // stops being true, with nothing to expire it.
 //
 // Matched on the line this file wrote: "- <text>  (<date>)". A line the operator has since edited

Plugin/unraid/pages/ai.php

@@ -470,7 +470,7 @@ vv_ai_chat_markup('vv-ai', [
     <span id="vv-ai-mem-count" style="margin-left:auto;font-size:10px;color:#3a3a3a;font-family:monospace;"></span>
   </div>
   <textarea id="vv-ai-mem-text" class="vv-ai-input" rows="10" spellcheck="false"
-    placeholder="Who you are, how this install is set up, decisions already made, things it should stop asking.&#10;&#10;e.g.&#10;- HOST2 (unRAID-Jayred36) is being rebuilt and is offline. Do not suggest syncing to it.&#10;- RSYNC_ENABLED is deliberately false until HOST2 is onboarded.&#10;- I verify everything before trusting it. Show your sources."></textarea>
+    placeholder="Who you are, how this install is set up, decisions already made, things it should stop asking.&#10;&#10;e.g.&#10;- Media lives on the array, never on the cache pool. Do not suggest moving it.&#10;- RSYNC_ENABLED is deliberately false right now. Do not suggest turning it on.&#10;- I verify everything before trusting it. Show your sources."></textarea>
   <div style="display:flex;gap:8px;align-items:center;margin-top:7px;">
     <span id="vv-ai-mem-status" style="font-size:10px;color:#4a4a4a;"></span>
     <button class="vv-ai-btn ghost" style="margin-left:auto" id="vv-ai-mem-cancel" type="button">Close</button>
@@ -967,7 +967,7 @@ vv_ai_chat_markup('vv-ai', [
     // of ordinary suggestions read as a card of problems.
     //
     // A decision is not final. An accepted line joins every future prompt and nothing expires it,
-    // so a fact that is true today — HOST2 is offline — needs a way back out on the day it stops
+    // so a fact that is true today — a gate is off, a host is unreachable — needs a way back out on the day it stops
     // being true. Retract is that way; Keep is the same door in the other direction.
     const B = (act, cls, label, tip) =>
       `<button class="vv-ai-btn${cls}" data-mem-act="${act}" data-id="${esc(r.id)}" `

Plugin/unraid/pages/readme/ui-map.md

@@ -1256,7 +1256,7 @@ Saved into `master.conf`, which does not need to be opened by hand.
 
 | Setting | Control | Where | What it does |
 |---|---|---|---|
-| `CONF_SYNC_ENABLED` | a switch | in this section | HOST2 rebuild in progress — re-enable when HOST2 is back online |
+| `CONF_SYNC_ENABLED` | a switch | in this section | partner conf caching — armed by onboard Step 1d |
 
 ## Critical Containers