.editorconfig verbatim carry mixes line-ending governance with a large C#-only style block

[ptr727]

Problem

.editorconfig is a mandatory verbatim carry (per AGENTS.md "Files and Sections Derived Repos Must Carry Verbatim"), justified by its per-extension line-ending rules - the thing that prevents LF/CRLF drift. But the file also carries ~160 lines of [*.cs] + ReSharper style rules that are meaningless in a non-.NET repo. "Carry verbatim" then conflicts with the doc's own "write docs/config in the current state" / drop-what-doesn't-apply guidance.

ptr727/ESPHome-NonRoot (Docker-only) kept all the per-extension EOL/indent blocks verbatim but trimmed the [*.cs]/ReSharper block, with an inline note documenting the deviation so a re-sync doesn't silently restore it.

Suggestion

Either (a) split the EOL governance into its own always-verbatim section and mark the C# style block as ".NET repos only," or (b) explicitly bless trimming the C# block in non-.NET derived repos in the "Files ... Must Carry Verbatim" entry. Today the carry instruction and the trim instruction point in opposite directions for Docker-only / Python-only repos.

---

Surfaced while adopting the template in ptr727/ESPHome-NonRoot (see ptr727/ESPHome-NonRoot#61).

[ptr727]

Marked the [*.cs]/ReSharper block in .editorconfig as .NET-only (EOL block stays always-verbatim), updated the AGENTS.md carry entries, and documented the one-time line-ending normalization needed when adopting .gitattributes.

Addressed in #167 (merged to develop; not yet promoted to main, pending any further feedback as these changes are applied downstream).