Measure semantic activation refresh independently from download and idle time

docs/EARLY-TEXT-SETUP.md

@@ -61,9 +61,14 @@ passed **51**, and both strict all-target Clippy checks, formatting and the
 frontend production build passed. The actual Google integration above was run
 separately; ignored entries in the default suite are not execution evidence.
 
-Native UI interaction during a genuine delayed HTTPS media download, failure,
-retry and promotion remains to be executed. The prepared Linux QA plan uses only
-an owned loopback CONNECT proxy and isolated app environment; it does not change
+Native Linux UI interaction during a genuine delayed HTTPS media download,
+failure, retry and full promotion passed on `9aae3f8`, retaining the query worker
+and explicit selection. Its actual first unseen query reported 84 ms native and
+293 ms through the DOM update on four fixture files. A later cached debug request
+is a separate sample. The test exposed a semantic-activation clock defect;
+the frontend now starts an independent refresh measurement, but a focused native
+retest remains pending. See [native evidence](LINUX-DESKTOP-VALIDATION.md).
+The owned loopback CONNECT proxy and isolated app environment do not change
 the product's pinned download URL or verification. Native Windows/macOS, GPU,
 large libraries and actual first-input measurements remain open. Document indexing
 still needs to finish a publishable generation; earlier model readiness does not