hermes - 💡(How to fix) Fix Expose stable message metadata in TUI session.history

Problem

The TUI gateway session.history RPC currently returns display-oriented message objects from _history_to_messages(...), e.g. { role, text } for user/assistant messages and { role: "tool", name, context } for tool results.

Those objects preserve array order but do not expose stable per-message metadata such as:

• SQLite message row id
• persisted message timestamp
• stable history index / sequence number

Hermes already persists message timestamps in hermes_state.py (messages.timestamp REAL NOT NULL) and restores sessions with ORDER BY timestamp, id, but that metadata is not available to clients of session.history.

Downstream impact

External UI adapters that integrate through the TUI JSON-RPC bridge need a stable way to merge, deduplicate, cache, and display session history. Without timestamps or ids, clients may be forced to synthesize createdAt values at read time. That can cause stale conversations to appear newly active after simply reading/resuming history, and can make ordering fragile when history is cached outside Hermes.

Request

Please include stable metadata in session.history responses, ideally:

• id: persisted message row id when available, or another stable message id
• timestamp: original persisted timestamp, preferably seconds or milliseconds since epoch, or ISO string
• index: stable ordinal within the returned history as a fallback

This can be additive so existing clients that only read role/text/name/context keep working.

Relevant code

• tui_gateway/server.py: @method("session.history") and _history_to_messages(...)
• hermes_state.py: messages.timestamp, get_messages(), get_messages_as_conversation()