rename: failover → fallback throughout codebase — this system is Fallback, state is FALLBACK; preserve conventional failover comparisons

Tools/Manual-Tools.md

@@ -572,7 +572,7 @@ docker_watchdog
   Memory-monitored containers
   Recent restart history + skip list
 
-failover (fallback.sh)
+fallback (fallback.sh)
   Current state (NORMAL / FALLBACK / HANDBACK)
   Tier flags and timestamps
   Remote Tailscale visibility

Tools/README-Tools.md

@@ -13,8 +13,8 @@ the scheduled maintenance model. These scripts sit ready for the moment you need
 
 ## ━━━ THE PROBLEM THAT BUILT THIS ━━━
 
-**Failover State Stuck After Testing**  
-Run a failover test, something exits uncleanly, state file shows `FALLBACK`.
+**Fallback State Stuck After Testing**  
+Run a fallback test, something exits uncleanly, state file shows `FALLBACK`.
 `fallback.sh` resumes and reads FALLBACK — starts containers it shouldn't, makes
 decisions based on a state that doesn't reflect reality. Manual recovery means
 knowing the exact file format and every field to reset. At 2am after a failed test.  
@@ -90,7 +90,7 @@ unRAID_Essentials/  ← regular system maintenance    — scheduled
 Docker_Essentials/  ← regular container management  — scheduled
 Monitors/           ← regular health reporting       — scheduled
 Orchestrators/      ← regular maintenance windows   — scheduled
-Fallback/           ← automated failover/handback   — event-driven
+Fallback/           ← automated fallback/handback   — event-driven
 Tools/              ← situational utilities          — run when needed
 ```
 
@@ -116,7 +116,7 @@ The relationship is one-way: Tools act on state that other scripts have written.
 
 | Script | What It Fixes | When to Run |
 |--------|--------------|-------------|
-| `fallback_state_reset.sh` | State file stuck in FALLBACK after test or failed handback | After failover testing or manual intervention |
+| `fallback_state_reset.sh` | State file stuck in FALLBACK after test or failed handback | After fallback testing or manual intervention |
 | `watchdog_skip_list_manager.sh` | Container stuck on watchdog skip list after fixing root cause | After fixing a container that hit the restart loop limit |
 | `bulk_permissions_repair.sh` | Files owned by wrong user after admin copy or bad container config | When arr operations fail due to permissions |
 | `container_data_export.sh` | Need a clean backup before a risky container update or migration | Before major updates, appdata migrations, or container removals |
@@ -143,7 +143,7 @@ Situation arises
 ┌──────────────────────────────────────────────────────────────────────┐
 │  Tools/                          Run directly when needed             │
 │                                                                       │
-│  fallback_state_reset.sh     ◄── after failover test / failed handback│
+│  fallback_state_reset.sh     ◄── after fallback test / failed handback│
 │  watchdog_skip_list_manager  ◄── after fixing a crash-looping container│
 │  bulk_permissions_repair     ◄── wrong ownership after copy or rsync  │
 │  container_data_export       ◄── before a risky update or migration   │

Tools/fallback_state_reset.sh

@@ -1,12 +1,12 @@
 #!/bin/bash
 # ==============================================================================================
-# ============================= Failover State Reset ===========================================
+# ============================= fallback State Reset ===========================================
 # ==============================================================================================
 #
 # PURPOSE
 # ─────────────────────────────────────────────────────────────────────────────
 # Resets the fallback state file to NORMAL and clears all tier flags. Use when
-# the state file is stuck after failover testing, a failed handback, manual
+# the state file is stuck after fallback testing, a failed handback, manual
 # intervention, or fallback.sh being killed mid-cycle.
 #
 # Writes a fresh state file with:
@@ -17,8 +17,8 @@
 # resumes from NORMAL on its next cycle.
 #
 # WARNING: Only run when you have verified the stack is actually in a normal
-# state — right containers on the right server, DDNS correct, no active failover
-# in progress. Resetting state during a real failover causes fallback.sh to stop
+# state — right containers on the right server, DDNS correct, no active fallback
+# in progress. Resetting state during a real fallback causes fallback.sh to stop
 # covering the remote server until the next detection cycle.
 #
 # ==============================================================================================