fix(gateway): honor configured cwd in gateway sessions

[qdaszx]

What does this PR do?

Fixes gateway workspace drift for configured terminal.cwd: gateway sessions should show and use the user's configured workspace, not the long-lived Hermes daemon/source checkout.

This is based on the same root cause identified in #27488, but expands the regression coverage around the shared gateway/tool cwd contract instead of only testing the prompt-builder surface.

Related Issue

Fixes #29265

Related PRs / context:

• fix(gateway): re-read terminal.cwd on session reset; use TERMINAL_CWD in environment hints #27488 — same production fix direction: prefer TERMINAL_CWD in environment hints and re-read terminal.cwd for long-lived gateway resets.
• [Bug]: change working directory for Telegram agent #27383 — earlier gateway cwd/session reset context referenced by fix(gateway): re-read terminal.cwd on session reset; use TERMINAL_CWD in environment hints #27488.
• fix(cron): use TERMINAL_CWD for system prompt working directory #24985 / fix(prompt_builder): use TERMINAL_CWD in system prompt when configured #24888 — prior TERMINAL_CWD prompt/cwd fixes in adjacent surfaces.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• agent/prompt_builder.py
  • Prefer TERMINAL_CWD when rendering the system prompt's Current working directory hint.
  • Preserve the previous os.getcwd() fallback when TERMINAL_CWD is unset.
• gateway/run.py
  • Re-bridge explicit terminal.cwd values from config.yaml into TERMINAL_CWD during runtime env reloads, so long-lived gateway sessions can pick up cwd config changes without restart.
  • Avoid clobbering an already-resolved cwd with placeholders such as ., auto, or cwd.
• tests/gateway/test_gateway_cwd_contract.py
  • Adds platform-neutral gateway cwd contract coverage for prompt hints and reload behavior.
• tests/tools/test_gateway_cwd_contract.py
  • Adds tool-surface contract coverage for terminal, file/search/patch path resolution, and execute_code project mode.
• tests/gateway/test_issue_29265_qqbot_weixin_cwd.py
  • Adds narrow QQBot/Weixin smoke coverage for the platforms named in [Feature]: Configurable default working directory for QQBot and Weixin gateway sessions #29265 while keeping the main contract tests platform-neutral.

How to Test

1. Configure a messaging gateway with an explicit workspace, for example:

   terminal:
     cwd: /path/to/workspace

2. Start or keep a gateway running, then use /new or /reset after changing terminal.cwd.
3. Ask the gateway for its working directory or use relative file/tool operations.
4. Confirm the prompt/tool surfaces are anchored to the configured workspace instead of the Hermes source checkout.

Automated validation run locally:

scripts/run_tests.sh \
  tests/gateway/test_gateway_cwd_contract.py \
  tests/tools/test_gateway_cwd_contract.py \
  tests/gateway/test_issue_29265_qqbot_weixin_cwd.py \
  tests/agent/test_prompt_builder.py \
  tests/gateway/test_config_cwd_bridge.py \
  tests/tools/test_resolve_path.py \
  tests/tools/test_parse_env_var.py \
  -q

Result:

176 passed in 8.08s

Additional checks:

git diff --cached --check: passed
scripts/check-windows-footguns.py: passed, 5 files scanned
static secret / shell-injection / eval / pickle / SQL-pattern scan: no findings
independent review agent: passed; no blocking security concerns or logic errors

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: Ubuntu/Linux

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

Not applicable; this is a gateway runtime/env contract fix with automated regression coverage.

[pinguarmy]

Thanks for building this out — this looks like a more complete/generalized version of the root cause I was seeing in #27488.

I especially like the gateway/tool cwd contract coverage and regression tests.

My PR (#27488) was focused on the immediate production fix direction, but this seems like the broader/systemic approach. Happy to close or mark #27488 as superseded if maintainers prefer consolidating on this direction.

If useful, I'm also happy to help test edge cases from the original repro.

[qdaszx]

@pinguarmy Thanks — really appreciate the context, and especially the original production-fix direction in #27488.

I tried to preserve that root-cause fix while adding a bit more contract coverage around the shared gateway/tool cwd behavior, so the #29265 QQBot/Weixin report does not end up as a platform-only regression test.

I’ll defer to you and the maintainers on whether #27488 should stay open or be marked superseded. If you still have edge cases from the original repro, I’d be happy to check whether they’re covered here and add coverage if there’s a gap.

[qdaszx]

Closing this PR because the underlying cwd issue is already resolved on main.

Verification summary:

• [Feature]: Configurable default working directory for QQBot and Weixin gateway sessions #29265 is already closed with reporter confirmation that the channel now uses the configured default cwd.
• fix(agent): resolve agent cwd from TERMINAL_CWD via one reader (closes #24882, #24969, #27383) #35028 was merged and supersedes this PR's core fix direction by routing the prompt cwd through resolve_agent_cwd() / TERMINAL_CWD as the single reader.
• The fix commits from fix(agent): resolve agent cwd from TERMINAL_CWD via one reader (closes #24882, #24969, #27383) #35028 are present on current main.
• Current main includes agent/runtime_cwd.py and agent/prompt_builder.py now emits Current working directory: via resolve_agent_cwd().
• Targeted cwd regression coverage on current main passes:
  • tests/agent/test_runtime_cwd.py
  • tests/agent/test_prompt_builder.py
  • tests/agent/test_system_prompt.py
  • tests/tools/test_gateway_cwd_contract.py
  • tests/gateway/test_config_cwd_bridge.py
  • Result: 206 passed

I also rechecked this PR branch before closing:

• No Git conflict boundary markers (<<<<<<< / >>>>>>>).
• GitHub reports the PR as MERGEABLE, so the previous conflict is resolved.
• Local merge simulation against latest upstream/main reported no conflicts.
• Targeted PR-branch tests passed: 212 passed.
• Relevant ruff check passed.

The PR is still blocked by unrelated/failing CI checks (Python tests / Run tests slice 7/8, Build&Test Docker image / build-arm64), while the actual #29265/#cwd behavior is now covered and resolved on main. So closing this as superseded/resolved rather than continuing to push this duplicate PR forward.