MCP-Client fuer HTTP-Server: externe Werkzeuge durch dieselben Pruefstellen (#197)

- Core/Mcp/McpClient: Streamable HTTP (MCP 2025-06-18) - initialize, tools/list
  with paging, tools/call; answers as JSON or event stream; session kept and
  opened again when the server forgets it; answers capped at 4 MB.
- McpServerTool: one server is one tool (mcp_<id>); its remote tools are the
  operations, so rights, preflight, staging, lead approvals, votes, audit and
  budget apply. On approval by default unless the human trusts an operation;
  reads foreign content; the server's descriptions are cut short and marked.
- McpConnections: registers, refreshes every 15 minutes, follows changes.
- InstanceConfig.mcpServers with protected headers; /api/mcp-servers;
  settings card "External MCP servers"; tool catalog includes the servers.
- stdio servers are not part of this (sandbox runner, separate step).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

src/ClawdDotNet.Core/Config/InstanceConfig.cs

@@ -159,6 +159,10 @@ public sealed class InstanceConfig
     [JsonPropertyName("fileHistory")]
     public Files.FileHistorySettings FileHistory { get; set; } = new();
 
+    /// <summary>#197: External MCP servers whose tools the agents may use — set up by a human only.</summary>
+    [JsonPropertyName("mcpServers")]
+    public List<Mcp.McpServerConfig> McpServers { get; set; } = new();
+
     /// <summary>#699: When a change in the units' costs is reported.</summary>
     [JsonPropertyName("costWatch")]
     public Accounting.CostWatchSettings CostWatch { get; set; } = new();