What does this PR do?

HonchoClientConfig.resolve_session_name() does a raw dict lookup self.sessions.get(cwd) on whatever string the caller passed in. When Hermes is launched from different shells the same project directory can be spelled multiple equivalent ways — with/without a trailing slash, as ~/proj vs /home/user/proj, with a . or .. segment — and all but one miss the override, so Hermes silently falls through to the basename-derived session name and effectively starts a fresh Honcho session every time.

Adds a small _match_session_override() helper that tries the existing fast-path dict lookup first (so configs with already-normalized keys keep their exact behaviour) and then falls back to comparing the absolute, ~-expanded, normalized form of both the lookup cwd and each override key.

Normalization uses pathlib.Path.resolve(strict=False), so it doesn't require the directory to actually exist on disk — which matters for test fixtures and remote-cwd callers. A defensive fallback to os.path.normpath(os.path.expanduser(...)) covers pathological inputs.

Related Issue

Fixes #13284

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• plugins/memory/honcho/client.py (+43 / −2): new _match_session_override() + _normalize_cwd() helpers; resolve_session_name() delegates to them.
• tests/honcho_plugin/test_client.py (+33): regression tests for normalized spellings and ~ expansion.

def _match_session_override(self, cwd: str) -> str | None:
    if not self.sessions:
        return None
    direct = self.sessions.get(cwd)           # fast path
    if direct:
        return direct
    target = self._normalize_cwd(cwd)
    for key, value in self.sessions.items():
        if self._normalize_cwd(key) == target:
            return value
    return None

How to Test

1. Add a sessions override in ~/.hermes/config.yaml keyed by ~/proj (or with a trailing slash).
2. Launch Hermes from /Users/you/proj (no trailing slash, no tilde).
3. Before: basename-derived session name. After: the configured override is used.

Run the regression suite:

pytest tests/honcho_plugin/test_client.py -q

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(honcho):)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes
• I've tested on my platform: macOS 26.5 (arm64)

Documentation & Housekeeping

• I've updated relevant documentation — N/A (internal helper)
• I've updated cli-config.yaml.example if I added/changed config keys — N/A
• I've updated CONTRIBUTING.md or AGENTS.md — N/A
• I've considered cross-platform impact (Windows, macOS) — uses pathlib.Path.resolve
• I've updated tool descriptions/schemas — N/A

Screenshots / Logs

Verification

• python3 -m py_compile plugins/memory/honcho/client.py tests/honcho_plugin/test_client.py → clean.
• The fast-path dict lookup is tried before normalization, so there's zero cost for callers whose override keys already match exactly.
• Normalization never calls the filesystem's stat() — it's string/path-manipulation only — so it's safe for cwd values that don't exist locally (remote task cwds, etc.).

Regression tests added

Kept the existing test_manual_override unchanged so the fast-path behaviour is still locked in.