feat: outbound destination fields on SingBoxNode (jump_edges producer) - #4
Merged
Conversation
Add OutboundServer/OutboundPort/OutboundType so an agent-captured outbound's downstream exit target (server:port/type) flows end-to-end, enabling the server to resolve cross-node relay (jump) edges. Claude-Session: https://claude.ai/code/session_01K3G7UAfcWNQkATYevDvnVM
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.
Part of the jump_edges producer — lets the vpn-core Lines graph draw cross-node hub→exit relay edges (UI already renders them; server never populated them). Coordinated change: SDK fields → agent parses sing-box
outbounds→ server resolves fleet-wide intojump_edges. Verified: builds + unit tests green against local SDK via go.work.https://claude.ai/code/session_01K3G7UAfcWNQkATYevDvnVM