fix: standardize file parameter naming across all tools

- Change `relevant_files` to `files` in debug_issue tool
- Change `reference_files` to `files` in think_deeper tool
- Now all tools consistently use `files` parameter name
- Fix cross-platform test for Windows path separators
- Update README to reflect consistent parameter naming

This improves API consistency and reduces confusion when using different tools.

🤖 Generated with [Claude Code](https://claude.ai/code)

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

tools/debug_issue.py

@@ -22,7 +22,7 @@ class DebugIssueRequest(ToolRequest):
     error_context: Optional[str] = Field(
         None, description="Stack trace, logs, or additional error context"
     )
-    relevant_files: Optional[List[str]] = Field(
+    files: Optional[List[str]] = Field(
         None, description="Files or directories that might be related to the issue"
     )
     runtime_info: Optional[str] = Field(
@@ -60,10 +60,10 @@ class DebugIssueTool(BaseTool):
                     "type": "string",
                     "description": "Stack trace, logs, or additional error context",
                 },
-                "relevant_files": {
+                "files": {
                     "type": "array",
                     "items": {"type": "string"},
-                    "description": "Files that might be related to the issue",
+                    "description": "Files or directories that might be related to the issue",
                 },
                 "runtime_info": {
                     "type": "string",
@@ -115,8 +115,8 @@ class DebugIssueTool(BaseTool):
             )
 
         # Add relevant files if provided
-        if request.relevant_files:
-            file_content, _ = read_files(request.relevant_files)
+        if request.files:
+            file_content, _ = read_files(request.files)
             context_parts.append(
                 f"\n=== RELEVANT CODE ===\n{file_content}\n=== END CODE ==="
             )