clipboard, n/N and the tty prompt: three things that were half-wired

Three changes that all turned out to be the same shape -- a feature that
worked in one direction, or for one pane kind, and quietly did not in the
others.

CLIPBOARD. Every register write emitted set_clipboard, so deleting one
character threw away whatever the desktop was holding; multi-cursor yank took
the join's early return and emitted nothing at all, so the same key reached
the clipboard on one cursor and not on two. Nothing could READ the clipboard:
the SDL shell had no SDL_GetClipboardText anywhere in it, and the tty shell
never asked for OSC 52, so `p` from another application was dead in both.

Now it is helix's split. y/d/c/p/P/R and the acme chords are the DEFAULT
REGISTER and nothing else; the system clipboard is five words on helix's own
letters -- SPC y, SPC Y, SPC p, SPC P, SPC R -- spelled as builtins so they
land in Help and are executable like every other verb. The one exception is
the tag `y` chord, which still mirrors out because a tag is always insert, so
SPC cannot be pressed there, and copying the path out is the whole point of
the chord.

Reading is a new read_clipboard effect answered by an ordinary Event.paste, so
the round trip is honest about being one: SDL and NSPasteboard answer inside
the same drain, the browser answers a promise, and a terminal answers over
OSC 52 or -- far more often -- refuses. A refused read is a paste that does
not happen, and the request dies at the next keystroke rather than landing
minutes late in whatever pane is focused by then.

The tty shell also enables BRACKETED PASTE now and coalesces
paste_start..paste_end into one event. Before this a paste arrived as a flood
of individual key presses: plausible in insert mode, and in normal mode every
pasted character ran as a command.

n/N. They stepped the armed results buffer and immediately Looked each row, so
you could not walk past a hit without opening it. They are a MOTION now:
select the next look-able text, open nothing, and let Enter decide. What they
step is the largest whitespace-delimited run look.resolve can act on
(look.lookableSpan, wrapper punctuation peeled), over a RING of panes -- every
pane that has performed a look, most recent first, then the output buffers
that have not, newest first, and only if both are empty the pane in front of
you. N is the exact inverse of n, computed rather than remembered: both
directions ask the same question about the same spans and compare against the
column the walk parks on, so x presses one way and x back land exactly where
you started, pane boundaries and the ring's seam included.

A ring rather than a list with two ends because a shell's cursor sits at the
prompt, below everything it has printed, so a walk that could not come round
would have nowhere to go on the very first press -- which is the case n/N were
written for.

