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/Operations/Fleet Audit and Posture.md

@@ -217,7 +217,7 @@ done
 ```
 
 Ground truth (verify, don't assume — IPs can move): 192.168.0.143 = dankclaw
-= AI stack + `frank-large` :7770 + `frank-small` :7771 (RTX 3090 + Strix
+= AI stack + `frank-large` :7770 + `frank-secondary` :7771 (RTX 3090 + Strix
 Halo iGPU); 192.168.0.235 = dankserver = media stack + `frank-primary`
 :7770 (2× R9700). Repo dirs + live hostnames agree; the deploy tooling is
 hostname-anchored (`ssh dankclaw`/`ssh dankserver` via `~/.ssh/config`), so

serverAppConfigs-docs/Operations/Fleet Ops Playbook.md

@@ -12,7 +12,7 @@ timestamp: 2026-10-05T00:00:00-07:00
 
 Use when `:7770`/`:7771` gives **connection refused** (not a timeout) and the
 service was not crashed. Applies to `frank-medium` (dankserver, root unit),
-`frank-small` (dankclaw, root unit), `frank-large` (dankclaw, rootless
+`frank-secondary` (dankclaw, root unit), `frank-large` (dankclaw, rootless
 Quadlet).
 
 **1. Classify the stop before touching anything**
@@ -103,7 +103,7 @@ the sudo journal names who and when: `journalctl -b | grep sudo`.
 ## Scratch vLLM boot on a fleet GPU host — stop-first law
 
 Any scratch/experimental vLLM container on a host that also runs a production
-LLM service (`frank-primary`, `frank-large`, `frank-small`) MUST stop the
+LLM service (`frank-primary`, `frank-large`, `frank-secondary`) MUST stop the
 production unit first, and the window script must verify it. Two independent
 failure modes if skipped:
 

serverAppConfigs-docs/Operations/Payload and Disk Reclaim.md

@@ -64,7 +64,7 @@ done
 Then **read every hit**; do not count them. Most are benign (comments,
 retired fetch-script destinations, `retire_*_quadlet` helpers that move a
 quadlet not a model) — but on Dankclaw this check found a live bug:
-`serve-frank-small.sh`'s `: "${MODEL_DIR:=...}"` fallback still pointed at a
+`serve-frank-secondary.sh`'s `: "${MODEL_DIR:=...}"` fallback still pointed at a
 payload retired a week earlier. The env file always overrode it, so it was
 invisible; a missing env file would have produced a "missing asset" naming a
 model that no longer exists.
@@ -99,7 +99,7 @@ active).
 ## 5. Verify, then report — and do not purge
 
 ```sh
-systemctl is-active frank-large frank-small
+systemctl is-active frank-large frank-secondary
 curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:7770/health
 ```