ci(release): write the release page from a template, with an English summary

[fylorn]

What this changes

Release pages get a title and a fixed layout. A release is titled "ThinkWatch Core ", and its text is, in order: an English summary from release-notes/<version>.md when that file exists, a table of the files for each platform, the commands that install this version on a Linux server and switch an existing installation to it, how to verify a download against its .sha256, and GitHub's generated list of pull requests. Until now the page was only the generated list, under the bare tag.

Why

#191 fixed the list being written four times, but the page still did not say which file is for which platform, how to install twcore on a server, or how to check a download, and the tag alone made a poor title next to ThinkWatch Lite's releases.

How it works

• scripts/release_notes.py <version> <generated list> writes the text. It refuses a malformed version, and a summary that is empty, contains Chinese characters or starts with a top-level heading (the workflow sets the title).
• publish checks out the repository (before downloading the artifacts, since checkout cleans the workspace), asks releases/generate-notes for the list itself, runs the script, and hands the result to action-gh-release as body_path with name: ThinkWatch Core <version>. The action no longer generates anything.
• The rule from Publish releases from one job; correct the server docs and crate metadata #191 stays: a release that already exists keeps its text (body_path is empty and the action leaves the body alone), and only release not found counts as "does not exist".
• A rehearsal (workflow_dispatch) now also writes the text into the run summary, using the version in Cargo.toml, and still publishes nothing.
• CONTRIBUTING's "Cutting a release" describes the text and where the summary goes.
• release-notes/0.47.0.md summarizes 0.47.0 from Configuration reference, server deployment, and twcore upgrade #183-chore: v0.47.0 #190, and release-notes/0.48.0.md summarizes 0.48.0 from Publish releases from one job; correct the server docs and crate metadata #191-chore: v0.48.0 #198. v0.48.0 was published before this change, so its page still holds only the generated list; the 0.48.0 summary is there so the page can be rewritten from the template. Its upgrade notes cover CONTROL_API_VERSION 21 (ThinkWatch Lite 2026.9.16 includes 0.47.0, protocol 20, and does not connect to 0.48.0), the request store's schema 20 (the request history starts empty on the first start), and the changed /in-flight, RequestStarted and ChatgptUsage shapes.

FILES is unchanged, so twcore upgrade's test that reads release.yml is unaffected.

How it was verified

• python3 scripts/release_notes_test.py: 17 tests, run on Python 3.14 and 3.9 (the Linux CI job has 3.10). They check that the table links exactly the seven files in FILES and that each has a .sha256 there, that the install.sh and twcore upgrade options in the commands exist, the checksum commands, the summary checks, and every file in release-notes/. Renaming one file in the table, or adding a Chinese line to a summary, fails them. The Linux CI job runs them before compiling.
• actionlint with shellcheck on release.yml and ci.yml: clean.
• The list from generate-notes for v0.47.0 is byte-identical to the list the v0.47.0 page carried before this change.
• Rehearsal: run 36091692733 on this branch. All jobs passed (15 min). In Publish, the new step ran with the version from Cargo.toml (0.47.0) and wrote the text into the run summary; the release step was skipped, so nothing was published. The step's inputs are the committed release-notes/0.47.0.md and the generate-notes list for v0.47.0, so its output is the text now on the live v0.47.0 release, which was rendered locally from the same inputs.
• Rebased onto main at v0.48.0. The body for v0.48.0 was rendered locally with scripts/release_notes.py 0.48.0 from the committed summary and the generate-notes list for v0.48.0, which is byte-identical to the list on the live v0.48.0 page. All seven files it links exist on the v0.48.0 release, each with its .sha256, and every link answers 200; the three checksum commands name files on the release. The rendered text has no CJK characters and renders through the GitHub Markdown API (one table, every bold label closed).

Notes for review

• Code comments follow the language already used in release.yml; everything that reaches the release page is English.
• The live v0.47.0 release page now has this layout and title; its text is the script's output for 0.47.0.

🤖 Generated with Claude Code