Views generated by each read stat 0, as acme's do: data, xdata, index, layout, recent and listeners; fs.md says which files have real lengths

A stat of index, layout, recent or listeners built the whole view to
count it, and data and xdata reported the body's length though a read
answers what addr selects. Those now stat 0, as screen and pane/new
already did, and fs.md lists the files whose length is real and says to
read the rest to the end.

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

1 files changed, 8 insertions, 2 deletions

diff --git a/docs/fs.md b/docs/fs.md
index 6b73a124..d8324d47 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -194,8 +194,14 @@ reads at once; the next is refused `too many reads waiting: 128`. A mount
 keeps answering everything else beside them. Through a FUSE mount bash's
 `read -t` cannot time out: wrap the loop in `timeout N`.
 
-**Stats.** Lengths are real (for `event` and `pty/data` the next record's,
-zero when none waits; for `log` what an open would freeze). The qid
+**Stats.** A file whose text is kept has its real length: a pane's
+`body`, `tag`, `name`, `ctl`, `sel` and the range and flag files, the
+workspace's `tag`, the root `ctl`, `status`, `commands`, `README`, the
+`look`/`exec` answers, `focus`; `event` and `pty/data` the next record's,
+zero when none waits; `log` what an open would freeze. A view generated by
+each read stats 0, as acme's do: `screen`, `data`, `xdata`, `index`,
+`layout`, `recent`, `listeners`, `pane/new`. Read those to the end rather
+than trust a length (`cat` does). The qid
 version of `body`, `data` and `xdata` is the pane's revision, so a stat sees
 an edit land. Modes are 0644/0666, 0444 read-only, 0222 write-only.