deploy: drop Gitea Actions deploy job, cron autodeploy is sole path

.gitea/workflows/deploy.yml

@@ -1,16 +0,0 @@
-name: Deploy
-
-# Auto-deploy on push to main. Runs on the self-hosted Gitea runner (which has the
-# host Docker socket) and rebuilds + restarts the stack on the same host.
-# The public site ends up on host port 1337 (see deploy/docker-compose.yml).
-on:
-  push:
-    branches: [main]
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Build and (re)start the stack
-        run: docker compose -f deploy/docker-compose.yml up -d --build --remove-orphans

PROJECT_STATUS.md

@@ -65,8 +65,9 @@
   (nginx static, publishes 1337) + `deploy-relay-1` (contact relay, internal). Verified: all
   routes + `/no/`, case studies, CV PDFs, images, `/Linkedin` 301, `/api/contact` proxy.
 - **Auto-deploy:** a 1-minute cron on the host (`deploy/autodeploy.sh`) pulls `main` and
-  `docker compose up -d --build` on change. `.gitea/workflows/deploy.yml` also exists for the
+  `docker compose up -d --build` on change. Sole deploy path — the Gitea Actions `deploy.yml`
-  Gitea runner (activate once its job image has the Docker CLI + socket).
+  job was removed (its runner's job containers have no Docker socket, and mounting one in would
+  give any CI job root-equivalent host access).
 - Repo cloned at `/home/pi/resumesite` (remote carries the deploy token — rotate/scrub if desired).
 
 ## Owner action remaining