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.