    /* the one face of the six that a real build can show without arming
       anything: `__ssMock` does not exist here. One already-terminal row
       goes into the transfer store — the same thing the shade steps above
       do — and comes straight back out. Nothing is downloaded, no room is
       joined, no message is sent, nobody is signed in, and neither the
       config nor the library is written. A `failed` row is not in flight,
       so no notice is posted either. The id is far above the backend's own
       counter and `list()` sorts id-descending, so it is the first row on
       the screen even if Kyle's own session is carrying real failures. */
    { do: `(function () { __ss.transfers.items[990011] = { id: 990011, username: 'walk_peer', path: 'Walk\\\\walk-c.flac', name: 'walk-c.flac', state: 'failed', queue_place: null, local_path: null, error: 'transfer rejected: File not shared.', received: 0, total: 0 }; __ss.push('transfers', {}); return true; })()`, name: "trouble-xfer", wait: 1400 },
    { do: `(function () { delete __ss.transfers.items[990011]; __ss.back(); return true; })()`, name: "trouble-xfer-gone", wait: 1000 },
