Publish Linux timestamp-fix packages with actual CPU package evidence

docs/ROADMAP.md

@@ -1,6 +1,6 @@
 # Production readiness roadmap
 
-Status: Windows v0.1.4 and Linux v0.1.3 previews published; initial Windows v0.1.0 installed. Broader production gates remain open. Windows VM tests use CPU only.
+Status: Windows and Linux v0.1.4 previews published; initial Windows v0.1.0 installed. Broader production gates remain open. Windows VM tests use CPU only.
 
 Karl's release priority, 2026-10-13: publish a usable first Windows version and
 install it on DEV-WIN11 now. Extensive platform/GPU, clean-machine, signing and
@@ -343,7 +343,7 @@ build was inferred from that lookup; macOS execution gates remain unchecked.
 - [x] Audit core/service and desktop/CLI Rust boundaries; avoid unnecessary naming/module churn.
 - [x] Correct valid pre-1970 filesystem timestamps across indexing, source eligibility and previews. Changed crates passed 100 tests (six ignored), desktop 47; strict Clippy and formatting passed. See [audit](RUST-AUDIT.md).
 - [x] Publish Windows v0.1.4 with the timestamp correction; verify public bytes, packaged helper provenance and isolated real Google CPU query-worker startup. See [evidence](WINDOWS-0.1.4.md).
-- [ ] Include the timestamp correction in updated Linux packages; published Linux v0.1.3 artifacts precede it.
+- [x] Publish updated Linux headless and Debian packages with the timestamp correction; genuine archived-document CPU search, unchanged rescan and packaged query-worker startup passed. Public bytes verified; [evidence](LINUX-0.1.4.md).
 
 Initial Windows delivery is complete. Native interaction/upgrade, actual GPU,
 macOS execution and independent media-quality work remain real follow-up; the