windows-compatibility

ISO timestamps cause errors on Windows because colons are illegal in filenames. You must sanitize timestamps using a safeTimestamp utility to replace colons with hyphens before using them in file path generation.

To handle git commands safely across platforms, never use `git -C {path}` due to Windows path issues. Always cd into the repository directory first before executing git commands to ensure consistent behavior.

The best way to concatenate paths for cross-platform compatibility is using `path.join()` or `path.resolve()`. Never assume the current working directory is the repo root; instead, use `git rev-parse --show-toplevel` to find it.

To pass multi-line commit messages safely on Windows, never embed newlines directly in the `-m` flag. Write your commit message to a temporary file and use the git `-F` flag to read from that file instead.

Yes, cross-platform path handling requires checking the current working directory because you should never assume CWD is the repo root. Extract the `TEAM ROOT` from the spawn prompt or run `git rev-parse --show-toplevel` to anchor paths correctly.