ops: re-trigger Hetzner deploy (#71)

ops: re-trigger Hetzner deploy (#71)

Empty commit to force hetzner-deploy.yml to run. The live site is
serving an older SHA (3fa949c, BLOCK M era) even though origin/main
is at b1be050 (BLOCK S). Most likely the previous deploy's
bun-compile or systemctl step silently no-op'd. With the BLOCK S
auto-rollback + smoke suite now on main, this re-run will either
succeed cleanly or fail loudly with the exact reason logged.

Co-authored-by: Test User <test@gluecron.com>