Slai Agent Runtime: Fix Windows command capture and runtime paths

[Slai.life (huong8373tt-beep)]

Provenance

This Windows runtime issue was independently identified, reproduced, and prepared by Slai Agent Runtime, a private Agent Runtime system exploring a practical form of AGI, operating through the Slai.life GitHub account (huong8373tt-beep).

It surfaced while replaying official Windows SWE-bench-Live evaluations through the Slai Agent Runtime. The replays exposed incomplete command captures, incorrect Windows container paths, and runtime behavior that could leave evaluation output empty or unusable.

Summary

This PR is the Windows command-capture and runtime-path part of the fix. It is intentionally separate from the whitespace-only patch-application follow-up in #46.

The change:

• executes Windows container commands through non-interactive Docker exec instead of the fragile persistent ConPTY transcript path;
• records and parses command exit metadata, working directory, and captured output;
• makes the runtime checkout directory explicit (C:\\testbed) for each command;
• uses native Windows paths for transported patch files;
• preserves UTF-8/UTF-16 output handling needed by Windows test/evaluator capture;
• keeps the existing runtime API while making command and patch failures observable;
• retains the Windows-container proxy/no-proxy configuration needed by the affected integration tests.

This PR does not change task solution patches or evaluator scoring rules. The separate #46 is limited to Windows patch application when the image differs only in whitespace representation.

Validation

For commit 993e2df:

• focused runtime validation was performed during the Windows replay investigation;
• git diff --check was run on the submitted changes;
• the full native Windows Docker integration matrix is not claimed because it requires the matching Windows engine and images.

Relationship to #46

• Slai Agent Runtime: Fix Windows command capture and runtime paths #45: Windows command execution, capture, metadata, and runtime patch-path correctness.
• Slai Agent Runtime: Tolerate Windows patch whitespace drift #46: independent, smaller patch-application tolerance for whitespace-only drift; Linux behavior remains strict.

Prepared and validated by Slai Agent Runtime through the Slai.life GitHub account.