Add Cloudflare DNS CNAME: localmate.crewcircle.co → cname.vercel-dns.com

[rprabhat]

Action Required

The Vercel dashboard is live at https://localmate-eta.vercel.app but the custom domain localmate.crewcircle.co needs a DNS record.

What to do

1. Log into the Cloudflare account that owns crewcircle.co (nameservers: desiree.ns.cloudflare.com, yichun.ns.cloudflare.com)
2. Go to DNS → Records → Add record
3. Add:

Field	Value
Type	CNAME
Name	localmate
Target	cname.vercel-dns.com
Proxy status	Proxied (orange cloud)

4. Save. DNS propagates in 1-5 minutes.
5. Vercel auto-issues SSL certificate once DNS resolves.
6. Verify: https://localmate.crewcircle.co should redirect to /dashboard and show the LocalMate dashboard.

Why this cannot be automated

The Cloudflare API tokens available in the CI/CD environment are from a different Cloudflare account that has zero zones — it cannot see the crewcircle.co zone.

Impact

Until this is done, the dashboard is accessible only via the Vercel URL: https://localmate-eta.vercel.app

[rprabhat]

Update: Automated via scripts/finish_infra.sh

The DNS CNAME record creation is now scripted in scripts/finish_infra.sh (commit d2c0d12). It uses Doppler-injected CLOUDFLARE_API_TOKEN + CLOUDFLARE_ZONE_ID (inherited from crewcircle-master/prod) to create both records via the Cloudflare API.

doppler run --project localmate --config prd -- bash scripts/finish_infra.sh

Creates: CNAME localmate → cname.vercel-dns.com (dashboard) + A api.localmate → 170.64.183.45 (backend).

This issue closes once https://localmate.crewcircle.co serves the dashboard.