feat(client): save files under a name every platform can write

A node serves the name its disk gave a file; the client now makes it
portable at save time (single file, zip entries, zip name) and says so
on the transfer row. Same rule as paths.sanitize_for_download, held by a
parity test.

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

1 files changed, 6 insertions, 1 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/transfers.js b/packages/meshbay-hub/src/meshbay_hub/static/transfers.js
index bde382f..0d012ed 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/transfers.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/transfers.js
@@ -73,6 +73,7 @@ export class TransferStore {
       queuedByOwnLimit: Boolean(
         it.lease && it.lease.cap && it.lease.used >= it.lease.cap),
       error: it.error || '',
+      note: it.note || '',
       speed: this._speed(it),
       // The ETA is drawn only once the window holds a few seconds of real
       // measurement -- see etaSeconds.
@@ -134,10 +135,14 @@ export class TransferStore {
    * there is somewhere to write — see file-utils.js's downloadEntry.
    */
   start({ kind, name, total = 0, transport = null, run, open = null,
-          lease = null, prepare = null, makeLease = null, pausable = false }) {
+          lease = null, prepare = null, makeLease = null, pausable = false,
+          note = '' }) {
     const item = {
       id: _nextId++,
       kind, name, total, transport, open, lease,
+      // One line said under the name for the life of the row — that a name was
+      // changed to be written here, for instance.
+      note,
       done: 0,
       // A transfer that has to wait for a slot starts as 'queued', not
       // 'running'. Two different things are true of it — nothing is moving, and