build(ci,deploy)!: the runner at home in a nightly window, deploys by hand (ADR 0039, D6, D13, D16)

The CI runner moves to halkyon.li's host at home and runs from 02:00 to
05:00 alone: a timer starts it, its unit's RuntimeMaxSec ends it, and
night.sh rests the instance's heavy sidecars around it as deploy, while
Caddy, PostgreSQL and the apps' servers keep serving. Jobs pushed during the
day wait in Forgejo's queue.

Its sandbox fits the new host: its folder on the HDD, the rest of /data
hidden, containerd's store out of reach, no private IPv4 network and no
IPv6 at all (the home network's IPv6 addresses are public ones under a
changing prefix, on the internet's own interface), 5 GB of memory with swap
beyond. The Sandbox step checks the tunnel, the home router and IPv6.

BREAKING CHANGE: CI deploys nothing any more: the deploy job goes with
learn.halkyon.eu's server, and halkyon.li deploys by hand with redeploy.sh
once a commit's night's run passed. Jobs run on the runner labelled
balthasar; sahaquiel's runner picks up none.

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

deploy/runner/forgejo-runner.timer

@@ -0,0 +1,15 @@
+# The CI runner's nightly window (ADR 0039, D6): started at 02:00, after night.sh has
+# rested the heavy sidecars (halkyon-night.timer, 01:55), and stopped by its own unit three
+# hours later (RuntimeMaxSec). Never started to catch up after a night the machine was
+# off: the queue waits for the next night. As /etc/systemd/system/forgejo-runner.timer,
+# enabled with `systemctl enable --now forgejo-runner.timer`.
+[Unit]
+Description=The CI runner's nightly window
+
+[Timer]
+OnCalendar=*-*-* 02:00:00
+Persistent=false
+Unit=forgejo-runner.service
+
+[Install]
+WantedBy=timers.target