From 3dae1f7335371ca4b015cdf5336db41868485153 Mon Sep 17 00:00:00 2001
From: kshitijk4poor <82637225+kshitijk4poor@users.noreply.github.com>
Date: Sun, 20 Sep 2026 15:43:38 +0530
Subject: [PATCH] docs(gateway): name the SIGUSR2 consumer in the stderr
 wrapper's forwarding comment

Review follow-up on #117052.
---
 hermes_cli/stderr_timestamp.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/hermes_cli/stderr_timestamp.py b/hermes_cli/stderr_timestamp.py
index 7b194cd549..a4f24b6d15 100644
--- a/hermes_cli/stderr_timestamp.py
+++ b/hermes_cli/stderr_timestamp.py
@@ -52,7 +52,9 @@ def _install_signal_forwarders(proc: subprocess.Popen[bytes]) -> dict[int, objec
     # SIGUSR1 is the gateway's drain-aware restart request. launchd owns THIS wrapper's PID,
     # so `hermes update` signals us, not the gateway; an unforwarded SIGUSR1 kills the wrapper
     # (Python's default action), launchd tears the group down with SIGTERM and applies its
-    # ~60 s crash back-off per sibling profile (#101426).
+    # ~60 s crash back-off per sibling profile (#101426). SIGUSR2 is the gateway's
+    # faulthandler stack-dump request (gateway/run_startup.py); unforwarded it terminates
+    # the wrapper the same way instead of dumping stacks.
     forwarded = (
         signal.SIGTERM,
         signal.SIGINT,