On Windows, agent-driven tracker body replacements frequently corrupt Markdown through:
- Literal newline escapes such as
`r`n
- Mojibake when replacing non-ASCII content
This may be less common on Linux/macOS due to different shell and UTF-8 defaults.
Please make body edits encoding-safe and verify content after writes. Prefer UTF-8 files over PowerShell string replacement or stdin, and add Windows tests covering newlines and non-ASCII round trips.
Suggested fix: update the Agent Issues agent instructions and operating contract to require UTF-8 body files, write verification, and Windows round-trip tests for newlines and non-ASCII text. Avoid PowerShell string replacement and stdin.
On Windows, agent-driven tracker body replacements frequently corrupt Markdown through:
`r`nThis may be less common on Linux/macOS due to different shell and UTF-8 defaults.
Please make body edits encoding-safe and verify content after writes. Prefer UTF-8 files over PowerShell string replacement or stdin, and add Windows tests covering newlines and non-ASCII round trips.
Suggested fix: update the Agent Issues agent instructions and operating contract to require UTF-8 body files, write verification, and Windows round-trip tests for newlines and non-ASCII text. Avoid PowerShell string replacement and stdin.