1684

The specific third-party tool is outside the project's scope, but the underlying problem you're describing is valid: scrapers can silently fail on Cloudflare-protected (HTTP 403) pages instead of surfacing a clear error or falling back. I'm relabeling this as a bug to track that generic behavior — a clearer error / fallback path on 403 would be the right fix. Thanks for flagging it.