It might be a MVP but since (at the very least) I have to install software that is not currently on my system (VSCode or the Intellij LSP plugin, at least) it is not yet viable for me and my current environment
There might be a misunderstanding regarding what this "is".
This is a language server.
The purpose of a language server is to connect to a language client (which are each hooked to a respective text editor, most notably IDEs).
While a portion of IDEs support the LSP natively, the majority of them still
require a plugin to access it (even when the plugin is made by the same team who made the IDE).
(The plugin can range from containing the whole language client, to only containing the means of pointing to a language server)
Maybe it's to give users to possibility to make their own plugin/not force theirs onto the users. Maybe it's because a language client is just meant to be a plugin. I don't know, and that's not the point.
The point is:
- The language server is the minimum viable product (and yes, I made sure to look up the specific definition of "minimum viable product" beforehand)
A language server adhering to the Language Server Protocol is nothing more than half of the equation. Going further than that beats the whole point.
- Language servers are nothing without a language client, which is a separate product.
Since we're not supplying it (as that would mean supplying 3 different products: server + client + text editor to go with the client, and would also beat the purpose of the LSP as it would force the use of a specific text editor), accessing it requires users to use an existing text editor/IDE's language client.
- Most text editors/IDEs who support the LSP give access to their client via a plugin (even when they are the one who made both).
So in short, you seem to be expecting the server to be working as a standalone, which is literally impossible without going against its purpose.
It is also somewhat unclear to me what I then do next. [...] That will change when I have more time to devote to this or when the "viability" for my environment (which may just be better instructions with an example of use) improves.
I'm not sure what you're expecting to be able to do next. You just... open .ash files in the IDE, and it points out errors in them (and any file they import, if any).
More features will be available later, but this is as far as the prototype goes...