Refresh Workspace Changes on agent disk writes

[adamhulme]

Problem

Terminal agents write files straight to disk, which fires no onDidSaveTextDocument event and matches neither the image nor the plan watcher. Workspace Changes therefore only self-corrected on the 10-second poll, so an agent's edits looked stale in Review for up to 10s.

Change

• Add a general **/* workspace watcher in ReviewTreeProvider. Disk-write events route through the cheap git-only refreshChanges() path on their own 250ms debounce — not the full findFiles refresh — since a source edit can only move git state. Plans/docs and images keep their dedicated watchers.
• Filter build/dependency churn (node_modules, .git, out, dist), mirroring the findFiles excludes, so agent write bursts don't pin the refresh pipeline.
• Invalidate verification evidence for the changed URI, matching what the save handler already does, so freshness signatures stay honest for on-disk edits.
• Known limitation (documented in the code): string-glob watchers only cover workspace folders, so agents in worktrees outside the workspace still rely on the 10s poll.
• Add .nvmrc (Node 24) to document the contributor toolchain — deliberately not engines.node, which would ship a false runtime claim in the extension manifest (the extension host runs Node ~20 at VS Code 1.96, and the notify hook helper only needs node:http).

Testing

• npm run check — lint clean, 220/220 unit tests pass.

🤖 Generated with Claude Code