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)
 

docs/PLAN.md

@@ -232,7 +232,7 @@ Smaller questions from the design, with the default the build takes unless told
 12. Partspecs, title or folded-operation target changes on an in-shop packet: default no change order, as the old build.
 13. Work-order-gone confirmation after 2 consecutive runs and the 10% suspect-batch guard: defaults as stated.
 14. Pause scope: default pauses the feed, the drawing job and auto-release together.
-15. Gitea runner: whether the Samba DC container can run there (overlayfs xattrs, possibly cap SYS_ADMIN). Checked in phase 1; if not, CI uses a runner with a Docker socket on docker-1. Phase 1 finding (2026-10-16): the container needs `cap_add: [SYS_ADMIN]` (Samba 4.17 sets sysvol NT ACLs through `security.*` xattrs) and runs that way on docker-1; the Gitea runner itself is still to be tried. Phase 2 (2026-10-16): an act_runner with the host Docker socket is registered on docker-1 as `docker-1` (deploy/runner/); the first workflow run, after the repository is pushed to Gitea, shows whether its Docker proxy passes `cap_add` to the DC.
+15. Gitea runner: whether the Samba DC container can run there (overlayfs xattrs, possibly cap SYS_ADMIN). Checked in phase 1; if not, CI uses a runner with a Docker socket on docker-1. Phase 1 finding (2026-10-16): the container needs `cap_add: [SYS_ADMIN]` (Samba 4.17 sets sysvol NT ACLs through `security.*` xattrs) and runs that way on docker-1; the Gitea runner itself is still to be tried. Phase 2 (2026-10-16): an act_runner with the host Docker socket is registered on docker-1 as `docker-1` (deploy/runner/); resolved: the runner passes `cap_add` through, and the e2e job (stack with the DC plus the Playwright scenarios) passed on it on 2026-10-16.
 16. NPM: confirm `Block common exploits` does not interfere with uploads; checked when the test proxy host is made in phase 0.
 17. SET_DATABOOK_AT is writable by anyone in the old build, even when filed: default restrict to Clerical and Q.C.
 18. CO verifications cannot be withdrawn; ITP line signatures can be undone by the same inspector or an Admin before the block is signed.