A session can only reach its own workspace directory, so folders spread over
several places could not be read and written by one session. The new farm
route builds one real directory whose entries are links to the user's folders
(junction on Windows, directory symlink elsewhere) and registers it as a
workspace.
Nothing is copied or moved. Removal unlinks entries only and aborts as soon as
it meets a real directory, so a farm can never take a user's folder with it.
Extra folders were rendered as their own rows with their own sessions, so a
project that carried a second directory split into two session lists. On a
cloud workspace the base row also exposed the local mirror id
(`wmvl31c7ilkuc`) as a folder name, which read as a project nested inside
itself.
Folders are now extra DIRECTORIES of one project: `applyFolders` returns the
workspace's sessions untouched, so the owner row and every member workspace
share a single list. Folders stay manageable from the workspace menu
(⋯ → 管理文件夹) where they can still be added, rooted, opened or removed.
Drops the now-unused folder-label/label-matching helpers, updates the
regression test to assert one merged row, and rewrites the CHANGELOG entry.
typecheck 0 errors, 290 tests pass, all three verifiers pass.
A workspace with extra folders used to grow one folder row per directory,
including its own base directory. For a cloud workspace the base is the
locally generated mirror (`wmvl31c7ilkuc`), so the sidebar showed that id as
a folder name and hid every session owned by the workspace inside it — one
cloud project read as a project nested inside itself.
The base directory is now the workspace row itself: `nodes[].sessions` keeps
its sessions and only real extras become folder rows. `folderNode` no longer
takes `isBase`, so a mirror id can never be labelled as a folder again, and a
workspace without extras keeps the exact pre-folders node shape.
Adds a regression test covering the mirror case (extra folder only, base
sessions on the workspace, no `wmvl31c7ilkuc` label) and documents the change
in CHANGELOG. typecheck 0 errors, 290 tests pass.
The folder sidecar was written as a whole document with no concurrency
control, and any read failure silently degraded to an empty document, so a
later edit could erase every workspace's folder configuration. Rework the
read/write path end to end:
- Agent side: expose a content revision, require If-Match on PUT, answer
409 with the current document, serialise read-compare-write, and fail the
GET loudly instead of serving an empty overlay. Unknown schema versions
are reported and never downgraded back to v1.
- Client: load/save report failure instead of fabricating an empty
document, edits go through one serial queue with optimistic update,
rollback on error, and reload on conflict. Editing is blocked while the
overlay cannot be read. Creating a workspace is compensated when the
follow-up save fails, so no orphan workspace is left behind.
- Paths: normalise NFC and lexically fold "." and "..", decide
absoluteness by spelling instead of process.platform, share one
implementation between core and host, and keep an existing root when a
member is re-registered at the same path.
- Remote folders: resolve the owner root from the SSH probe instead of the
"~" alias, and make "subfolder of this project" versus "register a new
cloud workspace" an explicit choice in the dialog.
- Stop shipping the client source map, which embedded the full TypeScript
sources in the published package.
- Track the SSH integration plan and cover the new behaviour with tests
(CAS, persistence, remote path parsing).
Verification: both tsconfigs typecheck clean, 288 tests pass, build
succeeds, and all three ad-hoc verifiers pass.