rename appdata-Failover→appdata-Fallback in docs; critical sync 15→30min; transcode 3→7min

appdata-Failover → appdata-Fallback:
  All .md files updated — scripts and confs already used appdata-Fallback.
  Share was renamed; docs were the only stale references.

critical_sync_maintenance.sh: */15 → */30, 96/day → 48/day:
  critical_sync_maintenance.sh header, master.conf, host1/2.conf comments,
  Orchestrators README, User Script Plug-in README, Partnership README/manual/script,
  Docker_Essentials README/downloaders_reset.sh, Fallback README,
  weekly_sync_maintenance.sh, user_script_plug-in.sh all updated.

rsync_emby_failover User Script superseded:
  Emby dirty sync was already in HOST1_CRITICAL_SYNC_SHARES — it now runs inside
  critical_sync_maintenance.sh every 30min alongside auth sync and partnership check.
  Section in User Script Plug-in README marked for deletion from plugin.

transcode_management.sh: */3 → */7:
  transcode_management.sh, transcode_manager.sh, transcode_cleanup.sh headers,
  Transcodes README/manual, Orchestrators README, User Script Plug-in README,
  user_script_plug-in.sh all updated.

Partnership/README-Partnership.md

@@ -34,7 +34,7 @@ in one place and forgotten in the other.
 **The fix:** one auth stack with a managed mirror. HOST1 owns the configuration.
 HOST2 runs a warm copy that stays current via 15-minute sync. HOST2's operator makes
 zero auth management decisions — clicking an auth container opens HOST1's WebUI via
-Tailscale. Changes happen there, propagate to HOST2 in 15 minutes. One place to
+Tailscale. Changes happen there, propagate to HOST2 in 30 minutes. One place to
 manage everything for both households.
 
 ---
@@ -107,7 +107,7 @@ Called by `partnership_manager.sh --offboard` but runnable directly.
 
 **Lifecycle management** (`partnership_manager.sh`) — dispatcher and monitor.
 - Manually: `--onboard`, `--offboard` (delegates to offboard script), `--transfer`, `--status`, `--unblock`
-- Automatically: `--check` called every 15 minutes by `critical_sync_maintenance.sh`
+- Automatically: `--check` called every 30 minutes by `critical_sync_maintenance.sh`
 
 **SSH management** (`ssh_setup.sh`) — generates the keypair for rsync automation,
 installs it on the remote, and tracks auth failures with a configurable strike system.
@@ -119,7 +119,7 @@ re-keying.
 ## ━━━ RELATIONSHIP TO OTHER FOLDERS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Orchestrators/** — `critical_sync_maintenance.sh` calls `partnership_manager.sh --check`
-every 15 minutes, passing `--remote-seen` or `--remote-unseen` based on whether the
+every 30 minutes, passing `--remote-seen` or `--remote-unseen` based on whether the
 rsync to the partner succeeded. The rsync outcome is the connectivity signal — no
 separate ping needed.
 
@@ -140,7 +140,7 @@ independently at 4-hour cadence.
 |--------|------|--------------|
 | `partnership_onboard.sh` | One-time setup — SSH keys, stack deploy, arr bootstrap | Manually, once per server per partnership |
 | `partnership_offboard.sh` | Clean separation — both paths, both roles | Via `partnership_manager.sh --offboard`; or directly |
-| `partnership_manager.sh` | Dispatcher + monitor — onboard WebUIs, health check, transfer, status | `--check` every 15min; all other modes manually |
+| `partnership_manager.sh` | Dispatcher + monitor — onboard WebUIs, health check, transfer, status | `--check` every 30min; all other modes manually |
 | `ssh_setup.sh` | SSH key generation, remote install, auth validation | Called by onboard; manually for re-keying or validation |
 
 ---
@@ -166,7 +166,7 @@ HOST1 (owner) runs:
     ├─ partnership_manager.sh --onboard  reconfigures WebUIs, writes ACTIVE state
     └─ arr_sync.sh                    bootstraps full library on both servers
 
-ONGOING OPERATION (every 15min)
+ONGOING OPERATION (every 30min)
 ─────────────────────────────────────────────────────────────────────────────
 critical_sync_maintenance.sh
   ├─ Critical-Data rsync              keeps auth appdata current on mirror