Windows: run_from_args_propagates_find_exit_status compares rtk against a different find — std resolves System32's find.exe before PATH #4610

run_from_args_propagates_find_exit_status (src/cmds/system/find_cmd.rs) builds its oracle with a bare std::process::Command::new("find") and compares its exit code with rtk's:

let argv = ["/definitely/missing/xyz", "-mtime", "+0"];
let expected = std::process::Command::new("find")
    .args(argv)
    .output()
    .map(|o| o.status.code().unwrap_or(1))
    .unwrap_or(127);
let code = run_from_args(&args(&argv), 0).unwrap();
assert_eq!(code, expected);

On Windows the two sides can resolve different programs. std searches the system directories before PATH, so the oracle runs C:\Windows\system32\find.exe — the DOS text-search utility — which rejects /definitely/missing/xyz and exits 2. rtk resolves find through PATH and gets Git's usr\bin\find.exe, which exits 1.

thread 'cmds::system::find_cmd::tests::run_from_args_propagates_find_exit_status' panicked at
src\cmds\system\find_cmd.rs:1528:9:
assertion `left == right` failed
  left: 1
 right: 2

Confirmed directly from PowerShell on that machine: system32\find.exe → 2, Git\usr\bin\find.exe → 1.

Any machine with Git's usr\bin on PATH reproduces it. CI's Windows runner does not, because Git's usr\bin is not on its PATH and both sides then resolve to the DOS find.

Reported twice independently, on two machines and both Windows toolchains, failing the same way on develop:

• refactor(core): make MSYS-safe child argument encoding unforgettable #4103 (comment) and the diagnosis in refactor(core): make MSYS-safe child argument encoding unforgettable #4103 (comment) (x86_64-pc-windows-gnu)
• fix(windows): quote glob patterns passed to MSYS children #4260's test plan (MSVC)

This is the case .claude/rules/cli-testing.md describes under "Machine independence": a test that spawns a real process must not depend on the machine it runs on. Here it is not a tool's wording but a different binary altogether.

Fix direction: build the oracle through rtk's own resolution instead of a bare Command::new("find"), so both sides run the same program. src/core/utils.rs's resolver already honours PATH and PATHEXT.

Not covered elsewhere: #4491 makes two other environment-dependent tests machine independent (copilot_selfheal_test.rs, guard_integration_test.rs) and does not touch this one, and the lex/ stack leaves find_cmd.rs alone.

The other failure those reports mention, stream::test_read_lines_lossy_preserves_lines_after_invalid_utf8, is already tracked as #3730.