Repository navigation
Enforce mandatory Discord channel scopes across dispatch and recall - #13
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.
Discord policy rules can admit outside-channel content through command bypasses, automatic supplemental context and historical raw recall. Add a mandatory account/guild/root-or-thread admission boundary before sinks and dispatch, enforce it for both recall paths, and require provenance stamped at admission.
Protected turns with unverified quotes, starters, forwards or media fail closed. A dedicated agent/workspace and restricted tools are required; native transport may fetch supplemental content before plugin hooks. Existing unrelated guild behavior is preserved. Includes the previously installed native sender-exclusion guard and CI.
Validation: 218 OpenClaw tests, Hermes tests, syntax build, and independent review, including native provider-context routing and recall isolation.