v2.0.2

build: publish releases to the public download repository

This repository is private now, and a private repository cannot distribute
anything: its release assets and its releases API both answer 404 without a
token, so the app's update check and the download page would both go blind.

The two things want opposite treatment. The source can be hidden. What
users install has to be reachable by anyone, without a credential - there
is nothing to put in an APK that cannot be read straight back out of it,
and a proxy in front of the asset would mean a token living at runtime and
a service to keep alive.

So the build stays here and the result goes to hojin-v/Shit-download, which
is public and already holds the download page. The only token involved is
RELEASE_TOKEN, and it exists only while the build runs.

The app follows the APK: UpdateCheck reads that repository's releases, and
the release page it offers as a fallback is one a user can actually open.

generate_release_notes had to go with it - it composes notes from the target
repository's history, which is now the download page's commits and says
nothing about the release. The tagged commit's own message is used instead,
which is where the reasons have been written all along. That needs the full
history, hence fetch-depth: 0.

Existing installs point at the old location and will not find this. One
manual install bridges it; after that the check works from the new one.

Android 16: 9 checks, no failures. 57 unit tests. Verified against the
now-empty download repository that the check logs HTTP 404 and carries on
without a banner or a crash, and that the page falls back to its own link
rather than showing a version it cannot confirm.