fix(cli): prefer launch cwd for local sessions

[LeonSGP43]

Summary

Fixes #19214.

Interactive local CLI/TUI sessions should run from the directory where the user launched Hermes. A persisted terminal.cwd from full setup or hermes setup terminal should not silently pin cd ~/project && hermes back to an old directory, and a stale .env TERMINAL_CWD should not do that either.

This PR:

• forces local interactive CLI/TUI config loading to bridge TERMINAL_CWD=os.getcwd()
• keeps gateway/daemon runtime on configured terminal.cwd by marking the gateway process before lazy CLI imports
• preserves the existing gateway lazy-import guard for pre-resolved cwd values
• expands cwd-resolution tests to cover interactive config, stale env, and gateway runtime behavior

Verification

• scripts/run_tests.sh tests/cli/test_cwd_env_respect.py tests/gateway/test_config_cwd_bridge.py tests/hermes_cli/test_config_env_expansion.py
  • 45 passed, 4 warnings

[teknium1]

Thanks! Closing as redundant — main already forces os.getcwd() for local backend in load_cli_config (no HERMES_GATEWAY_PROCESS marker needed, main's simpler approach achieves the same end result: interactive CLI tools run from the shell's cwd, gateway has its own config bridge in gateway/run.py).

If you've hit a scenario where gateway still rewrites TERMINAL_CWD during a lazy cli.py import (the issue #10817 case), please file a fresh reproducer.