fix(desktop): retain plugin archives and start fresh sessions for alpha.5 - #46
Merged
Merged
Conversation
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
1 participant
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.
Installing another plugin failed when a previously installed local archive had been moved or deleted. Desktop now retains local TGZ files by SHA256 in the current account Home and delegates installation to the bundled official pnpm using the retained path.
New Session previously reused an unsent expert task, retaining its expert, MCP and Library draft. The shared Web/Desktop navigation now requests a new native Session; old drafts remain intact and explicit expert switching still transfers their references.
Prepare Desktop 2.0.6-alpha.5 with these fixes. Validation: Desktop build/typecheck, 128 unit tests and 13 release checks passed; actual bundled pnpm installed a second plugin after deletion of the first source archive; 11 browser acceptance checks passed; local arm64 DMG and five-feature runtime inventory passed. The user accepted the local candidate. No upstream source or existing user data was changed.