Update @github/copilot to 1.0.83-5 (#2516)

* Update Copilot CLI to 1.0.83-5

- Updated the Node.js CLI release pin
- Re-ran code generators
- Formatted generated code

* Fix Java MCP server coverage test

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

* Format Java MCP server coverage test

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix transient Windows .NET timing failures

Avoid surfacing a diagnostic stderr drain timeout after the owned process has exited, and allow Windows shell commands enough time to start before testing runtime timeout cleanup.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Stephen Toub <stoub@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: 3 people

dotnet/src/Client.cs

@@ -762,7 +762,13 @@ private static async Task CleanupCliProcessAsync(Process childProcess, ProcessSt
                         s_stderrPumpShutdownTimeout);
                 }
 
-                AddCleanupError(errors, ex, logger);
+                // Once the owned process has exited, stderr is diagnostic-only. A descendant
+                // can briefly retain the inherited pipe on Windows, but that must not turn a
+                // successful process shutdown into a client cleanup failure.
+                if (!processExited)
+                {
+                    AddCleanupError(errors, ex, logger);
+                }
             }
             catch (Exception ex)
             {

dotnet/src/Generated/Rpc.cs

@@ -28,16 +28,21 @@ public async Task Shell_Exec_With_Timeout_Kills_Long_Running_Command()
         var markerPath = Path.Join(Ctx.WorkDir, $"shell-timeout-{Guid.NewGuid():N}.txt");
         var startedPath = Path.Join(Ctx.WorkDir, $"shell-timeout-started-{Guid.NewGuid():N}.txt");
 
-        // Sleep 30s but timeout at 200ms — runtime should SIGTERM the child before the
+        // Sleep 30s but use a much shorter timeout — runtime should SIGTERM the child before the
         // sleep completes, which means the marker file must NEVER appear within a wait
         // window comfortably greater than the timeout but well under the sleep duration.
+        // Process startup on Windows can exceed 200ms on loaded runners, so match the
+        // platform-specific allowance used by the Rust coverage for this RPC.
+        var timeout = OperatingSystem.IsWindows()
+            ? TimeSpan.FromSeconds(2)
+            : TimeSpan.FromMilliseconds(200);
         var command = OperatingSystem.IsWindows()
-            ? $"echo started>\"{startedPath}\" & for /L %i in (1,1,2147483647) do @rem & echo should-not-exist>\"{markerPath}\""
+            ? $"powershell -NoLogo -NoProfile -Command \"Set-Content -LiteralPath '{startedPath}' -Value started; Start-Sleep -Seconds 30; Set-Content -LiteralPath '{markerPath}' -Value should-not-exist\""
             : $"printf 'started' > '{startedPath}'; sleep 30; printf 'should-not-exist' > '{markerPath}'";
 
         // On Windows, terminating the shell wrapper can briefly leave children alive.
         // Keep this long-running command outside the fixture workspace so cleanup is not blocked by cwd handles.
-        var result = await session.Rpc.Shell.ExecAsync(command, cwd: Path.GetTempPath(), timeout: TimeSpan.FromMilliseconds(200));
+        var result = await session.Rpc.Shell.ExecAsync(command, cwd: Path.GetTempPath(), timeout: timeout);
         Assert.False(string.IsNullOrWhiteSpace(result.ProcessId));
 
         await TestHelper.WaitForConditionAsync(