Scan took the live log's size and offset by path, and Follow reopened
it by path and caught a swap only when the new file was shorter than
the offset. A rotation while the history was replaying lost what was
written to the old file in the meantime. If the new file had already
grown past the offset, its head was lost too, with no rotation notice.
Now that -f replays the whole history by default, that window lasts as
long as the replay.

Scan now opens the live log once, reads it only through that handle,
and returns the handle for Follow to carry on from. Follow reads the
old file to its end before it moves to the new one. An archive path
the rotation has pointed at the live log is skipped rather than read
twice.

--since 0s was described as a stream that starts at now, but Keep never
drops a line without a timestamp, and --since bounds the region read
rather than each line in it. Crash output near the end of the log is
still replayed. The help text, man page and decision record now say
that it skips the timestamped history, and a test pins the plain-text
case.

fix(sdk-list): update .NET SDK links, unnest page in sidebar

docs: add Intermezzo concepts and API reference pages

Fix/pyteal beaker deprecation

docs: note Homebrew tap trust requirement for AlgoKit brew commands