Update comment on delimeter handling

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: Thuraabtech

plugins/communication_protocols/socket/src/utcp_socket/tcp_communication_protocol.py

@@ -207,13 +207,13 @@ def _decode_response_with_framing(self, sock: socket.socket, provider: TCPProvid
 
         elif provider.framing_strategy == "delimiter":
             # Read until delimiter is found
-            # Copilot AI (5 days ago):
-            # The default delimiter has been changed from "\\x00" (escaped backslash) to "\x00" (null character).
-            # This changes the semantic meaning - the old code expected the literal string \x00 (4 characters: backslash, x, 0, 0),
-            # while the new code expects a single null byte. Ensure this is intentional and that all servers using this protocol are
-            # updated accordingly, as this is a breaking change in the wire protocol.
-            # Suggested change:
-            #     delimiter = provider.message_delimiter or "\\x00"
+            # Delimiter handling:
+            # The code supports both literal delimiters (e.g., "\\x00") and escape-sequence interpreted delimiters (e.g., "\x00")
+            # via the `interpret_escape_sequences` flag in TCPProvider. This ensures compatibility with both legacy and updated
+            # wire protocols. The delimiter is interpreted according to the flag, so no breaking change occurs unless the flag
+            # is set differently than expected by the server/client.
+            # Example:
+            #     If interpret_escape_sequences is True, "\\x00" becomes a null byte; if False, it remains four literal bytes.
             #     delimiter = delimiter.encode('utf-8')
             delimiter = provider.message_delimiter or "\x00"
             if provider.interpret_escape_sequences: