Connection is lost after save

I don't remember if this is a consequence of VSCode's document management, but it's not a desired behavior. We're used to saving often so it should not trigger connection closure when one mistakenly saves a GhostText document.

Extracted from:

- #291

Start by reproducing a save in a GhostText document opened through VSCode and trace where the editor connection is closed. Done means saving the document no longer closes the active connection; the issue does not name a file or test to run.

Written by the indexing model from the issue text.