Stage and require verified extraction helper in Windows release packages

This commit is contained in:
karl committed 2026-10-13 15:23:24 +02:00
1 parent ab31870260
commit e250577740
8 files changed
+304

No files matched your search

+21
View File
@@ -150,3 +150,24 @@ installer contains this helper. Do not publish current source without it.
Desktop integration validation: 46 native tests passed on Windows with CPU-only
settings. The desktop lockfile now records the shared process adapter dependencies.
This checks compiled integration, not installed helper discovery or native UI interaction.
The optimized Windows helper built successfully and was copied into an owned
validation directory outside `target`. The normal-adapter genuine PDF test
passed against that relocated release helper (one test, 1.11 s). Its SHA-256 is
`983156ddb96de1b4fb307564c1b882ffb75300e05f03f705ee8e2e668ff96ae1`.
This is helper relocation evidence, not a finished installer check.
## Windows release staging
`tools/stage_extraction_worker.py` performs a locked optimized Cargo build,
compares bounded core/worker/media build inputs before and after it, and stages
only the helper and `extraction-worker.json`. Binary hash, size, architecture
and source provenance are verified. Unrelated runtime resources are retained.
Windows archive packaging requires the verified pair before output replacement;
release desktop builds run the same verification before bundling.
The real Windows build/stage/verification passed. Twenty-two tooling tests
passed normally and under Python `-O`, including missing, stale, tampered and
architecture-mismatched helpers plus failed builds and preserved unrelated files.
Linux headless packaging and native macOS helper staging remain open. A complete
updated Windows archive/installer has not yet been verified or published.