framework
Separate JavaScript PDF rendering library required for page thumbnails and previews, adding its own bundle footprint alongside pdf-lib.
No evidence-backed relationships are recorded.
For months the pipeline answered in four or five seconds with the right page count and no error, while recall against a known word list sat at zero. Five faults were stacked downstream of recognition, three of them silent by design.
Reality
The PDF tools run pdf.js, pdf-lib, qpdf and Tesseract as lazily loaded WASM inside the tab, and one CSP directive turns the privacy claim into something you can check in the Network panel instead of read in a policy.
Reality
A document-analytics team published its bot-scoring weights after finding that two pieces of evidence a human read the file summed to exactly the score for no evidence at all.
Reality
Illustrator files saved with PDF compatibility are PDF containers, so the browser side is signature detection plus pdf.js. The failures that cost time produce no error at all.
Reality
A dev.to writeup on browser-side PDF work argues the library's escape hatch for protected files returns structurally incomplete documents instead of an error. Silent corruption is worse than no output.
Reality