fix: recover display-name telegram authors - #13
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.
Summary
Telegram support can now recover evidence for users whose visible author identity is stored as a display name rather than
author_username. Adraft-context --user crinx7style lookup no longer falls through tomissing_user_historywhen the local Telegram message is linked tousers.display_name, and indexed chunks now render the visible author label instead ofunknown.This also cleans up noisy Telegram chunk text by dropping blank neighbor messages, and adds rebuildable language/translation helper metadata so English helper context can aid search without replacing the original Telegram text. Agent-facing instructions now treat
target.languageas the reply-language signal and keeptranslated_textas operator/helper context only.Design Notes
author_usernameis absent, so arbitrary text mentions are not promoted into author matches.draft-contextprefers the target message language over neighboring context when drafting from a message ID.Validation
uv run pytest-> 136 passedgit diff --check-> cleanKnown Residuals
Post-Deploy Monitoring & Validation
scripts/tg-support --profile default indexscripts/tg-support --profile default search crinx7scripts/tg-support --profile default draft-context --user crinx7scripts/tg-support --profile default draft-context --message-id <known-non-English-message-id>missing_user_historyis absent for known display-name histories, blankauthor:lines do not appear in evidence text, and non-English target contexts includetarget.languagewhen inferred.missing_user_historyfor visible display-name users, or replies are guided by translated helper text rather than target language.syncandindex; if the issue persists, fall back todraft-context --message-idand disable reliance ontarget.languageuntil language detection is tightened.