Keep current setup and examples ahead of background - #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.
First-time readers still encountered historical material and repeated explanations before completing the current usage path.
Remove duplicated endpoint and legacy introductions. Complete the example by saving the create response and extracting event.json before verification; describe the expected successful result.
Validation: checked 119 local/cross-repository links and anchors across this documentation change set. Ran the revised API Python example and published CLI 0.7.2 create/extract/verify commands against a local reference API; both returned valid cryptographic results. Only README content changes; runtime code and protocol behavior remain unchanged.