chore: merge develop to main for Cloudflare production custom domains

[ayoub3bidi]

Contribution workflow

• Base branch is main: This PR targets main from develop.
• Guidelines and docs: Read CONTRIBUTING.md and relevant docs.
• This template: PR template structure kept; sections below filled in.

Description

Final migration merge: ships the production custom-domain routes in wrangler.jsonc to main so the bayan-flow worker deploys with bayanflow.com and www.bayanflow.com.

This is not a v0.5.0 release PR. It completes the Netlify → Cloudflare cutover on the production branch. Staging (dev.bayanflow.com) should already be on Cloudflare from the prior develop deploy.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Style/UI improvement
• ⚡ Performance improvement
• 🧪 Test addition or improvement
• 🔧 Chore (maintenance, dependencies, etc.)

Related Issues

Fixes #

Changes Made

Migration (why this PR exists)

• Production routes in wrangler.jsonc: bayanflow.com, www.bayanflow.com
• Triggers Deploy (Cloudflare Workers) on main with --env production

Also on develop (rides along with merge)

Everything already merged to develop since the last main sync — including staging custom domain config, Cloudflare hosting (#183), and ongoing v0.5.0 work. No separate release tag planned.

Algorithm Details (if applicable)

N/A

Testing

• workers.dev production + staging smoke-tested
• dev.bayanflow.com verified on Cloudflare (staging) after prior develop merge
• After this merge: Deploy (Cloudflare Workers) green on main
• bayan-flow → Domains → bayanflow.com + www.bayanflow.com active
• DNS updated for apex + www (remove stale Netlify records if needed)
• Smoke https://bayanflow.com and https://www.bayanflow.com

Test Results

Rely on CI + post-merge deploy success and live URL checks.

Screenshots/GIFs

N/A

Code Quality

• develop CI green
• Merge-only; no new commits expected on this PR

Performance Impact

• No performance impact

Accessibility

• N/A

Breaking Changes

• Production DNS cutover is manual after deploy. bayanflow.com may still resolve to Netlify until DNS records are updated.
• Netlify projects retained ~2 weeks as rollback.

Checklist

• Staging custom domain live on Cloudflare
• Merge this PR → production worker deploy succeeds
• Confirm domains on bayan-flow worker
• DNS cutover for bayanflow.com / www
• Production smoke test (SPA refresh, badge, locales)
• Keep Netlify as rollback ~2 weeks, then cleanup

Additional Notes

After merge

1. Actions → Deploy (Cloudflare Workers) on main → green
2. bayan-flow → Domains → confirm bayanflow.com, www.bayanflow.com
3. DNS (zone on Cloudflare): remove/replace Netlify CNAMEs if traffic still hits Netlify
4. Smoke production URLs (same checklist as workers.dev + legal pages)

Migration complete when

• dev.bayanflow.com → Cloudflare staging worker
• bayanflow.com / www → Cloudflare production worker
• Both stable ~2 weeks → delete Netlify Bayan Flow projects

Then: Supabase auth (next phase).

Rollback

Point DNS back to Netlify. Projects and netlify.toml still available.

---

Reviewer Guidelines:

• Treat as migration merge, not feature review
• Confirm production deploy workflow will run on main

[netlify]

✅ Deploy Preview for dev-bayanflow ready!

Name	Link
🔨 Latest commit	6eca5d9
🔍 Latest deploy log	https://app.netlify.com/projects/dev-bayanflow/deploys/6a3af82b9119510008e86696
😎 Deploy Preview	https://deploy-preview-186--dev-bayanflow.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 797a32c6-02d7-4af8-952a-0b61119349a3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch develop

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!