Move Custom Scripts out of the repo and add an Import Script picker

Custom Scripts (the Scheduler page's inline editor) used to save into the
git-tracked Custom/ folder, so anything saved there would end up on GitHub.
They now live in /boot/config/plugins/user.scripts/Varaverk/Scripts, same
folder family as Unraid's own User Scripts plugin. Import Script lets you
browse the whole server and move an existing script in instead of only
creating new ones inline — always a move, never a copy, so no stray
duplicate is left where it came from.

Manual.md

@@ -305,7 +305,31 @@ entries needed. The plugin handles all triggers natively:
 - **Cron** → `Plugin/unraid/event/disks_mounted/rebuild_cron` rebuilds the cron file from `schedule.json` on every boot
 
 Configure via the Varaverk plugin Scheduler tab (or edit `schedule.json` directly).
-Individual scripts are never scheduled — only orchestrators.
+The built-in job list schedules orchestrators, never individual repo scripts directly —
+but the Scheduler tab's **Custom Scripts** card is the one place individual scripts
+*are* scheduled directly (see below).
+
+---
+
+### ── Custom Scripts ────────────────────────────────────────────────────────────
+
+The Scheduler tab has a **Custom Scripts** card for one-off scripts that aren't part of
+the repo's orchestrator pipeline — personal tooling, quick fixes, anything you don't
+want to wire into `master.conf`.
+
+Scripts live in `/boot/config/plugins/user.scripts/Varaverk/Scripts/` — deliberately
+**outside** the Varaverk git repo (that folder is never pushed to GitHub), in the same
+place the Unraid User Scripts plugin keeps its own scripts, so it's a folder location
+admins are already used to.
+
+Two ways to get a script there:
+
+- Click **+ Create Script** on the Scheduler tab — opens an inline editor, writes the
+  file to that folder, and adds a `schedule.json` entry automatically.
+- Drop any `.sh` file into the folder yourself (e.g. via terminal, or Unraid's own
+  Custom Scripts / User Scripts plugin pointed at the same path). The Scheduler tab
+  **auto-detects** it — discovery is a folder scan, not a registry, so it doesn't matter
+  how the file got there. It shows up disabled with no cron until you configure one.
 
 ---