clangd's database is the one CMake Tools copies from the selected preset,
as in libavr, rather than one chip's tree. .gitattributes drops two Studio
patterns nothing here matches, .clangd is ASCII, and the comments in it,
check.sh and .gitattributes state the reason without the account of how it
was found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The libavr pin moves to the preset loop's own fix. `tools/check-presets.sh` -
which this repository's gate calls - parsed `cmake --list-presets` by anchoring
a preset name's closing quote to the end of the line, and a preset carrying a
`displayName` is listed as `"name" - description`. The presets here are
undescribed, so the loop found them either way; one `displayName` away it would
have found none and said the repository had no presets. The loop has a test
aimed at it now, which it did not before - libavr runs none of its own presets
through it.
`.gitattributes` gains `* text=auto eol=lf`. Naming the source extensions left
Markdown, Python, shell and CMake to whatever wrote them, and on the Windows
side of this bench that is CRLF - which turns an eighty-line edit into a rewrite
of every file it touched and buries the change in the diff. Rule 50 carries the
sentence now, so it is the repository's default rather than a habit.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BlackMarkandClaude Opus 5.5