docs: Hermes creation settings go in the seat's config, not in flags

Hermes's CLI creates a `-c <name> --create-if-missing` session with no
launch flags, then reopens it and refuses any creation flag that differs
from that empty launch. So a model, provider or --max-turns flag fails
even on a new name. The example preset's command now carries none, and
the docs say to set them in each seat's Hermes config.yaml.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/reference/community-harness-examples/hermes/hermes.yaml

@@ -1,11 +1,12 @@
 # Install as $OPENRIG_HOME/community-harnesses/hermes.yaml, with openrig-hermes-launch on the seat's PATH.
 format: 1
 name: hermes
-command: openrig-hermes-launch --provider openrouter --model anthropic/claude-sonnet-4
+command: openrig-hermes-launch    # no model, provider or --max-turns here: they go in the seat's Hermes config.yaml
 maintainer: Your name or team
 limits:
   - resume not declared until reopening a named session, and a missing one, have been checked with a real Hermes
   - closing a seat's pane detaches it; Hermes finishes any accepted turn, and its gateway exits when idle
+  - creation settings (model, provider, max turns) come from the seat's Hermes config.yaml, not from flags
   - no guidance, skills or startup files are placed
   - needs-input and approval prompts are read from the screen only
 names_conversation: true

docs/reference/community-harness-examples/hermes/openrig-hermes-launch

@@ -4,8 +4,9 @@
 #   - a new launch (OPENRIG_CONVERSATION set): Hermes creates the session titled with that name;
 #   - a resume (OPENRIG_RESUME_REF set): Hermes reopens that session, and never creates one. A name that matches nothing
 #     ends with Hermes's own "No session found" error, so a gone conversation isn't replaced by a new one.
-# Arguments after the launcher's name (a provider, model or --max-turns, say) go only to a new session: Hermes fixes them
-# when the session is created, and refuses them on a resume when they differ from that session's own.
+# Put the model, provider and max turns in the seat's Hermes config.yaml, not on the command line. Hermes v0.22.4's CLI
+# creates a `-c <name> --create-if-missing` session with no launch flags, then reopens it and refuses any creation flag
+# that differs, so such flags fail even on a new name. Other arguments go only to a new session, never to a resume.
 set -eu
 
 hermes="${OPENRIG_HERMES:-hermes}"

docs/reference/community-harness-presets.md

@@ -107,8 +107,10 @@ For a reported conversation, OpenRig also says so plainly when:
 [`community-harness-examples/hermes/`](community-harness-examples/hermes/) has a preset and a small launcher for Hermes
 Agent's CLI.
 - **The launcher:** it creates the session OpenRig named (`-c <name> --create-if-missing`), and on a resume reopens it
-  without `--create-if-missing`, with its own Hermes home per seat. The preset's own arguments (a provider, model or
-  `--max-turns`) go only to a new session: Hermes fixes them at creation and refuses them on a resume. A name that matches nothing ends with Hermes's own
+  without `--create-if-missing`, with its own Hermes home per seat.
+- **Settings go in the seat's Hermes `config.yaml`, not in flags:** Hermes's CLI creates a named session with no launch
+  flags and then reopens it, refusing any creation flag (model, provider, `--max-turns`) that differs. So the preset's
+  command carries none, and each seat's `config.yaml`, in its Hermes home, sets them. A name that matches nothing ends with Hermes's own
   "No session found" error.
 - **The preset:** it declares `names_conversation` but not `resume`, until reopening a named session, and a missing one,
   have been checked with a real Hermes.