docs+AGENTS: model ids officially frank-archon/frank-dragoon/frank-zealot (services keep old names)

AGENTS.md

@@ -286,9 +286,13 @@ deletes the unit file from `/etc/systemd/system/`, not just the symlink.
 The harness reaches the fleet through `.omp/agent/models.yml` in the
 operator's home — `/home/blank/.omp/agent/models.yml` on the dev box, which is
 where the harness runs; there is no copy on the servers. Each provider is one
-HOST:PORT; each model `id` is the served alias: `frank-primary` →
+HOST:PORT; each model `id` is the served alias. **Official model ids are
-`192.168.0.235:7770`, `frank-large` → `192.168.0.143:7770`, `frank-secondary` →
+the StarCraft unit names (2026-10-08):** `frank-archon` →
-`modelRoles`.
+`192.168.0.235:7770`, `frank-dragoon` → `192.168.0.143:7770`,
+`frank-zealot` → `192.168.0.143:7771` (was `frank-primary`, `frank-large`,
+`frank-secondary` — the SERVICES, units, scripts, env files and runbooks
+keep the old names; the rename is model ids in `models.yml`/`config.yml`
+and the homepage model cards). `modelRoles`.
 
 Resolution rules: the default model resolves as a `defaultProvider` +
 `defaultModel` pair (the provider must serve the model); a subagent override
@@ -475,7 +479,7 @@ carry over: ≥256 px probe images or the model answers "video", and only the
 OpenAI `image_url` content part reaches the model.
 
 **Compaction hub**: `models.yml` routes `compactionModel` for
-`frank-primary`, `frank-large` and `frank-secondary` here — 200,704 is the
+`frank-archon`, `frank-dragoon` and `frank-zealot` (the 3090 endpoint) here — 200,704 is the
 only window in the fleet that fits a worst-case compaction input (~170k
 tokens). With `--parallel 2` a compaction request no longer serializes behind
 a live generation (the Gemma4 era's `--parallel 1` law).

serverAppConfigs-docs/Agent/OMP Harness.md

@@ -13,6 +13,14 @@ registry; single source of truth — there is no copy on the servers) and
 `~/.omp/agent/config.yml` (roles, compaction, global samplers). Nothing in
 this file is repo-managed; edits are harness-side only.
 
+**Model ids are the StarCraft unit names (official 2026-10-08):**
+`frank-archon` (dankserver :7770, radiance), `frank-dragoon` (dankclaw
+:7770, flash-server), `frank-zealot` (dankclaw :7771, the 3090
+compaction hub) — formerly `frank-primary`, `frank-large`,
+`frank-secondary`. The SERVICES keep the old names (units, scripts, env
+files, runbook pages); pages written in the old era name the service,
+the harness names the model.
+
 ## Compaction chain arithmetic (verify before ANY window change)
 
 When a fleet endpoint's context grows past its harness-declared window, OMP

serverAppConfigs-docs/Infrastructure/Homepage.md

@@ -198,6 +198,13 @@ state — the only animation left is the speaking-voice pulse. The result
 is flat navy panels on crisp 1px borders: same Protoss direction, half
 the pixels.
 
+**Model ids official (2026-10-08):** the card ids `frank-zealot`,
+`frank-dragoon`, `frank-archon` are now the harness's official model ids
+in `models.yml`/`config.yml` (see [[OMP Harness]]); the
+systemd services keep the `frank-primary`/`frank-large`/
+`frank-secondary` names. Homepage, docs page and harness now agree on
+one name per model.
+
 ## Design decision — 2026-08-22
 
 The live up/down check runs server-side. A checker on Dankclaw probes each backend and writes a same-origin `status.json`. The page fetches only that file and renders the badges. The browser never calls a backend directly. The checker runs as a systemd timer every 3 minutes.