[Feature]: Render Markdown in sent user messages

[MIOsystems]

Problem

Hermes One renders Markdown formatting in assistant responses, but sent user messages are displayed primarily as plain text.

This causes Markdown syntax to remain visible in the message bubble, for example:

## Context

- First requirement
- Second requirement

**Important:** keep this section visible.

This is particularly difficult to read for:

• long prompts;
• automation instructions;
• pasted email histories;
• headings and structured lists;
• links;
• code blocks;
• emphasized text.

Current behavior

Assistant messages use the existing Markdown renderer.

User messages are rendered directly as their raw text content, so most Markdown syntax is displayed literally.

Requested behavior

Use the existing Markdown renderer for sent user messages as well.

The user-message renderer should support at least:

• headings;
• bold and italic text;
• ordered and unordered lists;
• links;
• blockquotes;
• inline code;
• fenced code blocks;
• tables.

Additional requirements

• Preserve the existing visual distinction between user and assistant messages.
• Keep the copy button copying the original raw Markdown source.
• Apply the same rendering to restored session history and automation prompts.
• Use the same sanitization and security rules as assistant messages.
• Preserve plain-text line breaks where the content is not valid Markdown.

An optional setting such as Render Markdown in sent messages could be provided if some users prefer raw text, but rendered Markdown would be the more consistent default.

Expected result

After a Markdown-formatted message is sent, its bubble displays the formatted structure while the original raw source remains available for copying.

Environment

• Hermes One: latest version
• Operating system: Windows 11
• Connection mode: remote Hermes server