fix(suspend): only inhibit for SSH-spawned zellij sessions

A local zellij session (sway terminal, attended) shouldn't keep the
laptop awake — that's the user actively in front of the machine, and
normal suspend behaviour should apply. Only zellij sessions that were
spawned from an SSH context need the persistent inhibit, so detach +
disconnect leaves the host awake until the session ends.

Use /proc/<pid>/environ to detect SSH-spawned zellij: the daemonised
zellij server is exec'd by the client and Linux preserves the exec-time
environment for the life of the process, so SSH_CONNECTION= survives
the SSH session closing. Walk every running `zellij` pid; hold the
lock as long as at least one of them has SSH_CONNECTION in its environ.

The .path unit still fires on every zellij socket creation, but if no
SSH-spawned zellij exists the watcher exits immediately and the service
stops with no harm done — a couple of cheap process spawns per local
session start, no inhibitor side-effects.

1 files changed, 3 insertions, 0 deletions

diff --git a/dot_config/systemd/user/zellij-inhibit-suspend.path b/dot_config/systemd/user/zellij-inhibit-suspend.path
index 72c509c..2a4be21 100644
--- a/dot_config/systemd/user/zellij-inhibit-suspend.path
+++ b/dot_config/systemd/user/zellij-inhibit-suspend.path
@@ -5,6 +5,9 @@ Description=Activate suspend inhibitor whenever zellij has a live session
 # %t expands to $XDG_RUNTIME_DIR (typically /run/user/$UID); zellij keeps
 # its per-version session sockets under this directory. Whenever the dir
 # transitions from empty to non-empty, the service is (re)activated.
+# The service's watcher then decides whether to actually hold the lock
+# (only if at least one zellij was spawned from an SSH session); if not,
+# it exits immediately and the service stops with no harm done.
 DirectoryNotEmpty=%t/zellij
 Unit=zellij-inhibit-suspend.service