From 4e9df52d600c81314dc3b027572706aae56be2ef Mon Sep 17 00:00:00 2001
From: zccyman <16263913+zccyman@users.noreply.github.com>
Date: Mon, 18 May 2026 19:35:36 -0700
Subject: [PATCH] fix: elevate plugin discovery failures from debug to warning
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Plugin discovery exceptions in gateway startup (gateway/run.py) and
CLI startup (hermes_cli/main.py) are caught and logged at DEBUG
level, making them invisible at the default INFO log level.

If any plugin import fails — syntax error, missing dependency, import
cycle — operators get zero indication unless they bump the log level
to DEBUG. This makes broken plugins appear enabled but silently
non-functional.

Change both locations to logger.warning() so failures are visible at
production log levels.

Closes #28137
---
 gateway/run.py     | 2 +-
 hermes_cli/main.py | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gateway/run.py b/gateway/run.py
index 81a2466b73..33a16d883b 100644
--- a/gateway/run.py
+++ b/gateway/run.py
@@ -3474,7 +3474,7 @@ class GatewayRunner:
             from hermes_cli.plugins import discover_plugins
             discover_plugins()
         except Exception:
-            logger.debug(
+            logger.warning(
                 "plugin discovery failed at gateway startup", exc_info=True,
             )
 
diff --git a/hermes_cli/main.py b/hermes_cli/main.py
index 370e5eafc1..fec6709977 100644
--- a/hermes_cli/main.py
+++ b/hermes_cli/main.py
@@ -12672,7 +12672,7 @@ Examples:
 
             discover_plugins()
         except Exception:
-            logger.debug(
+            logger.warning(
                 "plugin discovery failed at CLI startup",
                 exc_info=True,
             )