build(todo): Todo deployable beside Learn's server, and released as an APK, on F-Droid and as a snap (ADR 0033, step 5)

deploy/compose.todo.yaml adds Todo's server at todo.halkyon.eu, a member
of Learn's register, its database halkyon_todo in the instance's
PostgreSQL, its image built as Train's. redeploy.sh and backup.sh go over
every app server .env switches on (train, todo). Each compose file names
its server to the register in a variable of its own
(INSTANCE_MEMBER_TRAIN, INSTANCE_MEMBER_TODO), which halkyon_base adds to
INSTANCE_MEMBERS, each address once, as a second compose file's default
would have replaced Train's.

apps/todo/release.dart configures the release tool for Todo's APK and
snap: a key of its own (pinned once made; until then nothing is
released), the F-Droid listing (Time, NonFreeNet), and the snap from
apps/todo/snap/, which the tool builds in a clone of the repository at the
tag with that folder in place of snap/, as snapcraft builds one recipe a
folder and the root's is Learn's. What's new for 0.1.0 in English and
German, now shown. Android's backup and transfer are off, as Train's
(D53): the reminders scheduled keep their tasks' titles unsealed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

deploy/backups.md

@@ -211,6 +211,11 @@ docker compose exec -T postgres \
 whose role is the cluster's and so survives the restore (on a new server, make it first:
 `sidecars/README.md`, *Train*, step 2).
 
+Todo's database, where `.env` switches Todo on (`compose.todo.yaml`, Halkyon Todo's
+ADR 0033), is `latest-todo.dump` in the same snapshots, restored as Train's, with
+`todo` for `train` (its role made first on a new server: `sidecars/README.md`, *Todo*,
+step 1).
+
 To check a backup without touching the instance, restore it into a database of its own
 next to the real one, look, and drop it: