follow new: a log follower that starts at the end

A follower read the ring's whole history before anything new, and there
was no way to skip it. Writing follow new instead of follow skips what the
open froze and waits for what comes after (tail -n0 -f); fs.md and the
skill say that follow replays first.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 4 insertions, 1 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 04cef2f9..7c13d223 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -721,7 +721,10 @@ text, a cluster to a cell, is apart from this.) A click in a
 tag gives offsets into the whole tag as `tag` reads it, the path first.) An
 open freezes the ring's text the way `/screen` freezes a frame: reads walk it
 and end. Writing `follow` to that same open makes reads past it wait for the
-next record, one per read; a follower the ring outran reads `lost N` first.
+next record, one per read, after first reading all that the open froze (the
+ring's whole history, up to 64 KiB); `follow new` skips that and waits for
+what comes after, as `tail -n0 -f` does. A follower the ring outran reads
+`lost N` first.
 Closing the open is the only way back, as with rio's `consctl`. A follower
 misses nothing within a session only: a Restore hangs its connection up
 (and a 9ns mount with it, which must be restarted), so it dials again and