Record native Linux desktop and automatic update validation

docs/AUTOMATIC-INDEXING.md

@@ -24,7 +24,8 @@ Scans own separate SQLite connections. They do not hold the foreground search
 mutex during traversal or extraction. A changed scan prepares its reader and
 briefly swaps it into the desktop. UI events refresh counts and the active query,
 reject results from before the change, and request normal semantic indexing.
-The original input/first-response timing survives an automatic query refresh.
+Refresh timing must start at the change event rather than include idle time since
+the original input; native Linux interaction exposed a regression in this clock.
 
 ## Targeted reconciliation
 
@@ -80,7 +81,15 @@ image encode, unchanged hinted image/audio sources reuse vectors, and current
 revision tokens restore eligibility. This is correctness evidence on a tiny
 fixture, not relevance quality or search/indexing throughput evidence.
 
-Linux and macOS native watcher execution, root disappearance/reappearance on
+Current-source native Linux checks also passed: 124 workspace tests, 28 desktop
+Release tests including actual inotify create/update/rename/delete, and the
+updated real Google mixed-media regression in 67.95 seconds. Native Linux
+interaction evidence is in
+[LINUX-DESKTOP-VALIDATION.md](LINUX-DESKTOP-VALIDATION.md). Actual watcher-driven
+UI change/create/rename/delete passed on `657de3d`; timing and selection issues
+found during those interactions require separate fixes and retesting.
+
+macOS native watcher execution, root disappearance/reappearance on
 real removable/network storage, native UI refresh interaction, representative
 large-corpus contention and power-loss behavior remain open. Full reconciliation
 still holds a write transaction during extraction and can contend with semantic