ci: deploy a green main again

The hackathon's judging is over, so learn.halkyon.eu follows main once
more. Pushed together with build 21's release, as released apps up to
build 20 can't sign in against the new server.

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

.forgejo/workflows/ci.yaml

@@ -1,6 +1,6 @@
 # CI: every push of a branch runs the checks of the pre-push hook (tool/check.dart, every app's and
-# shared package's); a push to main is then deployed to learn.halkyon.eu (deploy/redeploy.sh; paused until 22 Oct 2026, see the deploy
-# job). Both jobs run on the runner on learn.halkyon.eu's server, directly on the host as an
+# shared package's); a push to main is then deployed to learn.halkyon.eu (deploy/redeploy.sh).
+# Both jobs run on the runner on learn.halkyon.eu's server, directly on the host as an
 # unprivileged user (deploy/runner/). A commit that passed the checks before isn't checked again
 # (see "Checked before?").
 #
@@ -152,10 +152,7 @@ jobs:
 
   deploy:
     needs: check
-    # Paused until the hackathon's judging ends (22 Oct 2026): the judges' v0.17.0 uses
-    # learn.halkyon.eu, which stays at v0.17.0 meanwhile, while main moves on and is
-    # tested locally. Afterwards, put back: if: github.ref == 'refs/heads/main'
-    if: false
+    if: github.ref == 'refs/heads/main'
     runs-on: sahaquiel
     timeout-minutes: 30
     steps: