Restore pruned releases and verify CI publishing with v0.2.12

- Host root filesystem was expanded from 7.8G to 16G (~7.8G free), so the disk
  blocker is gone.
- Re-published v0.2.0 (4 artifacts) and v0.2.9 (5 artifacts) from the local build/
  outputs; both releases verify.
- Root SSH from the workstation is not available (publickey denied, password auth
  closes the banner); the host is administered via the zwitschi login.
- Version 0.2.12 exists to verify the tag pipeline end to end: the workflow should
  create the release via the checkout-credential fallback and upload all five
  artifacts.

TODO.md

@@ -35,11 +35,8 @@ Verified via API+host credentials (2026-10-31):
       Gitea runner does not expose `github.token`).
 - [x] Uploads now fail loudly and the release is verified to carry every artifact
       (a silent HTTP 4xx used to leave an empty release with a green job).
-- [x] Unblocked by pruning the superseded v0.2.0 and v0.2.9 releases (~565 MB) and
-      publishing v0.2.11 locally; all five artifacts are on the release.
-- [ ] **Host disk is still tight** (`/` 7.8G, ~150 MB free). Before the next release, run
-      on 192.168.88.30 as root: `journalctl --vacuum-size=100M` (journal is 837 MB),
-      `apt-get clean` (91 MB), and clear `/var/lib/gitea/data/attachments/tmp`.
+- [x] Host disk expanded to 16G (~7.8G free on `/`); v0.2.0 and v0.2.9 releases restored from
+      the local artifacts and verified. No cleanup needed any more.
 - [ ] Verify the fallback on the next tag push produces a release automatically (the
       v0.2.11 tag build reached the publish step and created the release; only the
       upload failed on disk space).