Method maybeScheduleForRemovedDir

src/sync/watcher.ts:610–622

* A deleted DIRECTORY arrives as one event on the directory's own path — * no source extension, so the source-file filter drops it, and the files * underneath may never get events of their own (Windows's recursive * watcher reports only the top-most removed entry; macOS FSEvents can * co

(rel: string)

   * costs at most one no-op scan-diff, absorbed by the debounce.
   */
  private maybeScheduleForRemovedDir(rel: string): void {
    try {
      fs.statSync(path.join(this.projectRoot, rel));
      return; // still on disk — an ordinary non-source change, ignore
    } catch {
      /* gone — fall through */
    }
    logDebug('Non-source path removed; scheduling sync for possible directory removal', {
      path: rel,
    });
    this.needsFullScan = true;
    this.scheduleSync();
  }

  /** Close and forget the watch for a directory that errored/was removed. */
  private unwatchDir(dir: string): void {