docs(status): rc6, and the two defects in the diagnostic we were about to use - #119
Merged
Conversation
…t to use Records what Mark's second email establishes, the correction to my own report that #111 was unmerged (it was not — stale origin/main), and the part that survives it: rc5 was built four hours before that merge, so the shim has still reached nobody. Also records the #113 decision reversing half of #112, and that rc6 is built but deliberately not published to R2.
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.
Session log for 2026-08-18. Records:
origin/mainref was stale. What survives the correction is that rc5 was built four hours before that merge, verified in the artifact.Next uprewritten around the single question the Client traffic report answers, including the premise that would falsify the whole diagnosis.Docs only.