fix: separate author identity from search text - #14
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.
Summary
Telegram author retrieval now treats the author identity as an explicit input instead of inferring it from the free-text search query. Draft context and CLI search can boost source-linked Telegram evidence for exact username/display-name matches, while query-only search stays focused on normal lexical and semantic evidence.
The retrieval projection also keeps visible author identities available to indexed evidence, so display names, handles, fuzzy identity candidates, and multilingual helper context can work without changing the evidence shape or letting fuzzy matches become draft targets.
Validation
uv run pytest— 149 passed