merge: restore the 1cd41927 pin lineage onto main (features + cap superset) - #3
Merged
Merged
Conversation
list_messages returns only sanitize_user_content(msg.message) — Telethon's plain-text body. A URL carried solely by a MessageEntityTextUrl (hyperlinked text) or a MessageMediaWebPage (link preview) never appears in any record field, so a consumer extracting links from `text` cannot recover it. Add an optional `urls` field, populated from message entities + webpage media. Additive and non-breaking: `text` is unchanged; `urls` is present only when such links exist.
list_messages records carried no media indicator, so a consumer could not
tell that a message holds a downloadable document (PDF / docx / slide
export) without calling download_media. This adds an additive, read-only
`document` field — {file_id, size, mime_type, file_name?} — emitted only
when `msg.document` is set, so PHOTOS are excluded (msg.document is None
for MessageMediaPhoto; photo media is handled by the vision path
elsewhere). Mirrors the additive spirit of the existing `urls` field; the
user-controllable file name is sanitized like all surfaced content. No new
tool, no new Telegram API call, no behavior change for non-document
messages.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
pkb's pinned SHA 1cd4192 carried two feature commits absent from main (text_link/webpage URL surfacing and document attachment metadata in list_messages) — load-bearing for pkb's pull_telegram_links. Bumping the pin to the capped main would have silently dropped them. Pure auto-merge, zero hand-resolved lines; brings main to a superset of every consumer's lineage: features + story-header fix + the mcp<2 cap.
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
2 participants
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.
Pure auto-merge of the
1cd41927pin lineage onto main — zero hand-resolved lines. pkb's pinned SHA carries twolist_messagesfeature commits (text_link/webpage URLs, document attachment metadata) that never landed on main; bumping the pin to the capped main (#2) without them would silently drop features pkb'spull_telegram_linksdepends on. After this, main supersets every consumer lineage: features + story-header fix (chigwell#128) + themcp<2cap.Part of agenthill/personal-knowledge-base#1354 — no closing keyword: the pkb pin bump is the remaining step.