fix(plugin): update project-scoped marketplaces - #446
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
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
Project-scoped marketplace plugins can now be updated through both the headless CLI and interactive TUI. Previously, project marketplace add, list, install, and sync all worked, but
plugin update --scope projectsearched only the user registry and failed withMarketplace not found.Update targets now retain their installation scope through marketplace lookup, refresh, and deduplication. User updates remain user-registry-only, project updates use the workspace registry with project-over-user precedence, and
--scope allupdates the same plugin independently when it is installed in both scopes.Related: #224
Validation
The regression suite exercises project-only, user-only, and identical user + project installations using local network-free marketplaces:
--scope allregression was confirmed red before the fix and green afterward.Manual WTG.AI.Prompts validation used the built CLI with an isolated user registry:
The final update completed with one plugin updated, zero skipped, zero failed, and the project workspace resynced successfully.