A looked word selects its next place in its own pane, as acme's look3

A plain word looked at (a look write, a right click, an ML record written
back) opened another identically named +Search pane each time, until the
panes ran out, and never wrapped. As acme's look3 searches the text for
it (look.c:210), it now selects the word's next place in that pane after
the dot, wrapping at the end, and opens nothing. LookWord list, a new
root setting, keeps the +Search listing (search is the default); the
rsearch snapshot and an output test that walk the listing say LookWord
list. (The leader-path check over every builtin gets a comptime
branch quota, as one more builtin took the GUI build past the default.)

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 ab31e25b..5fdde10a 100644
--- a/docs/fs.md
+++ b/docs/fs.md
@@ -310,7 +310,10 @@ same tree without leaving the process.
 
 - a line written to `look` is a right click on it: a path opens a file,
   `file:12` jumps to a line, a directory opens a shell there, a URL opens in
-  the browser.
+  the browser, and a plain word, as acme's look3 does, selects its next
+  place in that pane after the dot, wrapping at the end, opening nothing
+  (`LookWord list` on the root ctl lists every place in a `+Search` pane
+  instead, as pardes did before; `LookWord search` is the default).
 - a line written to `exec` is a middle click: a command word from
   `src/builtins.zig` (`Save`, `Del`, `New`, `Newcol`, `Mount NAME DIAL`,
   `Unmount NAME`, `Dump`, `Restore`, `Msg TEXT`, `Find`, `Grep`, `Tty`, ...;