fix: separate package guidance from publication state - #9
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.
Corrects the immutable v0.2.3 package README and current guides so they no longer claim a mutable provider version or unpublished candidate state. Publication state now preserves independently evidenced npm, MCP Registry, Git tag, and GitHub Release observations, including partial publication, while package smoke coverage rejects stale mutable labels and mismatched package pins.
Validation:
CHECK_OF_REQUIRED=1 OBLIGATION_FIRST_DIR=/private/tmp/legal-graph-release-2026-09-12/obligation-first npm run verify:ci; exact 76-file package smoke passed.