docs(dedup): clarify survivor completeness scope - #708
Open
wesm wants to merge 1 commit into
Open
Conversation
Payload completeness is deterministic only when every eligible copy has the same normalized MIME. The merged documentation still described a pairwise check, which did not capture the final survivor-selection rule. Align the written guidance and diagram source with the implemented behavior so future asset regeneration cannot restore misleading instructions. Generated with Codex Co-authored-by: Codex <codex@openai.com>
roborev: Combined Review (
|
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.
The dedup docs now state the final survivor rule from #703: attachment count, attachment presence, and payload size are considered only when every eligible copy has the same normalized MIME.
This also updates the survivor-selection diagram source and accessible text so future generated assets preserve that group-wide rule. The matching generated diagram is now published on the
docs-generated-assetsbranch.