Repository navigation
Revert accidental main merges from 2026-09-10 - #657
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
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.
Summary
Revert the two changes that were accidentally merged into
mainon 2026-09-10 but were intended fordev:Split server start/wait/stop lifecycle)Decouple client lifecycle from remote readiness)Recovery target
The resulting tree is intentionally identical to
mainimmediately before #647 was merged:21ed74fda07aa13ec620b93669c6699b33431eceThe history is preserved; this does not force-push or rewrite
main.Verification
A commit comparison between the recovery branch head and
21ed74fda07aa13ec620b93669c6699b33431ecereports no changed files.