Repository navigation
Resolve native Discord thread provenance and preserve Lab routing - #16
Merged
Merged
Conversation
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.
Normal Discord thread hooks omit the parent, and reduced dispatch hooks omit the guild. Resolve thread provenance from approved native metadata or authenticated Discord channel metadata, and preserve CC Lab routing through synchronous account-local guild classification. Reject ambiguous protected routes before ingestion and model dispatch.
Validation: 229 OpenClaw tests, Hermes integration test and build pass; regression fixtures exercise normal fire-and-forget received hooks, reduced dispatch, SecretRef resolution, account isolation and unchanged CC Lab policy decisions. No real Discord messages or inference calls.