Instruction file imported from adrianpothuaud/UTO (.github/instructions/rust-uto.instructions.md). Copyright stays with the author.

UTO Rust Guidance

• Keep the layering intact: env discovers or provisions dependencies, driver manages child processes, and session speaks W3C WebDriver.
• New automation features should fit the existing zero-config model: discover first, provision only when necessary, and keep version pinning explicit.
• Process-management code must preserve clean shutdown semantics across Unix and Windows.
• Prefer extending the shared session abstractions over adding one-off flows in the POC binaries.
• For new public APIs, add Rustdoc and keep error messages actionable.
• For framework-facing workflow features, include structured reporting hooks so users can understand setup, intent resolution, actions, assertions, and driver-level outcomes.
• Keep code clean and testable: prefer small functions/modules and explicit separation of concerns instead of large multi-purpose files.

Validate Rust changes with:

• cargo fmt --all --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace