3 people 3f9cd3b87d M1: every PDF leaves the engine checked, and every writer uses one staging-file writer (#2166) (#2182) ...

New files from Combine, Extract, Split and Create, signed, timestamped and
LTV-embedded files and the OCR batch output reopen with their pages before
anyone writes them, as saves already did. The desktop app, the automation
tools (with or without --root) and the CLI's edit, combine, extract and
split write through pdfcraft_platform::staging::write_atomically, so a
failed write or --out naming the input never leaves a half-written file.
Special files such as /dev/stdout are still written as given.


Claude-Session: https://claude.ai/code/session_01RUNQSPVXx3dDBabRZHAnjz

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Brandon Thomas <echelon@gmail.com>

2026-10-15 02:48:09 -04:00

..

src

M1: every PDF leaves the engine checked, and every writer uses one staging-file writer (#2166) (#2182)

2026-10-15 02:48:09 -04:00

tests

M1: every PDF leaves the engine checked, and every writer uses one staging-file writer (#2166) (#2182)

2026-10-15 02:48:09 -04:00

build.rs

CLI: pdfcraft-cli.exe carries a Windows version resource (#598)

2026-10-09 19:09:23 -04:00

Cargo.toml

M1: every PDF leaves the engine checked, and every writer uses one staging-file writer (#2166) (#2182)

2026-10-15 02:48:09 -04:00