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.

Partnership/partnership_onboard.sh

@@ -211,7 +211,7 @@ SKIP_SERVICES_STACK=false
 SKIP_ARR_SYNC=false
 SKIP_WEBHOOK_SETUP=false
 SKIP_WEBHOOK_LISTENER=false
-PHASE1_ONLY=false   # OWNER: SSH + conf push only (HOST2 not yet installed)
+PHASE1_ONLY=false   # OWNER: SSH + conf push only (mirror not yet installed)
                     # MIRROR: SSH key install only, no owner notification
 PHASE2_ONLY=false   # OWNER: containers/arr/onboard only (triggered by HOST2 after it onboards)
 PHASE3_ONLY=false   # OWNER: media seed only — a separate decision, see the PHASE 3 block
@@ -757,7 +757,7 @@ if [[ "$PHASE1_ONLY" == true ]]; then
     #
     # Push always; pull only if the mirror actually has a conf yet. Before HOST2 installs Varaverk
     # there is nothing to pull, and an unconditional pull would count a failure and notify about
-    # a condition that is simply "HOST2 is not installed". The pull lands on the re-run after the
+    # a condition that is simply "the mirror is not installed". The pull lands on the re-run after the
     # install — the same --phase1-only --skip-ssh the operator uses to push conf again.
     echo ""
     echo "━━━ Phase 1 — Partner Conf Cache ━━━"