Measure refresh latency independently and retain intended result selection

docs/AUTOMATIC-INDEXING.md

@@ -24,8 +24,10 @@ 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.
-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.
+Refresh timing starts at the change event rather than include idle time since
+the original input. A bounded numeric snapshot retains the original input
+timings separately. Intended selection survives temporary result absence;
+explicit navigation changes that intent, and a new query or filter clears it.
 
 ## Targeted reconciliation