test(sessions): stabilize extended-stable reply-init proof#107832
Merged
RomneyDa merged 2 commits intoJul 14, 2026
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
2 participants
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.
What Problem This Solves
Fixes an issue where the 2026.6.33 release candidate's reply-session process-concurrency proof could observe its readiness marker while the child process was still writing JSON, causing a nondeterministic
Unexpected end of JSON inputfailure in exact-SHA CI.Why This Change Was Made
Cherry-picks upstream a004e18 so the child publishes marker JSON with write-then-rename atomicity, then refreshes the generated 2026.6.33 contribution record to include PR #99212. This PR intentionally contains no runtime, SQLite, package, workflow, version, or publication-scope changes.
User Impact
No runtime behavior changes. This makes the required extended-stable validation deterministic and establishes merge-backed canonical-branch provenance for the trusted Telegram release check.
Evidence
session-accessor.reply-init-concurrency.test.tswithUnexpected end of JSON input.tbx_01kxhe3zk1d0yt79hb56yc9nst: exact focused regression passed 20/20 repetitions.patch is correct, confidence 0.99.git diff --check: passed.AI-assisted: yes. The complete release ledger remains untracked as required.