fix: tolerate deleted cwd in terminal config

[nodar]

Summary

• prevent terminal tool config resolution from crashing when the Hermes process cwd/worktree has been deleted
• add safe cwd/path resolution for local terminal backend and Docker cwd passthrough
• cover local, Docker default mount, and relative TERMINAL_CWD Docker mount regression cases

Test Plan

• uv run --with pytest python -m pytest tests/tools/test_terminal_tool.py -o 'addopts=' -q
• uv run python -m compileall -q tools/terminal_tool.py tests/tools/test_terminal_tool.py
• independent review pass

[alt-glitch]

Competing fix with #33377 (and its duplicate #33407) — both guard os.getcwd() in terminal_tool.py _get_env_config() against FileNotFoundError when CWD is deleted. Complementary to #4982/#10233 (cli.py getcwd guard, different call site).

[teknium1]

Thanks for the focused deleted-CWD handling and regression cases. This is an automated hermes-sweeper review; current main already provides this guarantee.

• ad69d3edc7359310233fa789b300bfcc5a5c3f7a (fix(terminal): guard os.getcwd() against a deleted CWD) added _safe_getcwd().
• tools/terminal_tool.py:1293 uses it for the local default CWD, and tools/terminal_tool.py:1309 uses it for Docker cwd passthrough.
• tests/tools/test_terminal_task_cwd.py:231 and :240 cover deleted-CWD fallbacks to TERMINAL_CWD and home.
• The fix is contained in release tag v2026.6.5.

The member comment correctly identified this as competing with the same terminal-tool guard; the later mainline implementation also covers the sibling debug-config call site.