One motion everywhere, no pane-kind or buffer-kind special case. The only
thing a buffer may change is the GRAIN of what a step selects, and it does it
with one flag rather than a branch: output_pane.Traits.commands (renamed from
`executes`, which named one reader's behaviour rather than the fact) makes a
row select WHOLE, because a ThemeSel line is a word to run and has no path
inside it to pick out. `]d`/`[d` are not n/N -- they are helix's diagnostic
motions, their job is to ARRIVE, and they still reach searchStep.

THE TTY PROMPT. Leaving raw tty blanked the prompt row, and the command you
had typed at that prompt shares the row, so it went too -- a shell out of tty
read as output only. OSC 133 marks the row CELL by cell, so the two are
separable: config.tty_blank = .prompt cuts the prompt's own columns and leaves
the command, left-hugged at column 0 in line with the output under it rather
than in a bay of blanks. .prompt_and_input is the old behaviour, kept.

Because the row is now something you can put a cursor in, enterTty adds the
hidden prompt width back before asking ghostty to walk the shell's own cursor
to it -- the modal column on a cut row is short by exactly that much.

Verified: unit-test 186/186 (nine new), snap 87/87 (new ttyprompt.snap),
hxdiff 481 and hxparity 561 with 0 mismatches, tty and gui both build. And
against the real binaries rather than the harness: in a pty, SPC y emits OSC
52 carrying exactly the selection while plain y emits nothing, SPC p issues
the read and pastes the reply, and a bracketed paste of "dd..." inserts text
instead of deleting two lines. In a real SDL window, SPC y then SPC p round
trips through the system clipboard while the default register holds different
text. Setting tty_blank back to .prompt_and_input reproduces all 86 old
goldens byte for byte.

1 files changed, 22 insertions, 14 deletions

diff --git a/src/output_pane.zig b/src/output_pane.zig
index 8ff98845..37ec6033 100644
--- a/src/output_pane.zig
+++ b/src/output_pane.zig
@@ -83,19 +83,27 @@ pub const Traits = struct {
     /// look path resolves, so the buffer IS helix's picker. Prose (a hover
     /// blurb, a formatting diff) has nowhere to step to.
     steps: bool = false,
-    /// ...and what a step DOES with the row it lands on. Off, the row is a
-    /// LOCATION and its leading word is LOOKED. On, the row is a COMMAND LINE
-    /// and the whole of it is EXECUTED — so walking the list runs each row in
-    /// turn, which is what makes a picker over things that take effect
-    /// immediately (ThemeSel) a plain list of the words you would have typed.
-    /// Both go through the ordinary builtin (config.look_cmd / exec_cmd), so a
-    /// row does exactly what the matching mouse button on it would.
+    /// ...and WHAT THE ROWS ARE. Off, each is a LOCATION with a look-able
+    /// `path:LINE:COL` word inside it. On, each is a COMMAND LINE — the whole
+    /// row, exactly as you would have typed it (ThemeSel's `Theme gruvbox`) —
+    /// with no path in it to pick out.
+    ///
+    /// TWO readers, one fact, which is why the column is named for the fact:
+    ///   n/N (lookWalk)  select the look-able span inside a location row, and
+    ///                   THE WHOLE LINE of a command row, since the line is
+    ///                   the unit there. Either way they only select; Enter
+    ///                   looks what they left, Tab runs it.
+    ///   searchStep      Looks a location row's leading word and Execs a
+    ///                   command row whole — still how `]d`/`[d` and acme's
+    ///                   button-3 arrive somewhere in one gesture.
+    /// Both go through the ordinary builtins (config.look_cmd / exec_cmd), so
+    /// a row does exactly what the matching mouse button on it would.
     ///
     /// Nothing about this is output-pane specific, which is why it is a column
-    /// here and not a branch in searchStep: `file_row` answers it too, so a
+    /// here and not a branch in either reader: `file_row` answers it too, so a
     /// file pane whose lines happen to be commands is one word away from
     /// behaving the same.
-    executes: bool = false,
+    commands: bool = false,
     /// an answer of exactly ONE row jumps straight there instead of opening
     /// this buffer at all — helix: the gotos jump on a single location and
     /// show a picker on several, a symbol list is always a picker.
@@ -129,7 +137,7 @@ pub fn traits(o: Origin) Traits {
                 .name = meta.name,
                 .steps = meta.steps,
                 .jumps = meta.jumps,
-                .executes = meta.executes,
+                .commands = meta.commands,
             };
         },
         .query => |k| switch (k) {
@@ -358,10 +366,10 @@ pub fn openJumps(p: *Pardes, id: usize) !void {
 
 /// The ThemeSel builtin: the theme ring written out as one `Theme <name>` row
 /// per theme — the ordinary builtin with its argument, exactly the line you
-/// would type — into a buffer whose `executes` trait makes n/N RUN each row
-/// rather than look it. So walking the list is trying the themes on, and
-/// stopping on one is choosing it; there is no picker mode, no preview state
-/// and nothing to commit or cancel, because every step already did the thing.
+/// would type — into a buffer whose `commands` trait says the rows are words
+/// and not places. n/N therefore select each row WHOLE and Tab runs it, so
+/// walking the list is trying the themes on and stopping on one is choosing
+/// it: no picker mode, no preview state, nothing to commit or cancel.
 ///
 /// The command's own name comes from the builtin rather than a literal: the
 /// word is derived from the struct in exactly one place (builtins.word), and a