Normalize Hermes local provider names

dankclaw/hermes/config.yaml.example

@@ -7,15 +7,18 @@
 # The live directory is bind-mounted into the containers as /data.
 
 model:
-  provider: custom
-  base_url: http://192.168.0.143:52625/v1
+  provider: dankclaw-large
+  base_url: http://192.168.0.143:7770/v1
   api_key: not-needed
   default: frank-default-large
 
 providers:
-  custom:
-    stale_timeout_seconds: 1800
-    request_timeout_seconds: 1800
+  dankclaw-large:
+    api: http://192.168.0.143:7770/v1
+    discover_models: false
+    models:
+      frank-default-large:
+        context_length: 262144
   dankserver-small:
     api: http://192.168.0.235:7770/v1
     discover_models: false

docs/Dankclaw/Hermes.md

@@ -24,9 +24,10 @@ both containers. The tracked, sanitized configuration baseline is
 - Point Hermes at the local model endpoint or an external provider through its provider config.
 - The gateway process exposes one port for chat integration; the exact port is set in the Hermes config (`8090` convention in this repo).
 - The data volume persists skills, memory, and session history.
-- The configured `dankserver-small` provider reaches `http://192.168.0.235:7770/v1`
-  and exposes the `frank-default-small` alias. It is a named provider, so it can
-  coexist with the existing `custom` provider for the large model.
+- Hermes has two named local providers: `dankclaw-large` reaches
+  `http://192.168.0.143:7770/v1` and exposes `frank-default-large`;
+  `dankserver-small` reaches `http://192.168.0.235:7770/v1` and exposes
+  `frank-default-small`.
 - The live `config.yaml` contains secrets and user state and is not committed;
   the tracked example is the sanitized backup of its non-secret settings.