Add documentation for exec websocket

[backspace]

This is a continuation of #6604. You can preview it in situ here.

[DingoEatingFuzz]

I read through it and it makes sense to me!

The thing that wasn't clear to me was if the response frames should be appended to output or if they represent the full buffer.

I know things like top work but it wasn't clear what the mechanics are for line clearing. Maybe those are just xterm instructions that come through the stdout messages?

[DingoEatingFuzz]

nit: extra newline (I tried to get rid of it with a suggestion but it didn't seem to work).

[backspace]

Maybe those are just xterm instructions that come through the stdout messages?

This is correct! Do you think this is worth mentioning?

[DingoEatingFuzz]

I don't think it would hurt to add it.

[backspace]

I don't think it would hurt to add it.

👍 I added an example request and response to provide some explanation of the content of frames, thoughts?

[DingoEatingFuzz]

I like it! That sample gives just enough guidance on what to expect while also introducing some vocab someone can do further research on.

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.