CRLF issue with StrReplaceFile

What version of Kimi Code CLI is running?

1.35.0

Which open platform/subscription were you using?

/login

Which model were you using?

kimi k2.6

What platform is your computer?

MacOS

What issue are you seeing?

When Kimi CLI edits files with CRLF line endings, a small StrReplaceFile edit can rewrite the whole file with LF line endings, causing large unrelated diffs.

What steps can reproduce the bug?

1. Create a repo with Git text normalization disabled:

mkdir /tmp/kimi-crlf-repro
cd /tmp/kimi-crlf-repro
git init
git config core.autocrlf false
printf '* -text\n' > .gitattributes
printf 'const a = 1;\r\nconst b = 2;\r\n' > test.ts
git add .
git commit -m 'init'

2. Run Kimi CLI and ask it to edit one line:

kimi --work-dir /tmp/kimi-crlf-repro --print --prompt 'Read test.ts and change const b = 2; to const b = 3;'

3. Check the diff and bytes:

git diff -- test.ts
python - <<'PY'
from pathlib import Path
raw = Path("test.ts").read_bytes()
print(repr(raw))
print("CRLF:", raw.count(b"\r\n"))
print("bare LF:", raw.count(b"\n") - raw.count(b"\r\n"))
PY

What is the expected behavior?

Kimi CLI should preserve the original line endings when reading and editing files, so the diff only contains the real content change.
The content change is small, but the file may be rewritten from CRLF to LF, producing noisy line-ending churn.

Additional information

No response

Start by locating the StrReplaceFile implementation and reproduce the issue with the commands in this report, especially the byte-count check for test.ts. Trace how the file is read and written when changing one line. Done means the original CRLF endings remain and git diff shows only the requested content change.