chore: remove ARC52 mention

A string field was quoted only when it held a space or an equals sign,
so a value carrying a newline and neither was written out raw and split
one entry over two lines, which is exactly what Render promises not to
do and what makes the output greppable.

Nothing algod writes reaches this today: a stack trace goes into the
message, where collapseNewlines handles it, and the one structurally
multi-line field is built by a telemetry hook on a copy of the entry
that never reaches the file. The guarantee is Render's own, though, and
--file points the command at whatever file the user names, so the test
now covers control characters, quotes and backslashes alike -- %q
escapes them together and the guarantee stops depending on the producer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy

reportEmptyLogResult counted the sources the scan opened, which is the
list after PruneSources has already run. A --since newer than every
archive collapsed that count to the live log alone, so an empty live log
reported "the log file is empty, the node has not logged anything yet"
against a node with a year of rotated history behind it -- and sent the
user off to *start* a node that was already running.

The count is now the unpruned history, which leaves LogsNoMatchMsg to
explain the result. That is also the true answer: an archive pruned for
predating --since held nothing the search wanted either.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy

ArchiveFiles skipped every path os.Stat failed on, permission denied
included. With a separate LogArchiveDir the user cannot enter, the
archive was removed before the scan ever saw it, so nothing recorded it
as skipped and no warning was printed: the command reported a complete
history it had never read, which is the one failure this package works
to avoid.

Only absence is skipped now. Anything else keeps the path and lets the
read path fail on it, which puts it in ScanResult.Skipped and gets it
warned about -- the same choice PruneSources already makes, for the same
reason. An archive whose age could not be read sorts last, so it cannot
reorder the history around it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy

Follow's initial open failed on ENOENT while its polling loop waited the
same absence out in two places. The scan that produced the offset has
just read the file, so a path missing here is a rename in flight, not a
node that never started -- but the error reached the user as exactly
that, telling them to run *start* against a node that was running and
had merely rotated its log.

The open now retries at the poll interval while the context is live, and
a cancellation while waiting returns nil the way every other
cancellation does. Only absence is waited on: a permission error asked
again is still a permission error.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy

An entry with no readable level was dropped once the floor passed error,
which is the one place the exemption had to hold: a runtime panic is
written by the Go runtime and not through logrus, so it carries no level
field, and `logs --level panic` on a node that died of a nil dereference
answered with nothing at all while the default warn view showed the dump.
The floor now never judges a line it could not read a level from, which is
what the command's help has been promising.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy

The message broke off at "adding your account to the 'algorand' group
after", and it blamed the algod data directory's ownership for every
permission failure, including one on a file the user named with --file. It
now finishes the instruction, and a file the user chose gets a message that
only says which path could not be read.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PqPSx1wqM8rMdo4EHPa4jy