fix widespread naming errors across all docs — array_started, fallback, FALLBACK_

array_start.sh → array_started.sh (bulk rename — actual file has always been
array_started.sh; docs consistently used the wrong name across 9 files)

failover.sh → fallback.sh (bulk rename — script is Fallback/fallback.sh;
docs used the old name throughout)

FAILOVER_HOST2_RUNS_FOR_HOST1_TIER1 → FALLBACK_HOST2_COVERS_HOST1_TIER1
(README.md — wrong variable name, actual vars use FALLBACK_ prefix and
COVERS_ not RUNS_FOR_)

docker_watchdog.sh attribution: "started by array_started.sh" → "called every
minute by watchdog_orchestrator.sh" (docker_watchdog is not in ARRAY_START_SCRIPTS)

server_reboot.sh shutdown sequence: step 7 "rc.docker stop" → calls
array_stopping.sh (user_scripts, fallback, rsync, mover, docker_container_stop)

Rsync manual ARRAY_START_SCRIPTS list: removed stability_watchdog and
docker_watchdog (now in watchdog_orchestrator); failover → fallback

Fallback/README-Fallback.md

@@ -242,7 +242,7 @@ movement required. The fallback and rsync scripts are configuration-driven.
 
 | Script | Role | When It Runs |
 |--------|------|--------------|
-| `fallback.sh` | Continuous state machine — monitors remote, manages fallback and handback | Continuously (started by `array_start.sh`) |
+| `fallback.sh` | Continuous state machine — monitors remote, manages fallback and handback | Continuously (started by `array_started.sh`) |
 | `fallback_test.sh` | 7-phase test harness — validates the entire fallback lifecycle via iptables simulation | On demand — maintenance window only |
 
 ---
@@ -250,7 +250,7 @@ movement required. The fallback and rsync scripts are configuration-driven.
 ## ━━━ HOW THE SCRIPTS RELATE ━━━
 
 ```
-array_start.sh
+array_started.sh
       │
       └── starts fallback.sh (continuous loop)
                 │