A tag write over the limit is refused "no space: over 4096 bytes", so its err record says tag: once

The refusal's text began with "tag: ", and the log's err record puts the
file's name before the reason. So the record read `err - col/1/tag: tag:
no space: over 4096 bytes`. The text is now the reason alone, as the
control-character refusal's is, and the record names the file once.

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

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/fs.md b/docs/fs.md
index c7ef0857..7a4ce0b3 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -349,7 +349,7 @@ blank matters; `echo` would start a second line). A pane tag may hold
 several lines; a column or workspace tag is one, a newline written into it
 becoming a space. Control characters other than tab, DEL, C1 controls and
 non-UTF-8 bytes are refused (`invalid tag text`). The editable text is at
-most 4096 bytes (`tag: no space: over 4096 bytes`, ENOSPC). All three kinds
+most 4096 bytes (`no space: over 4096 bytes`, ENOSPC; the log says `err <serial> tag: no space: ...`). All three kinds
 take the same checks, whole or not at all, and a `>` whose write is refused
 changes nothing: its truncation is done with the write that fits, or at the
 close (or a read) when none came. A clear is an ordinary edit