From 9758e26349a0a74c7d23c1c721df63df964b7c11 Mon Sep 17 00:00:00 2001
From: Hunter Bown <hmbown@gmail.com>
Date: Sun, 26 Apr 2026 15:56:01 -0500
Subject: [PATCH] fix(docs): escape `<no body>` in mcp doc-comment so rustdoc
 accepts it

CI Documentation job was failing with `error: unclosed HTML tag 'no'` at
crates/tui/src/mcp.rs:71. Rustdoc parses unescaped `<no body>` as an HTML
tag and `RUSTDOCFLAGS=-Dwarnings` (used in CI) promotes that to a hard
error. Reword the comment to refer to the literal string instead.
---
 crates/tui/src/mcp.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crates/tui/src/mcp.rs b/crates/tui/src/mcp.rs
index 98aab9f3..32c507c2 100644
--- a/crates/tui/src/mcp.rs
+++ b/crates/tui/src/mcp.rs
@@ -68,7 +68,7 @@ fn redact_body_preview(body: &str) -> String {
 
 /// Read up to `max_bytes` of a reqwest Response body and produce a single-line
 /// excerpt suitable for an error message. Best-effort — if the body can't be
-/// read, returns "<no body>".
+/// read, returns the literal string `<no body>`.
 async fn bounded_body_excerpt(response: reqwest::Response, max_bytes: usize) -> String {
     let body_text = response.text().await.unwrap_or_default();
     if body_text.is_empty() {