Migrate enrichment to Dench gateway (dench_enrich, hybrid async)

[vedworks]

Summary

• Migrates Apollo-era enrichment routes to the FullEnrich-backed Dench gateway APIs across both the web app and the agent plugin.
• Renames the agent tool apollo_enrich → dench_enrich with hybrid async behavior: a cache hit returns the person inline, while queued jobs return an enrichmentId + poll path.
• Web SSE enrich route now polls queued jobs with a short per-row timeout and surfaces pending / error events; email-only person enrichment is rejected (LinkedIn URL required).
• Adds a shared gateway client (extensions/shared/dench-gateway-client.ts) mirrored into apps/web/lib/dench-gateway-enrichment.ts to avoid a cross-workspace import the Turbopack bundler can't resolve.
• Removes dead Composio tool-router code, updates the dench-identity prompt/skills, rebuilds plugin .mjs bundles, and adds activation + contracts.tools to plugin manifests so the gateway loads and registers the tools.
• Rewrites/extends tests (enrich route, enrichment-columns, apollo-enrichment plugin) for the new gateway contract and field mapping (requiredFields → enrichFields).

Notes / Findings

• During verification, dench_enrich works end-to-end and reaches the gateway, but enrichment calls return 402 insufficient_credits (requiredCents: 5, availableCents: 0) from gateway.merseoriginals.com. LLM chat works because it bills against a separate on-demand usage meter; enrichment requires a separate prepaid credit ledger that is currently empty for the org. This is a gateway-side billing/provisioning configuration, not a code bug in this repo.

Test plan

• apps/web enrich route tests pass (LinkedIn person, queued-job polling, pending state, company search, email rejection, entryIds narrowing/validation).
• enrichment-columns tests pass for getEnrichFieldsForApolloPath.
• extensions/apollo-enrichment plugin tests pass for dench_enrich.
• Plugin .mjs bundles rebuilt; gateway loads apollo-enrichment, exa-search, posthog-analytics and registers their tools.
• Agent has dench_enrich available (no Composio fallback) once tool policy allows it.

---

Note

High Risk
Enrichment is a breaking contract change (LinkedIn-only people, new gateway endpoints, tool rename) across API routes, CRM column UX, and agent tools; incorrect mapping or polling could drop data or confuse agents until clients adapt.

Overview
This PR moves workspace and agent enrichment off legacy Apollo HTTP onto the Dench Cloud gateway (person contact, company search, people search, job polling). The web enrich route calls shared gateway helpers instead of raw fetch, maps column metadata to enrichFields, polls queued LinkedIn jobs with a short timeout, and emits pending SSE events when work is still in flight.

People enrichment behavior tightens: email is no longer an eligible input field or row identifier; validation rejects email-typed fields with 400, and per-row email values error without calling the gateway. Company enrichment uses POST /company/search by domain rather than GET with requiredFields query params.

A new apps/web/lib/dench-gateway-enrichment.ts mirrors the extension shared client so Next.js/Turbopack does not cross the workspace boundary. The apollo_enrich agent tool becomes dench_enrich with actions job_status, hybrid sync (inline person vs enrichmentId), and enrichFields instead of default Apollo requiredFields lists; plugin manifests gain activation.onStartup and contracts.tools. Agent prompts in dench-identity are updated accordingly, and a large block of unused Composio tool-router resolver code is removed from that plugin.

Tests for the enrich route, enrichment-columns, and the enrichment plugin are rewritten for the new contract. Layout/sidebar tweaks switch h-screen to h-dvh / h-full min-h-0 so the deprecation banner and main shell scroll correctly.

^{Reviewed by Cursor Bugbot for commit 701b78e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 4 potential issues.

Autofix Details

Bugbot Autofix prepared fixes for all 4 issues found in the latest run.

• ✅ Fixed: Email default breaks people enrich
  • Swapped priority in autoDetectInputField to prefer LinkedIn fields over email fields for people category, matching the gateway's LinkedIn URL requirement.
• ✅ Fixed: Poll loop on empty success
  • Added an explicit branch in pollEnrichmentJobWithTimeout for succeeded-with-no-data that returns a clear error immediately instead of falling through to a tight retry loop.
• ✅ Fixed: Apollo-only fields map to emails
  • Changed mapRequiredFieldsToEnrichFields to return undefined instead of defaulting to ["work_emails"] when all tokens are unmapped Apollo-only fields, letting the gateway use its full default backfill.
• ✅ Fixed: Polls placeholder enrichment job id
  • Added a guard in callDenchGateway to fail fast with a descriptive error when enrichmentId is missing or "unknown" instead of polling a placeholder endpoint.

Or push these changes by commenting:

@cursor push 35c4368854

Preview (35c4368854)

diff --git a/apps/web/app/api/workspace/objects/[name]/enrich/route.ts b/apps/web/app/api/workspace/objects/[name]/enrich/route.ts
--- a/apps/web/app/api/workspace/objects/[name]/enrich/route.ts
+++ b/apps/web/app/api/workspace/objects/[name]/enrich/route.ts
@@ -372,6 +372,10 @@
 				return { ok: true, payload: contact.result.person };
 			}
 
