fix: track algod spec instead of pinning a stale one

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

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

Size against offset only catches a truncation that is still visible when
the poll arrives. A file emptied and written back past the old offset
inside one interval never looks short, and the next drain reads new bytes
at a stale position: the prefix is lost and a pending fragment of the old
file is spliced onto what followed.

Polling has no way to close that. Nothing separates a truncate-and-regrow
from an append once the inode is unchanged and the length has recovered,
so the alternative is a different mechanism rather than a better check.
The window is one interval wide, algod rotates by renaming, and tail -F
has the same hole; it is left open on purpose, and now says so.

The truncation test slept to stay out of that window without explaining
which window, which read as timing noise rather than as the point.

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

Every other registered top-level command has one, and the README's
command list is where the published docs link from. Generated with
cobra/doc and put through the same banner substitution the existing
pages carry, checked by regenerating nodekit_restart.md and diffing it
against the committed copy.

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

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

Scan reported the live log's size as the follow offset, but a log caught
mid-write ends mid-line: the scan shows that fragment, and Follow then
resumed past it, so the remainder of the line arrived as a line of its own
and the entry algod was writing never appeared whole. The offset is now
rounded back to the last line boundary, within one read buffer, so the
completed entry is delivered once the newline lands.

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

Render's one-line guarantee was only half enforced. Values were escaped
and keys were concatenated raw, but a field name is decoded from the same
JSON object the value is, and an object key may hold anything a JSON
string can. A key carrying a newline split one entry across two physical
lines, which is the defect the value quoting was there to prevent.

The predicate moves into quoteIfNeeded and both halves of the pair go
through it.

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

IsEqual and MergeAlgodConfigs still handled only the two P2P flags, so the
log fields added for the logs command were invisible to both: two configs
differing only in BaseLoggerDebugLevel, LogSizeLimit or a log path compared
equal, and a value passed through the merge was dropped before anything
could write it. Both now cover every field, through a pair of generic
helpers rather than a block each, and a reflection-driven test fails on the
next field added to Config that either of them forgets.

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

--all names no level. It asks for whatever the log holds, and the log
holds everything the node wrote, so nothing the user asked for is
missing from it. Measuring the request against the node's floor anyway
meant --all asked for trace, which no algod writes, and every node with
a configured BaseLoggerDebugLevel was reported as withholding something
-- on the one run where the request was for all of it.

The warning stays for a level the user named and the node never writes,
which is what it is for. A node genuinely holding levels back is still
explained by reportEmptyLogResult, at the point where that leaves
nothing to show and the reason matters.

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