Fix active Node and replay E2E flakes

[roji]

July CI runs exposed three hermetic test failures: arbitrary Node E2E tests exhausted the fixed Windows timeout budget, the two .NET target-framework suites competed on the same Windows runner, and a repurposed Rust metadata test still selected an unrelated compaction snapshot.

This change:

• gives Node tests and hooks a 60-second budget on Windows while retaining 30 seconds elsewhere, covering both default and in-process transports;
• runs .NET net8.0 and net472 coverage in separate parallel Windows matrix jobs, isolating each CLI/replay-proxy fixture graph without extending the workflow critical path;
• gives the Rust processing/context metadata test a dedicated snapshot matching its RUST_CONTEXT_INFO prompt, while preserving the shared compaction fixture used by Python.

Validation included workflow YAML and shell syntax checks, Rust nightly formatting, Rust test-target compilation, snapshot parsing and preservation checks, and commit whitespace checks. Full local E2E execution was blocked because the configured package-feed proxy returned 404 for @github/copilot@1.0.76-5.

[github-actions]

SDK Consistency Review ✅

This PR makes CI and test infrastructure fixes only — no SDK API surface changes:

• Node.js (vitest.config.ts): Adjusts test timeout for Windows (60s vs 30s)
• .NET (workflow YAML): Adds net472 matrix job alongside net8.0 for Windows isolation
• Rust (rpc_session_state.rs): Renames a test function to match its new dedicated snapshot
• Snapshot (should_report_processing_and_context_metadata.yaml): New fixture for the renamed Rust test

None of these changes affect public API methods, signatures, or behavior. No cross-SDK consistency concerns.

Generated by SDK Consistency Review Agent for #2186 · sonnet46 16.1 AIC · ⌖ 6.84 AIC · ⊞ 6.5K · ◷

[Copilot]

Pull request overview

Note

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Reduces CI flakiness across Node/.NET/Rust E2E coverage by adjusting timeouts, isolating Windows .NET target frameworks into separate jobs, and aligning a Rust E2E snapshot with its actual prompt/expectations.

Changes:

• Adjust Node Vitest integration timeouts to allow longer execution on Windows while keeping other OS budgets unchanged.
• Split .NET net8.0 and net472 runs into distinct Windows matrix jobs via a framework dimension and pass --framework to dotnet test.
• Add a dedicated Rust snapshot and rename the Rust E2E test to match the new snapshot/intent.

Show a summary per file

File	Description
nodejs/vitest.config.ts	Introduces OS-specific test/hook timeouts to reduce Windows E2E flakiness.
.github/workflows/dotnet-sdk-tests.yml	Adds a framework matrix dimension and runs dotnet test with explicit framework selection to avoid Windows runner contention.
rust/tests/e2e/rpc_session_state.rs	Renames the Rust E2E test to match the new processing/context metadata behavior/snapshot.
test/snapshots/rpc_session_state/should_report_processing_and_context_metadata.yaml	Adds a dedicated snapshot aligned with the Rust context metadata test prompt/expected output.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Lite

[Copilot]

🟢 Ready to approve

The focused changes consistently address the three documented CI flakes without introducing unresolved issues.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0 new
• Review effort level: Balanced

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.