fix(dashboard): show full session history safely

[proCaj]

Summary

• add an include_compacted option for session message retrieval so dashboard history can show durable compaction-archived rows without including rewound/undone rows
• add a dedicated /sessions/:sessionId full-history route and wire session titles/history buttons to it, keeping the play button focused on resume-in-chat
• normalize non-string multimodal message content before rendering so session history does not crash on stored image/tool content arrays

Related issues

• Refs [Bug]: Web Dashboard: Session resume doesn't show full conversation history #32561 — provides a dedicated full-history view so the dashboard can access the whole stored session without relying on resume-chat scrollback behavior
• Related to Dashboard: virtual scrolling causes blank/empty history when scrolling up #51307 — avoids the inline fixed-height/scrolling history path for full-session review, but does not claim to fix the separate virtual-scrolling bug described there

Why

The dashboard history view previously loaded only active messages. Older prompts preserved by context compaction are stored as active=0, compacted=1, so they were missing from history even though they are durable transcript history.

Some stored sessions also contain multimodal content arrays. Passing those directly into the Markdown renderer can crash the SPA with TypeError: ...split is not a function, leaving the session page blank.

Tests

• python3 -m pytest tests/hermes_cli/test_session_messages_history.py tests/hermes_cli/test_web_server_session_search.py tests/hermes_cli/test_sessions_delete.py -q
• npm --prefix web run build
• git diff --check

Note: npm --prefix web run lint currently reports pre-existing repository lint errors outside this change; the build/typecheck path passes.

[teknium1]

Thanks for addressing a real dashboard history gap. Current main preserves pre-compaction rows as active=0, compacted=1 in hermes_state.py:4070-4079, while the dashboard still loads only active rows through hermes_cli/web_server.py:9987; MessageBubble also assumes string content at web/src/pages/SessionsPage.tsx:298-335.

Problems

• This branch conflicts with current main. Since its July base, commit 0d5549a945d7ba320c14415840058710be0a9d3b added limit/offset to SessionDB.get_messages (hermes_state.py:4095-4127) and pagination metadata to the endpoint (hermes_cli/web_server.py:9972-9995). The salvage must preserve that contract while adding include_compacted.
• The added tests do not render the changed dashboard path or non-string content. The state layer explicitly returns both list content (tests/test_hermes_state.py:1076-1106) and dict content (tests/test_hermes_state.py:1109-1116).

Suggested changes

• Compose include_compacted with the existing pagination parameters and response shape.
• Add a web regression covering the detail route and list/dict message content.

Automated hermes-sweeper review.

[teknium1]

Current main has added limit and offset parameters to this method for the session-message pagination contract. During salvage, retain them and make include_compacted compose with pagination rather than replacing that newer signature.

[teknium1]

Current main's endpoint now preserves limit/offset, clamps a requested limit to 500, and returns pagination metadata. Carry those fields forward when adding these history flags.

[teknium1]

Please add a browser-side regression for this normalizer through the session-detail route. The storage layer also round-trips dict-shaped content, not only content-part arrays (tests/test_hermes_state.py:1109-1116).