Freeze and test the dormant sync IPC bridge - #161
Merged
Conversation
myobie
force-pushed
the
refactor/sync-ipc-bridge
branch
from
September 5, 2026 00:16
2840ba2 to
4244121
Compare
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
Red proof
The focused library target failed before implementation because the IPC listener, nonce, messages, relay, and transport did not exist. This established the complete missing bridge surface before production code was added.
Verification
The conformance test resolves a peer and runs the real sync wire client through the Unix bridge to the test-only reference server. Separate tests cover both raw relay directions, half-close, owner-only permissions, nonce refusal, version refusal, required features, authenticated inbound identity, oversized frames, status, shutdown, and a stalled handshake.
No production request selects this path. The embedded engine remains the owner. No release or deployment is part of this change.