release: publish truthful marketplace recovery guidance - #44
Merged
Merged
Conversation
…uth-20260917 docs: qualify failed purchases and saved revocation
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.
Promotes reviewed documentation PR #43 from develop to main. The activity guide now distinguishes reported failure from an unknown payment outcome and preserves the existing marketplace request for recovery. The connections guide requires a saved revocation acknowledgement plus readback, explains permission read/write failures, and matches identification fields to the current wallet card. The generated llms.txt entry is included.
Source PR #43 head 5b506bd passed all CI checks, including the full browser accessibility and overflow audit. Develop merge: dd74046. Local npm test, build (81 pages, internal links and CSP), and diff checks also pass.
Require successful promotion CI before merge. This legitimate documentation release will trigger one normal Pages attempt; the prior Pages build succeeded but artifact upload was blocked by GitHub's organization storage quota. Publication must be verified independently and must not be inferred from a successful merge. No release artifacts or retained historical branches have been deleted.