Move files to and from a host over SFTP

M2's file transfer, built bottom-up: an SFTP session on the SSH layer, a
transfer queue in a project of its own, and the two-pane browser the design
asked for replacing the screen that said it did not exist. Remote listings
carry names, sizes, modification times and a real drwxr-xr-x — nothing in this
repository could render a POSIX mode before — and the queue moves one file at a
time with progress, throughput and resume.

The design import assumed this would be an SFTP subsystem channel on
ISshConnection, beside the shell on a transport that is already up. SSH.NET
does not offer that: SftpClient derives from BaseClient and owns its own
transport, and there is no supported way to hand it an SshClient's session. So
file transfer opens a second authenticated connection, and it is named for
that rather than dressed up as a channel — OpenSftpAsync is on
ISftpSessionFactory, not on a connection. The difference is visible to a user:
the host records a second login, and a host whose password is typed each time
asks for it again on this screen. It goes through the same host key gate, the
same pin and the same two refusals a shell does, so a fingerprint approved for
a terminal is approved here and one approved here reaches the other machines
with the next sync. docs/design-import-gaps.md is corrected, and marked as the
one row where what shipped differs from what it predicted.

Nothing is written at its final name until it is complete. Every transfer goes
to a .dodossh-part file beside its destination and is renamed into place at the
end, so an interrupted transfer can never be mistaken for a finished one —
which matters most for what this screen is actually for, which is copying a
build artefact onto a server and then running it. A destination that already
exists is refused outright rather than overwritten: the queue has no way to
ask, and silently replacing a file somebody's process is serving is the worse
of the two failures. The remote pane has DELETE and MKDIR so that refusal is
not a dead end. A test against the container pins the assumption underneath all
of this — that SFTP's rename does not clobber.

Resume works within a run of the application and not across a restart, and the
limit is deliberate rather than unfinished. Nothing records which source wrote
a part file, and resuming one on the strength of its name matching is how a
corrupt artefact gets delivered with nothing reporting a failure; a part file
found at startup is started over. Making it survive a restart needs the
preferences store this client still has not got. The offset a resume starts at
is the part file's own length rather than the transfer's recorded progress: a
cancellation can land between a write completing and the counter moving, and
only one of those two is a fact about the bytes that are there.

The queue and its connection outlive a lock, as shells do. LockAsync already
argues that locking must not destroy work in flight — it is what somebody does
when they walk away from the machine, which is exactly when a long transfer is
most likely to be running — so TransfersViewModel is created once and the vault
is attached on unlock and detached on lock. What locking takes is the host
list, and it has to: those rows carry decrypted secrets.

DodoSSH.Client.Transfer is a new project rather than more of Client.Ssh. The
two answer different questions — one is about reaching a host, the other about
moving bytes and what to do when moving them stops halfway — and this is the
only client project that deliberately touches the local filesystem.

Three defects the tests found, none of which review would have. SftpPath.Name
answered an empty string for the root. NavigateRemoteAsync wrapped itself in
the busy guard, so navigating from inside another command did nothing at all
and the remote pane simply stayed empty after connecting, with no failure
anywhere to explain it. And opening an SFTP session per test made two
handshakes per test — this client learns a host key by being refused — which
pushed the SSH assembly past sshd's MaxStartups and failed a different few
unrelated tests each run; the session is shared through the fixture now, with
the reason written where the next person will hit it.

1004 tests green across 18 projects, 24 of them new: the SFTP subsystem against
the OpenSSH container, the queue against a real temporary directory and a fake
host, and three more layout measurements because a screen this window has never
laid out is a screen never checked.

Not verified: the screen has not been looked at running. The layout harness
measures it at the window's minimum in three shapes, which is the class of
defect that has shipped here before, but reaching it in the application needs
the compose stack, the migrations, the API and a browser sign-in. What is still
absent — the status bar's transfer count, dragging between the panes,
transferring a directory, and sftp over a bastion — is in
docs/design-import-gaps.md.

