docs: comments state what is, not how it came to be

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>

README.md

@@ -18,7 +18,7 @@ Commands may be abbreviated to any unambiguous-by-order prefix, as the legacy
 firmware allowed: `up` is `uptime`, `st` is `statistics`, `sa` is `save`. The
 table order resolves ties, so `s` is `show` — and `reset` is deliberately the one
 command that cannot be abbreviated, because `r` should not be able to wipe the
-histogram. `save` (new) forces a writeback, which otherwise happens every 30
+histogram. `save` forces a writeback, which otherwise happens every 30
 minutes and on the way into the bootloader.
 
 `show`, `statistics` and the histogram print one value per line behind a dotted
@@ -28,9 +28,8 @@ from 10 to 60 with a bar, because the curve is a cubic and five-degree samples
 without a graph show none of its shape.
 
 **Ctrl+C** abandons a half-typed line and gives a fresh prompt, echoing `^C`, and
-it is what stops `monitor`. Stopping on *any* byte, which is what the port did
-first, reads well right up until a host sends a line ending: `monitor\r\n` then
-stopped itself on the `\n` it arrived with, one reading in.
+it is what stops `monitor`. Stopping on *any* byte would not do: a host's line
+ending would stop `monitor\r\n` on the `\n` it arrived with, one reading in.
 
 ## Reaching the bootloader