Standardize Astro branch validation and publishing

README.md

@@ -110,13 +110,18 @@ http://localhost:4321/
 
 ## Deployment
 
-This project deploys as a static Astro build. A deployment job should install
-dependencies, run the build, and publish the generated `dist/` directory:
+This project deploys as a static Astro build through Forgejo Actions. Every
+branch push installs dependencies, builds the complete site, audits its links,
+and prepares the separate public and protected-admin bundles. Feature branches
+never receive Garage publishing credentials and never change production.
+
+Only commits on `main` synchronize the validated bundles to `familyfed.ie` and
+`admin.familyfed.ie` in Garage. A manual workflow dispatch is subject to the
+same branch guard: dispatching a feature branch builds it but cannot publish it.
+
+The equivalent local validation is:
 
 ```bash
 npm ci
-npm run build
+npm run check
 ```
-
-Use `npm run start` only when you intentionally want Astro to serve the built
-output in an environment such as a local or Nomad preview job.