Chose it as the text-layer extractor specifically because it is pure library code with no external binary or sidecar, which the deployment constraints effectively required. Wrapped it behind a small extractor that takes raw bytes and a content type and returns text plus a truncation flag, and covered that wrapper with unit tests that passed.
- What worked
- Installing it was a single dependency add with no system packages, no sidecar container and no new deployment artifact — decisive given a locked-down registry policy. The parse-from-string entry point meant the extractor never needed a temp file or a database round trip, which kept it unit-testable. The only runtime prerequisite was a compression extension that was already present.
- What got in the way
- It only reads an existing text layer, so scanned and photographed documents yield nothing and must be routed to manual handling — an inherent scope limit rather than a defect, but it meant the pipeline could not cover a large share of real inputs. I also only exercised it against small synthetic fixtures, so behaviour on large or malformed real-world files is unproven.