Runner: host-directory job workspace (bind_workdir) so the e2e compose stack can bind-mount the checkout

Co-Authored-By: Claude Fable 5.1 <[email protected]>

deploy/runner/compose.yaml

@@ -1,7 +1,8 @@
 # Gitea Actions runner for docker-1. One act_runner container with the host Docker socket.
-# Jobs run in docker.gitea.com/runner-images:ubuntu-latest containers started through the socket;
-# the runner's Docker proxy lets a job's `docker compose` bind-mount the workspace by its own path,
-# which is what the e2e job needs for deploy/compose.ci.yaml.
+# Jobs run in docker.gitea.com/runner-images:ubuntu-latest containers started through the socket.
+# The job workspace is a host directory (container.bind_workdir) mounted into the runner and into
+# the job container at the same absolute path, so a job's `docker compose` can bind-mount files of
+# the checkout (the CI secrets, deploy/postgres/initdb, tests/e2e) and the host daemon finds them.
 #
 # Install on docker-1 (see README.md): copy this folder to ~/gitea/runner, register once, then up -d.
 #   cd ~/gitea/runner
@@ -27,6 +28,8 @@ services:
       GITEA_RUNNER_NAME: docker-1
     volumes:
       - ./data:/data                                   # .runner (the registration), config.yaml, cache, job logs
+      # Job workspaces. The host path and the container path must be the same (see data/config.yaml).
+      - /home/spencerm/gitea/runner/work:/home/spencerm/gitea/runner/work
       - /var/run/docker.sock:/var/run/docker.sock      # job containers and the Docker proxy
     restart: unless-stopped
     logging: