Prepare Plexus 0.2.1 with verified GitHub install recipes - #14
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.
Align Plexus metadata at 0.2.1 and make GitHub release installation verify both exact artifact names and hashes before invoking pip. Document declarative discovery separately from optional probes that can launch a configured process.
The README recipes now stop on empty, missing, duplicate, extra, path-bearing or invalid checksum entries. Tests execute the actual Bash and PowerShell documentation blocks with mocked downloaders and installers.
Validation: 115 local tests passed; independent six-file review accepted; rebuilt wheel passed fresh installed CLI/MCP smoke outside the checkout. GitHub-only release candidate; no PyPI publication or live external-tool acceptance is claimed.