I think this should document why we ignore cases where `!entry` or `entry.isFile`.  I'm assuming it's (a) because we know wholesale change events are currently noisy and generally meaningless, and (b) because file content changes and renames are listened for separately, and handling external changes to the contents of non-open files was out of scope in the original version on master too.  Is that a fair assessment?