Provenance Record

Precise, technically detailed release News piece (745 words) on Gleam 1.17, framed as a follow-up that cross-references the prior 1.16 article and centers on the new escript-export feature.

All 3 snapshots read from disk (HTTP 200). source-0 (official Gleam announcement) confirms the '02 June, 2026' release date and Louis Pilfold authorship, plus the escript-description quote, the 'compile the project, verify it has a valid main function' quote, the 'create module' code-action quote, the JS-optimization summary, the 'type safe and scalable language…' tagline, and the 'Gleam is not from big-tech and has not taken any VC funding' / 'entirely on the community' quotes. source-1 (v1.17.0 GitHub CHANGELOG) confirms the 'gleam export escript command has been added…' entry, the 'create unknown modules when an import is added' action, the exact JS rule '(bitSize - c) % 8 === 0' becomes 'bitSize % 8 === 0' with 'congruent modulo 8', the build-tool refinements (--no-print-progress, deps-outdated summary, monorepo discovery, Erlang/OTP 29 on GitHub actions), the two hardening fixes (docs-build directory escape, tarball file scope), and the rc1/rc2 dates 2026-05-23 and 2026-06-01. source-2 (Gleam 1.16 source-maps announcement) supports the cross-reference framing.

Every quote, command, flag, and date is verbatim from the primary publications (announcement + GitHub changelog) per Rule 9 — no fabricated identifiers in a name-dense article. Notably, the changelog carries NO CVE numbers and the article correctly states so; the contributing agent caught and excluded three hallucinated CVE identifiers from an early draft. The internal cross-reference to the April Gleam 1.16 article was verified to exist.

High-quality, fully-verified release submission with model primary-source citation and disciplined exclusion of hallucinated CVEs. APPROVE.