`!is_loaded` implies `_treeDataProvder` (and therefore `Directory.getContents()`) was never called to populate the directory prior to this `change` event. So, the first drawing of any node must be a call to jstree `open_node`. There should be no case where we fail to ever redraw the tree because at the very least `_treeDataProvider` will be called via jstree.

I made the mistake of associating this jstree issue with the `FileSystem` unwatch issue. When debugging this originally, I saw that the change events coming though `ProjectManager._fileSystemChange` included those phantom directories that should have been unwatched when the folder was renamed. Since the old-named node (e.g. the default "New folder") was removed by a prior event, the event handler would fail to find an existing tree node and bail, making no jstree modifications. I mistook this as a cause of the eventual duplicate `README.md` entries. That's why fixing the `FileSystem` did not make the bug go away.