Web search restrictions after internal content (#1074)

Co-authored-by: Thorsten Sommer <SommerEngineering@users.noreply.github.com>

app/MindWork AI Studio/Chat/ChatThread.cs

@@ -145,14 +145,16 @@ public sealed record ChatThread
     };
 
     /// <summary>
-    /// Where this chat may still send data, because of the mailboxes it read from.
+    /// Where this chat may still send data, because of the internal content it holds: mails, a
+    /// search of the wiki, or an internal web page.
     /// </summary>
     /// <remarks>
     /// The third thing the thread ratchets, next to the data security and the required provider
-    /// confidence: once mail content is in the thread, every tool which runs afterwards could carry
-    /// it out, in a search query or in the address of a web page. It only ever gets stricter, and a
-    /// later change of the mailbox settings does not loosen it either, because the content was
-    /// read under the old one. A chat which read no mailbox demands nothing.
+    /// confidence: once internal content is in the thread, every tool which runs afterwards could
+    /// carry it out, in a search query or in the address of a web page. It only ever gets stricter,
+    /// and a later change of the settings of a mailbox or of Read Web Page does not loosen it
+    /// either, because the content was read under the old one. A chat which holds no internal
+    /// content demands nothing.
     /// </remarks>
     [JsonInclude]
     public OutboundDataRequirement RequiredOutboundDataRestriction { get; private set; } = OutboundDataRequirement.NONE;