fix: gate libsignal session logs behind verbose

CHANGELOG.md

@@ -25,6 +25,7 @@
 - WhatsApp inbound now normalizes more wrapper types so quoted reply bodies are extracted reliably.
 - WhatsApp send now preserves existing JIDs (including group `@g.us`) instead of coercing to `@s.whatsapp.net`. (Thanks @arun-8687.)
 - Telegram/WhatsApp: reply context stays in `Body`/`ReplyTo*`, but outbound replies no longer thread to the original message. (Thanks @joshp123 for the PR and follow-up question.)
+- Suppressed libsignal session cleanup spam from console logs unless verbose mode is enabled.
 - WhatsApp web creds persistence hardened; credentials are restored before auth checks and QR login auto-restarts if it stalls.
 - Group chats now honor `routing.groupChat.requireMention=false` as the default activation when no per-group override exists.
 - Gateway auth no longer supports PAM/system mode; use token or shared password.

src/logging.ts

@@ -253,9 +253,16 @@ export function routeLogsToStderr(): void {
   forceConsoleToStderr = true;
 }
 
-const SUPPRESSED_CONSOLE_PREFIXES = ["Closing session:"] as const;
+const SUPPRESSED_CONSOLE_PREFIXES = [
+  "Closing session:",
+  "Opening session:",
+  "Removing old closed session:",
+  "Session already closed",
+  "Session already open",
+] as const;
 
 function shouldSuppressConsoleMessage(message: string): boolean {
+  if (isVerbose()) return false;
   return SUPPRESSED_CONSOLE_PREFIXES.some((prefix) =>
     message.startsWith(prefix),
   );