Tree View transition to native file watcher in Atom 1.22+

The goal is to decide whether Atom should enable the native file‑system watcher for the Tree View by default in a future release, thereby reducing latency under concurrent file‑change events.

Constraints include the watcher’s opt‑in status due to reported incompatibilities with certain network filesystems and virtualized environments, possible CPU spikes on large monorepos, and the requirement to restart Atom when switching modes.

Uncertainty remains about the breadth of testing needed across diverse workloads and filesystems before changing the default.

What metrics should define acceptable latency improvement versus compatibility risk? How can the team safely roll out the native watcher to users with network‑mounted directories? Should the setting be migrated automatically across Atom upgrades to avoid manual re‑configuration?