Throws Error on File Change after a Client has Connected

When I start the patch server initially, I can initially watch (and see the feedback) that a file has changed without an error.

After starting my app and connecting to the patch server

Any change to a watched file produces an error:

No files or tests are named. First reproduce the sequence of starting the patch server, connecting an app, and changing a watched file, then inspect the file-watching path used after a client connects. Done means watched-file changes no longer produce an error and the change feedback continues.

Written by the indexing model from the issue text.