test(watcher): fix fs.watch flake by adding settle delay

[andreinknv]

Summary

Three watcher tests wrote files immediately after watcher.start(), hitting a race with macOS FSEvents (and Linux inotify): there's a small but real latency between fs.watch() returning and the kernel actually delivering events. Under parallel test load (when the host CPU is busy running other test files in worker threads), that latency balloons and the file-change event is dropped before the watcher is fully registered. Result: the test waits 5s for a sync that never fires and times out.

Affected tests

• debounced sync > should trigger sync after file change — most frequently affected
• callbacks > should call onSyncComplete after successful sync
• callbacks > should call onSyncError when sync throws
• debounced sync > should debounce rapid changes — less affected (its 50ms-spaced loop incidentally settles, but explicit is better)
• CodeGraph integration > should auto-sync when files change

What changed

The filtering tests in this file already had a 400ms settle delay with a comment ("Let watcher settle — fs.watch may fire residual events from beforeEach"). This PR:

• Factors that out into a single letWatcherSettle() helper with a docstring explaining the FSEvents/inotify latency.
• Applies it consistently to every test that writes immediately after start().
• No production code change — the flake had no user impact, it was purely a test-order artifact under parallel load.

Verification

• Pre-fix: ran npm test 8+ times across the session that produced PRs fix(sync): detect HEAD-moving git operations to prevent stale index #100–perf(db): batch node lookups, fix insertNode cache, auto-ANALYZE after writes #108. The fs.watch flake fired in roughly 1 of 3 runs under parallel load.
• Post-fix: 3 consecutive npm test runs, 380/380 each, zero flakes.

🤖 Generated with Claude Code