Automate primary production deployments from main

docs/cutover-runbook.md

@@ -20,10 +20,10 @@ static assets to a distinct Worker.
 - Existing Pages production deployment: `2fb1b659-5928-4470-bb04-ef4c9105b843`
   from the `main` branch.
 - Preview Worker: `3031023-xyz-www-preview`, with no custom domains or routes.
-- Production candidate Worker: `3031023-xyz-www`, deployed only through the
-  dedicated `Deploy primary production Worker candidate` workflow. Its push
-  trigger is limited to changes to that workflow file; ordinary site commits
-  cannot update this Worker.
+- Production Worker: `3031023-xyz-www`, deployed by the dedicated `Deploy
+  primary production Worker` workflow for relevant pushes to `main`. The
+  workflow updates static assets only; it cannot change DNS, custom domains,
+  routes, or redirect rules.
 
 ## Cutover sequence (requires separate approval)
 
@@ -76,8 +76,9 @@ the cutover. Review it with the site's AI-search policy before final acceptance.
 
 - Source commit: `2b7f8d8` (`main`), the accepted Git-backed Markdown content
   pilot.
-- Release path: the manually approved `Deploy primary production Worker
-  candidate` workflow completed successfully in 22 seconds.
+- Release path: the manually approved production workflow completed
+  successfully in 22 seconds. Subsequent relevant `main` pushes use the same
+  static-asset-only workflow automatically.
 - Scope: updated only the static assets of the existing `3031023-xyz-www`
   Worker. No custom domain, DNS, redirect rule, Pages project, form workflow,
   CMS, or client-editing boundary changed.