Docs(api): Describe the tmux Server object - #47
Merged
Merged
Conversation
why: Server's transport does not explain its role in tmux. what: - Lead Java and Kotlin Server documentation with the tmux object model. - Explain socket selection, session queries and resource cleanup. - Keep Kotlin suspend and Java interoperability behavior explicit.
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.
Server documentation led with its transport rather than the tmux objects callers manage. Java and Kotlin now explain sessions, windows, panes, socket selection, and the difference between closing this handle and stopping tmux. Kotlin keeps its suspend and Java interoperability contracts explicit.
Validation:
./gradlew :libtmux-mcp:test checkpassed on Temurin 25 in 4m 16s, including Javadoc link validation, formatting, and the native test suites. This changes API comments only.