README.md

@@ -65,8 +65,9 @@ src/
   DodoSSH.Client.Storage   the local cache: ciphertext mirror, outbox, offline unlock material
   DodoSSH.Client.Sync      the pull/apply/push loop and the conflict policy
   DodoSSH.Client.Session   where a profile lives, unlocking it, and getting one in the first place
-  DodoSSH.Client.Ssh       connections, PTY shells, host key trust
+  DodoSSH.Client.Ssh       connections, PTY shells, SFTP, host key trust
   DodoSSH.Client.Terminal  the loopback data plane and credit-based flow control
+  DodoSSH.Client.Transfer  the transfer queue, part files and resume, and the local file listing
   DodoSSH.Client.App       Avalonia; the only project that knows about a UI toolkit
 tests/                     one test project per source project
 docs/adr/                  architecture decision records
@@ -150,6 +151,37 @@ authentication asks for the password every time, because nothing in the interfac
 credential yet (they do sync — there is just no editor for one); and unlock asks for the passphrase on every
 launch, because no device key is registered.
 
+### Moving files
+
+**FILES** in the nav rail is a two-pane browser: this machine on the left, the host on the right, and a
+queue underneath. Choose a host, press **CONNECT**, then select a file in either pane and press the arrow
+pointing the way you want it to go.
+
+Two things about it are worth expecting rather than discovering.
+
+**It is a second connection, not a second channel.** SSH itself would allow the SFTP subsystem to open
+beside a shell on the transport that is already up; SSH.NET does not offer that — its `SftpClient` owns its
+own transport — so pressing CONNECT here authenticates again. The host records a second login, and a host
+whose password you type each time will ask for it again on this screen. Host key trust is shared: a
+fingerprint approved for a terminal is approved here, and one approved here reaches your other machines with
+the next sync.
+
+**Nothing is written at its final name until it is complete.** Every transfer goes to a `.dodossh-part` file
+beside its destination and is renamed into place at the end, so an interrupted transfer can never be
+mistaken for a finished one — which matters most for what people actually use this for, which is copying a
+build artefact onto a server and then running it. A destination that already exists is refused outright
+rather than overwritten; the remote pane has **DELETE** and **MKDIR** so that refusal is not a dead end.
+**RESUME** on a stopped transfer carries on from what the part file already holds.
+
+Resume works within a run of the application and not across a restart, and that limit is deliberate: nothing
+records which source wrote a part file, and resuming one on the strength of its name matching is how a
+corrupt artefact gets delivered with nothing reporting a failure. A part file found at startup is started
+over.
+
+What is not here: transferring a directory, dragging between the panes, and routing a transfer through a
+bastion — the last needs jump hosts the connection layer has not got. All three are in
+[`docs/design-import-gaps.md`](docs/design-import-gaps.md).
+
 ### End-to-end verification
 
 One suite runs against a real server rather than a stub. It needs a Docker daemon and nothing else, so it
@@ -230,7 +262,11 @@ off-Windows.
   a key are written at version 2 and become read-only on an older build. Hosts that do not are still
   written at version 1, byte-identically to before the field existed — which is what keeps upgrading one
   machine from making a team's whole vault uneditable everywhere else.
-- **M2 — full personal vault**, robust sync, relay.
+- **M2 — full personal vault**, robust sync, relay. *File transfer done:* an SFTP session, a two-pane file
+  browser with a real remote listing — names, sizes, modification times and `drwxr-xr-x` permission bits —
+  and a queue that moves one file at a time with progress, throughput and resume. See
+  [Moving files](#moving-files) for the two things about it worth knowing before you use it, both of which
+  are consequences rather than choices.
 - **M3 — teams**, sharing, ACLs.
 - **M4 — hardening and ops**, packaging, self-hosting guide.
 - **M5 — multi-provider OIDC**, key rotation, per-item content keys.