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.

app/api/preview-link/route.ts

@@ -1,7 +1,7 @@
 /**
  * GET /api/preview-link?cid=<contactId>&token=<HEALTH_TOKEN>
  *
- * Returns a ready-to-send check-in URL for a given contact, plus enough
+ * Returns a ready-to-send survey URL for a given contact, plus enough
  * context for staff to verify it's the right org. Used for:
  *   - Generating links to paste into ad-hoc emails (or external tools)
  *   - Testing a contact's setup before sending the real CiviCRM email

app/api/report/route.ts

@@ -49,11 +49,11 @@ const STUB_PAYLOAD: ReportPayload = (() => {
     orgName: "Sample Co-op (stub)",
     currentStage: "Organizing",
     activities: [
-      { id: 9012, date: daysAgo(3), subject: "Co-op Check-in (form submission)" },
-      { id: 9008, date: daysAgo(34), subject: "Co-op Check-in (form submission)" },
+      { id: 9012, date: daysAgo(3), subject: "Co-op Survey (form submission)" },
+      { id: 9008, date: daysAgo(34), subject: "Co-op Survey (form submission)" },
       { id: 9001, date: daysAgo(62), stage: "Organizing", subject: "Stage transition (staff)" },
-      { id: 8995, date: daysAgo(95), subject: "Co-op Check-in (form submission)" },
-      { id: 8980, date: daysAgo(180), stage: "Inquiry", subject: "Initial check-in (staff)" },
+      { id: 8995, date: daysAgo(95), subject: "Co-op Survey (form submission)" },
+      { id: 8980, date: daysAgo(180), stage: "Inquiry", subject: "Initial survey (staff)" },
     ],
     fieldHistory: {
       Peer_Group_Participation: [

app/api/submit/route.ts

@@ -70,7 +70,7 @@ export async function POST(req: Request) {
     return NextResponse.json(
       {
         error: appEnv().isProduction
-          ? "Could not save your check-in. Please try again, or contact your engagement coordinator."
+          ? "Could not save your survey. Please try again, or contact your engagement coordinator."
           : `Save failed: ${redact(msg)}`,
       },
       { status: 500 },
@@ -110,7 +110,7 @@ async function runSubmit(cid: string, cs: string, values: Record<string, unknown
     "status_id:name": "Completed",
     target_contact_id: orgId,
     source_contact_id: Number(cid),
-    subject: "Co-op Check-in (form submission)",
+    subject: "Co-op Survey (form submission)",
   };
   for (const [name, value] of Object.entries(values)) {
     const field = FIELD_BY_NAME.get(name);

app/layout.tsx

@@ -28,7 +28,7 @@ const body = Open_Sans({
 });
 
 export const metadata: Metadata = {
-  title: "Co-op Check-in · Food Co-op Initiative",
+  title: "Co-op Survey · Food Co-op Initiative",
   description:
     "Update your co-op's progress through the FCI organizing Framework. A survey for food co-ops in development.",
   robots: { index: false, follow: false }, // Form pages are tokenized; not for crawlers.

app/report/page.tsx

@@ -52,7 +52,7 @@ function ReportIntro() {
       </h1>
       <p className="mt-4 max-w-prose text-[17px] leading-relaxed text-ink-soft">
         A read-only summary of every value your co-op has shared through past
-        check-ins, grouped by stage. The most recent entry sits at the top of
+        surveys, grouped by stage. The most recent entry sits at the top of
         each row; expand a row to see how a number or note has changed over
         time.
       </p>