🚦 Apex cutover: router claims agentrelay.com (DO NOT MERGE until cloud deploys)

[willwashburn]

The final flip. Changes the router's custom domain router-next.agentrelay.com
→ agentrelay.com, and WEBHOOK_WORKER_ORIGIN → the stable
https://incoming-webhooks.agentrelay.com.

⚠️ Merge/deploy ordering — do NOT merge until both cloud deploys land

1. Deploy cloud#2460 →
   incoming-webhooks.agentrelay.com exists.
2. Deploy cloud#2461
   (full-SST) → cloud releases the agentrelay.com custom domain.
3. Then merge this → deploy-router.yml runs wrangler deploy, and the new
   router claims the apex.

If merged before step 2, the deploy will fail/conflict (apex still owned by
cloud's router). If merged before step 1, webhook routing would 5xx (the
incoming-webhooks domain wouldn't exist yet).

Verify after

• curl -sI https://agentrelay.com/ → served by agentrelay-router, no CloudFront headers
• /, /cloud, /observer*, /docs/quickstart all 200
• webhook ingress still reaches the webhook worker (flag is worker)

Rollback

Revert cloud#2461 + redeploy → cloud's router re-claims the apex. (Keep
router-next available as a standby by reverting this PR's route line.)

---

Summary by cubic

Cut the router over to the apex agentrelay.com and point WEBHOOK_WORKER_ORIGIN to the stable https://incoming-webhooks.agentrelay.com. This makes the new router the front door and routes webhooks via the dedicated subdomain.

• Migration
  • Order: deploy cloud#2460 (create incoming-webhooks.agentrelay.com), then cloud#2461 (release agentrelay.com), then merge this PR to let deploy-router.yml claim the apex.
  • Verify: curl -I https://agentrelay.com/ returns from agentrelay-router (no CloudFront); /, /cloud, /observer*, /docs/quickstart return 200; webhook ingress still hits the worker.
  • Rollback: redeploy cloud#2461 to re-claim the apex; revert this route if keeping router-next as standby.

^{Written for commit 79483ed. Summary will update on new commits.}

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 41c3afff-a665-47e9-9ded-0d39c6b11f22

📥 Commits

Reviewing files that changed from the base of the PR and between e90a439 and 79483ed.

📒 Files selected for processing (1)

• router/wrangler.jsonc

---

📝 Walkthrough

Walkthrough

router/wrangler.jsonc is updated to point WEBHOOK_WORKER_ORIGIN at https://incoming-webhooks.agentrelay.com and to switch the Cloudflare route pattern from the staging hostname router-next.agentrelay.com to the apex domain agentrelay.com, with surrounding comments updated accordingly.

Changes

Production domain cutover

Layer / File(s)	Summary
Webhook origin and route pattern cutover router/wrangler.jsonc	WEBHOOK_WORKER_ORIGIN is changed to https://incoming-webhooks.agentrelay.com and the Cloudflare route pattern is switched from router-next.agentrelay.com to the apex agentrelay.com; surrounding comments are updated to reflect the cutover.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• AgentWorkforce/agentrelay.com#2: Initial setup of the same WEBHOOK_WORKER_ORIGIN binding and pattern field in router/wrangler.jsonc that this PR now updates.
• AgentWorkforce/agentrelay.com#3: Introduced the WEBHOOK_WORKER_ORIGIN variable by replacing the unresolvable service binding, which this PR now points at the production custom domain.

Poem

🐇 Hop, hop, the staging days are done,
The apex domain shines like the morning sun!
Webhooks now land on their own special place,
incoming-webhooks — what a splendid space.
The router points home, the cutover is won! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: router claiming the apex domain agentrelay.com during a cutover, with a critical deployment ordering note.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, providing detailed context about the apex cutover, deployment ordering, verification steps, and rollback procedures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch router-apex-cutover

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Preview deployed!

Environment	URL
Web	https://081137b7-agentrelay-web.agent-workforce.workers.dev

This is a Cloudflare Workers preview version of this PR's build.