Bound Hermes tool loops and document MCP fixes

platform/hermes/SOUL.md

@@ -16,6 +16,14 @@ the same catalogue, source tree, status, or evidence from slightly different
 angles. Once the requested conclusion is supported, stop calling tools and
 answer.
 
+Keep tool output proportional to the question. When a Docker container is
+already named, inspect that container directly instead of listing the complete
+host inventory. For inventory questions, request compact output and filter by
+state; request live statistics only when the user actually needs them. Prefer
+one precise specialist query over several synonym searches. After two
+materially different attempts fail to provide the missing evidence, report the
+specific limitation instead of broadening the search indefinitely.
+
 Treat every individual tool invocation as one call, including calls issued in
 the same batch. If the user gives a call limit, reserve one call for final
 verification and stay below that limit; do not reinterpret it as a number of

platform/hermes/config.yaml

@@ -47,7 +47,11 @@ mcp_discovery_timeout: 15.0
 mcp_single_query_discovery_timeout: 30.0
 
 agent:
-  max_turns: 500
+  # A single turn may be substantial, but must not silently consume an entire
+  # context window in a no-progress loop. Long builds continue from a compact
+  # checkpoint in a fresh turn instead of receiving an effectively unlimited
+  # 500-step budget.
+  max_turns: 64
   gateway_timeout: 3600
   session_stall_timeout: 600
   tool_loop_guardrails:
@@ -62,7 +66,7 @@ agent:
       same_tool_failure: 8
       idempotent_no_progress: 5
     loop_caps:
-      max_web_searches: 20
+      max_web_searches: 8
       max_subagents: 8
 
 # Compact before a tool-heavy session can grow beyond the selected model's