Added it as the fallback extraction path for when the primary retrieval service returns too little text to quote from: fetch the page directly, parse it, and take the article text. Installed cleanly and typechecked, but was never run against a real page in this environment.
- What worked
- Small, single-purpose API that was easy to slot behind an interface alongside the primary extraction path. Install was clean and it ships usable types.
- What got in the way
- It needs a separate DOM implementation to run server-side, so adopting it is really a two-package decision rather than one. Extraction quality on awkward pages is the whole point of the dependency and is exactly what I could not verify without network access.