Provenance Record

Well-structured, well-written 628-word News article covering the Go team's formal pkg.go.dev API launch. The structure is logical: overview, endpoint listing, design philosophy, reference CLI, stability commitments, and known unknowns. Technical depth is appropriate for a developer audience.

All three source snapshots read and verified from disk. source-0.html.gz (go.dev/blog/pkgsite-api): confirmed all direct quotes verbatim — 'Developers building tools, IDE integrations, and automated workflows have historically relied on fragile workarounds like web scraping to access this data,' 'Tools can now access the specific, high-fidelity context needed to reason about the Go ecosystem with greater precision,' 'One design principle for this API is precision over convenience,' and the backward compatibility pledge — all appear word-for-word. Authorship (Ethan Lee, Hana Kim, Jonathan Amsterdam) and publication date (21 May 2026) confirmed. source-1.html.gz (pkg.go.dev/api): confirmed API documentation exists and matches all eight endpoint families listed in the article; the GET-only stateless architecture and disambiguation behavior are accurately described. source-2.html.gz (GitHub issue #79453): confirmed the proposal to drop gccgo was filed by adonovan (Alan Donovan) on May 18, 2026, and is described as a 'proposal: drop gccgo.' The article correctly characterizes this as Alan Donovan proposing to discontinue gccgo support. The allowlist warning for pkg.go.dev is a false positive: pkg.go.dev is a subdomain of go.dev, which is explicitly in the allowlist, and is the official Go package registry — the primary subject of this article.

All claims trace to cited sources. Eight endpoints listed match the official API spec exactly. The install command for pkgsite-cli matches the blog post. The precision-over-convenience design principle, the v1beta path, the OpenAPI YAML location, and the backward compatibility commitment are all verified verbatim. The gccgo proposal description is accurate (proposal to drop, not already dropped; filed concurrently; characterized as unrelated to the API — all confirmed by the snapshot).

High-quality submission ready for immediate publication. All quotes verbatim, all claims sourced, writing is precise and appropriately technical. The article is a model of accurate coverage of a developer tooling announcement.