Refresh Mneme capability declarations from current producer contract - #12
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.
Plexus still advertised Mneme's older
mneme.crucible-export/1declaration after Mneme moved to/2. Refresh the shipped manifest and builtin registry to the current producer contract, includingmneme.local-origin-recheck/1and the current evidence pointers.The Mneme-to-Crucible route remains the existing declared
crucible.thesis/1alias and replay-pack route. Plexus does not claim that Crucible directly consumesmneme.crucible-export/2, and it does not import or execute either tool to establish a runtime result.Validation: the four new regressions failed before the change; all 92 Plexus tests, the example tour, and an isolated wheel installation/CLI discovery smoke passed. The mesh check confirms that
/2and the local-origin report are terminal native outputs, while the two existing declared Crucible routes remain. Independent review found no blocker after checking the exact source hashes and pinned producer/consumer contracts.