Several paths misbehaved when ADK was imported or run on Windows: drive-letter paths were split at the wrong colon (including for paths that did not exist yet), text writes could rewrite explicit newlines, telemetry detection assumed POSIX separators, and the Bash tool imported the POSIX-only resource module at import time. This splits eval selectors from the right while preserving drive paths, writes text with exact newline handling, normalizes telemetry paths before matching, and imports the Bash tool safely on Windows with an explicit POSIX-only error after confirmation.
Co-authored-by: George Weale <gweale@google.com>
PiperOrigin-RevId: 952417974