fix(enrichments): treat provider 404 as no-match, not a cell error

Providers like People Data Labs signal 'no record found' with HTTP 404, which
executeTool surfaces as a failed ToolResponse (status on output.status). The
cascade now treats a 404 as a clean miss — falls through to the next provider
and lets the cell render 'Not found' — instead of marking the cell errored.
Auth/rate-limit/5xx still propagate as real errors.

Author: TheodoreSpeaks

apps/sim/enrichments/run.ts

@@ -64,6 +64,13 @@ export async function runEnrichment(
         { signal: ctx.signal }
       )
       if (!response.success) {
+        // A 404 means the provider simply has no record for these inputs — a
+        // clean no-match, not an infra failure. Fall through to the next
+        // provider without counting it as an error (so the cell shows "Not
+        // found" rather than an error). Other statuses (auth, rate-limit, 5xx)
+        // are real errors and propagate.
+        const status = (response.output as { status?: unknown } | undefined)?.status
+        if (status === 404) continue
         throw new Error(response.error ?? `${provider.toolId} failed`)
       }
       cost += readCost(response.output)