ci: move forgejo workflow to an example (no codeberg runner; gate via deploy hook)

e2e/README.md

@@ -23,4 +23,7 @@ and runs `e2e/*.spec.ts`. Ergo is torn down afterwards.
   rewritten.
 - `install-ergo.sh`: downloads and pins the Ergo version (`ERGO_VERSION`).
 
-CI runs the same flow in [`.forgejo/workflows/e2e.yml`](../.forgejo/workflows/e2e.yml).
+A Forgejo Actions workflow that runs the same flow is provided as
+[`ci-forgejo.yml.example`](./ci-forgejo.yml.example). Codeberg has no shared
+runners, so to run it there: attach your own Forgejo runner, then copy the file
+to `.forgejo/workflows/e2e.yml` and set `runs-on:` to your runner's label.

e2e/ci-forgejo.yml.example

@@ -1,9 +1,10 @@
 # End-to-end tests: the real built client, driven by Playwright, against a live
 # Ergo IRCv3 server over WebSocket (the same transport as production).
 #
-# Forgejo Actions (Codeberg). Needs a runner advertising the "docker" label and
-# an x86_64 host (Ergo ships a linux-x86_64 binary). Enable Actions for the repo
-# in Settings to run this.
+# Forgejo Actions (Codeberg). Codeberg has no shared runners: attach your own
+# Forgejo runner, then set `runs-on` below to a label that runner advertises (the
+# default "docker" matches nothing on Codeberg). Needs an x86_64 host (Ergo ships
+# a linux-x86_64 binary). Copy this file to .forgejo/workflows/e2e.yml to enable.
 name: e2e
 
 on:
@@ -14,7 +15,7 @@ on:
 
 jobs:
   e2e:
-    runs-on: docker
+    runs-on: self-hosted   # set to your runner's label
     container:
       image: node:22-bookworm
     steps: