windows-compatibility

Windows filenames cannot contain colons, so ISO 8601 timestamps like 2026-03-15T05:30:00Z are illegal. Use a safeTimestamp() utility that replaces colons with hyphens, producing 2026-03-15T05-30-00Z, and centralize it instead of inlining replacements.

git -C is unreliable with Windows paths containing backslashes, spaces, or drive letters. Instead, change directory first with cd and then run git commands, and check git diff --cached --quiet before committing to avoid empty commits.

Windows and macOS filesystems are case-insensitive, so lowercase both paths before comparing with startsWith or equality checks. Linux is case-sensitive, so do not lowercase there; gate the behavior on process.platform being win32 or darwin.

Embedding backtick-n newlines in git commit -m fails silently in PowerShell. Write the message to a temporary file and commit with git commit -F $msgFile, then delete the temp file.

Do not lowercase paths on Linux, where the filesystem is case-sensitive and /Home/ and /home/ are different directories. Case-insensitive comparison only applies to Windows and macOS, typically for security checks like path traversal prevention.