style: run prettier on updated docs pages

Line-rewrap only (pinned prettier 3.8.1); no semantic wording changed.
Fixes the Static Quality / prettier CI check on this branch.

Author: jpr5

docs/multi-turn/index.html

@@ -104,9 +104,9 @@ <h2>How matching works across turns</h2>
             <code>hasToolResult</code> checks whether the <strong>current turn</strong> &mdash; the
             messages after the last <code>role: "user"</code> message &mdash; contains a
             <code>role: "tool"</code> result. <code>true</code> means &ldquo;a tool has executed in
-            this turn&rdquo;; <code>false</code> means &ldquo;no tool result yet this turn.&rdquo; It
-            is scoped to the current turn, not the whole conversation &mdash; that is what keeps the
-            leg-1 tool-call fixture (<code>false</code>) and the leg-2 narration fixture
+            this turn&rdquo;; <code>false</code> means &ldquo;no tool result yet this turn.&rdquo;
+            It is scoped to the current turn, not the whole conversation &mdash; that is what keeps
+            the leg-1 tool-call fixture (<code>false</code>) and the leg-2 narration fixture
             (<code>true</code>) working on <em>every</em> turn of a multi-turn session, because
             earlier turns&rsquo; tool results no longer force <code>true</code> forever. (If the
             request carries no <code>user</code> message at all, it falls back to scanning the whole

docs/record-replay/index.html

@@ -637,9 +637,8 @@ <h2>Fixture Auto-Generation</h2>
           requests the recorder also writes the multi-turn disambiguators
           <code>turnIndex</code> (the number of assistant messages already in the conversation) and
           <code>hasToolResult</code> (whether the current turn &mdash; the messages after the last
-          user message &mdash; contains a tool result). If no match
-          criteria can be derived (e.g., empty messages), the fixture is saved to disk with a
-          warning but not registered in memory.
+          user message &mdash; contains a tool result). If no match criteria can be derived (e.g.,
+          empty messages), the fixture is saved to disk with a warning but not registered in memory.
         </p>
 
         <h2 id="model-aware-recording">Model-Aware Recording</h2>
@@ -1042,11 +1041,10 @@ <h2 id="recording-multi-turn-conversations">Recording Multi-Turn Conversations</
           <code>model</code>, and two shape disambiguators read off the request itself:
           <code>turnIndex</code> (how many assistant messages the conversation already contains) and
           <code>hasToolResult</code> (whether the current turn &mdash; the messages after the last
-          user message &mdash; contains a tool result). Embedding requests
-          key on the input text instead. There is no history-based fingerprinting of the full
-          request body &mdash; but because a growing conversation carries a growing
-          <code>turnIndex</code>, successive turns that happen to end with the same user message
-          still record as <em>distinct</em> fixtures.
+          user message &mdash; contains a tool result). Embedding requests key on the input text
+          instead. There is no history-based fingerprinting of the full request body &mdash; but
+          because a growing conversation carries a growing <code>turnIndex</code>, successive turns
+          that happen to end with the same user message still record as <em>distinct</em> fixtures.
         </p>
 
         <div class="code-block">