The fixes for #2 and #3 aren't playing nicely together. If you run the "Purple Yolk: Restart" command, the status bar item gets stuck saying "Purple Yolk: Running :quit ...". I think this happens because the restart command effectively crashes the server, which causes VSCode to kill the client. I'll bet that since the client doesn't tear down the status bar item, VSCode prevents a new instance of the client from creating another item.
The fixes for #2 and #3 aren't playing nicely together. If you run the "Purple Yolk: Restart" command, the status bar item gets stuck saying "Purple Yolk: Running :quit ...". I think this happens because the restart command effectively crashes the server, which causes VSCode to kill the client. I'll bet that since the client doesn't tear down the status bar item, VSCode prevents a new instance of the client from creating another item.