fix(fonts): honour the monospace setting in context-free render helpers (T-472)

Eleven leaf sites rendered monospace text from top-level/static helpers that
take no BuildContext, so they hard-coded clideMonoFamily and ignored the
Settings → Appearance Monospace choice that the D-101 facade made live
everywhere else.

Thread the resolved family in from the nearest context-bearing caller:
- claude tool bodies/results: a required `mono` field on _ConversationTurn +
  a `mono` arg on the shared toolInputBody chain;
- markdown inline `code`/record/file-ref spans: carried on ClideMarkdownHooks,
  which build() already constructs from context and threads to every static;
- search preview styles and welcome tips: a `mono` parameter on the helpers.

No behaviour change when the setting is default; these surfaces now switch
live with the rest.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

CHANGELOG.md

@@ -79,6 +79,13 @@ heading, and (b) bumping `pubspec.yaml` `version:` in the same commit.
   changed from "Settings…" to "Theme…" so it no longer collides with the new
   Settings panel in the palette; behaviour is unchanged. (T-445)
 
+### Fixed
+
+- **Monospace setting now applies everywhere.** Eleven context-free render
+  helpers (Claude tool bodies + results, inline markdown code/refs, search
+  previews, welcome tips) hard-coded JetBrains Mono and ignored the Monospace
+  font setting; they now honour it live. (T-472)
+
 ## [2.6.0] — 2026-06-16
 
 ### Added