Wire up automated deploy via Gitea Releases + site-deployer watcher

README.md

@@ -24,18 +24,20 @@ npm run build
 
 Output goes to `dist/`.
 
-## Deploy (manual, for now)
+## Deploy
 
-CI builds and uploads `dist/` as an artifact on every push to `main`, but
-does not yet sync it to the server automatically — the Gitea act runner
-uses ephemeral job containers with no host-visible workspace path, so an
-auto-deploy step needs an SSH deploy key added as a Gitea Actions secret
-first. Until that's set up, deploy manually:
+Every push to `main` builds the site and publishes `dist/` (zipped) as the
+asset on a Gitea Release tagged `deploy`, using the automatic per-job
+`GITEA_TOKEN` — no secrets to configure. A separate `site-deployer` watcher
+container on octo-winsrv polls that release (`releases/tags/deploy`) every
+~45s and, when it changes, extracts it into `/mnt/e/sites/continuum-3d-com/`,
+which Caddy serves as the document root for `continuum-3d.com`. No SSH keys
+or admin credentials are involved — the watcher only has filesystem access
+to `/mnt/e/sites`, nothing else on the host.
+
+Manual deploy still works if you need it immediately (bypasses the watcher):
 
 ```
 npm run build
 scp -r dist/* <host>:/mnt/e/sites/continuum-3d-com/
 ```
-
-Caddy serves `/mnt/e/sites/continuum-3d-com` as the document root for
-`continuum-3d.com`.