refactor(plugin): preserve Windows filenames in native helpers

[kmbroai]

Summary

Preserve Windows filenames when replacing Python path handling with TypeScript. Helpers receive original UTF-16 arguments, environment values, directory names, and paths, including lone surrogates.

Changes

• Use std::fs::read_dir and cached entry types for one typed directory enumerator, preserving raw names and numeric Windows errors.
• Delegate absolute paths to Rust std::path::absolute, preserving native errors and the existing empty-input result. Normalize verbatim paths below their drive or share root, including doubled separators and parent traversal.
• Use the existing handles for metadata, reads, and writes, and Rust create_dir_all for recursive directory creation. Retain raw process-value transport.
• Clear the Windows error state before resolving empty input; retain the compatibility branch because the public Rust path API rejects empty paths before reaching Win32.
• Use Rust-created surrogate fixtures to test the adapter. A held file-sharing guard verifies enumeration succeeds while a data read fails.

Testing

• Both MSVC-target Clippy checks, Rust formatting, CI-tool compilation, TypeScript formatting, Ruff, portable source checks, and all nine checker tests passed.
• Twelve adapter normalization cases passed on Node 22.13.0, including doubled separators under drive and UNC roots.
• Windows CI runs the actual filesystem and process proofs on x64 and arm64 with Node 20 and 22. The proofs cover recursive creation, existing-file errors, and empty-input error-state independence.

Risk and rollout

Stacked on #797. Adds native operations without changing command routing or public CLI syntax. Junction directory entries now carry Rust's directory and symbolic-link flags; the following resolver still excludes their traversal. Sharing restrictions do not block attribute-only requests, so the proof checks a data read without changing product stat access.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	✅ Completed 2026-09-08T22:32:34.452123Z	ec4dd08	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[mldangelo-oai]

Re-reviewed the exact current head after the latest fixes. The four earlier threads are resolved. I found one remaining Windows path correctness bug and two nonblocking simplifications.

[mldangelo-oai]

Re-reviewed exact head d8951fc. Recursive directory creation is now one std::fs::create_dir_all call through the native error adapter. The retained empty-path branch is justified by pinned Rust 1.97 rejecting empty input before Win32, with LastError cleared before the compatibility call. All prior threads are resolved and all required checks pass.