Scrub remaining Claude references from docs

Tools/Manual-Tools.md

@@ -21,7 +21,6 @@ making any changes.
 - [smart_long_test.sh](#smart_long_testsh)
 - [arr_profile_enforcer.sh](#arr_profile_enforcersh)
 - [webhook_setup.sh](#webhook_setupsh)
-- [claude_startup.sh](#claude_startupsh)
 - [ramdisk_stop.sh](#ramdisk_stopsh)
 - [Adding a New Tool](#adding-a-new-tool)
 
@@ -666,41 +665,6 @@ webhook_setup.sh --dry-run
 
 ---
 
-## claude_startup.sh
-
-Restores Claude Code's persistent data after an unRAID reboot and optionally launches
-Claude. Standalone script — no common.sh dependency.
-
-### Why This Exists
-
-unRAID's root filesystem lives in RAM — `/root/.claude` and `/root/.local` are wiped on
-every reboot. This script symlinks both directories back to persistent appdata storage
-at `/mnt/user/appdata/claude-code/` before launching Claude.
-
-### First Run Migration
-
-On first run, if persistent storage is empty, the script migrates from current live locations:
-
-```
-/root/.claude              → /mnt/user/appdata/claude-code/.claude
-/root/.local/share/claude  → /mnt/user/appdata/claude-code/local/share/claude
-```
-
-Subsequent runs skip the migration and only create the symlinks.
-
-### Calling from array_started.sh
-
-`array_started.sh` calls `claude_startup.sh` directly (no flags). This sets up the
-symlinks only — no interactive session is launched. That is the default behavior.
-
-### Usage
-
-```bash
-claude_startup.sh           # set up persistent symlinks only (default — used by array_started.sh)
-claude_startup.sh --launch  # set up symlinks and launch Claude interactively
-```
-
----
 
 ## ramdisk_stop.sh
 

Tools/README-Tools.md

@@ -69,7 +69,7 @@ something new, write the tool. Store it here. Find it at 2am next time.
 `bulk_permissions_repair.sh`, `arr_profile_enforcer.sh`
 
 **Lifecycle Tools** — Backup, setup, and migration support  
-`container_data_export.sh`, `claude_startup.sh`, `ramdisk_stop.sh`, `webhook_setup.sh`
+`container_data_export.sh`, `ramdisk_stop.sh`, `webhook_setup.sh`
 
 **Library Sync Bootstrap** — Close the gap between Emby and arr libraries  
 `emby_to_lidarr_sync.sh`, `emby_to_sonarr_sync.sh`, `emby_to_radarr_sync.sh`
@@ -113,7 +113,6 @@ The relationship is one-way: Tools act on state that other scripts have written.
 | `emby_database_repair.sh` | Emby crashing with database errors after power loss or crash | When Emby logs show corruption or repeated crashes |
 | `zfs_pool_scrub.sh` | Verify ZFS pool integrity — catch silent corruption before it spreads | Monthly, or after any disk or power event |
 | `smart_long_test.sh` | Run SMART extended self-test on all drives — full sector scan | Monthly via monthly_maintenance.sh, or after any disk event |
-| `claude_startup.sh` | Claude Code session setup after reboot — symlinks persistent storage | After each unRAID reboot, or called by array_started.sh |
 | `docker_prune_images.sh` | Remove dangling or unused Docker images accumulated after updates | After update cycles, or when disk space is low |
 | `ramdisk_stop.sh` | Safely stop the transcode ramdisk — redirect symlink to SSD, unmount, update state | Before re-running ramdisk_setup.sh with new size or thresholds |
 | `arr_profile_enforcer.sh` | Enforce correct quality profiles across all Sonarr/Radarr libraries | After arr setup, profile changes, or when library was imported with wrong profile |
@@ -144,7 +143,6 @@ Situation arises
 │  smart_long_test             ◄── monthly SMART scan / post-disk event │
 │  arr_profile_enforcer        ◄── wrong profiles after import or setup │
 │  webhook_setup               ◄── after install or adding a new arr    │
-│  claude_startup              ◄── after each unRAID reboot             │
 │  ramdisk_stop                ◄── before ramdisk resize / remount      │
 │                                                                       │
 │  emby_to_lidarr_sync         ◄── Lidarr setup / database wipe / gap  │