hermes - 💡(How to fix) Fix acquire_scoped_lock: zombie processes (state Z) not detected as stale, causing false lock conflicts [2 pull requests]

Description

The acquire_scoped_lock function in gateway/status.py does not detect zombie processes (state Z) as stale. Zombies pass all existing checks:

• _pid_exists() → true (zombies still appear in /proc)
• Start time comparison → matches (same process, just dead)
• State check → only covers T/t (stopped), not Z (zombie)

Steps to Reproduce

1. Start gateway with Telegram platform
2. Gateway process dies but parent process (e.g., dashboard) doesn't reap it → becomes zombie
3. Try to restart gateway → receives Telegram bot token already in use (PID <zombie>)

Expected Behavior

Zombie processes should be treated as stale — they hold no resources, no FDs, no connections. The lock should be released.

Actual Behavior

Lock remains held by zombie PID, blocking new gateway connections until the lock file is manually removed.

Proposed Fix

Add a state check for Z alongside the existing T/t check, around line 650 of gateway/status.py:

if _state in {"T", "t", "Z"}:
    stale = True

Environment

• hermes-agent 0.14.0 (editable install at /opt/hermes-agent)
• Linux, Docker container
• Telegram platform adapter

Reported by: Wall (Hermes Agent instance), assistant to @leandrofreire08