Update all docs to reflect watchdog restructure

README-Watchdogs.md: new tier diagram, updated script table, execution flow,
  state file table, and folder relationship diagram
Manual-Watchdogs.md: added system_watchdog (thin), System/storage_watchdog,
  System/webgui_watchdog, and stability_watchdog sections; updated TOC and troubleshooting
README.md: updated schedule listing, folder description, daily cycle examples
README-User_Script_Plug-in.md: stability_watchdog references throughout
unRAID_Essentials/README + Manual: stability_watchdog, updated storage path
Monitors/README, Rsync/Manual, Tools/Manual: lock name list updates

unRAID_Essentials/Manual-Unraid_Essentials.md

@@ -4,7 +4,7 @@ Configuration reference, operational procedures, and troubleshooting for
 system-level scripts. Read the ARRAY_START_SCRIPTS order section before
 adding or reordering scripts at array start.
 
-> **Watchdog scripts have moved.** `system_watchdog.sh` and `resource_watchdog.sh`
+> **Watchdog scripts have moved.** `stability_watchdog.sh` and `resource_watchdog.sh`
 > now live in `Watchdogs/`. Their configuration reference and troubleshooting
 > procedures are in `Watchdogs/Manual-Watchdogs.md`.
 
@@ -452,8 +452,8 @@ server_reboot.sh --reason="disk work"    # include reason in notification
 
 ## Full Configuration Reference
 
-> Watchdog configuration (`system_watchdog.sh`, `resource_watchdog.sh`,
-> `docker_watchdog.sh`, `storage_watchdog.sh`) lives in `Watchdogs/Manual-Watchdogs.md`.
+> Watchdog configuration (`stability_watchdog.sh`, `resource_watchdog.sh`,
+> `docker_watchdog.sh`, `System/storage_watchdog.sh`) lives in `Watchdogs/Manual-Watchdogs.md`.
 
 ```bash
 # master.conf
@@ -494,8 +494,8 @@ REBOOT_VM_WAIT=30
 
 ## Troubleshooting
 
-> Watchdog troubleshooting (system_watchdog, resource_watchdog, docker_watchdog,
-> storage_watchdog) is in `Watchdogs/Manual-Watchdogs.md`.
+> Watchdog troubleshooting (stability_watchdog, resource_watchdog, docker_watchdog,
+> System/System/storage_watchdog) is in `Watchdogs/Manual-Watchdogs.md`.
 
 ### rsync_stop Killed the Wrong Thing
 

unRAID_Essentials/README-Unraid_Essentials.md

@@ -16,7 +16,7 @@ The restart hangs. The server needs a reboot, but nothing in the ecosystem is
 authorized to call one. Or: rootfs fills to 99%. SSH stops working. Docker can't
 write log files. The server is functionally dead but still technically running.
 
-Fix: `system_watchdog.sh` — three-tier response: immediate reboot on critical
+Fix: `stability_watchdog.sh` — three-tier response: immediate reboot on critical
 failures, OOM-confirmed bypass for RAM crises, strike system for sustained
 threshold breaches. Last line of defense before a hard crash.
 
@@ -82,7 +82,7 @@ Graceful operations     mover_stop.sh            — clean mover stop
                         server_reboot.sh         — clean reboot with pre-flight warnings
 ```
 
-> `system_watchdog.sh` and `resource_watchdog.sh` have moved to `Watchdogs/`.
+> `stability_watchdog.sh` and `resource_watchdog.sh` have moved to `Watchdogs/`.
 > See `Watchdogs/README-Watchdogs.md` for the full watchdog suite.
 
 ---
@@ -99,9 +99,9 @@ Orchestrators/
   server_reboot.sh ────────────────────────► user_scripts_stop.sh   (called internally)
 
 Watchdogs/
-  system_watchdog.sh and resource_watchdog.sh now live here.
+  stability_watchdog.sh and resource_watchdog.sh now live here.
   See Watchdogs/README-Watchdogs.md for how they relate to each other
-  and to docker_watchdog.sh and storage_watchdog.sh.
+  and to docker_watchdog.sh and System/storage_watchdog.sh.
 ```
 
 ---