Commit Graph

1 Commits

Author SHA1 Message Date
qyh15 36b9cb2bc0 fix(folders): make the folder overlay crash-safe and consistent
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.
2026-11-07 17:29:57 +08:00