Summary

This is a CI-scope follow-up for the send-side rich message slice in upstream python-telegram-bot#5263.

It does two small things:

• Uses Chango's requested PR-numbered fragment filename/content so the Chango check does not try, and fail, to push an auto-generated fragment to the fork.
• Teaches test_official to explicitly ignore Bot API 10.1 methods/objects/fields that are outside this PR's intentionally narrow send-side scope:
  • full receive-side RichText* / RichBlock* hierarchy
  • RichMessage
  • Link / InputMediaLink
  • join request query methods/fields
  • editMessageText rich-message editing changes
  • other newly scraped 10.1 fields not implemented in this slice

This keeps python-telegram-bot#5263 honest: the PR remains a send-side slice, while CI stops implying that it attempted the full 10.1 hierarchy.

Tests

• TEST_OFFICIAL=true PYTHONPATH=src python -m pytest -o 'addopts=' tests/test_official/test_official.py -q
  • 481 passed
• python -m pytest -o 'addopts=' tests/test_inputrichmessage.py tests/test_bot.py tests/test_chat.py tests/test_user.py tests/test_message.py -k 'rich_message or inputrichmessage' -q
  • 34 passed, 2814 deselected
• python -m ruff check tests/test_official/exceptions.py tests/test_official/scraper.py
  • passed
• python -m ruff format --check tests/test_official/exceptions.py tests/test_official/scraper.py
  • passed
• git diff --check
  • passed