docs: one knowledge base for both workloads

- docs/index.md: LLM Fleet section (all 34 pages linked), merge note,
  See Also now internal
- docs/LLM/index.md: retitled, dangling [[Dankserver]]/[[Dankclaw]]
  links fixed, sibling section replaced with internal links
- docs/LLM/deployment.md: rewritten for the unified deploy flow,
  manual-update paths point at the merged checkout, incident history
  kept intact
- Deployment Flow / Dankclaw Stack / Gitea: stale vllmScripts
  references and retired-topology notes updated to the 2026-08-22
  state
- Historical docs (frank-redo, PP deployment, FastFlowLM) keep their
  dated runbook paths as-is (records of retired topologies)

docs/Architecture/Deployment Flow.md

@@ -1,6 +1,8 @@
 # Deployment Flow
 
-Deployment mirrors the `vllmScripts` repository: git is the single source of truth, and a `deploy.sh` script moves committed changes to the target hosts over SSH.
+Git is the single source of truth. A `deploy.sh` script moves committed
+changes to the target hosts over SSH. One run per target covers both
+workloads on that host: the podman stack and the LLM service.
 
 ## Workflow
 
@@ -16,8 +18,9 @@ graph LR
 1. Edit files locally in this repository.
 2. Commit and push.
 3. Run `./scripts/deploy.sh <dankclaw|dankserver>`.
-4. The script pulls the repo on the target and restarts the podman stack.
-5. It verifies service health after restart.
+4. The script pulls the repo on the target and restarts the podman stack
+   and the LLM service.
+5. It verifies service health after restart (homepage and LLM endpoint).
 
 ## Deploy Script
 
@@ -54,4 +57,4 @@ The suite validates compose YAML, env consistency, Caddyfiles, docs completeness
 
 - [[Storage Policy]]
 - [[Testing Policy]]
-- [vllmScripts deployment docs](../../../vllmScripts/docs/deployment.md) — the model this follows
+- [LLM deployment docs](../LLM/deployment.md) — the LLM half of the same flow