Repository navigation
docs: WO64 — Option B concretized (pinned-release chain) - #394
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
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.
Summary
The p047-large-strip recovery flickered: a jobs-artifacts listing showed the export zip at exactly WO44's recorded size, then the entry vanished (retention or consistency). WO64 now records Option B concretely — arms = the shipped r7 lineage + the shipped news specialist, init = the shipped r7 artifact, gate re-baselined on that init — fully executable from pinned, checksummed releases with no archaeology. Option A stays opportunistically revisitable if the bucket entry reappears.