[professorDeveloper]

Every release now gets what v3.2.0 had by hand.

Banner. tool/release_banner.py draws docs/images/v<version>/banner.svg from the v3.2.0 artwork and animation. Only the right column changes:

• the version badge, which widens for a version like v3.2.10
• NEW RELEASE or PATCH RELEASE with the month
• two tagline lines
• up to four chips

The wording comes from a comment in the notes:

<!-- banner
line1: Playback that recovers,
line2: downloads that finish.
chips: Server switching | Corner player | Downloads | 16 languages
-->

If the notes have no such comment, the chips are the areas merged since the last tag. The version job commits the banner with the bump. A banner already in the repo is kept.

Release page.

• The banner goes on top.
• A version without docs/releases/v<version>.md now gets a page in the v3.2.0 layout instead of the bare file table. It has badges, what's new grouped by area (from merged PR titles, with internal ones like Release/CI/docs left out), downloads, community links and a compare link.

Telegram.

• The banner is sent as a photo; the runner renders the still frame to PNG with headless Chrome, with rsvg as the fallback. Under it goes an HTML caption: the notes' Uzbek summary, or else the merged changes. The caption is capped at 1024 characters.
• The photo has buttons: Android from the CDN, all platforms (only when the release is public; a draft's page is a 404 for the channel), the channel and Discord.
• The files follow one by one. The install notes (ABI, TV, macOS) and the CDN/updater status go under the last file.
• If the photo or the HTML is refused, it falls back to plain text.

Tested

• 19 unit tests in tool/compose_release_notes_test.py (11 new).
• The banner was rendered for 3.2.1 and 3.2.2 and checked by eye.
• The Telegram step ran against a local mock API, with two chats and draft mode.
• actionlint shows nothing new apart from shellcheck style notes.