Bug Description

In the server-side Send.ps1, text messages were incorrectly sent with 'Binary' frame type instead of 'Text', which violates the WebSocket protocol and causes clients to misinterpret text data as binary.

Fix

Changed the frame type parameter in socket.SendAsync() from 'Binary' to 'Text' for the text message branch (the else branch that handles non-binary data).

Before

$null = $socket.SendAsync($messageSegment, 'Binary', 'EndOfMessage',[Threading.Cancellationtoken]::None)

After

$null = $socket.SendAsync($messageSegment, 'Text', 'EndOfMessage',[Threading.Cancellationtoken]::None)

Impact

• Text messages are now correctly framed according to WebSocket protocol
• Clients will properly interpret text data as text rather than binary
• No breaking changes to API or functionality

This PR was generated by PRJanitor — an automated tool that finds and fixes small bugs in open-source projects.

We respect your contribution guidelines — if your project doesn't accept bot PRs, we won't send more. You can also add a .github/prjanitor.yml file with enabled: false to opt out explicitly.