fix(whatsapp): always record per-contact last-route regardless of pin guard

chinar-amrutkar · chinar-amrutkar · commit 96e3bc871370 · 2026-05-03T10:35:09.000+01:00
The pin guard (pinnedMainDmRecipient) applies only to main session updates.
Per-contact sessions should always record their last-route since they are
independent of the main session pin state.

Updated test to use pinnedMainDmRecipient that differs from dmRouteTarget
to verify the per-contact session is updated even when not the pinned owner.
diff --git a/extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.test.ts b/extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.test.ts
@@ -824,7 +824,7 @@ describe("whatsapp inbound dispatch", () => {
       cfg: {} as never,
       ctx: { Body: "hello" },
       dmRouteTarget: "+3000",
-      pinnedMainDmRecipient: null,
+      pinnedMainDmRecipient: "+1000", // owner different from dmRouteTarget
       route: makeRoute({
         sessionKey: "agent:main:whatsapp:direct:+3000",
         mainSessionKey: "agent:main:main",
diff --git a/extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.ts b/extensions/whatsapp/src/auto-reply/monitor/inbound-dispatch.ts
@@ -256,12 +256,10 @@ export function updateWhatsAppMainLastRoute(params: {
     return;
   }
 
-  // Record last-route for per-contact session when using scoped dmScope
-  if (
-    params.dmRouteTarget &&
-    params.route.sessionKey !== params.route.mainSessionKey &&
-    shouldUpdateMainLastRoute
-  ) {
+  // Record last-route for per-contact session when using scoped dmScope.
+  // Always record per-contact sessions regardless of pinnedMainDmRecipient,
+  // since the pin guard only applies to main session updates.
+  if (params.dmRouteTarget && params.route.sessionKey !== params.route.mainSessionKey) {
     params.updateLastRoute({
       cfg: params.cfg,
       backgroundTasks: params.backgroundTasks,
