fix: enforce audience-scoped actor recall - #17
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
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.
Actor-scoped memory retrieval previously indexed participant events without applying event audience, and ActorKnowledge list/search could only return all scopes before caller-side filtering. This adds optional, backwards-compatible disclosure and audience filters to ActorKnowledgeService and EventService. Player queries now exclude DM-only knowledge and events, while DM queries retain full authorized recall. Branch heads, participant roles, knowledge-source events, legacy calls, invalid scopes, and player/DM projections are covered by regression tests. Verification: full Core suite passed; focused 5 passed; Ruff and git diff --check passed.