remote-ssh resolves a session's remote side by reading .remote-ssh.json at the session cwd and never walks up, so a session started in <mirror>/sub silently fell back to a local terminal. The folders route gained POST, which stamps the workspace's connection record into the new subfolder with remotePath adjusted to the matching remote directory; remote-ssh always excludes that file from sync. The client asks for the stamp right after adding such a folder.
@zhangfengshun/dsh-remote-ssh registers a remote workspace as an ordinary workspace whose directory is a local mirror of the remote root. The folder picker would have accepted any local directory for such a project, and sessions started there would never sync. The host now reports the mirror base alongside the overlay, the dialog swaps the picker for a relative-path field for mirror-backed projects, and joinSubpath refuses absolute input and .. escapes so a typo cannot leave the mirror.
A DSH workspace owns exactly one canonical directory, so the folder layer is a plugin-side overlay instead of a core change: \/workspace-groups.folders.json stores extra folders and the chosen root per workspace id (strict on write, tolerant on read). The tree gains a folder row only when a project actually has extras, and sessions are partitioned by their recorded cwd with the most specific folder winning. A folder row can start a session in its own directory through sessions.create({workspaceId, cwd}); the base folder keeps the platform gesture so repeated clicks reuse the blank session. Folders start expanded so attaching one never hides rows that were already visible.