refactor: prefix the manual entry-point scripts with run-

Makes it unambiguous at a glance that these are meant to be run by
hand, not something a timer or another script calls.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011qAds5qr7nZRq5R4yAuxUk

TOOLING.md

@@ -30,19 +30,19 @@ with no deploy or restart.
 ```sh
 ssh mattellite
 
-~/gdl/stories.sh      # ~1 min.    DO THIS OFTEN - stories die in 24h
-~/gdl/profiles.sh     # ~5 min.    posts, highlights, stories (not reels -- see below)
-~/gdl/reels-all.sh    # ~15-20 min. reels, all six profiles, by scrolling
-~/gdl/full-sweep.sh   # rarely, ~420 requests. Read its own comment first.
+~/gdl/run-stories.sh      # ~1 min.    DO THIS OFTEN - stories die in 24h
+~/gdl/run-profiles.sh     # ~5 min.    posts, highlights, stories (not reels -- see below)
+~/gdl/run-reels-all.sh    # ~15-20 min. reels, all six profiles, by scrolling
+~/gdl/run-full-sweep.sh   # rarely, ~420 requests. Read its own comment first.
 ```
 
 Fixed-mode entry points around `gdl-cron.sh`/`reels-sync.sh`, so the mode
 never has to be remembered or typed — each just runs its own thing with the
-right flags already set. `profiles.sh` covers every surface gallery-dl's API
+right flags already set. `run-profiles.sh` covers every surface gallery-dl's API
 still reaches, so it is the one to run if you only run one, but it is no
-substitute for `stories.sh` (a story posted and expired between two runs of
-it is simply gone) or `reels-all.sh` (`/api/v1/clips/user/` is blocked --
-see "Reels: the API is blocked" below -- `profiles.sh` silently fails that
+substitute for `run-stories.sh` (a story posted and expired between two runs of
+it is simply gone) or `run-reels-all.sh` (`/api/v1/clips/user/` is blocked --
+see "Reels: the API is blocked" below -- `run-profiles.sh` silently fails that
 one surface every time, by design, until that changes). All four are safe to
 run back-to-back; the `--min-interval` floor makes a repeat a no-op rather
 than a re-fetch.
@@ -62,8 +62,8 @@ redeploy. The archive index re-reads a directory when its mtime changes.
 - `400 Bad Request` on `/api/v1/feed/reels_media/` — the account is behind a
   scraping-warning interstitial; check the browser before anything else.
 
-Long runs: `setsid nohup ~/gdl/profiles.sh >/dev/null 2>&1 &` (or `full-sweep.sh`
-/ `reels-all.sh`) and `tail -f ~/gdl/logs/$(ls -1t ~/gdl/logs | head -1)`.
+Long runs: `setsid nohup ~/gdl/run-profiles.sh >/dev/null 2>&1 &` (or `run-full-sweep.sh`
+/ `run-reels-all.sh`) and `tail -f ~/gdl/logs/$(ls -1t ~/gdl/logs | head -1)`.
 Nothing reaches the archive until a run finishes, so killing one midway is
 safe.
 
@@ -584,7 +584,7 @@ slower by design (real scrolling, not an API call) — both good reasons not
 to run this unattended without deciding that deliberately. Today it is a
 per-profile, by-hand tool only.
 
-For all six ARTMS profiles in one go, `~/gdl/reels-all.sh` just calls
+For all six ARTMS profiles in one go, `~/gdl/run-reels-all.sh` just calls
 `reels-sync.sh` once per profile in `artms_account_links.txt`, same
 reasoning as above — real scrolling, so still by hand. Run 2026-09-03:
 `official_artms` alone has 609 real reels and took ~14 minutes of scrolling;