Can a prompt replace Foxit PDF Editor?

Build a local, offline PDF pipeline that never makes a network request.

It watches a folder. Any PDF dropped into a subfolder named after a recipe gets that recipe applied and the result written to an output folder alongside a small JSON report. Ship four recipes to start: ocr (Tesseract, keeping the original image layer and adding a text layer under it), compress (Ghostscript, with the target quality named in the recipe rather than guessed), split (by page range or by every occurrence of a bookmark), and to-docx (LibreOffice headless).

Make the offline guarantee real rather than implied: run the whole pipeline in a container with no network, and add a test that asserts the process makes zero outbound connections while processing a document. A claim of "your files never leave your machine" is worth nothing unless something enforces it.

The report per file lists the input hash, the recipe, each step's duration, the output hash, and any warning worth seeing — fonts that could not be embedded, a page that OCR scored badly, a compression ratio so high it probably destroyed something. Print warnings loudly; silent degradation of a scanned document is the failure mode that costs people real work.

Give it a minimal local GUI only if you want one: a single window that shows the queue and lets you open the output folder. Nothing more.

Out of scope: interactive text editing, form design, e-signatures, and any hosted component at all.