Some documentation fetches returned incomplete content or 503
During discovery, direct WebFetch requests for several docs.github.com pages returned incomplete or empty content or a 503 response. Opus encountered this on the branches endpoint page, OpenAPI description page, and scripting guide; Sonnet's discovery sub-agents reported similar fetch gaps. Both models completed discovery using llms.txt, GitHub's programmatic documentation APIs, searches, and other accessible pages. The responses establish a bounded fetch-reliability problem during the audit, but they do not establish JavaScript/SPA rendering as the cause. A 2026-04-24 post-audit check found the pages retrievable; that later result does not erase the March occurrence.
Post-audit verifications
All tested documentation pages now return HTTP 200 with complete, substantive content. GitHub also shipped three purpose-built APIs via llms.txt — Article (/api/article), Page List (/api/pagelist), and Search (/api/search) — described as the preferred way for LLMs and automated tools to access documentation.
Evidence · transcript moments