rename frank-small → frank-secondary (Dankclaw llama.cpp :7771)

Cross-cutting rename of the current llama.cpp endpoint on the RTX 3090
(port 7771) from frank-small to frank-secondary:

- Service trio: scripts/{frank-small.env,frank-small.service,
  serve-frank-small.sh,download-frank-small.sh} → frank-secondary.*
- Test: tests/frank_small_unit.bats → tests/frank_secondary_unit.bats
- Runbooks: serverAppConfigs-docs/LLM/frank-small-*.md →
  frank-secondary-*.md (9 files); the FreeToken runbook stays
  freetoken-frank-small.md (it documents the retired CUDA-era service)
- Identifiers: FRANK_SMALL→FRANK_SECONDARY, llm_small→llm_secondary,
  LLM_SMALL_*→LLM_SECONDARY_*, deploy_llm_small→deploy_llm_secondary
- Historical references to the OLD frank-small (FreeToken/CUDA on the
  3090, and the Dankserver service that became frank-medium) are
  preserved verbatim — they describe what the service was called
  at the time.

serverAppConfigs-docs/LLM/deployment.md

@@ -21,7 +21,7 @@ SearXNG, Caddy, or another container service does **not** restart inference.
 |---|---|---|---:|
 | Dankserver | `dank@dankserver` | `frank-medium` | 7770 |
 | Dankclaw | `dank@dankclaw` | `frank-large` | 7770 |
-| Dankclaw | `dank@dankclaw` | `frank-small` | 7771 |
+| Dankclaw | `dank@dankclaw` | `frank-secondary` | 7771 |
 
 ## Scoped workflow
 
@@ -53,13 +53,13 @@ on the selected host. The following files select the corresponding service:
   checkout, so any file there changes deployed state.
 - `scripts/frank-large.env`, `frank-large.service`, and
   `serve-frank-large.sh` select `frank-large` on Dankclaw.
-- `scripts/frank-small.env`, `frank-small.service`, and
-  `serve-frank-small.sh` select `frank-small` on Dankclaw.
+- `scripts/frank-secondary.env`, `frank-secondary.service`, and
+  `serve-frank-secondary.sh` select `frank-secondary` on Dankclaw.
 - Documentation, tests, deployment tooling, and unrelated container changes
   do not select any inference service.
 
 The target-side `scripts/deploy-remote.sh` installs the selected service.
-`frank-large` and `frank-small` are **root units**: the handler relinks the
+`frank-large` and `frank-secondary` are **root units**: the handler relinks the
 repo file into `/etc/systemd/system/` (`relink_unit`), reloads systemd,
 enables it and restarts it. `frank-medium` is a **rootless Quadlet**: the
 handler retires its predecessors (the replica Quadlets and the retired llama
@@ -67,7 +67,7 @@ root unit), stops the service's own unit, waits for the published port to
 clear, installs the `.container` and restarts the generated unit. Each
 handler then waits on that service's health endpoint —
 `http://127.0.0.1:7770/health` for frank-large and frank-medium,
-`http://127.0.0.1:7771/health` for frank-small. The wait budget is 20 minutes
+`http://127.0.0.1:7771/health` for frank-secondary. The wait budget is 20 minutes
 because cold model loads are slow. A failed handler does not advance its
 per-service state.
 
@@ -76,7 +76,7 @@ per-service state.
 The root units point into the stable target checkout:
 ```text
 /home/dank/serverAppConfigs/scripts/frank-large.service
-/home/dank/serverAppConfigs/scripts/frank-small.service
+/home/dank/serverAppConfigs/scripts/frank-secondary.service
 ```
 `frank-medium` is a Quadlet under `dankserver/frank-medium/quadlet/`
 (`frank-medium.container`) rather than a unit in `scripts/`.
@@ -110,7 +110,7 @@ change in that service's inputs.
 
 If the LLM handler fails after the target pull:
 
-1. Inspect `journalctl -u frank-large -n 200` or `journalctl -u frank-small
+1. Inspect `journalctl -u frank-large -n 200` or `journalctl -u frank-secondary
    -n 200` (root units), or `journalctl --user -u frank-medium -n 200`
    (rootless Quadlet).
 2. Confirm the model files, the runtime binary and (for frank-medium) the
@@ -120,13 +120,13 @@ If the LLM handler fails after the target pull:
    ```bash
    ./scripts/deploy.sh dankserver --service frank-medium
    ./scripts/deploy.sh dankclaw --service frank-large
-   ./scripts/deploy.sh dankclaw --service frank-small
+   ./scripts/deploy.sh dankclaw --service frank-secondary
    ```
 4. Verify the matching health endpoint before declaring recovery.
 
 Do not stop the other host's inference service during recovery. The two
 Dankclaw endpoints are independent processes on different devices: restarting
-frank-large does not disturb frank-small, and the reverse holds too — with one
+frank-large does not disturb frank-secondary, and the reverse holds too — with one
 exception worth knowing, that the deployer waits for port 7770 to be released
 before it starts the replacement container. For benchmark work, follow the
 separate stop/benchmark/restart procedure in [[Testing Policy]] and the