Use blue/green content prefixes for consistent deployments

What information was incorrect, unhelpful, or incomplete?

Deployments currently synchronize the generated site directly into the live fred/ bucket prefix before updating the regional Cloud Functions.

Requests can therefore observe partially synchronized content or a mismatch between content and the redirects and canonicals embedded in the function.

What did you expect to see?

Alternate deployments between blue/ and green/ prefixes:

1. Read SOURCE_CONTENT from every regional function and abort if they do not agree on the active prefix.
2. Synchronize the complete build into the inactive prefix.
3. Synchronize static assets to both prefixes without deleting older hashed assets, so cached pages continue to work after a cutover or rollback.
4. Deploy every regional function with SOURCE_CONTENT pointing at the prepared prefix.
5. Leave the previous prefix unchanged for rollback.

Deployments for each environment should be serialized so concurrent runs cannot select the same inactive prefix.

Do you have any supporting links, references, or citations?

The current production deployment synchronizes content and deploys the functions in .github/workflows/prod-build.yml.

Do you have anything more you want to share?

Each prefix could include a manifest containing the release commit so the workflow and deployed function can verify that they reference the expected build.

This would not make the three regional function updates atomic, but every region would serve a complete, internally consistent release throughout deployment. A load-balancer-level cutover could be considered separately if a single global switch is later required.

Start by reading .github/workflows/prod-build.yml to understand the current content synchronization and regional function deployment steps. Implement serialized blue/green deployments with agreed SOURCE_CONTENT values, complete inactive-prefix content, preserved assets, and rollback safety; done means each region serves a complete consistent release and concurrent runs cannot select the same prefix.