Rebrand: Co-op Check-in -> Co-op Survey in user-facing copy

Updates the tool product name across the app UI (header, page title,
section labels, form buttons, success/error states, report stat labels),
README, deployment docs, and the CiviCRM email template guidance.
Custom domain references move from check-in.fci.coop to survey.fci.coop
(DNS update still required).

The underlying CiviCRM "Check-in (organizing)" activity type, custom
group machine names (Check_in_data__organizing_), health-check ids,
and the internal org_engagement_check_in form id are unchanged --
those are CiviCRM contract surfaces, not product copy.

EMAIL_DELIVERY.md

@@ -1,10 +1,10 @@
 # Email link delivery
 
-The check-in form is reached via a personalized URL that carries the
+The survey form is reached via a personalized URL that carries the
 contact's CiviCRM ID + a server-issued checksum:
 
 ```
-https://check-in.fci.coop/?cid=<contact_id>&cs=<checksum>
+https://survey.fci.coop/?cid=<contact_id>&cs=<checksum>
 ```
 
 This document covers the three pieces needed to actually get those links
@@ -24,10 +24,10 @@ The preview endpoint (#3) is a debugging convenience.
 In CiviCRM:
 
 1. Navigate to **Mailings → Message Templates → Add Message Template**.
-2. Title: `Co-op Check-in invitation`
+2. Title: `Co-op Survey invitation`
 3. Subject:
    ```
-   Time for your co-op check-in
+   Time for your co-op survey
    ```
 4. Plain-text body (substitute your real domain):
 
@@ -38,8 +38,8 @@ In CiviCRM:
    month. The form pre-fills your prior responses — you only need to update
    what's changed.
 
-   Open your check-in:
-   https://check-in.fci.coop/?cid={contact.contact_id}&cs={contact.checksum}
+   Open your survey:
+   https://survey.fci.coop/?cid={contact.contact_id}&cs={contact.checksum}
 
    The link is personalized to you and expires in 14 days. If you no longer
    have it, reply to this email and we'll send a fresh one.
@@ -58,11 +58,11 @@ In CiviCRM:
    what's changed.</p>
 
    <p style="margin: 24px 0;">
-     <a href="https://check-in.fci.coop/?cid={contact.contact_id}&amp;cs={contact.checksum}"
+     <a href="https://survey.fci.coop/?cid={contact.contact_id}&amp;cs={contact.checksum}"
         style="display: inline-block; background: #3a5520; color: #fafaf7;
                padding: 10px 20px; border-radius: 6px; text-decoration: none;
                font-weight: 500;">
-       Open your check-in
+       Open your survey
      </a>
    </p>
 
@@ -95,14 +95,14 @@ Best for: low volume, one-at-a-time, or you want to review each send.
 1. Open the **organization's contact record** in CiviCRM.
 2. **Relationships** tab → find the row with **"Primary Contact"** → click the related individual's name.
 3. On the individual's contact view: **Actions → Send Email**.
-4. **Use Template**: select `Co-op Check-in invitation`. The subject and body populate; tokens render in the preview.
+4. **Use Template**: select `Co-op Survey invitation`. The subject and body populate; tokens render in the preview.
 5. **Send**. CiviCRM logs the email as an Activity on the contact.
 
 Repeat per contact. Slow but bulletproof.
 
 ### Option B — Bulk: CiviMail (campaign-style send)
 
-Best for: send the check-in invitation to every active co-op at once (e.g. monthly).
+Best for: send the survey invitation to every active co-op at once (e.g. monthly).
 
 1. Build a Smart Group of contacts whose Primary Contact relationships point at orgs in active stages. Example query:
    - **Contacts** → **Advanced Search**
@@ -112,7 +112,7 @@ Best for: send the check-in invitation to every active co-op at once (e.g. month
 
 2. **Mailings → New Mailing**.
 3. Recipients: the smart group above.
-4. Choose template: `Co-op Check-in invitation`.
+4. Choose template: `Co-op Survey invitation`.
 5. Schedule send.
 
 Each recipient gets their own checksum embedded in the URL — CiviMail
@@ -125,10 +125,10 @@ Best for: a button-on-the-org-record workflow.
 Setup:
 
 1. **Administer → CiviRules → Manage Rules → New Rule**.
-2. Title: `Send Co-op Check-in invitation`.
+2. Title: `Send Co-op Survey invitation`.
 3. **Trigger**: pick a "manually trigger from org row" action if your CiviRules version supports it. Otherwise: trigger on org Stage change (auto-fires when staff advance an org).
 4. **Action**: `Send email to contact via message template`.
-   - Template: `Co-op Check-in invitation`.
+   - Template: `Co-op Survey invitation`.
    - Recipient: **Contact in relationship** → "Primary Contact" → side B (the Individual).
 5. Save.
 
@@ -153,7 +153,7 @@ contact/org context for verification.
 **Request:**
 
 ```bash
-curl "https://check-in.fci.coop/api/preview-link?cid=513&token=$HEALTH_TOKEN"
+curl "https://survey.fci.coop/api/preview-link?cid=513&token=$HEALTH_TOKEN"
 ```
 
 **Response:**
@@ -165,7 +165,7 @@ curl "https://check-in.fci.coop/api/preview-link?cid=513&token=$HEALTH_TOKEN"
   "orgId": 9609,
   "orgName": "A Sample Food Co-op",
   "orgStage": "Organizing",
-  "url": "https://check-in.fci.coop/?cid=513&cs=8d1f...",
+  "url": "https://survey.fci.coop/?cid=513&cs=8d1f...",
   "checksum": "8d1f...",
   "ttlHours": 336
 }