+			if (!contact.result.enrichmentId || contact.result.enrichmentId === "unknown") {
+				return { ok: false, error: "No enrichment data returned" };
+			}
+
 			const poll = await pollEnrichmentJobWithTimeout(
 				gatewayUrl,
 				apiKey,

diff --git a/apps/web/lib/dench-gateway-enrichment.ts b/apps/web/lib/dench-gateway-enrichment.ts
--- a/apps/web/lib/dench-gateway-enrichment.ts
+++ b/apps/web/lib/dench-gateway-enrichment.ts
@@ -85,7 +85,7 @@
     }
     // Apollo-only fields (fullName, headline, linkedinID, etc.) have no enrichFields equivalent.
   }
-  if (tokens.size === 0) return ["work_emails"];
+  if (tokens.size === 0) return undefined;
   return [...tokens];
 }
 
@@ -434,6 +434,12 @@
         person: normalizePersonRecord(job.people[0] as Record<string, unknown>),
       };
     }
+    if (job.status === "succeeded") {
+      return {
+        ok: false,
+        error: "Enrichment succeeded but returned no data",
+      };
+    }
     if (job.status === "pending" && attempt < maxAttempts - 1) {
       await new Promise((resolve) => setTimeout(resolve, delayMs));
       continue;

diff --git a/apps/web/lib/enrichment-columns.ts b/apps/web/lib/enrichment-columns.ts
--- a/apps/web/lib/enrichment-columns.ts
+++ b/apps/web/lib/enrichment-columns.ts
@@ -255,14 +255,14 @@
 ): FieldCandidate | null {
 	const eligibleFields = getEligibleInputFields(category, fields);
 	if (category === "people") {
+		const linkedinField = eligibleFields.find(
+			(f) => /linkedin/i.test(f.name),
+		);
+		if (linkedinField) return linkedinField;
 		const emailField = eligibleFields.find(
 			(f) => f.type === "email" || /^e[-_]?mail/i.test(f.name),
 		);
 		if (emailField) return emailField;
-		const linkedinField = eligibleFields.find(
-			(f) => /linkedin/i.test(f.name),
-		);
-		if (linkedinField) return linkedinField;
 	} else {
 		const domainField = eligibleFields.find(
 			(f) => /website|domain|^url$/i.test(f.name),

diff --git a/extensions/shared/dench-gateway-client.ts b/extensions/shared/dench-gateway-client.ts
--- a/extensions/shared/dench-gateway-client.ts
+++ b/extensions/shared/dench-gateway-client.ts
@@ -72,7 +72,7 @@
     }
     // Apollo-only fields (fullName, headline, linkedinID, etc.) have no enrichFields equivalent.
   }
-  if (tokens.size === 0) return ["work_emails"];
+  if (tokens.size === 0) return undefined;
   return [...tokens];
 }
 
@@ -422,6 +422,12 @@
         person: normalizePersonRecord(job.people[0] as Record<string, unknown>),
       };
     }
+    if (job.status === "succeeded") {
+      return {
+        ok: false,
+        error: "Enrichment succeeded but returned no data",
+      };
+    }
     if (job.status === "pending" && attempt < maxAttempts - 1) {
       await new Promise((resolve) => setTimeout(resolve, delayMs));
       continue;

_{You can send follow-ups to the cloud agent here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Timeout poll marks pending incorrectly
  • Removed the incorrect pending: true from the timeout fallback return in pollEnrichmentJobWithTimeout, so only genuinely pending jobs (last attempt with status 'pending') are flagged as pending.

Or push these changes by commenting:

@cursor push b7ba9ddd82

Preview (b7ba9ddd82)

diff --git a/apps/web/lib/dench-gateway-enrichment.ts b/apps/web/lib/dench-gateway-enrichment.ts
--- a/apps/web/lib/dench-gateway-enrichment.ts
+++ b/apps/web/lib/dench-gateway-enrichment.ts
@@ -454,5 +454,5 @@
     }
   }
 
-  return { ok: false, error: "Enrichment timed out", pending: true };
+  return { ok: false, error: "Enrichment timed out" };
 }

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 701b78e. Configure here.}

[cursor]

Timeout poll marks pending incorrectly

Medium Severity

When pollEnrichmentJobWithTimeout exhausts its attempts, it returns failure with message Enrichment timed out but still sets pending: true. The enrich SSE handler treats any pending result as a signal to emit a pending event with enrichmentId, so rows that timed out during polling can be shown as still in progress even though the route has already stopped waiting.

Additional Locations (1)

• apps/web/app/api/workspace/objects/[name]/enrich/route.ts#L271-L279

 

^{Reviewed by Cursor Bugbot for commit 701b78e. Configure here.}