Make the terminal's right button copy and paste, and never open a menu

Selecting output and right-clicking it opened the WebView's own context menu with
Copy on it, which is correct behaviour for a web page and wrong for a terminal.
What a terminal's right button has meant since the Windows console got QuickEdit,
and since PuTTY shipped, is this: with something selected it copies and drops the
selection, with nothing selected it pastes. No menu, no second click.

The gesture can only live in the page. The selection is drawn into a canvas the
host never sees, and once a terminal has focus the host's window receives no input
events at all — the same reason the Ctrl+plus chords are handled there.

◆ THE CLIPBOARD IS THE HOST'S IN BOTH DIRECTIONS, AND THE READING IS WHY.

navigator.clipboard.readText() is gated behind the clipboard-read permission in
every Chromium, and an embedded WebView with no PermissionRequested handler
answers a permission request by putting a prompt on the screen. Trading a context
menu for a permission dialog is not this change. So the page asks and the host
answers, exactly as requestFontSizeStep does.

Writing does not go the other way either, although navigator.clipboard.writeText
would have worked from the page on Windows: a clipboard that is the host's in one
direction and the page's in the other is two mechanisms to keep working across
WebView2, WebKitGTK and Android's WebView. The host has owned a clipboard delegate
since the keychain grew its COPY buttons, so each App.axaml.cs grows a
ClipboardReader beside its ClipboardWriter and MainWindowViewModel takes it.

Three opcodes: client ClipboardCopy and ClipboardPaste, server Clipboard.

◆ Clipboard IS NOT Paste, AND THE DIFFERENCE IS THE BRACKETING.

Paste carries a snippet off the sidebar, and the page deliberately *types* a
single-line one rather than bracketing it, because bash marks a bracketed paste as
an active region and a snippet should read as though it had been typed. A clipboard
paste is the case those markers are for — readline uses them to decide it has been
pasted into — so Clipboard is always bracketed and never followed by an Enter. One
opcode for both would have needed a flag meaning "which of the two kinds of paste
is this", on a payload whose existing flag byte means something else.

Both client frames are dispatched before the session lookup, which is what keeps
the gesture working in a pane whose shell has just ended: squinting at the message
a remote left behind is exactly when somebody copies the line. Dispatch was past
MA0051's length once it grew a second such branch, so the frames no pump needs to
see moved into Announce() and the font-size chord went with them.

◆ CAPTURED AND STOPPED, RATHER THAN MERELY PREVENTED.

preventDefault alone suppresses the menu and still lets xterm's own contextmenu
handler run, which moves its helper textarea under the pointer at z-index 1000 and
leaves the selection sitting in it, selected. Both of those exist to serve the
native menu. Taking the event in the capture phase on the pane and stopping it
there is what keeps the gesture wholly the page's.

rightClickSelectsWord is now false, which on macOS is a change of default rather
than a restatement of it: xterm sets it true there alone, so a right-click would
have selected the word under the pointer and copied that instead of pasting —
wrong on one platform only, which is the worst way for it to be wrong.

The renderer harness grows the pane it has been inviting since
RendererReconnectionTests: a fake Terminal, the two addons, and a real UTF-8 codec,
because both directions run through the page's own TextEncoder and TextDecoder and
a Latin-1 stub would pass a test with an em dash in the selection. Its warning
about declaring names terminal.js declares now covers the half that does not
SyntaxError — a harness frame() was silently replaced by the page's frame() and
failed six tests on a type error a long way from the cause.

Manual checks 1.11 and 11.13 are what is left for a person: that a real contextmenu
event reaches a capture listener, that no native menu is drawn once it is
prevented, and that xterm's real paste() brackets. 11.13 also records what is
unverified — whether Android's WebView delivers a pointer's secondary click as a
contextmenu event at all. ClipboardReader is wired on that head regardless,
because the alternative is a head where the paste half silently does nothing and
nobody finds out; that head is not compiled here either, this machine having no
android workload.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/DodoSSH.Client.Terminal.Tests/TerminalWorkspaceTests.cs

@@ -268,6 +268,69 @@ public sealed class TerminalWorkspaceTests
             .ShouldBeFalse("the tab it names is gone");
     }
 
+    /// <remarks>
+    /// <para>
+    /// The right-click paste's answer, and it is a separate frame from the snippet one above rather than the
+    /// same frame with a flag: the page brackets this unconditionally and types a single-line snippet, which
+    /// is a difference of behaviour and not of degree. See <see cref="TerminalServerOpcode.Clipboard"/>.
+    /// </para>
+    /// <para>
+    /// The payload is the clipboard's text and nothing else — no leading flag byte, because there is no
+    /// Enter to ask for. A frame that grew one would put a stray character at the front of every paste, and
+    /// this is what would catch it.
+    /// </para>
+    /// </remarks>
+    [Fact]
+    public async Task TheClipboard_ReachesThePaneThatAskedForIt()
+    {
+        var connections = new FakeConnectionFactory(blockShellReads: true);
+
+        await using var workspace = CreateWorkspace(connections);
+        workspace.Start();
+
+        using var renderer = await ConnectRendererAsync(workspace);
+
+        var sessionId = await workspace.OpenSessionAsync(
+            Request(), TerminalSize.Default, progress: null, TestContext.Current.CancellationToken);
+
+        // The session's opening frame, read and discarded so the clipboard frame below is the next one.
+        await ReceiveFrameAsync(renderer);
+
+        (await workspace.SendClipboardAsync(
+            sessionId, "sudo systemctl restart sshd", TestContext.Current.CancellationToken))
+            .ShouldBeTrue("the session is live");
+
+        var frame = await ReceiveFrameAsync(renderer);
+
+        frame.Opcode.ShouldBe((byte)TerminalServerOpcode.Clipboard);
+        frame.SessionId.ShouldBe(sessionId);
+        Encoding.UTF8.GetString(frame.Payload).ShouldBe("sudo systemctl restart sshd");
+    }
+
+    /// <remarks>
+    /// Refused rather than sent and dropped, for the reason <c>PasteAsync</c> is — with the difference that
+    /// nothing on screen would have shown it either way, so this answer exists to be honest rather than to
+    /// be reported. See <see cref="TerminalWorkspace.SendClipboardAsync"/>.
+    /// </remarks>
+    [Fact]
+    public async Task SendingTheClipboardToADeadSession_SaysSoRatherThanDroppingIt()
+    {
+        var connections = new FakeConnectionFactory();
+
+        await using var workspace = CreateWorkspace(connections);
+
+        var sessionId = await workspace.OpenSessionAsync(
+            Request(), TerminalSize.Default, progress: null, TestContext.Current.CancellationToken);
+
+        (await workspace.SendClipboardAsync(9999, "uptime", TestContext.Current.CancellationToken))
+            .ShouldBeFalse("this workspace never issued that id");
+
+        await workspace.CloseSessionAsync(sessionId);
+
+        (await workspace.SendClipboardAsync(sessionId, "uptime", TestContext.Current.CancellationToken))
+            .ShouldBeFalse("the tab it names is gone");
+    }
+
     /// <remarks>
     /// The event the tab strip and the phone's keep-alive listen to, so a dot can go out — and a foreground
     /// notification can come down — the moment a shell exits rather than at the next thing that happens to