Publish dynamic WinKeyer runtime endpoint - #8
Merged
Conversation
rtreit
marked this pull request as ready for review
July 26, 2026 18:38
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.
Adds a launcher-facing CatHub runtime endpoint contract.\n\nCatHub can bind its typed WinKeyer API to an OS-selected loopback port and publishes the effective endpoint with its process ID after listeners bind.\n\nThis prevents Windows port reservations from blocking startup.\n\nValidated with the CatHub workspace tests and Clippy.