v0.11.0 Orifold — Fold the whole stack, compare the drafts

v0.11.0 Orifold — Fold the whole stack, compare the drafts

Release: August 30, 2026

Tag: v0.11.0

---

What Changed Since v0.10.2

This release delivers two long-promised roadmap items — batch folder operations and
side-by-side compare — plus a preservation-first OCR workbench, stronger PDF editing,
and a smaller reading-aid refinement. Every workflow remains local-first.

Fold the whole stack

• File → Fold a Folder… applies the selected steps to every PDF found under a chosen
  folder in one pass: make scanned pages searchable (OCR), add a watermark, and/or reduce
  file size with the existing compression presets.
• Results are written to a Folded subfolder with collision-proof names; the original files
  are never modified, and later runs skip that output subtree instead of folding generated
  files again.
• The run shows per-file progress with Cancel, and one unreadable PDF becomes one failed
  outcome instead of aborting the batch. A PDF that is already compact, or has nothing to
  recognize, keeps its prior bytes and still folds.
• Every output passes qpdf structural validation before it lands on disk, through the same
  crash-safe write-and-verify path as every export.

Side-by-side compare

• File → Compare With… (also in the More menu) pairs the current workspace's pages with
  a picked PDF and shows them side by side.
• Changed regions are highlighted on both pages via a resolution- and anti-aliasing-tolerant
  visual diff; text changes are summarized as word-level added/removed counts.
• A changed-pages strip jumps straight to differences, and a manual page offset re-aligns
  drafts whose pages shifted.
• Visual comparison reads exactly what is displayed (page rotations and crop boxes applied);
  text comparison reads the members' preserved bytes, so re-serialization can't manufacture
  phantom differences. Encrypted PDFs are declined with a clear message.

Read aloud, from here

• A new View-menu command starts read-aloud at the sentence containing the current text
  selection instead of the top of the page, keeping the follow-along highlight in sync.
• With no selection — or a selection that can't be located in the page's speakable text —
  it falls back to the existing start-of-page behavior.

Preservation-first OCR workbench

• The Inspector now makes the OCR policy explicit: process likely scanned pages only or all
  visible pages, let Vision choose a language or choose one yourself, and decide whether one
  unreadable page should stop the run.
• OCR adds a searchable layer to the original page instead of rebuilding it. Existing page
  geometry, annotations, and untouched workspace members remain intact.
• Every run ends with a quality receipt covering requested and recognized pages, skipped page
  numbers, line count, average confidence, low-confidence lines, and structural validation.
  Anything that deserves a human look is called out instead of being silently accepted.
• The operation is cancellable and participates in the workspace's normal undo/redo history.

Editing that keeps its shape

• Inline text replacement now preserves the surrounding composition more reliably across
  save, reopen, export, rotation, and deeper undo/redo histories.
• Compatible page objects continue to support move, resize, layer, delete, and existing
  fill/stroke/line-width changes; text and object edits compose without replaying stale page
  identities over each other.
• Unsupported styles and ambiguous geometry fail closed instead of producing a plausible but
  damaged PDF. Object editing remains beta while the supported surface grows.

Privacy and Compatibility

• All of these features are local: batch folding reads and writes only the folder the user
  picks, comparison renders and diffs entirely on the Mac, OCR uses Apple Vision on-device,
  and nothing is uploaded.
• Orifold still requires macOS 14 Sonoma or newer and ships as one universal Apple Silicon +
  Intel build.
• Release builds remain ad-hoc signed and are not Apple-notarized unless the release signing
  secrets are configured.

Verification Contract

• The integrated Swift suite contains 1,160 tests: 33 are skipped by their documented
  environment gates and 0 failed in the final local integration gate.
• Focused regressions cover batch output naming and collision avoidance, the per-file
  OCR → watermark → compress pipeline (watermarks asserted via ink coverage, OCR via an
  injected recognition provider), per-file failure isolation and between-file cancellation,
  the visual tile diff's placement and thresholds, word-level LCS counts with the coarse
  long-page fallback, page pairing with offsets and one-sided pages, and the
  offset-aware read-aloud start.
• OCR regressions cover page-selection policy, automatic and explicit languages,
  partial-success handling, low-confidence receipts, cancellation, undo/redo, and validation.
  Editor regressions cover inline/object composition, page identity through replay, formatting
  preservation, unsupported-style refusal, rotation, save/reopen, and export.
• SwiftPM, XcodeGen, universal packaging, strict code-sign verification, installed-app
  workflows, hosted CI, published assets, installer behavior, and production documentation
  are release gates.

Publication Order

The release tag is published and its stable GitHub assets are verified before the documentation
fallback advances to v0.11.0. Only then is main pushed to deploy the updated release site. This
keeps the public download page on the last verified stable release if asset publication fails.

Full Changelog: v0.10.2...v0.11.0