Fix Railway image tag

Co-authored-by: npub1jh9wn95s0472h86ahapupaf7m6kx4v9sx2n0atj2hltcfer8k06s5n3pyf <95cae996907d7cab9f5dbf43c0f53edeac6ab0b032a6feae4abfd784e467b3f5@sprout-oss.stage.blox.sqprod.co>
Signed-off-by: npub1jh9wn95s0472h86ahapupaf7m6kx4v9sx2n0atj2hltcfer8k06s5n3pyf <95cae996907d7cab9f5dbf43c0f53edeac6ab0b032a6feae4abfd784e467b3f5@sprout-oss.stage.blox.sqprod.co>

deploy/railway/README.md

@@ -10,7 +10,7 @@ This directory contains Buzz's first-party Railway template draft. It is intenti
 
 `railway.template.json` models the current full Buzz deployment as six Railway services:
 
-- `Buzz` (`ghcr.io/block/buzz:latest`) — the relay and bundled web UI.
+- `Buzz` (`ghcr.io/block/buzz:main`) — the relay and bundled web UI. `:main` is the rolling pre-release image published from the repository's default branch; production operators should pin `:sha-<7>` or a semver tag once releases exist.
 - `Postgres` — persistent database volume with daily backups requested in the template.
 - `Redis` — authenticated persistent pub/sub/cache service.
 - `Typesense` — persistent search service.
@@ -43,7 +43,7 @@ This template is mechanically valid JSON and follows the v2 template mechanics o
 
 End-to-end click-through validation is intentionally blocked until:
 
-1. `ghcr.io/block/buzz:<version>` is publicly published.
+1. `ghcr.io/block/buzz:main` is publicly published by the image pipeline.
 2. Buzz owns fresh-database migrations at startup or through the same image.
 
 Until both land, this template should be treated as first-party deploy wiring, not a proven production install.

deploy/railway/railway.template.json

@@ -6,7 +6,7 @@
     "buzz": {
       "name": "Buzz",
       "source": {
-        "image": "ghcr.io/block/buzz:latest"
+        "image": "ghcr.io/block/buzz:main"
       },
       "deploy": {
         "healthcheckPath": "/_readiness",