fix: honor configured cwd during snapshot init

[kaizhoumasha]

Summary

• cd into the configured cwd before creating the local shell snapshot
• prevent launchd WorkingDirectory from overriding the messaging workspace
• add a regression test covering snapshot init with an explicit cwd

Verification

• /Users/kaizhou/.hermes/hermes-agent/venv/bin/python -m pytest -q tests/tools/test_base_environment.py

[alt-glitch]

Likely duplicate of #7802 — same fix: cd into configured cwd before capturing local shell snapshot. See also #9798 and #11019.

[teknium1]

Thanks for the contribution, @kaizhoumasha! This fix was already merged to main via a different (but equivalent) approach before this PR could be merged.

Evidence:

• Commit 4c1362884 by @WuTianyi123 (2026-04-20) fixes the same root cause by passing cwd=self.cwd directly to subprocess.Popen in LocalEnvironment._run_bash() (tools/environments/local.py, line 364). This ensures init_session()'s pwd -P runs in the configured directory rather than the gateway process's startup directory.
• Your PR injects a cd into the base.py bootstrap script; the landed fix achieves the same outcome at the subprocess spawn level, which is the canonical fix location for LocalEnvironment.
• Member @alt-glitch noted this was likely a duplicate of fix(terminal): honor configured cwd at session init #7802 / fix: preserve configured cwd in local terminal snapshots #9798 / fix: preserve configured cwd during environment bootstrap snapshot #11019 — all addressing the same issue.

This is an automated hermes-sweeper review. Closing as implemented on main.