Hi! Context: I’m a Korean developer and a heavy user of Codex and Claude Code-style agentic coding workflows. In those tools, persisted workspace context is part of what makes session resume feel reliable; I noticed Hermes doesn’t currently persist that context.

Hermes can restore transcript history, but it doesn’t persist which workspace/directories a session was associated with. For local CLI use this is often implicit, but for dashboards, remote clients, resume flows, and multi-repo workflows, it would be useful to persist at least the primary workspace and last cwd.

Summary

This PR adds a small first step toward persisted workspace context for sessions:

• Adds workspace_path and last_cwd columns to the session store.
• Allows create_session() and ensure_session() to persist those values.
• Stores the current TERMINAL_CWD/os.getcwd() context for CLI-created sessions and fallback session creation.
• Adds update_session_cwd() as a small SessionDB helper for callers that can observe cwd changes.
• Covers creation, fallback creation, migration, and export behavior in tests/test_hermes_state.py.

I kept this intentionally narrow. A richer follow-up could track multiple referenced workspaces/directories per session, but this gives clients a stable primary workspace and current/last cwd field without changing existing session behavior.

Tests

• python3 -m py_compile hermes_state.py cli.py run_agent.py
• uv run --extra dev pytest tests/test_hermes_state.py -q
• git diff --check