Rebase on newer runtime and harden Rust lifecycle E2E

Rebased this lifecycle/reliability branch onto current main, which now includes
CLI 1.0.84-4 and additional in-process E2E stabilization. Retried the exact
Rust/.NET Windows in-process cells that previously exposed native
AccessViolation/SIGSEGV crashes; the newer runtime still reproduces the
blocker, so keep those cells excluded and update the workflow comments with
that fresh evidence.

The full retry also exposed two small Rust Windows lifecycle fixture issues
unrelated to the FFI shutdown fix: the stdio job-object containment test was
running under the in-process matrix, and the PID-file waiter accepted an empty
file before the fixture had finished writing the child process id. Skip that
stdio-only test for in-process runs and wait for a parseable PID instead.

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

Author: SteveSandersonMS

.github/workflows/dotnet-sdk-tests.yml

@@ -196,7 +196,8 @@ jobs:
           # ordinary connection I/O -- unrelated to shutdown/disposal, and independently
           # matched by a SIGSEGV in the Rust SDK's own Windows in-process CI in the same
           # PR. That rules out an SDK-side binding bug; tracked upstream at
-          # github/copilot-agent-runtime#18990. Re-add windows-latest here once resolved.
+          # github/copilot-agent-runtime#18990. Retrying after rebasing onto CLI 1.0.84-4
+          # reproduced the same blocker, so re-add windows-latest here once resolved.
     runs-on: ${{ matrix.os }}
     # A hung test used to run until the runner died (~50 min) and the dying
     # runner never uploaded its logs, so the failures were undiagnosable.

.github/workflows/rust-sdk-tests.yml

@@ -224,8 +224,9 @@ jobs:
         # shared runtime cdylib rather than anything fixable from this SDK's
         # FFI bindings. An identical crash class (AccessViolationException)
         # was independently reproduced on Windows in-process in the .NET SDK
-        # in the same PR, ruling out a per-language binding bug. Tracked
-        # upstream at github/copilot-agent-runtime#18990; re-add
+        # in the same PR, ruling out a per-language binding bug. Retrying
+        # after rebasing onto CLI 1.0.84-4 reproduced the same blocker.
+        # Tracked upstream at github/copilot-agent-runtime#18990; re-add
         # windows-latest here once that's resolved. See github/copilot-sdk#2525.
         os: [ubuntu-latest, macos-latest]
     runs-on: ${{ matrix.os }}

rust/tests/e2e/client_lifecycle.rs

@@ -3,6 +3,8 @@ use github_copilot_sdk::CliProgram;
 use github_copilot_sdk::SessionLifecycleEventType;
 use serde_json::json;
 
+#[cfg(windows)]
+use super::support::skip_inprocess;
 use super::support::{wait_for_lifecycle_event, with_e2e_context};
 
 #[tokio::test]
@@ -144,6 +146,10 @@ async fn dispose_disconnects_client_and_disposes_rpc_surface_drop() {
 #[cfg(windows)]
 #[tokio::test]
 async fn abrupt_host_termination_still_kills_cli_via_job_object() {
+    if skip_inprocess("job-object containment is specific to the stdio CLI child process") {
+        return;
+    }
+
     with_e2e_context(
         "client_lifecycle",
         "abrupt_host_termination_still_kills_cli_via_job_object",
@@ -226,14 +232,17 @@ async fn abrupt_host_termination_still_kills_cli_via_job_object() {
 #[cfg(windows)]
 async fn wait_for_pid_file_windows(path: &std::path::Path) -> u32 {
     super::support::wait_for_condition("host-crash fixture CLI pid file", || async {
-        path.exists()
+        std::fs::read_to_string(path)
+            .ok()
+            .and_then(|contents| contents.trim().parse::<u32>().ok())
+            .is_some()
     })
     .await;
-    std::fs::read_to_string(path)
-        .expect("read host-crash fixture CLI pid")
+    let contents = std::fs::read_to_string(path).expect("read host-crash fixture CLI pid");
+    contents
         .trim()
         .parse()
-        .expect("parse host-crash fixture CLI pid")
+        .unwrap_or_else(|err| panic!("parse host-crash fixture CLI pid from {contents:?}: {err}"))
 }
 
 #[cfg(windows)]