fix: standardize test mode values to match Unity's naming convention

- Changed default mode from "edit" to "EditMode" in C# code
- Updated Python tool to use "EditMode" and "PlayMode" instead of lowercase variants

Author: msanatan

MCPForUnity/Editor/Tools/RunTests.cs

@@ -20,7 +20,7 @@ public static async Task<object> HandleCommand(JObject @params)
             string modeStr = @params?["mode"]?.ToString();
             if (string.IsNullOrWhiteSpace(modeStr))
             {
-                modeStr = "edit";
+                modeStr = "EditMode";
             }
 
             if (!ModeParser.TryParse(modeStr, out var parsedMode, out var parseError))

MCPForUnity/UnityMcpServer~/src/tools/run_tests.py

@@ -41,8 +41,8 @@ class RunTestsResponse(MCPResponse):
 @mcp_for_unity_tool(description="Runs Unity tests for the specified mode")
 async def run_tests(
     ctx: Context,
-    mode: Annotated[Literal["edit", "play"], Field(
-        description="Unity test mode to run")] = "edit",
+    mode: Annotated[Literal["EditMode", "PlayMode"], Field(
+        description="Unity test mode to run")] = "EditMode",
     timeout_seconds: Annotated[str, Field(
         description="Optional timeout in seconds for the Unity test run (string, e.g. '30')")] | None = None,
 ) -> RunTestsResponse: