feat: make --strict-mcp-config configurable via settings

[shahartaite-talon]

Summary

• Adds a strict_mcp_config boolean setting (default true) that controls whether --strict-mcp-config and --mcp-config flags are passed to Claude Code
• When strict_mcp_config: false is set in the app settings JSON, both flags are omitted — allowing Tolaria to work in environments where Claude Code has an enterprise managed-settings.json (which rejects these flags)
• Current behavior is fully preserved when the setting is absent or true

Problem

Organizations using Claude Code with enterprise-managed settings (~/.claude/managed-settings.json) cannot use Tolaria's AI features because Claude Code rejects --strict-mcp-config and --mcp-config with:

"You cannot use --strict-mcp-config when an enterprise MCP config is present"
"You cannot dynamically configure MCP servers when an enterprise MCP config is present"

Changes

• src-tauri/src/settings.rs — Added strict_mcp_config: Option<bool> to the Settings struct
• src-tauri/src/claude_cli.rs — Reads the setting and passes it to the invocation layer
• src-tauri/src/claude_invocation.rs — Conditionally applies --strict-mcp-config and --mcp-config flags based on the setting; adds test for the disabled case
• docs/ARCHITECTURE.md — Documents the configurable behavior

Usage

Add to settings.json (macOS: ~/Library/Application Support/com.tolaria.app/settings.json):

{
  "strict_mcp_config": false
}

Test plan

• New test agent_args_omit_strict_mcp_config_when_disabled verifies both flags are absent when disabled
• All existing tests pass with strict_mcp_config: true (default behavior unchanged)
• Manually verified in enterprise environment with managed-settings.json

🤖 Generated with Claude Code