fix: check config.yaml for home channel setting

[nightq]

Summary

Fix home channel auto-prompt to check both env var and config.yaml.

Root Cause

The home channel auto-prompt only checked the environment variable, not the yaml config that /sethome writes to. This caused the prompt to re-fire even after /sethome was run.

Fix

Check both os.getenv() and config.yaml when determining if home channel is set. Falls back to config.yaml if env var is not set.

Closes #10581

[alt-glitch]

Competes with #10722 and #12391 for the same fix on #10581 — home channel auto-prompt should check config.yaml not just env var.

[alt-glitch]

Competes with #10722 and #12391 for the same fix on #10581.

[teknium1]

Thanks for the focused report and patch. The underlying /sethome persistence behavior is already implemented on current main through a different, now-authoritative storage path. This is an automated hermes-sweeper review.

• Commit 1d5e25f35367af7ff15856bca232ba44bd0bc84f changed /sethome to persist home-channel targets in .env rather than top-level config.yaml keys.
• Current gateway/slash_commands.py:2430-2452 saves the value through save_env_value() and keeps the running gateway configuration synchronized.
• hermes_cli/config.py:7602 updates os.environ immediately, gateway/run.py:1306-1311 reloads .env at gateway startup, and gateway/run.py:11401-11402 suppresses the prompt when the home target exists.
• The PR discussion notes competing fixes (fix: home channel auto-prompt now checks yaml config #10722 and fix: allow home channel from config.yaml to be recognized #12391); this PR predates the current persistence implementation.