fix: expose exact outbound session routes - #269
Open
scotthuang wants to merge 1 commit into
Open
scotthuang wants to merge 1 commit into
scotthuang wants to merge 1 commit into
Conversation
This was referenced Aug 27, 2026
8 tasks
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
This is the plugin-side companion to openclaw/openclaw#130871. That core change projects delivered heartbeat results only when a channel plugin certifies that the outbound recipient maps exactly to the canonical inbound session. The core also downgrades this certification when a binding belongs to another agent.
Validation
npm run typechecknpm run buildnpx vitest run src/channel.test.ts— 3/3 passednpm test— all 400 tests passed; the command exits non-zero only because the repository-wide pre-existing branch-coverage result is 89.15% against a 90% threshold. Excluding the new test still reports 89.13%, so this patch does not introduce the baseline gap.No merge is requested until the corresponding generic OpenClaw host contract is accepted.