The loader build, the gate script and the line-ending rule each carried the
story of their arrival - a measurement off the bench, a loop got wrong by
hand, a checkout reached from two hosts - where a sentence of what holds now
is enough. .gitattributes loses two patterns for files this repository does
not have, .clangd its two non-ASCII dashes, two headers a "per C" that read
as a stripped degree sign, and the README a "(new)" and the port's own
first attempt at stopping monitor.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
libavr moves to its USI I2C rate accounting, the two override surfaces the
fan-controller port filed - a PWM solve that can be pinned, a capture edge that
is a value - and the shared preset loop's own fix. pureboot moves with it. This
firmware names none of them and no image moved.
`tools/check.sh` is new, and its absence was the defect: there was no committed
gate at all, so "run the suite" was a snippet somebody remembered - and the
order in a snippet is the one thing nobody re-derives. Every preset built
before any is tested is subtle and load-bearing, because the mode-identity
check reads the sibling mode's tree and a build-then-test-per-preset run holds
a fresh image against a stale sibling. The loop is libavr's
`tools/check-presets.sh`.
Two defaults stop being the editing machine's. `.vscode/settings.json` named
`D:/dev/libavr/local/toolchain/avr-gcc-16.1.0-mingw`, which is a path true of
one machine (libavr guidance rule 50) and, since the in-repo toolchain copies
went, true of none - `local/machine.cmake` is where a checkout says that and it
already did. And `.gitattributes` gains `* text=auto eol=lf`: naming the source
extensions left Markdown, Python, shell and CMake to whatever wrote them, which
on the Windows side is CRLF, and a rewrite there buries the change it made.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
BlackMarkandClaude Opus 5.5