Docs: the Gitea runner runs the full workflow, e2e included; open question 15 resolved

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

docs/DEPLOY.md

@@ -170,10 +170,13 @@ the stack's bind mounts resolve and removes the stack when the job ends. The run
 token was never written down. [deploy/runner/README.md](../deploy/runner/README.md) has the install, update
 and re-register steps.
 
-The repository must exist on Gitea (`spencerm/packetstation`) with Actions enabled, and the image job needs
-the repository secrets `REGISTRY_USER` and `REGISTRY_TOKEN` (a Gitea token with package write). Until the
-first push, the workflow has not run on the runner; open question 15 in PLAN.md records what is still to be
-seen (the Samba DC's `cap_add` through the proxy).
+The repository is `spencerm/PacketStation` on Gitea with Actions enabled. The workflow ran there on
+2026-10-16: server, frontend and e2e pass (the e2e job builds the image, starts the CI stack with the Samba
+DC and runs the Playwright scenarios on docker-1's daemon). The image job needs the repository secrets
+`REGISTRY_USER` and `REGISTRY_TOKEN` (a Gitea token with package write) and fails until they are set.
+Two runner settings were needed and are in deploy/runner: the actions cache server published on docker0
+port 8088 (job containers cannot reach the runner's own network, and every cache call timed out), and the
+job workspace on a host directory allowed in `valid_volumes` (so the stack's bind mounts resolve).
 
 ## Backup (planned, phase 9)