hermes - 💡(How to fix) Fix [Feature]: Cross-client session sync (TUI ↔ messaging platforms)

Problem: When using /resume to load a session from another client (e.g. resuming a TUI session in Feishu), Hermes loads a snapshot at resume time. Any subsequent changes made on the original client are invisible.

Repro: In Feishu: /resume my-proj-dev → loads snapshot ✅ In TUI: continue working, add 50 more exchanges Back in Feishu: the new context is lost — the session has gone stale Running /resume again discards Feishu-side messages and starts over, so there's no way to incrementally sync.

Proposed solutions: /sync — reload the session's latest transcript into the current conversation (non-destructive) /push / /pull — explicit incremental context push/pull between clients Bidirectional auto-sync — when two clients are attached to the same session ID, forward new messages in real time

Use case: Power users alternating between desktop TUI (heavy dev work) and mobile messaging (quick check-ins, approvals). The current snapshot model forces a choice between stale context and losing messages.