Docs: the domains are on the azphalt Worker (merging deploys it)

[HereLiesAz]

Merge this to deploy the store. All four hostnames now point at the azphalt Worker, but that Worker still runs the dashboard's "Hello world" placeholder. The real Worker has never deployed, for two reasons:

• The push that should have deployed it (Everything store.azphalt → com.hereliesaz.azphalt; set PLAY_PACKAGE_NAME #230's merge) landed before the sync centralized the workflows.
• A manual run of deploy-storefront.yml deploys nothing, because the gateway ignores manual tracker runs.

This PR touches apps/storefront-worker/ and docs/, so merging it starts the central deploy. That deploy builds and tests the Worker, deploys it as azphalt, and verifies it.

Changes

• apps/storefront-worker/README.md § Domains: the domains are attached. Three steps are left: the secrets, the Stripe webhook, and deleting the Vercel project. The section also notes that manual runs don't deploy.
• docs/OPERATIONS.md § Cutover status: the same update.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv

---

Generated by Claude Code

Summary by Sourcery

Update storefront operations documentation for the completed domain cutover to the azphalt Worker and the remaining steps to retire Vercel.

Enhancements:

• Update storefront and operations documentation to reflect that all public domains now use the azphalt Worker and identify the remaining Vercel cutover tasks.
• Document the central deployment workflow and clarify that manual tracker workflow runs do not deploy the storefront.

Documentation:

• Document the completed domain cutover, remaining secrets, Stripe webhook, and Vercel cleanup steps, plus live deployment verification guidance.

[sourcery-ai]

Sorry @HereLiesAz, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 6 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
azphalt	Skipped		Sep 27, 2026 4:08pm UTC

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This documentation-only PR records that production domains have moved from Vercel to the azphalt Worker, explains the remaining cutover work and deployment behavior, and updates operational status; merging the touched paths is intended to trigger the centralized Worker deployment.

File-Level Changes

Change	Details	Files
Update storefront and operations documentation to reflect that the production domains now use the Cloudflare Worker and clarify the remaining cutover tasks.	Mark all four hostnames as attached to the azphalt Worker. Reduce the remaining migration checklist to secrets, Stripe webhook configuration, and Vercel project removal. Document the post-deploy verification URLs and the limitation that manual tracker workflow runs do not deploy. Update the operational cutover status and link it to the detailed storefront instructions.	apps/storefront-worker/README.md docs/OPERATIONS.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[HereLiesAz]

The red validate_* jobs in CI are not failures. The central CI Validation workflow received several dispatches for this commit, and its concurrency group cancelled the extra ones (runs 364 and 365: every job cancelled). The CI tracker attached to run 364 and reported its cancellation as failure. The run that does the work is 366.

This PR only changes docs, so none of that blocks merging. The merge is what triggers the first real deploy.

---

Generated by Claude Code

[HereLiesAz]

OpenCode security review

⚠️ Review unavailable. Neither model answered; see the shared workflow run. This is not a finding about the pull request.