feat: align hosted workspace paths across CLI and Desktop - #165
Draft
Saga4 wants to merge 6 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
locand Desktop attach, refresh, list, and relocate workflowsUser experience
A hosted workspace now keeps the same logical attachment identity while its machine-specific root can move. CLI and Desktop call the same coordinator, so a workspace attached or relocated in either surface is reflected consistently in the other.
Validation
locality-storesuite: passedloc-cliparser/coordinator tests: passedcargo check -p locality-desktop: passedgit diff --check: passedRemaining live validation
No hosted-service credential flow or installed Windows/Linux/macOS application smoke test has been run yet. Those are runtime acceptance gates, not database migrations or backend deployment requirements.