Fix: show top-level reasoning field in thinking card

[tgaalman]

Problem

Hermes stores reasoning as a top-level message field (m.reasoning) instead of in content arrays like Claude (which uses content: [{type: 'reasoning', reasoning: '...'}]).

The WebUI thinking/reasoning card only checked for structured content arrays, so Hermes reasoning was never displayed.

Fix

Added a fallback check for m.reasoning after the content array check in renderMessages():

// Also check top-level reasoning field (Hermes format)
if(!thinkingText && m.reasoning){
  thinkingText=m.reasoning;
}

This allows Hermes users to see the model's reasoning process in the WebUI.

Testing

• Patch applied locally on hermes-ai.gaalman.org
• Reasoning cards now display correctly in WebUI

[nesquena]

Thanks @tgaalman! Clean, minimal fix for a real gap — Hermes-format reasoning (m.reasoning top-level field) was invisible in the UI while Claude-format reasoning (content array with type: 'reasoning') worked fine.

The fallback check is correctly guarded (!thinkingText && m.reasoning) so it only activates when the structured content array didn't already extract reasoning. The output is properly escaped via esc() in the thinking card <pre> block.

Security audit clean (4-line JS change, no external resources, XSS-safe). Tests: 442 passed, 0 failed. Merging now.

[nesquena-hermes]

Thank you, @tgaalman!

Your fix for the top-level reasoning field in the thinking card is in and has been running since v0.39.0. Thank you for the catch — that's exactly the kind of edge case that's hard to spot without using the feature in anger. You're in the Contributors section.