feat(workspace): file-manager drag-and-drop — move within tree + import from OS into workspace

[pamnard]

Summary

The workspace file tree panel supports drag-and-drop, but only for referencing paths in the chat composer (#1097, closed). It does not behave like a desktop file manager for:

1. Moving existing files/folders within the workspace tree (drag item → drop on folder).
2. Importing files/folders dragged from the OS (Finder/Explorer) into the workspace panel (current directory), as opposed to attaching them to the chat.

Users often expect both because the panel looks like a file tree. Today that expectation is unmet by design of #1097, not by an obvious bug — but the gap is undocumented in-product and was deferred from #1104 (“Move/copy — lower priority, complex UX”).

Current behavior (intentional)

Action	What happens
Drag file/folder in workspace tree	draggable=true, effectAllowed='copy', sets application/ws-path
Drop on composer	Inserts @<workspace-relative-path> into the message textarea
Drag files from OS onto page	Global drop on composerWrap: addFiles() → chat attachments (session inbox), not workspace import
Drag in Settings → Workspaces list	Reorder registered workspaces (/api/workspaces/reorder) — unrelated to in-tree file ops

Backend: create, delete, rename in place only (/api/file/rename rejects / in new_name — no cross-directory move). No /api/file/move or workspace-panel drop target.

Requested behavior

A. Internal move (tree → tree)

• Drag file or folder onto another folder (or breadcrumb) to move within the workspace root.
• Visual drop targets, move effect, confirm on overwrite if needed.
• API: cross-directory move (POST /api/file/move or extend rename with validated to path).

B. OS import (OS → workspace panel)

• Drop files/folders onto the workspace file tree to copy/upload into active directory (S.currentDir), not only the composer.
• Folder drops: directory traversal via DataTransferItem / webkitGetAsEntry (document platform limits).
• Reuse upload/security patterns (/api/upload, zip extract feat(workspace): upload a zip/archive or folder and extract into workspace #525); clarify vs session attachment inbox (feat: store chat uploads outside workspace root #2319).

C. UX clarity (optional)

• In-product hint: tree drag → chat @path today; file-manager move once implemented.
• Do not break Feature Request: Drag and Drop Files/Folders from Workspace Panel to Chat #1097 composer drops.

Related

• Feature Request: Drag and Drop Files/Folders from Workspace Panel to Chat #1097 — workspace tree → chat @path (done)
• feat(workspace): file CRUD in workspace panel — rename, delete, create files without leaving the UI #1104 — CRUD; move/copy deferred
• feat(workspace): drag-to-reorder workspaces in the workspace list #492 — reorder workspace list in Settings
• feat(workspace): upload a zip/archive or folder and extract into workspace #525 — archive upload/extract

Acceptance criteria (draft)

• Drag tree item → folder moves file (validated paths, error toasts).
• OS drop on workspace panel imports into current workspace directory.
• Feature Request: Drag and Drop Files/Folders from Workspace Panel to Chat #1097 composer behavior unchanged.
• Tests for ws-path vs Files vs internal move routing.

[nesquena-hermes]

Thanks for the precise breakdown — the table distinguishing today's intentional compose-reference DnD (#1097) from the two missing file-manager behaviors (move-within-tree, import-from-OS) is exactly the right framing. Queued under Milestone 2, labeled enhancement / workspace.

One adjacent note: the "import from OS into workspace" half overlaps with #3411, where dropping an OS file on the tree currently both uploads it to the workspace and attaches it to the composer because two drop handlers fire for one event. Whoever picks this up should coordinate the two — #3411 is the bug-fix half (disambiguate the handlers) and this issue is the feature half (make the workspace drop a deliberate import with move semantics). Linking them so they don't fight over the same drop path.