fix(web): pass accountId in WhatsApp provider activity tracking

Recent changes added recordProviderActivity calls with accountId, but
the type definition and usage didn't include accountId in ActiveWebSendOptions.
This fix adds the optional accountId field and uses optional chaining
when accessing it to handle cases where options is undefined.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

src/web/active-listener.ts

@@ -3,6 +3,7 @@ import { DEFAULT_ACCOUNT_ID } from "../routing/session-key.js";
 
 export type ActiveWebSendOptions = {
   gifPlayback?: boolean;
+  accountId?: string;
 };
 
 export type ActiveWebListener = {

src/web/inbound.ts

@@ -587,7 +587,7 @@ export async function monitorWebInbox(options: {
       const result = await sock.sendMessage(jid, payload);
       recordProviderActivity({
         provider: "whatsapp",
-        accountId: options.accountId,
+        accountId: options?.accountId,
         direction: "outbound",
       });
       return { messageId: result?.key?.id ?? "unknown" };
@@ -610,7 +610,7 @@ export async function monitorWebInbox(options: {
       });
       recordProviderActivity({
         provider: "whatsapp",
-        accountId: options.accountId,
+        accountId: options?.accountId,
         direction: "outbound",
       });
       return { messageId: result?.key?.id ?? "unknown" };