release: explain held batch items and dated payment evidence - #59
Merged
Merged
Conversation
…60917 Clarify held batch items and timestamped payment evidence
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.
Promote the collector documentation from #58 for the quarantined batch incident.
The six changed pages distinguish each Feline's fulfillment from the shared payment, describe confirmation as timestamped evidence, explain guarded recovery, and tell affected buyers not to pay again.
Validation at 4cbe36b: artifact-provenance tests passed (2/2), publication gate passed (87 files, 53 Markdown pages), and the site built successfully (47 pages, 8 plates).
Publication remains blocked by GitHub Actions artifact storage quota, reproduced by attempt 3 of run 35195376534. Preserve the exact-SHA artifact and live-facts publication gates. After promotion, synchronize develop to the merge commit, obtain successful trusted CI for that exact commit, and rerun publication. Merging this PR alone does not prove that the live manual has updated.