fix(webapp): treat Loops 404 as successful contact deletion

When deleting a Loops contact, a 404 response indicates the contact
doesn’t exist, which is already the desired end state. Handle this
explicitly by returning true instead of falling through to the generic
error path.

- Treat HTTP 404 from Loops delete endpoint as success
- Add test coverage for the 404 case

Author: JosephDoUrden

apps/webapp/app/services/loops.server.ts

@@ -43,6 +43,11 @@ export class LoopsClient {
         body: JSON.stringify({ email }),
       });
 
+      if (response.status === 404) {
+        this.#logger.info(`Loops contact already deleted`, { email });
+        return true;
+      }
+
       if (!response.ok) {
         this.#logger.error(`Loops deleteContact bad status`, { status: response.status, email });
         return false;

apps/webapp/test/loopsClient.test.ts

@@ -58,6 +58,18 @@ describe("LoopsClient", () => {
       expect(result).toBe(true);
     });
 
+    it("should return true when API returns 404 (contact already deleted)", async () => {
+      mockFetch.mockResolvedValueOnce({
+        ok: false,
+        status: 404,
+      });
+
+      const client = new LoopsClient("test-api-key", noopLogger);
+      const result = await client.deleteContact({ email: "test@example.com" });
+
+      expect(result).toBe(true);
+    });
+
     it("should return false on API error (500)", async () => {
       mockFetch.mockResolvedValueOnce({
         ok: false,