This was generated by AI during triage.
Tier 2 of the AvyFx → Avy rebrand (#647): migrating the functional avy-fx footprint — domains, email addresses, and external services. Split out from #647 because, unlike the display rename, this requires external-service access and a domain decision, so it can't be delegated to an AFK agent.
Depends on #647 for the display/branding side; this issue is the infra half of the same rebrand.
Brief (ready-for-human)
Category: enhancement
Summary: Migrate the avy-fx domain, email addresses, and external-service references to the new "Avy" brand.
Why this needs a human (not an AFK agent):
- A domain must be chosen and acquired first — there is no confirmed "Avy" domain in the code today. This is a branding/procurement decision, not a code change.
- Requires access to external systems: the DNS registrar, Vercel domain config, the email provider (Resend — SPF/DKIM/deliverability), and Notion.
- It's a production cutover that must be sequenced to avoid breaking live sites and email delivery.
Scope (the functional avy-fx footprint):
- Production domain
avy-fx.org → the new Avy domain: DNS, Vercel domains, redirects from the old domain, and NEXT_PUBLIC_ROOT_DOMAIN.
- Email addresses
support@avy-fx.org and noreply@avy-fx.org (the default from-address / adapter and the contact-form sender) → new-domain addresses, with email-provider config and deliverability verification.
- Help links
avy-fx.notion.site (in the logout button and the getting-started dashboard widget) → the new Notion/help URL.
- Template-tenant demo domain
avy-fx-demo.org (the DVAC template tenant in the avalanche-centers definition, and referenced in docs/onboarding.md).
Acceptance criteria:
Out of scope:
Open decision for the maintainer: what is the new domain? Everything here waits on that.
Tier 2 of the AvyFx → Avy rebrand (#647): migrating the functional
avy-fxfootprint — domains, email addresses, and external services. Split out from #647 because, unlike the display rename, this requires external-service access and a domain decision, so it can't be delegated to an AFK agent.Depends on #647 for the display/branding side; this issue is the infra half of the same rebrand.
Brief (ready-for-human)
Category: enhancement
Summary: Migrate the
avy-fxdomain, email addresses, and external-service references to the new "Avy" brand.Why this needs a human (not an AFK agent):
Scope (the functional
avy-fxfootprint):avy-fx.org→ the new Avy domain: DNS, Vercel domains, redirects from the old domain, andNEXT_PUBLIC_ROOT_DOMAIN.support@avy-fx.organdnoreply@avy-fx.org(the default from-address / adapter and the contact-form sender) → new-domain addresses, with email-provider config and deliverability verification.avy-fx.notion.site(in the logout button and the getting-started dashboard widget) → the new Notion/help URL.avy-fx-demo.org(the DVAC template tenant in the avalanche-centers definition, and referenced indocs/onboarding.md).Acceptance criteria:
avy-fx.orgredirects to it (no broken links).docs/onboarding.mdreference the new domain.avy-fx.org/avy-fx-demo.org/avy-fx.notion.sitein code or docs.Out of scope:
Open decision for the maintainer: what is the new domain? Everything here waits on that.