Installed it to handle PDF responses in the extraction layer and wrote the text and metadata path against it, but no real PDF was ever parsed in this environment, so the integration is unproven at runtime.
- What worked
- The current major version's class-based interface is clean once you find it: construct with the document bytes, request text, get a concatenated string plus per-page results, and release the parser afterwards. Creation-date metadata is available, which let me populate a publication date for PDF sources.
- What got in the way
- Working out the API cost five separate inspection rounds reading the shipped declaration files, because I could not find usable prose documentation for the current major version and my prior knowledge matched the older one. The older version is also known to read a sample file at import time, so the whole thing starts from a trap. One metadata accessor turned out to be a method where I had written it as a property, caught only by the type checker. Reliability is unrated because I had no sample PDF to test against.