README.md is stored with CRLF line endings while every other file is LF, so one-line edits show as whole-file diffs

[dajiaohuang]

README.md is stored with CRLF line endings, while every other tracked file is LF. Because of that, normal edit PRs show up as whole-file rewrites.

Evidence on current main (57f05da):

• The README blob is 2,359 lines: 2,355 CRLF and 4 lone LF (L203, L1389, L1570, L1606). The 4 LF lines arrived with recent PRs (Add Darkmoon (GPL-3.0 autonomous pentest platform) #159, Add DomainIntel API #141, Add MetadataRemover.ai to Metadata & File Analysis #175, Add Malwagon to MALWARE #185).
• git ls-files --eol reports i/lf for all 14 other tracked files and i/mixed for README.md.
• PR Add SellToState #190 shows the cost: adding one entry appears as 2,341 insertions / 2,340 deletions. The contributor's editor wrote LF and the diff became the whole file.

Contributors with core.autocrlf=true (the Windows default) will hit this on any README edit, because Git normalizes the committed file to LF while the stored blob is CRLF. This also makes review and merge conflict resolution much harder than the actual change warrants.

Suggested fix, if you want it: normalize README.md to LF to match the rest of the repo, and add a .gitattributes rule such as *.md text eol=lf so it stays consistent. It rewrites every line once, but after that one-line changes produce one-line diffs.