Alright, now to test support for it:

• Can I get an executable? yes:
  • Download PSES (PowerShellEditorServices.zip):
    • https://github.com/PowerShell/PowerShellEditorServices/releases
  • Run the following script to start the server:
    • https://github.com/smartguy1196/PowerShell-Quick-Tray/blob/ccbca5ae07259e1a0b9ac370c0bbdf063d8a34d7/initialize.pses.server.ps1
• Can I access stdio? -not powershell readline...
• Can I access the named pipe?
  • Is there a consistent name for the pipe? no it is randomly generated
    • If not, can I write a script that detects it? yes, however it is uses c++ naming convention.
      • Can I write a PowerShell function that gets one under the c# convention? yes, just need to run "($name -split "\\") | select -last 1"
  • Can I write a powershell script that connects then disconnects from it?
  • Can I send anything to the server via powershell?
    • If yes, can I send the contents of a JSON file via an LSP request to the server?
• Can I get a unit testing script running? yes, I'm writing one
  • Posted yet?

If this works, I need to make a comprehensive list of every Request and Notification that I need to be able to send to the server.

Parsing responses will come with time, as I can just dump unknown responses to a text file and read them later.