fix(hermes): align config.yaml required_env with executor (HERMES_API_KEY)

The hermes config required NOUS_API_KEY but the executor
(workspace-template/adapters/hermes/executor.py from PR #49) checks
HERMES_API_KEY and OPENROUTER_API_KEY. A workspace created from this
template would have the provisioner block on a missing NOUS_API_KEY
even when HERMES_API_KEY was set, or pass provisioning but fail at
executor init. .env.example already documents HERMES_API_KEY.

Fix: rename the required_env entry to HERMES_API_KEY and update the
comments to match the executor's actual fallback order (HERMES_API_KEY
first, OPENROUTER_API_KEY second).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

workspace-configs-templates/hermes/config.yaml

@@ -15,10 +15,11 @@ runtime_config:
   model: nous-hermes-3-70b
 
   # Authentication — supply ONE of these env vars (checked in order):
-  #   NOUS_API_KEY       — Nous Research portal (https://portal.nousresearch.com)
-  #   OPENROUTER_API_KEY — OpenRouter as a Nous proxy (useful for dev / cost control)
+  #   HERMES_API_KEY     — Nous Research portal key (https://portal.nousresearch.com)
+  #   OPENROUTER_API_KEY — OpenRouter as a Hermes proxy (useful for dev / cost control)
+  # Both are checked by adapters/hermes/executor.py; at least one must be set.
   required_env:
-    - NOUS_API_KEY
+    - HERMES_API_KEY
 
   # 0 = no timeout; increase for long-running research tasks.
   timeout: 0