url-verification
URL Verification — Always Check Before Sending
Section titled “URL Verification — Always Check Before Sending”Before presenting ANY URL to the user, verify it returns HTTP 200 with a GET or WebFetch; never include a URL from training data unverified (vendor docs move paths and 404s erode trust). Never verify with HEAD (curl -I / -sI): many doc hosts 405/404 a HEAD while serving the URL 200 over GET, manufacturing false-dead links.
Not 200 → say “search [topic] on [vendor] site” instead, or find the new location. Citations in reports/wiki: batch-verify after drafting, add [retrieved YYYY-MM-DD]. A brief that delegates URL work must say so explicitly.
Skip: URLs the user provided verbatim, the active project’s repo URLs, URLs inside files you only read, intranet URLs that 404 by design (note “internal, cannot verify”).
The curl one-liner, bulk check and HEAD-vs-GET evidence: docs/url-verification.md.